Help - Task Scheduler won't run *.reg files

  • Thread starter Thread starter JAQK
  • Start date Start date
J

JAQK

Windows 2000 server, domain environment.

We've set up a couple of scheduled jobs to run registry changes (.reg
files), but the jobs "Could not start" and no further clues (in Event
viewer, or the Task Scheduler itself) were given as to why. The Task
Scheduler service is running and other tasks ran fine. The credentials
supplied for registry change tasks were the usual Domain admin username and
password.

What could we be missing? I'm wondering if there's a problem with running
..reg files using the scheduler. (The .reg files work perfectly when we
manually double-click on them.)

Should they be encapsulated into batch files? If so, what would be the
correct syntax?

Thanks in advance.
 
JAQK said:
Windows 2000 server, domain environment.

We've set up a couple of scheduled jobs to run registry changes (.reg
files), but the jobs "Could not start" and no further clues (in Event
viewer, or the Task Scheduler itself) were given as to why. The Task
Scheduler service is running and other tasks ran fine. The credentials
supplied for registry change tasks were the usual Domain admin username and
password.

What could we be missing? I'm wondering if there's a problem with running
.reg files using the scheduler. (The .reg files work perfectly when we
manually double-click on them.)

Should they be encapsulated into batch files? If so, what would be the
correct syntax?
Click to expand...

Jaq,

Yes, in a batch file write
---------- regme.bat -----------
@echo off
regedit /s "%1"
cls
------------- end snip -------------

then in your Scheduled Task commandline write
regme.bat myreg.reg

hth,
tlviewer
 
JAQK said:
Windows 2000 server, domain environment.

We've set up a couple of scheduled jobs to run registry changes (.reg
files), but the jobs "Could not start" and no further clues (in Event
viewer, or the Task Scheduler itself) were given as to why. The Task
Scheduler service is running and other tasks ran fine. The credentials
supplied for registry change tasks were the usual Domain admin username and
password.

What could we be missing? I'm wondering if there's a problem with running
.reg files using the scheduler. (The .reg files work perfectly when we
manually double-click on them.)

Should they be encapsulated into batch files? If so, what would be the
correct syntax?

Thanks in advance.
Click to expand...

What is the userid running the scheduled task? Whose registry is
supposed to get updated?
 
What is the userid running the scheduled task? Whose registry is supposed
to get updated?
Click to expand...

As I said, it's the (domain) administrator. The local registry is involved.
 
Thanks, that worked.


tlviewer said:
Jaq,

Yes, in a batch file write
---------- regme.bat -----------
@echo off
regedit /s "%1"
cls
------------- end snip -------------

then in your Scheduled Task commandline write
regme.bat myreg.reg

hth,
tlviewer
Click to expand...
 
Back
Top