#ADOBE ACROBAT READER DC MUI AT STARTUP INSTALL#
#ADOBE ACROBAT READER DC MUI AT STARTUP UPDATE#
#ADOBE ACROBAT READER DC MUI AT STARTUP MANUAL#
#ADOBE ACROBAT READER DC MUI AT STARTUP FULL#
#ADOBE ACROBAT READER DC MUI AT STARTUP WINDOWS 10#

The first notification will tell you there is a change to come. The Intune Management Extension will trigger the installation and you will receive 3 notifications

#ADOBE ACROBAT READER DC MUI AT STARTUP INSTALL#

When you click on “ Device install status” you’ll find more details about individual devices and their install status. The Overview blade will show a summary of Device and User status.Navigate to >Azure Portal> Microsoft Intune> Client Apps.You can monitor the installation status from the Intune management portal. To do so run the command Net Stop IntuneManagementExtension & Net Start IntuneManagementExtension Monitoring the installation status You can force a sync to install via the Management Extension by restarting the “ Microsoft Intune Management Extension” service. If not, the deployment of Adobe will firstr trigger the installation for the Intune Management Extension, followed by the installation of Adobe. My test devices already had PowerShell scripts assigned so the Intune Management Extension is already installed. 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. If not, It should be automatically pushed by Intune, prior to the app deployment. If you have assigned a PowerShell script previously, the Intune Management Extension will be installed already. When ready assign it to a user or device group as usual.

The application will now be uploaded to Microsoft Intune. I did not change any of the default return codes Click on OK when you are ready to continue.The setup will only continue if this file does not exist. The Rule type is File because I want to check for the existence of the AcroRd32.exe file. I choose to manually configure the detection rules with the following settings: You can manually configure detection rules or use a custom script. Click on OK to continue to the Detection rules.Configure these settings according to your needs.

#ADOBE ACROBAT READER DC MUI AT STARTUP WINDOWS 10#

The minimum OS version is Windows 10 1703.

Click on OK to continue to the App Requirementsįor the Operating system architecture I choose 64-bit ut you can choose both 32-bit and 64-bit.

This is why you need to know the app GUID and why you test the silent install & uninstall commands. Get-CimInstance -ClassName Win32_Product | Sort-Object -Property Name | Format-Table IdentifyingNumber, Name, LocalPackage -AutoSize

#ADOBE ACROBAT READER DC MUI AT STARTUP UPDATE#

Thx LaneCoin! He notified me about an update With newer powershell versions Get-WMIObject is depreciated.

Run this PowerShell command after installation of Adobe Reader DC: ( Thank you PJ1004 for the Sort-Object tip!!) Later on, when configuring your Win32 Application in Intune, you will also need the application GUID for the uninstall command. Go ahead and install Adobe Reader DC on your test device just to make sure your silent install works as expected.

Note:your command can be different depending on your Adobe Version. Go ahead and download your copy of Adobe Reader DC.Īs previously described you can install Adobe silently using the command: AcroRdrDC1900820071_en_US.exe /sAll /rs /rps /msi /norestart /quiet EULA_ACCEPT=YES

Sidenote: Remember you will need a free volume distribution license in order to distribute Adobe software to your clients. Install Adobe Reader DC using Win32 deployment and Microsoft Intune. This tool will package and convert your application to the new. This solution still relies on the Intune Management Extension and you will first need to prep your win32 application using the Microsoft Intune Win32 Content Prep Tool.

#ADOBE ACROBAT READER DC MUI AT STARTUP MANUAL#

Test device (for testing manual installation and Intune deployment).

Device must be (Hybrid) Azure AD joined and Intune MDM enrolled.

Go to and navigate to Microsoft Intune > Apps > Windows> Add app Note:I have tested with WindEnterprise and Pro versions. I can only hope this post is of add value and helps you understand these new configuration options a little better.

#ADOBE ACROBAT READER DC MUI AT STARTUP FULL#

There are some great blog posts out there I think you should also read for a full understanding. 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. This is great news because now we don’t have to use work-arounds like PowerShell scripts. During my visit at Microsoft Ignite 2018 in Orlando, one of the most awaited features for Microsoft Intune was announced We can finally deploy Win32 applications using Microsoft Intune.

Adobe acrobat reader dc mui at startup