Startup Script doesn't work - Group Policy Issue?

[benso37]

I am following Microsoft's instructions on how to deploy Office 2010 Pro but the startup script doesn't work after I reboot one of my clients.

This is what I know:

1. The new GPO I created and linked to the OU works because if I rename the script with .vbs (instead of .bat) or purposely make a syntax error in the script I get an error message on the client side after a reboot. In other words, the client will complain about the syntax error or wrong filename extension when it reboots.

2. I know the script works because from the same client workstation, I can navigate to the location (\\mydomain\SysVol\mydomain\Policies\{F1E3A4C0-8ABA-4AFD-8CE4-8AA8059B2171}\Machine\Scripts\Startup) of the script and double-click on the script to install Office. This tells me that I don't have a permission issue.

3. The client workstation is Windows XP and the AD Server is Windows Server 2008 R2

4. The only information related to software installation in the log is under Application and it states "Changes to software installation settings were applied successfully".

5. I run gpresult and it shows that the GPO is being applied

Can anyone point me in the right directory to fix this problem? I don't know what else to try.


Thanks in advance.

 

[ramam1]

When you double click the script does it actually install the software you expect it to?