Computer startup scripts runs but program not installed

[wuzzle]

Hello, I am attempting to install software remotely through a computer startup script. The script appears to be ran succesfully as seen in rsop.msc but the program never installs. When I run the script from the shared folder on a server(an .exe file..I use Push installer if anyone knows of it), it installs the program.

[JerryC]

Wuzzle,

In my experience, the RSoP report only really checks to see if the program was 'able to be launched' successfully, not that the script ran to successful completion. I've never heard of "Push Installer". Do you have a link? Does it create a log of it's activities like a Windows installation job can? What does your command line in the GPO look like? Are there any parameters to the command line?

Jerry

[wuzzle]

Hi Jerry, it is made by motivate systems. You install the desired software (in my case mcafee) on a test machine. Then you run the push installer which packages the install. Most of the time it works well. I not had too much luck using .msi to push to clients hence the reason for a 3rd party solution. Yes there is a log file but was not turned on. I was wonder what were some common reasons why a script would run if ran manually vs using GPO to push.

[JerryC]

Sure... here's an example. Ever since WindowsXP+SP1 you could NOT just double-click on, say, a 'HiWuzzle.vbs' script file without a confirmation dialog popping up asking if it was 'OK' to run the code. If you try that using Start | Run, you get the same dialog. However, if instead, you run 'WScript HiWuzzle.vbs' it runs without any promping at all. The OS trusts the WScript executable, not the random script. IN your case, you could be encountering an issue where the system was attempting to execute the installer code and presenting an 'OK | Cancel' interface that cannot be visibly observed. Here's something to try, use the Process Monitor utility from SYSINTERNALS (now frm Microsoft) and set it for BootLogging. See if the script (or whatever your script calls as an executable) ever attempts to run. If it doesn't run, then it's something in the GPO not launching it correctly. If it does launch, you know the GPO is working and the latter not.