计划任务无法在外部服务器上写入文件
我在 Windows 2003 服务器计划任务中运行计划任务时遇到问题
任务在 nt 权限/系统帐户下运行，将文件发送到同一域中的另一个 Windows2003 服务器。
执行任务的计算机在域和计算机中具有有限权限的域帐户下运行
在远程服务器中发送文件的文件夹已配置为向系统和用户授予完全权限，
当计划任务绑定在远程写入文件时会出现问题服务器，任务返回异常，例如“访问被拒绝路径......”
远程服务器检测到正在运行外部计划任务的用户是哪个？ 我应该在远程文件夹中授予哪些权限？
预先感谢
费尔南多
I'm having problems with a scheduled task running in a windows 2003 server scheduled task
Task is running under the nt authority/system account sending files to another windows2003 server in same domain.
Machine where task is executed runs under a domain account with limited permissions in domain and machine
Folder where files are sent in remote server has been configurated granting total rights to system and user which
The problem happens when scheduled task is tying to write the file in remote server, task returns an exception like "Access denied to path ...."
Which is the user which remote server detects running externat scheduled task?
Which permissions should i grant in remote folder?
Thanks in advance
Fernando
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
以系统用户身份运行的计划任务将无权访问网络上的另一台计算机。 当它运行时，就像您登录到本地计算机而不是网络一样。 您将需要以特殊网络用户身份运行该任务，或者将文件存储在运行该任务的计算机上，以便另一个进程稍后获取。
A Scheduled Task running as the System user will not have access to another machine on the network. When it runs it is the same as if you were to logon to the local machine instead of the network. You will need to run the task as a special network user or store the file on the machine running the task for another process to pick up later.
在本地系统帐户下运行的进程没有访问其他计算机资源的权限。 典型的解决方案是创建一个专门用于运行任务的单独域用户，并在该用户下运行任务。
A process run under Local System account doesn't have permissions to access other computers' resources. A typical solution is to create a separate domain user exactly for running the tasks and run the task under this user.
除了上面提到的创建域用户来运行的解决方案之外，如果您只需要匿名网络访问或“域成员”网络访问，您还可以作为
Network Service运行，从积极的一面来看，它几乎没有本地计算机上的权限（与本地系统不同，后者比管理员更强大）。Besides the mentioned solution of creating a domain user to run under, if you just need anonymous network access or "domain member" network access, you can also run as
Network Servicewhich as a positive side has almost no rights on the local computer (unlikeLocal Systemwhich is even more powerful thanAdministrator).