Scheduled Task & Run As question

  • Thread starter Thread starter parisjason
  • Start date Start date
P

parisjason

Hi folks,

I've got about 40 WinXP computers on a Win2003 Domain. I want to set
up a Scheduled Task to run on all the workstations.

Instead of physically going to each machine (or using RDP), I was
hoping to use the Domain's logon script to copy the *.job file from a
Share to c:\windows\tasks, as each user logs on.

Of course - as most of you would know, but I've only just discovered! -
the Run As credentials change once the *.job file arrives on the target
machine.

(Specifically, the sign-on of the current user is swapped in to the Run
As box, but the "Password" field is left blank).

Of course, this causes the job to fail to run at the Scheduled time.

Was wondering, is there any known way to get the *original* credentials
to stick?

Many thanks. :)

Jason Paris
 
Hi folks,

I've got about 40 WinXP computers on a Win2003 Domain. I want to set
up a Scheduled Task to run on all the workstations.

Instead of physically going to each machine (or using RDP), I was
hoping to use the Domain's logon script to copy the *.job file from a
Share to c:\windows\tasks, as each user logs on.

Of course - as most of you would know, but I've only just discovered! -
the Run As credentials change once the *.job file arrives on the target
machine.

(Specifically, the sign-on of the current user is swapped in to the Run
As box, but the "Password" field is left blank).

Of course, this causes the job to fail to run at the Scheduled time.

Was wondering, is there any known way to get the *original* credentials
to stick?

Many thanks. :)

Jason Paris

The credentials don't change but they are related to the
partition volume name, presumably in order to prevent
hackers from copying scheduled tasks to other PCs
and getting them to run without supplying their own
credentials.

Under WinXP you can create scheduled tasks on
other machines with schtasks.exe. You must, of course,
supply suitable credentials.
 
Back
Top