Link to home
Start Free TrialLog in
Avatar of scottman29
scottman29

asked on

Group Policy software pushing...

I have a 2003 active directory.  I have created a second OU for a lab that has 28 windows xp sp2 clients on the domain.

I created a GPO and linked it to the the second OU, I configured a software policy that will assign flash player 9 and shockwave 10 to the computers that I put in the OU.

I placed the 2 msi files in a shared folder to all users with read access.

I rebooted the clients.  I even ran gpupdate /force on some of the machines, but it doesn't seem to have pushed the software.

any help on this would be most appreciated.

Sincerely,
Scott
ASKER CERTIFIED SOLUTION
Avatar of strongline
strongline

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Bradley Fox
How did you push the software?  Was it User based or Computer based?  Did you assign or publish the packages.

If the packages are published then they will show in add/remove programs but will not install untill the user tries to use them.  If they were done via User (not recomended) then the users must have the approperitate permissions to install the software.
Also try and run rsop.msc

This will give you a complete listing of errors associated with GPO processing.  It will also tell you if the policy was even applied.
Avatar of scottman29
scottman29

ASKER

I see one error that could be related in the event viewer on the Server:

Product: Adobe Shockwave Player -- Error 1704. An installation for Adobe Flash Player 9 ActiveX is currently suspended.  You must undo the changes made by that installation to continue.  Do you want to undo those changes?

I'm wondering if the shockwave is already installed from an earlier version, that maybe overwriting it with this install is causing a problem?
i did find a program that cleans up 1704 errors.  I'm going to give it a try and see if everything works after that.
believe it or not, I actually had to edit the MSI file to make it work correctly.  there was nothing wrong with the Active Directory.  Ultimately though it was looking in the apps log that fixed the problem.... so I'm going to give points accordingly for that.

I was able to take that error in the log and then look it up on line.