/build/static/layout/Breadcrumb_cap_w.png

Deploy Adobe Reader 8.1.2 using GPO

I'm pulling my hair out here, trying to get this Deployment to work.

Scenario:
I need to install Adobe Reader 8.1.2 on all Notebooks in the Company and I thought, the easiest way would be a Group Policy.
So I created an OU and in there I created a Group (let's call it G-AdobeDeploy) which has the Computers which need the installation in it.

After I created the OU and the Group (and added a test Computer Account to the Group), I started with the Policy.

I went after the Guide which Adobe offers (created an MST using the Adobe Customization Wizard, copied the MSI, MST, CAB etc. files on a network share and then eventually set the install package in the GP) but it doesn't do anything. On the test Notebook I didn't get any Event Log messages, no reboot prompts, not even the msiexec process started up.

I tried putting a user in the Group instead of Computer accounts, same scenario.

Now what I thought would help me a lot, in the Guide that Adobe offers, they suggest turning on the logging feature in the Policy. Where do I find that log file? Or had anyone the same problems and knows what I'm missing?

Thanks in Advance

0 Comments   [ + ] Show comments

Answers (3)

Posted by: revizor 16 years ago
Third Degree Blue Belt
0
Try "gpupdate /sync /boot"
Posted by: Danchou 16 years ago
Yellow Belt
0
After lurking around here I had an Idea. Instead of using the security group, I tried adding the Computer Account itself into the OU (without security group) and there it was; an error message on the Client that the installtion source can't be accessed. That is impossible, to test it I gave the share full permission to everyone (and the destination of the MSI file in the GPO is definitely \\server\share).

Well, at least now I got *something*. But what about the security groups? Isn't it possible to use security groups to deploy software?
Posted by: ShaunC1000 15 years ago
Yellow Belt
0
Security Groups are not used when calculating Group Policies. In order to publish applications, the group policy for the program must be linked to the OU where the user or workstation lies. This goes for any group policy setting..
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ