Knowledgebase: Tips and tricks
How to back up a network drive on Windows
Posted by Sven Koester on 27 March 2012 13:39

When accessing drives in PresSTORE on Windows, Network drives via SMB, Samba or CIFS are usually not visible in PresSTORE.

The reason is that PresSTORE runs as a service, but Network drives are mounted in the process context of user processes and are thus not visible to the service.

In order to make a network drive accessible in PresSTORE , it must be mounted in the context of the local system account. That can be achieved with the Sysinternals tool psexec. Here is how:

Download sysinternals tools from
Create an elevated shell by running cmd.exe as administrator
Within that shell, call psexec -i -s net use s: \\server\share /persistent:yes

This will mount the drive in the true root environment and makes it available to PresSTORE.

(18 vote(s))
Not helpful

Comments (12)
erik akershoek
02 July 2014 10:21
Does this work for UNC mounted drives as well?
27 March 2015 0:00
The tips are really helpful!!
How about MAC, can we apply this method on MAC? Or is there any other way to apply it on MAC?

Andre Kuehnemund
07 April 2015 12:37
UNC paths are not currently supported. It's on our to-do list.
Andre Kuehnemund
07 April 2015 16:30
In Windows, volumes are being mounted in the context of the logged in user AFTER he/she logs in. Macs and Linux mount volumes at boot time and root account automatically has access to those volume. Therefore, the method described above is not necessary with Macs, Linux and other *NIX type operating systems.
17 March 2016 17:58
Thanks for the tip... but in which file do you recommend to add this command so that the mount survives to a machine reboot? and what about login and password which are then requested to mount the SMB volume?

Andre Kuehnemund
09 May 2016 17:05
Please see the KB article titled "HOWTO Automount AFP or SMB Volumes on Mac via fstab" for one example.
Christophe Rémond
12 June 2016 22:57
I reply to me:
Here is the script I use to mount the smb vol on the windows P5 server:

@echo on
set "svrname=mmi5"
set "share=heliosdemo"
set "usr=demouser"
set "pwd=xxxpassword"
for /f "tokens=2" %%# in ('net use^|find /i "\\%svrname%"') do net use %%# /delete
net use f: \\%svrname%\%share% %pwd% /user:workgroup\%usr% /persistent:yes

Then to call the script at Windows host boot, I used the "Group policy editor" as described in:
Cory Monden
12 August 2016 19:30
The command is actually psexec -i -s net use s: \\server\share /PERSISTENT:YES
Daniel Richter
16 August 2016 11:29
Guten Tag,
warum kann ich nicht einfach das Mapping mit einem User durchführen und mit diesem User den Dienst P5 starten?
Andre Kuehnemund
31 August 2016 18:40
In order to be able to do its job, P5 must have full permissions to all mounted filesystems. By default, the built-in SYSTEM account Windows, and the root account in UNIX type operating systems, have those permissions - which is why it makes sense to have P5 running as SYSTEM or root respectively.
Daniel Richter
07 September 2016 14:35
Und wann wird P5 UNC-Pfade mit einem User unterstützen? Sollte doch für eine Backup-Software wohl Standard sein oder muss ich mir Sorgen um P5 machen? Für mich zählt das zu Basics einer Software.
Andre Kuehnemund
28 December 2016 17:44
We have only had a few requests for this and, like everyone else, need to prioritize our resources. It is, however, on our to-do list.
Post a new comment
Full Name:
CAPTCHA Verification 
Please enter the text you see in the image into the textbox below (we use this to prevent automated submissions).

ERROR: This domain name (, does not match the domain name in the license key file

For assistance with your license, please contact the Kayako support team: