First off a little background:

We are using Windows 2000 workstations and Windows 2000 server

I have created an msi and mst combination to deploy Adobe Acrobat Professional 7.0 using the Installshield tuner program from Acrobat. This worked perfectly.

When I create a command line batch file to deploy the msi and mst it is successful. Acrobat 7.0 is deployed cleanly. Here it is:

C:\WINNT\system32\msiexec.exe /I "\\bcscnet.ca\dfs\dist\apps\CLIENT\Adobe\Adobe Acrobat Pro 7 CD\Adobe Acrobat 7.0 Professional\AcroPro.msi" /QB+ TRANSFORMS="\\bcscnet.ca\dfs\dist\apps\CLIENT\Adobe\Adobe Acrobat Pro 7 CD\Adobe Acrobat 7.0 Professional\AcroPro.mst"

I have created a group for this software to be deployed to. In this group are machine names:


When I add my msi and mst combination to group policy in active directory and select the security panel I add my special adobe group above with read rights to this package and remove authenticated users so that this and only this group of machine names gets the acrobat 7.0 software. I have done this successfuly in the past.

I have a new user / machine who needs to get this software. This users machine name is DJONES1

I added this new machine name to my special adobe group and restarted that machine.

Now I would have thought that group policy and active directory would pick up this new machine and deploy software but it does not - it appears as though AD and GP is not seeing this new addition to my application group for adobe acrobat professional.

I have tried refreshing GP but still no.

I can manually deploy the software with my batch file but AD does not seem to pick up new machine name additions to the special adobe group mentioned above.

Any thoughts on what and why this might be happening.

Thanks again for any input.

John Falloon
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Check the App Event log on DJONES1, see if the GPO's applying against it and failing and maybe why.

Also, try using the Group Policy Results wizard in GPMC and run it against DJONES1 and see what it says.
Answered 05/29/2006 by: fosteky
Purple Belt

Please log in to comment
[font="Trebuchet MS"]Do you able to apply the package to any other machine via GPO.?
Answered 05/30/2006 by: Ramu
Senior Yellow Belt

Please log in to comment
I did check the event log for the DJONES1 computer - nothing - no evidence that the package even got deployed!

Answered 05/30/2006 by: Zeke
Orange Belt

Please log in to comment
stupid question....but is the policy enabled (computer setting) enabled?
Answered 05/31/2006 by: sejacru
Second Degree Blue Belt

Please log in to comment