/build/static/layout/Breadcrumb_cap_w.png

adobe reader 9.3.1 msp active directory software installtion

Greetings,
The latest adobe reader 9.3.1 release is an patch msp file. Currently we have reader 9.3 installed via Active Directory Software installation. Has anyone upgraded if so what method did you use to distribute the new version in a GPO? Does anyone have a tried and true method to apply the msp / patch to the administrative / application installation point ? Any advise from AD GPO season Pro is greatly appreciated
thx

0 Comments   [ + ] Show comments

Answers (10)

Posted by: slay_u 14 years ago
Orange Belt
0
I haven't deployed the latest version(9.3.1) of Reader, however the general procedure we follow is...

1) patch the admin install of an msi with the latest msp
2) uninstall the older version
3) Deploy the latest patched admin msi
Posted by: skislowski 14 years ago
Senior Yellow Belt
0
I'm assuming the Administrative install point contunies to use the original mst transform file prior to the msp patch. Does anyone know for sure???
Posted by: joedown 14 years ago
Third Degree Brown Belt
0
When doing an AIP of Adobe Acrobat products and applying patches don't forget Adobe's little gotcha here:

http://kb2.adobe.com/cps/498/cpsid_49880.html
Posted by: skislowski 14 years ago
Senior Yellow Belt
0
thanks for the tip, I'm guessing the the original transform mst prior to the patch msp is still in use after the patch msp is applied or do u need to create a new mst for the newly patched AIP
Posted by: anonymous_9363 14 years ago
Red Belt
0
do u need to create a new mst for the newly patched AIP There should be no need, no.
Posted by: squeakstar 14 years ago
Orange Senior Belt
0
i didn't know how to apply these updates at all tbh but i found a useful blog post on the subject

http://www.404techsupport.com/2010/02/17/gpo-deploying-adobe-reader-9-3-1/
Posted by: rasczak 14 years ago
Yellow Belt
0
Ok, I hope you all can help me understand this. If you Create an Admin install point, I understand that you patch the AIP.

If I understand what adobe is saying correctly, for each FULL install ie.9.0, 9.1, 9.2 and 9.3, you should create an AIP. then you deploy the latest via either GPO or SCCM. However, if you create an AIP for 9.3 for instance, does that AIP also contain all of the other patches for 9.0, 9.1 and 9.2? or am i incorrect in this assumption? and if I am incorrect, what is the proper way to patch them so that ALL relevant security patches are included in the latest AIP?
Posted by: anonymous_9363 14 years ago
Red Belt
0
does that AIP also contain all of the other patches for 9.0, 9.1 and 9.2?One would hope but this is an Adobe product...
Posted by: rasczak 14 years ago
Yellow Belt
0
ORIGINAL: VBScab

does that AIP also contain all of the other patches for 9.0, 9.1 and 9.2?One would hope but this is an Adobe product...


Sadly, I concur. Is there a way to check if the proper patches have been applied to an installation?

Btw thanks for replying to the post.
Posted by: anonymous_9363 14 years ago
Red Belt
0
Here's a QAD script I had lying aboutOption Explicit

Dim objInstaller
Dim colPatchList
Dim objPatch
Dim strList`

Const strProductCode = "{90110409-6000-11D3-8CFE-0150048383C9}"

Set objInstaller = CreateObject("WindowsInstaller.Installer")
Set colPatchList = objInstaller.Patches(strProductCode)

strList = ""
strList = strList & "Patches applied:" & vbCRLF

For Each objPatch In colPatchList
strList = strList & objInstaller.PatchInfo(objPatch, "PackageName") & vbCRLF
Next

WScript.Echo strList
If you want more information about the patches themselves, have a peek at the Patches stuff on MSDN.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
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