Deploy Adobe Reader 11.0.3 with ConfigMgr 2012
Another Adobe Reader patch has been released, so it’s time to deploy it to your clients. This post will create a slipstreamed Adobe Reader application that will be deployed with ConfigMgr 2012. If you havn’t yet switched to a slipstreamed approach with Adobe Reader, I suggest that you do it now. The process is a bit more complex than rather just deploying the .msp file to your clients. With this approach you’ll not have to deal with patches not being installed in the correct order for example.
- Adobe Reader XI patches
- Create the folder structure
- Download the required files
- Create the AIP package
- Create a MST transform
- Create the Adobe Reader 11.0.3 application
Adobe Reader XI patches
Adobe uses an approach that exists of a Base installer (e.g. AdbeRdr11000_en_US.exe), Quaterly patches and Security patches. The idea is that when a new version e.g. 11.0.0 is released, they call it a base release. Patches that are released quarterly (Quaterly patches) can be applied to the base installer. Security patches needs to be applied to base installers with the latest quaterly patch applied first. The below behavoir applies to when you’re creating an Administrative Install Point (AIP) also called slipstreaming. It works like this:
Base release -> Quarterly patch
Base release -> Quarterly patch -> Security patch
If we turn this into release versions, these workflows will work out just fine:
11.0.0 -> 11.0.3
11.0.0 -> 11.0.1 -> 11.0.2
This will however not work:
Base release -> Quarterly patch -> Quaterly patch
Base release -> Quarterly patch -> Security patch -> Quaterly patch
If we turn this into release versions, these workflows will not work:
11.0.0 -> 11.0.1 -> 11.0.3
11.0.0 -> 11.0.1 -> 11.0.2 -> 11.0.3
So in order to create an AIP for the latest release Adobe Reader 11.0.3 (a quaterly patch), we need to follow this workflow:
11.0.0 -> 11.0.3
Create the folder structure
Create the following folder structure:
In the pictures from now on I’ll be using my E: drive instead on the C: drive.
Download the required files
Download the required files and save them in C:\AdobePatch\AdobeReaderDownloads.
Create the AIP package
1. Open an elevated command prompt and browse to C:\AdobePatch\AdobeReaderDownloads.
2. Run the following command:
AdbeRdr11000_en_US.exe -nos_o"C:\AdobePatch\AdobeReaderDownloads\11.0.0" -nos_ne
3. Run the following command:
msiexec /a 11.0.0\AcroRead.msi /qb TARGETDIR=C:\AdobePatch\AIP
4. Run the following command:
msiexec /a C:\AdobePatch\AIP\AcroRead.msi /qb /p AdbeRdrUpd11003.msp TARGETDIR=C:\AdobePatch\AIP
5. Copy Setup.ini from C:\AdobePatch\AdobeReaderDownloads\11.0.0 to C:\AdobePatch\AIP.
Create a MST transform
1. Download Adobe Customization Wizard XI from here.
2. Install the application and launch it when done.
3. Click on File -> Copy Package.
4. Enter the information as in the picture below.
5. From here on you have free hands. Make any desired configuration in the menus to the left that fits your environment. When completed move on to step 6.
6. Click File -> Save Package. Give the file a name and click Save.
7. Exit Adobe Customization Wizard XI.
In C:\AdobePatch\AcrobatTransform\Adobe Reader 11.0.3 you’ll now have the complete package that will be deployed to your clients with ConfigMgr 2012. Copy the contents of Adobe Reader 11.0.3 folder to your source structure on the ConfigMgr 2012 Primary Site server (or however your environment looks like). In my case it will be \\siteserver\SoftwareDistribution\AdobeReader\11_0_3.
Create the Adobe Reader 11.0.3 application
In this post I’ll not cover how to create an application in ConfigMgr as I assume that you already know how to do that. What’s important to point out thought is that an application with AIP source files will not be able to install “over” existing Adobe Reader installations since it’s not a patch to your existing Adobe Reader installations. You’d have to create an uninstall deployment for the previous Adobe Reader installations before you deploy this Adobe Reader 11.0.3 application. On the bright side though, once you’ce adapted and deployed this type of applications (AIP), you’ll only need to make use of the superseedence feature in the application model.
What’s good to know though, in order to make use of the transform file AcroRead.mst in my case (that’s what I named it when I saved the package in Adobe Customization Wizard XI) you need to run the following command to install the application:
msiexec /i AcroRead.msi /qn TRANSFORMS=AcroRead.mst
I hope this helps!