MOUNTING A WINDOWS SHARE AS THE SYSTEM USER
ISSUE
A windows environment device share or mapped drive cannot be seen by Arma, due to the programme running under the local system account. This prevents a network share or NAS device from being used as an Arma source for backup
WORK AROUND
Create a mapping to the source under the System user account
PRE-REQUISITE SOFTWARE
PSExec from SysInternals Suite
Step one: Open an elevated cmd.exe prompt (Run as administrator)
Step two: Elevate again to root using PSExec.exe: Navigate to the folder containing SysinternalsSuite and execute the following command psexec -i -s cmd.exe you are now inside of a prompt that is nt authority\system and you can prove this by typing whoami. The -i is needed because drive mappings need to interact with the user
Step Three: Create the persistent mapped drive as the SYSTEM account with the following (EG) command net use y: \\servername\sharedfolder /persistent:yes Enter network login credentials where required
WARNING: You can only remove this mapping the same way you created it, from the SYSTEM account. If you need to remove it, follow steps 1 and 2 but change the command on step 3 to net use z: /delete.
NOTE: The newly created mapped drive will now appear for ALL users of this system but they will see it displayed as "Disconnected Network Drive". It may claim to be disconnected but it should work for everyone.
ARMA SETUP EXAMPLE
Setting a mapped network drive as an Arma backup source
Create or amend a profile on the device on which you have performed the System Mount process โ Add the mapped network drive, or sub-level files here
Confirmation of files at destination