Adobe Reader is of course one of the most common applications on Windows desktops and if you’re moving to a Modern Management approach you’re likely looking at how to deploy Adobe Reader DC to Windows 10 via Microsoft Intune.
This is a challenge today because Adobe Reader DC comes as an executable, that while it can be extracted for the MSI, it includes support files that cannot be deployed via Intune. Microsoft only enables Windows desktop applications to be deployed from Intune where the installer is contained in a single file Windows Installer.
Adobe Reader DC Executable Installer
The Adobe Reader installer hasn’t changed much since as long as I’ve been writing about it (which has been way too long). What is different with Adobe Reader DC is that Adobe has moved to an evergreen model whereby they’re largely moved away from major releases and instead now deliver a continuous release cycle.
The current installer for Adobe Reader DC is a single executable that can run as is, or can be extracted for customisation typical of enterprise environments. When extracted it looks like this:
This just won’t work for deployment via Intune or the Windows 10 MDM channel. We need that single Windows Installer file. Better yet, we need Adobe to make Reader DC available via the Windows Store, but that’s a topic for another article.
Adobe Reader Windows Installer
Adobe does make a single file Windows Installer available for Adobe Reader DC, in various languages; however, the file was released in 2015 and unfortunately they’ve not updated it since. There has been several major releases and updates since March 2005.
So, now we have a way to deploy the file, let’s see how to customise it and deploy via Intune.
Customising the Installer
Customisation of the Adobe Reader installer for enterprise deployment is well documented and I’ve written about previous versions several times. The same process applies but pay attention to any version specific settings.
Just like previous versions, you use the Adobe Customization Wizard to customise the installer for your needs and deploy a custom package.
However, we can’t customise the single file Windows Installer directly because when saving the customisations, we get this:
To customise the installer, we need to use a 3 step process:
- Download and extract Adobe Reader DC executable installer
- Create a custom transform for this installer
- Apply the transform to the single file Windows Installer, so that the customisations are embedded into the installer. InstEd It! is a great free MSI editor to do that
I won’t go into a detailed step-by-step on how to use the Adobe Customization Wizard here because the documentation is detailed enough, but I will include a list of options I recommend you embed into the installer. There are some additional defaults and you may have specific options applicable to your environment.
|Personalization Options / EULA Option||Suppress display of End User License Agreement (EULA)|
|Installation Options / Run Installation||Silently|
|Installation Options / If reboot required at the end of installation||Suppress reboot|
|Shortcuts / Desktop||Remove the Adobe Reader DC shortcut (no one needs that one on the desktop…)|
|Online Services and Features / Disable product updates||Disabled (i.e. not ticked) - ensure Adobe Reader can update post-deployment|
|Online Services and Features / Disable Upsell||Enabled|
As I’ve listed in the table, it’s important to keep the Adobe Updater enabled, so that once Reader is deployed via Intune, end-points can manage updates themselves. I’ll cover more on updates in the next article.
Now that you have a customised single file Windows Installer for Adobe Reader DC, you can import that into Microsoft Intune, and make it available for deployment.
In this article, I’ve taken a look at how to deploy Adobe Reader DC as a mobile application for Windows 10 devices enrolled in Microsoft Intune via MDM by creating a customised package based on a single file Windows Installer.
In part 2, I’ll take a look at how Adobe Reader is updated post-deployment and discuss whether this type of deployment is the right approach. There are other options and ideally I’d like to see Adobe make Reader DC available via the Microsoft Store.