"regedit /s" is ignored in startup script

[chpicker]

I've run into a very strange problem recently, but I can't seem to find anything on the internet to suggest that my observations are correct.

I used Group Policy to implement a startup script on all of my workstations. The "script" is a .CMD file. Here's what it looks like:

@echo off
REGEDIT /S \\DC01\NETLOGON\RegChanges.reg
CSCRIPT \\DC01\NETLOGON\NoteChanges.vbs

The second line calls REGEDIT with a /s to load a .REG file into the registry silently. The second calls a VBS script which simply makes an entry in the Application Log.

Here's the problem: it works fine on Win2k; it doesn't work on WinXP. If I take out the /s, it works, but the user has to click "Yes" every time the computer starts up. With the /s, it simply...doesn't run. I can't make any other senses out of it than that. Even the VBS script doesn't run; no entry gets made in the application log. It's like XP sees the /s and just quits running the batch file.

Also, a user with Administrative rights can browse to the NETLOGON share and double-click the CMD file and it works fine, even with the /s.

Any suggestions? Is there a security setting somewhere that prevents Regedit /s from running in a startup script? Do I need to give the machine accounts a privilege that they don't have?

Ian

 

[TheLad]

Why don't you just create a VBS for this instead of using REGEDIT /S and referring to a REG file?

--------------------------------------
"Insert funny comment in here!"
--------------------------------------

 

[Jiminald]

If I remeber correctly, there is a setting in group policy to stop regedit running.

I believe it is under the computer settings, windows settings, and beyond your on your own for looking for it. (All coming off of the top of my head after a long day )
Also look in the user settings too, could be another one there.

Hope this helps
Jiminald