7 replies
by shortbus
by stargater
by beermonster
Hi,
Just to expand on the previous answer. The at scheduler will run the job under whatever account the schedule service is running under, this is typically localsystem. When you schedule the job, the localsystem account - which is purely a local machine account - doesn't have permissions to access the remote machine. What you can do is, via the services panel, set the schedule service to run under the context of an account which can access the remote share (typically a domain account). Be careful to give the account as few rights as possible to get the job done (IE definitely not an admin). An alternative would be to map a drive within the batch file using a specific users details -
net use F: \\myserver\share /user:mydomain\mynamemypassword
Note that this does mean that anyone who can access the batch file will be able to see the account details - you can minimise this risk by only giving localsystem (IE the schedule service) and yourself access to it. Hope this helps....
by stargater
There is nothing about users in the schedule service on the NT Workstation PC. Based on your ideas I have come up with a solution. I have shared a folder on the C drive of the NT Workstation PC and then setup the batch file to run on the Win 2000 Server. It maps to the NT Workstation PC and then gets the files I want. The only problem I had was that I could not use the Administrator user to schedule the job, it wouldn't start. I set up a new user and set this user on the scheduled job and it seems to work.
Thanks for all the help
by ja_seaton
by stargater
by stargater
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending