Startup Script Not running...

[srinu9]

Hi.. I'm new to here and this is my first question here..

I have a group policy configured to run a startup batch file to disable the usb's on client machines. I have attached the batch file to this thread as a text document. Below is the code for your quick reference.

regedit /s \\server name\shared folder\Subinacl\dword4.reg
\\server name\shared folder\Subinacl\subinacl.exe /keyreg \system\currentcontrolset\services\usbstor /deny=system


The batch file seems to work fine and perfectly when I run it manually, however it is not running in the startup through group policy. I have checked the rsop in client machines and the batch file is listed there in the startup scripts. But it is not working.

Server: Windows 2003 Server Enterprise Edition R2
Clients: Windows XP Professional SP3

Hope some one can help me to get out of this problem...
Thanking you....

Lakshmi Srinivas
Lakshmisrinivas.Kommina@Relianceada.com

[kbeckman]

Sounds like a possible permissions problem on your share. If this applying to all of the computers in your domain, you'll want to give "Domain Computers" read-only access to the share (don't forget to add the read-only permissions to the folder and its contents on the file system of your server). If it is just a small sub-set of computers, you can create a group for those computers and use it instead of Domain Computers.

[srinu9]

Thanks for the reply kbeckman,

I have already checked the permissions related issues and every thing is fine with them and i've reensured by checking again after your reply. Still facing the same problem.

[kbeckman]

First off, Do any of your shared folders or sub-folders have spaces? If so, you'll need to enclose the full UNC path including the file in quotes. Second, it may be possible that the script is running but getting denied somehow. If you add >> C:\test.log to the end of each command you're running, it will dump the output to a text file and you'll be able to see if the command is running and if it is generating any errors on the command line.

If that doesn't fix it, run a gpresult /v on the machine that is supposed to be running the startup script and post the results. Also, post screenshots of the file share's permissions and the permissions of the folder itself.