sothpaw Posted March 4, 2014 Report post Posted March 4, 2014 My usual packaging and deployment consists of extracting the installer exe and running the msi through the customization wizard Adobe provides. This latest 11.0.06 comes as a solo msp as well... I'm fully aware and works well to upgrade existing 11x installs. However my environment has regions where I do not control the release of Reader, and they might have PC's with 10x versions running wild. Plus I need to be able to do initial installs of Reader on new PC's. Here's what I've done: I've followed this article: http://www.scconfigmgr.com/2014/01/16/slipstream-adobe-reader-with-powershell/ Even the execmgr log files on the client machine also show that the installation was pushed out successfully, but when you log onto that particular client computer and check the program version either by launching Adobe Reader and go into About it's still showing version11.0.03. The Control Panel also shows version 11.0.03 in the Programs/Features area. Again- yes the msp works great on its own, but I would love to have just one script to install or upgrade any existing Reader! I expect major upgrades getting wonky, but, I absolutely dispise how Adobe cannot get their minor updates to be consistent! Any help on this would be greatly appreciated. Thanks, J Quote Share this post Link to post Share on other sites More sharing options...
core Posted February 26, 2015 Report post Posted February 26, 2015 I use applications to install Adobe Reader updates. Use "msiexec /p AdbeRdrUpd11.0.06.msp /qn" for your installation program. The key is to use "/p" for Adobe msp files. Quote Share this post Link to post Share on other sites More sharing options...
