adobe acrobat reader DC

Install Adobe Reader DC using Microsoft Intune Win32 application deployment

During my visit at Microsoft Ignite 2018 in Orlando, one of the most awaited features for Microsoft Intune was announced; Still in public preview but we can finally deploy Win32 applications using Microsoft Intune. This is great news because now we don’t have to use work-arounds like PowerShell scripts. I have another post guiding you through the installation process of Adobe Acrobat Reader DC using Intune and PowerShell, and in this post I’ll try to guide you through the Win32 application deployment process and install Adobe Reader DC using Win32 deployment and Microsoft Intune. There are some great blog posts out there I think you should also read for a full understanding. I can only hope this post is of add value and helps you understand these new configuration options a little better.

Note: I have tested with Windows 10 1803 Enterprise and Pro versions. You will know Win32 Application Deployment is available for your tenant when you add an application like usual and see the new option: Windows app (Win32) – Preview

Go to https://portal.azure.com and navigate to Microsoft Intune > Client Apps > Apps > Add app

Intune - Win32 Application

Prerequisites

  • Windows 10 version 1607 and later
  • Device must be (Hybrid) Azure AD joined and Intune MDM enrolled
  • Prepped Win32 Application
  • Test device (for testing manual installation and Intune deployment)

This solution still relies on the Intune Management Extension and you will first need to prep your win32 application using the Microsoft Intune Win32 App Upload Prep Tool. This tool will package and convert your application to the new .intunewin format.

Install Adobe Reader DC using Win32 deployment and Microsoft Intune.

Sidenote: Remember you will need a free volume distribution license in order to distribute Adobe software to your clients. Go ahead and download your copy of Adobe Reader DC.

As previously described you can install Adobe silently using the command:

AcroRdrDC1900820071_en_US.exe /sAll /rs /rps /msi /norestart /quiet EULA_ACCEPT=YES

Note: your command can be different depending on your Adobe Version. Keep that in mind when you copy/paste 😊

Go ahead and install Adobe Reader DC on your test device just to make sure your silent install works as expected. Later on, when configuring your Win32 Application in Intune, you will also need the application GUID for the uninstall command.

Run this PowerShell command after installation of Adobe Reader DC:

get-wmiobject Win32_Product | Format-Table IdentifyingNumber, Name, LocalPackage -AutoSize

 

Intune - Application GUID

Take a note of the GUID. Your uninstall command will be:

msiexec /x “{AC76BA86-7AD7-1033-7B44-AC0F074E4100}” /q

Prepping your application for Intune Win32 Application Deployment

  • Download your version of Adobe to a directory. I will use my own deployment as an example and start with AcroRdrDC1900820071_en_US.exe in the folder c:\temp\adobe\
  • Download the Microsoft Intune Win32 App Upload Prep Tool and extract it to c:\temp\
  • Create your output folder: c:\temp\AdobeIntune for the .intunewin package
  • Run the following command from the prep tool folder:
IntuneWinAppUtil.exe -c c:\temp\Adobe -s AcroRdrDC1900820071_en_US.exe -o c:\temp\AdobeIntune

The tool is very easy in use and with a simple strcture:

IntuneWinAppUtil.exe -c [source folder] -s [setup_file, such as setup.exe or setup.msi] -o [output_folder] for the generated .intunewin file.

The command will finish with [====================================] 100% Done!!!

IntuneWinAppUtil

In the output folder you will find a new file: AcroRdrDC1900820071_en_US.intunewin . Have a look at Oliver Kieselbach’s post for a deep dive in Microsoft Intune Management Extension and Win32 Apps.

You’re now ready to upload the package to Microsoft Intune.

Deploy the Win32 App with Intune

  • Navigate to >Azure Portal> Microsoft Intune> Client Apps
  • Click on App App
  • Select Windows app (Win32) – preview as your App type
  • Browse to the [your_adobe_setup_file].intunewin file
  • Click OK

Intune add win32 application

Move to the next part, App Information and configure to your needs. Here you will have to provide a Name, Description, Provider and some other values before you can continue.

Intune add win32 application

  • Click on OK at the bottom when you are done and continue to Program Configure

Here you will enter the install command and the uninstall command. Make sure you have update the following lines when you copy/paste!

Install command:

AcroRdrDC1900820071_en_US.exe /sAll /rs /rps /msi /norestart /quiet EULA_ACCEPT=YES

Uninstall command:

msiexec /x {AC76BA86-7AD7-1033-7B44-AC0F074E4100} /q

Intune win32 application program settings

This is why you need to know the app GUID and why you test the silent install & uninstall commands.

  • Click on OK to continue to the App Requirements

For the Operating system architecture I choose 64-bit ut you can choose both 32-bit and 64-bit. The minimum OS version is Windows 10 1703. Configure these settings according to your needs.

Intune win32 application program requirements

  • Click on OK to continue to the Detection rules

You can manually configure detection rules or use a custom script. I choose to manually configure the detection rules with the following settings:

Intune win32 application detection rules

The Rule type is File because I want to check for the existence of the AcroRd32.exe file. The setup will only continue if this file does not exist.

Intune win32 application detection rules

  • Click on OK when you are ready to continue. I did not change any of the default return codes

Intune win32 application return codes

  • Click on OK and finally click on Save

The application will now be uploaded to Microsoft Intune. When ready assign it to a user or device group as usual.

The Intune Management Extension

If you have assigned a PowerShell script previously, the Intune Management Extension will be installed already. If not, It should be automatically pushed by Intune, prior to the app deployment. It will install the service “Microsoft Intune Management Extension” and will setup a scheduled task “Intune Management Extension Health Evaluation” The agent will check for scripts every 60 minutes, and the health check will run once a day to see if the agent is functioning correctly.

My test devices already had PowerShell scripts assigned so the Intune Management Extension is already installed. If not, the deployment of Adobe will firstr trigger the installation for the Intune Management Extension, followed by the installation of Adobe.  You can force a sync to install via the Management Extension by restarting the “Microsoft Intune Management Extension” service. To do so run the command;

Net Stop IntuneManagementExtension && Net Start IntuneManagementExtension

Monitoring the installation status

You can monitor the installation status from the Intune management portal.

  • Navigate to >Azure Portal> Microsoft Intune> Client Apps
  • Click on the newly deployed Win32 App
  • The Overview blade will show a summary of Device and User status

Intune win32 application deployment monitoring

When you click on “Device install status” you’ll find more details about individual devices and their install status.

Intune win32 application device install status

Install experience on devices

The Intune Management Extension will trigger the installation and you will receive 3 notifications;

The first notification will tell you there is a change to come. The second one will inform you the download has started and finally when the software is installed the third notification will show.

Intune win32 application user experience

After the last notification, the Start menu shows the newly installed Adobe Reader DC app and there will be a shortcut on the Desktop.

When you look at “Programs and Features” you’ll also see that “Adobe Acrobat Reader DC” has been installed, along with “Microsoft Intune Management Extension

Intune win32 application user experience

Troubleshooting

One of the first places you can have a look when there are any issues, is the Intune Management Extension Logfile at: C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\

IntuneManagementExtension.log

Open the IntuneManagementExtension.log file and search for the keyword “adobe”. The log-file might not be that easy to read but it will give you a lot of info about application install status and possible error messages that might help you troubleshoot issues. I can’t post the logfile here since it contains information I don’t want out there in the open.

Detection Rules

Some interesting parts to look for after finding your keyword adobe are <![LOG[[Win32App] Start detectionManager SideCarFileDetectionManager]LOG]!> and <![LOG[[Win32App] Path doesn’t exists: C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\AcroRd32.exe applicationDetected: False]LOG]!>

Here you have your detection rules in action. The Intune Management Extensions looks for the existence of AcroRd32.exe and comes back with a value of False, meaning Adobe Reader DC is not installed.

Dowloading the app from Intune

A little further in the logfile you can see the download starts at <![LOG[[Win32App] ===Step=== Download]LOG]!> followed by <![LOG[[Win32App] ===Step=== ExecuteWithRetry]LOG]!> and <![LOG[AcroRdrDC1900820071_en_US.exe /sAll /rs /rps /msi /norestart /quiet EULA_ACCEPT=YES]LOG]!> which indicates the execution and installation of the Win32 application you deployed.

Application is Already installed

If the application is already installed, the detection rule will come back with a value of true like here:

<![LOG[[Win32App] Checked filePath: C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\AcroRd32.exe, Exists: True, applicationDetected: True]LOG]!>

Errors

Some errors you might encounter in the logfile are listed below. You will have to dig through the logfile and do a little more troubleshooting here.

  • Invalid detection rule: Bad filePath:
  • ArgumentException: System.ArgumentException: Illegal characters in path.
  • <![LOG[[Win32App] Failed on exception, set applicationDetected False]LOG]!>

Windows Registry

The Intune Management Extension store some info in the registry at the following locations. Have a look here to help you troubleshoot issues with Win32 Application deployment

  • HKLM\SOFTWARE\Microsoft\IntuneManagementExtension\Apps\
  • HKLM\SOFTWARE\Microsoft\IntuneManagementExtension\Win32Apps\

Eventlog

Then there is the good old eventlog. Have a look at the following logs:

  • Windows Logs>Application
  • Applications and Services Logs> Microsoft> Windows>
    • DeviceManagement-Enterprise-Diagnostics-Provider

References

8
Leave a Reply

avatar
3 Comment threads
5 Thread replies
0 Followers
 
Most reacted comment
Hottest comment thread
4 Comment authors
JohnnymacOktay SariRkastSeth Zwicker Recent comment authors

This site uses Akismet to reduce spam. Learn how your comment data is processed.

  Subscribe  
newest oldest most voted
Notify of
trackback

[…] UPDATE: Have a look at my new post: Installing Adobe Reader DC with Intune – Part 2 (Win32 application deployment with Intune) […]

Seth Zwicker
Guest

Thanks a million! I’ve been able to deploy most apps via Intune but this was a sticking point for me.

Johnnymac
Guest
Johnnymac

Many thanks for the above post, which has helped loads with my deployment 🙂

I have one quick question. Do you know if the below switches, get around the out of the box ‘post’ install prompts? (i.e. setting it as the default PDF reader etc)

AcroRdrDC1900820071_en_US.exe /sAll /rs /rps /msi /norestart /quiet EULA_ACCEPT=YES

John.