The MSI installer failed with a classic Not enough space exception. In my case, I tried to deploy the MSI package to a testing VM which had just 2 GByte left. To dig deeper, I enabled the /l*v parameter above, waited for a new installation run and looked into the c:\Adobe_DC_Install.log file. After looking through the C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log I noticed that the MSI installer had failed with a very generic error code 1603. The other security group contained some test users for installing the app through the company portal.Īfter assigning the newly created application to the proper security groups, Microsoft Endpoint Manager reported the error code 0x80070643 during installation.One security group contained a virtual machine for testing the device installation.~1.5 GByte for the installation processįor testing the installation procedures, two security groups had been set up in the Azure Active Directory:.Please note, that the target machine needs atleast 4.5 GByte of free hard disk space: I am using the directory C:\Program Files (x86)\Adobe\Acrobat DC\ as marker to identify an existing Acrobat DC installation. Get-wmiobject Win32_Product | Sort-Object -Property Name | Format-Table IdentifyingNumber, Name, LocalPackage -AutoSizeĪs a detection rule, I am going with a simple if directory exists then strategy. Without the latest patch you will likely see the error that your browser or operating system is not up-to-date when starting Adobe Acrobat DC.Įdit the setup.ini file to add the previously copied patch: AcroPro.mst Applying patchesĬopy the previously downloaded patch file next to the AcroPro.msi file. Acrobat DC Standard and Pro are using the same installer. Don’t get confused by the Pro suffix in the AcroPro.msi file. mst file is later used by the MSI installer to transform the installation process.
0 Comments
Leave a Reply. |