Updated script to Slipstream Adobe Reader with PowerShell
Time flies by and it’s already almost a year ago I released my PowerShell script to slipstream Adobe Reader for deployment with ConfigMgr 2012 as an application. During this time, I’ve received a lot of positive feedback from readers of this blog regarding on how to improve the script. I’ve finally come to my senses and actually updated it quite a bit.
The core functionality of the script to first extract the downloaded executable and then apply the patches haven’t been changed that much, except for modernizing the code a bit. Here’s what I’ve added and changed:
- Added a check to see if any version of Adobe Reader is already installed on the system where the slipstreaming is being performed, this to prevent error messages about that the product is already installed when applying the base installer to the AIP.
- Removed the output from Write-Output and replaced it with support for standard PowerShell parameters. Use -Verbose instead to see detailed messages about what the script is doing.
- In the script where Start-Process is calling msiexec, a check have been added to see if msiexec returned an exit code of 0. If not, the script will bail out and not continue.
- If there would be several quarterly or security patches, those results are now being sorted and should be executed in the correct order.
Download the script
You can download the script from the TechNet Gallery.
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 and user groups.