(jcwren) Re: Windows Scheduler Issues

I had a similiar problem under NT4.0. The problem was that the Scheduler task normally runs as 'System Account', a user with few priviledges. What I did to solve it was go into Start->Control Panel->Services, double-click on 'Scheduler', select the radio button for 'Log on as', and set the account/password you want the scheduler to run as.

I don't remember if that changes the scheduler instance only for jobs created by that user, or if other jobs scheduled by other users will now run under that account. I treat NT/Win2K as a single user system, not a casual terminal that people can log into, so I can't say.

I fought with this when it came to sharing drives. Everything was working fine, except I couldn't access a shared network resource. Anyway, I'm imagining that Win2K has something similiar, since it's so heavily NT based.

Update: Win2K has a similiar facility. Goto Start->Control Panel->Adminstrative Tools->Services. Scroll down and double-click 'RunAs Service', and select the 'Log On' tab.

--Chris

e-mail jcwren

Comment on (jcwren) Re: Windows Scheduler Issues

Replies are listed 'Best First'.
Re: (jcwren) Re: Windows Scheduler Issues by seigniory (Sexton) on Mar 30, 2001 at 21:28 UTC
Windows 2000 won't let you run the scheduler in the context of another account - it fails to start with the message "Run individual jobs in the context of the desired account" message. I also tried wrapping it in a batch file - same deal - when the batch file is double clicked, it works, when it's scheduled, it's not. I'm going to try a different file schedule utility - winat maybe - I'll keep you posted.	[reply]
(tye)Re5: Windows Scheduler Issues by tye (Sage) on Mar 31, 2001 at 00:40 UTC
"Run individual jobs in the context of the desired account" ...which seems to imply that you can configure what security context you want each job to run it. That sounds like the easiest solution if you can just find where that is documented. - tye (but my friends call me "Tye")	[reply]