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

您要么需要修改服务，要么将其包装到辅助进程中:除了会话/驱动器访问问题外，持久驱动器映射仅在交互式登录时恢复，而服务通常不会执行。

helper进程方法可以非常简单:只需创建一个映射驱动器的新服务并启动“真正的”服务。唯一不是完全无关紧要的事情是:

The helper service will need to pass on all appropriate SCM commands (start/stop, etc.) to the real service. If the real service accepts custom SCM commands, remember to pass those on as well (I don't expect a service that considers UNC paths exotic to use such commands, though...) Things may get a bit tricky credential-wise. If the real service runs under a normal user account, you can run the helper service under that account as well, and all should be OK as long as the account has appropriate access to the network share. If the real service will only work when run as LOCALSYSTEM or somesuch, things get more interesting, as it either won't be able to 'see' the network drive at all, or require some credential juggling to get things to work.

您既不想从“System”更改服务运行的用户，也不想找到一种狡猾的方式将映射运行为System。

有趣的是，这可以通过使用“at”命令，简单地将您的驱动器映射安排到未来一分钟，它将在系统帐户下运行，使驱动器对您的服务可见。

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.

我发现了一个解决方案，它与使用psexec的解决方案类似，但不需要额外的工具就可以工作，并且可以在重新启动后继续工作。

只需添加一个计划任务，在“作为运行”字段中插入“system”，并使用简单的命令将任务指向一个批处理文件

net use z: \servername\sharedfolder /persistent:yes

然后选择“在系统启动时运行”(或类似的，我没有英文版本)，你就完成了。

找到一种方法授予Windows服务访问网络驱动器。

以Windows Server 2012自带NFS磁盘为例:

步骤1:写一个批处理文件挂载。

写一个批处理文件，例如:C:\mount_nfs.bat

echo %time% >> c:\mount_nfs_log.txt
net use Z: \\{your ip}\{netdisk folder}\ >> C:\mount_nfs_log.txt 2>&1

步骤2:将磁盘挂载为NT AUTHORITY/SYSTEM。

打开“Task Scheduler”，创建一个新任务:

运行“系统”，在“系统启动”。 创建操作:运行"C:\mount_nfs.bat"。

经过这两个简单的步骤，我的Windows ActiveMQ服务在“本地系统”特权下运行，无需登录即可完美执行。