J
Jordan
I am having a problem where some scheduled tasks will run, however some will
not run. All use the same Administrator logon to run. It appears that
batch file tasks are the ones with the problem.
If I am logged on the console or even via a Terminal session as
Administrator, all the tasks run, but if I log off all the users, the
windows .exe type of commands run fine, but the batch file commands do not
run. As examples, my AV protection runs a program that checks for updates 4
times a day and my AV is always up to date, however I have a batch file that
calls a few "Net Stop" commands, then NTBackup.exe , and finally the "Net
Start" commands and this batch file and other batch files like it never run
unless I am logged in as the Administrator (or logged in with the console
locked)
Is there a reason why command line batch files are not running on my Windows
2003 Server unless I am logged in?
not run. All use the same Administrator logon to run. It appears that
batch file tasks are the ones with the problem.
If I am logged on the console or even via a Terminal session as
Administrator, all the tasks run, but if I log off all the users, the
windows .exe type of commands run fine, but the batch file commands do not
run. As examples, my AV protection runs a program that checks for updates 4
times a day and my AV is always up to date, however I have a batch file that
calls a few "Net Stop" commands, then NTBackup.exe , and finally the "Net
Start" commands and this batch file and other batch files like it never run
unless I am logged in as the Administrator (or logged in with the console
locked)
Is there a reason why command line batch files are not running on my Windows
2003 Server unless I am logged in?