而不是依赖于一个持久驱动器，你可以设置脚本映射/取消映射驱动器每次你使用它:

net use Q: \\share.domain.com\share 
forfiles /p Q:\myfolder /s /m *.txt /d -0 /c "cmd /c del @path"
net use Q: /delete

这对我很有用。

The reason why you are able to access the drive in when you normally run the executable from command prompt is that when u are executing it as normal exe you are running that application in the User account from which you have logged on . And that user has the privileges to access the network. But , when you install the executable as a service , by default if you see in the task manage it runs under 'SYSTEM' account . And you might be knowing that the 'SYSTEM' doesn't have rights to access network resources.

这个问题有两种解决方案。

To map the drive as persistent as already pointed above. There is one more approach that can be followed. If you open the service manager by typing in the 'services.msc'you can go to your service and in the properties of your service there is a logOn tab where you can specify the account as any other account than 'System' you can either start service from your own logged on user account or through 'Network Service'. When you do this .. the service can access any network component and drive even if they are not persistent also. To achieve this programmatically you can look into 'CreateService' function at http://msdn.microsoft.com/en-us/library/ms682450(v=vs.85).aspx and can set the parameter 'lpServiceStartName ' to 'NT AUTHORITY\NetworkService'. This will start your service under 'Network Service' account and then you are done. You can also try by making the service as interactive by specifying SERVICE_INTERACTIVE_PROCESS in the servicetype parameter flag of your CreateService() function but this will be limited only till XP as Vista and 7 donot support this feature.

希望这些解决方案对你有帮助。如果这对你有用，请告诉我。

我还不能评论(在声誉方面)，但创建了一个帐户，只是为了回答@Tech Jerk @spankmaster79(好名字lol)和@NMC问题，他们在回复“我发现了一个解决方案，与psexec类似，但不需要额外的工具，并在重启后幸存。”

解决方案是在登录帐户中浏览到该文件夹，即:

    \\servername\share  

并让它提示登录，并输入您在psexec中用于UNC的相同凭据。之后就开始工作了。在我的例子中，我认为这是因为提供服务的服务器与我要映射到的服务器不属于同一个域。我在想，如果UNC和计划任务都是指IP而不是主机名

    \\123.456.789.012\share 

它可能会完全避免这个问题。

如果我曾经得到足够的代表点在这里，我会把这作为一个回复。

这里有一个很好的答案: https://superuser.com/a/651015/299678

例如，你可以使用符号链接。

mklink /D C:\myLink \\127.0.0.1\c$

ForcePush,

注意:新创建的映射驱动器现在会出现在这个系统的所有用户面前，但他们会看到它显示为“断开连接的网络驱动器(Z:)”。别被名字骗了。它可能声称是断开连接的，但它对每个人都适用。这就是为什么你可以告诉这个黑客是不支持M$…

It all depends on the share permissions. If you have Everyone in the share permissions, this mapped drive will be accessible by other users. But if you have only some particular user whose credentials you used in your batch script and this batch script was added to the Startup scripts, only System account will have access to that share not even Administrator. So if you use, for example, a scheduled ntbackuo job, System account must be used in 'Run as'. If your service's 'Log on as: Local System account' it should work.

What I did, I didn't map any drive letter in my startup script, just used net use \\\server\share ... and used UNC path in my scheduled jobs. Added a logon script (or just add a batch file to the startup folder) with the mapping to the same share with some drive letter: net use Z: \\\... with the same credentials. Now the logged user can see and access that mapped drive. There are 2 connections to the same share. In this case the user doesn't see that annoying "Disconnected network drive ...". But if you really need access to that share by the drive letter not just UNC, map that share with the different drive letters, e.g. Y for System and Z for users.

更好的方法是使用mklink.exe使用符号链接。你可以在文件系统中创建一个任何应用程序都可以使用的链接。见http://en.wikipedia.org/wiki/NTFS_symbolic_link。