Deploy Adobe Reader 11.0.6 with ConfigMgr 2012

This is going to be a very short blog post, since I’ve improved the method of slipstreaming Adobe Reader mentioned in this blog post. The latest version of Adobe Reader is 11.0.6 and it’s a quarterly released patch.
Simply download the file below and then read my post on how to slipstream Adobe Reader. In that post I’m referring to Adobe Reader 11.0.5, but this process works for all releases of Adobe Reader 11.0.x.
If you have any questions, please go ahead and send me an email or write a comment.

Nickolaj Andersen

Chief Technical Architect and Enterprise Mobility MVP since 2016. Nickolaj has been in the IT industry for the past 10 years specializing in Enterprise Mobility and Security, Windows devices and deployments including automation. Awarded as PowerShell Hero in 2015 by the community for his script and tools contributions. Creator of ConfigMgr Prerequisites Tool, ConfigMgr OSD FrontEnd, ConfigMgr WebService to name a few. Frequent speaker at conferences such as Microsoft Ignite, NIC Conference and IT/Dev Connections including nordic user groups.


  • When you add the application to SCCM it automatically creates a detection method with a clause for the MSI Product Code. When you say to include the version number do you mean to add another clause to the detection method? Do you have a blog post where you detail how to do this?

    • Hi Carl,
      What I mean by that is that you edit the clause, browse for the MSI file and select it. Then select the option called:
      “This MSI product code must exist on the target system and the following condition must be met to indicate presence of this application”
      MSI Property: Version
      Operator: Equals

  • Is there a specific way of dealing with the removal? running a report for all machines with Adobe reader brings back the same product GUID’s, and it’s set to the same for both 11.06 and 11.07 as the uninstall program, This seems to make my deployment re run each time, as it removes 11.07 and then installs it again only to repeat this process again afterwards.
    I have the rule to replace and uninstall for the latest application?
    Many Thanks in advance

    • Hi K,
      Yes, by deploying Adobe Reader with this method you need to make use of supersedence. The detection method rule should also include Version and not only the Product Code.

  • Hi Nikolaj,
    I tried to slipstream 11.0.00 straight to 11.0.06 is this OK?
    I’m asking because when i created a package and deployed to a workstation with Adobe 11.0.00, i was hoping that the outcome would be version 11.0.06, but somehow it did not work.
    Please advise

  • NIckolaj
    Thanks for your quick response!
    I tried to slipstream the 11.0.06 same way you did from your previous post thinking that the 11.0.00 is the same with MUI.
    When i deployed it, under control panel>programs and features…there is one entry for 11.0.06 and a separate entry for the Adobe Reader XI MUI.
    I will also try to to slipstream the MUI, but please try it too when you have the time and let me know.
    Thanks and more power!

  • Nicolaj
    This slipstreaming is a big help, thanks
    1. We are using Adobe Reader XI MUI. Will this slipstreaming work on Adobe Reader XI MUI?
    2. Do you also deploy Adobe Flash Player update on SCCM 2012? If so, kindly share 🙂

    • Hi Jim,
      I’ve myself never deployed the MUI of Adobe, so I can’t say for use. Unless you want to just go ahead and try it yourself, give me a few days and I’ll look into it 🙂

  • Wrong MSI product code used from Adobe (use registry key DisplayVersion=11.0.06)

  • Hi,
    I’m testing your slipstream method at the moment and it works very well, thanks. The problem I have is that I have an Adobe Reader distribution that is already deployed that I need to remove to use this method on all my clients. Is there an easy way to link the new install to a removal of the old version of reader?

    • Hi Al,
      Cool that you’re looking into the slipstream method!
      If you’ve deployed the ‘old’ version with ConfigMgr and have an application for it (with a working uninstall command on the Deployment Type), you can use supersedence on the new Adobe Reader application to remove the old version.

      • Hi Nickolaj,
        My old deploy was before I upgraded to system center 2012, so it wasn’t deployed as an application but as a package.

  • My base image has AdobeReader 11.0.00, I want to update to version 11.0.06.
    When I sent the package to a test computer without AcrobatReader, it is installed without problem. But when I sent to PCs with AdobeReader 11.0.00 installed, I got a error 0x87D00324 (-2016410844) for some computers and others stay “in progress” content Downloaded

    • Hi Oscar,
      Slipstreaming Adobe Reader this way requires you do use supersedence on the latest version to remove any previous installations of Adobe Reader.

      • “The application was not detected after installation”
        Its installed, but its not detected. I set detection to the MSI code and version 11.0.06, but it doesn’t appear to be returning with a success code, even though its installed

      • Hi Joe,
        Then I would recommend to look into this, since that’s the only way to get it to work 🙂
        (Maybe not the ONLY way, but it works really great)

  • Something I’ve not seen (perhaps you’ve written it, but I haven’t seen it) is what your detection rule is for Reader versions, since the MSI code doesn’t change.
    I’m successfully deploying 11.0.06, however SCCM is kicking back that the app isn’t detected after deployment. I’m trying to use the version of AcroRd32.exe

    • Hi Joe,
      I’ve always used the MSI Product code on the AcroRead.msi together with the version property, that way it works out fine.

  • ps: I should have said then I copied it to the AIR folder for use with the customiser program.

  • I did as you said but when it came to editing the msi and creating a mst file the customiser reported that there was no, setup.ini.
    I overcame this by commenting out the line that removed the AdobeReader folder, as it contains the setup.ini file but get’s deleted at the end of the poiwershell script.
    #Remove-Item “$($DownloadFolder)\AdobeReader” -Recurse -Force


Categories use cookies to ensure that we give you the best experience on our website.