Cannot update DC products through Microsoft Intune

[rsheldon_asg]

I use Microsoft Intune to manage my applications and software updates.  Acrobat X and XI worked wonderfully as I could distribute the apps and apply any patches by uploading the .msp file when published by Adobe. 

However, I cannot update Adobe Acrobat DC through Microsoft Intune.  While the .msp file provided by Adobe works when manually installing, Intune will not allow me to upload the .msp file because it says that the file is corrupt.

According to Microsoft Intune support, the .msp file created by Adobe does not correlate to the .msp specification outlined by Microsoft.  Their exact details are below:

The schema for PatchFamily is as follows: <xs:element name="PatchFamily" type="Identifier" />

and the Identifier type is defined by this regex: [_a-zA-Z0-9][_a-zA-Z0-9\.]*

Cracking open the msp provided, the value for PatchFamily is {AC76D4781033F45034780E0F06755100}. That does not match the regex defined for the identifier type. The issue is with the curly brackets.

Is it possible for Adobe to update their .msp files for Adobe Acrobat DC to conform to this requirement so we can use software management to continue to patch the application?  Otherwise, how can I bundle the .msp file with the application installer?  My attempts to do so thus far have failed when using the Adobe Customization Wizard DC. I have attempted to add the update at the end of the installation through the "Launch Other Applications" section, though that section appears to be ignored on the Adobe Reader installations.

Many thanks for any thoughts or time on this issue.

[Mohd Amish]

Hi Ryan. Thank you for reporting this issue.

We are looking into this issue and will update you as soon as possible. Thank you.

[Mohd Amish]

Hi Ryan,  This is an issue in DC and we are currently working on a fix. The fix will be available in the  future update of Acrobat DC. Thank you for your patience.

[rsheldon_asg · Accepted solution]

Mohd, I can confirm that the latest release of Acrobat DC and Acrobat Reader DC (15.009.20069) both resolve this issue.  Thanks!

[Mohd Amish]

Thanks Ryan for the prompt response. Glad it worked for you.