Christopher,
If you scroll beneath all the advertisements on the
Experts Exchange page you can see the responses, typically. If that
doesn't work then send me the link and I'll send you the responses to
see if they help.
Have you used Process Explorer to verify the credentials and rights the
process has when it is running? You should be able to see that.
http://live.sysinternals.com/procexp.exe
Good luck,
Joe
From: Christopher [mailto:[email protected]]
Sent: Friday, August 07, 2009 2:21 PM
To: NT System Admin Issues
Subject: Scheduled Tasks/Batch logons, etc
OK - here's the scenario. Windows XP, SP2 workstaions joined to a
domain.. User has several scheduled tasks that run every 5 minutes.
The tasks basically just run a batch file that looks for a specific file
in a direcory. If it finds it, it runs another batch file that performs
a few other misc. checks and then actually calls an executable to
process these large data sets.
This is all basically to allow the user to have these data processing
runs happen automatically, no matter who has the workstation locked,
etc.. all he has to do is drop data in a specific folder and create one
file over the network and within the next 5 minutes, it starts up.
After working out a few GPO issues that were kicking the users out of
the "Log on as batch job" user right, the jobs run fine. The problem
now, is that if the owner of the job (whoever's credentials it's running
under) is logged in when the job kicks off, the processes that were
started by the scheduled task are killed. This doesn't happen if the
owner of the job is not logged on, or any other user is logged on, of
course. My assumption is that only the initial batch file called by the
scheduled task is run under the batch login type, so if the scheduled
task was directly calling the executable then it would stay running, but
since this the job is runnig a batch file that is calling another batch
file, which in turn is actually calling the executable, the exe doesn't
run under the batch type login and is killed just like every other user
proccess when he logs off.
I looked at a few shell commands to see if there was any specific way to
call the 2nd batch file, or executable, that would run it under the same
logon that the original batch file was run under but didn't hae any
luck. I also googled a bit, but could only find an Expert's Exchange
question (that sounded exactly like my problem) but of course I'm not
signing up and paying any cash for it.
Any thoughts, suggestions, flames? Also, if there is a better way to
accomplish this, I wouldn't mind hearing it. Thanks in advance..
-cb
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
