I'm trying to figure out if there's a way to set up a single application in Intune that combines both Adobe Acrobat Reader and the Pro functions. We want most of our users to have access to the free version of Reader without annoying login prompts, upsells, or marketing distractions. At the same time, we need an option for licensed users to access the premium Pro features with a sign-in button. Has anyone successfully created a unified installer using .mst customization or registry tweaks that allows for this setup? I've gone through the documentation which suggests this is possible, but after two days of trying, I'm almost ready to just create two separate apps.
4 Answers
It sounds like you're trying to avoid the sign-in prompt for the Reader. I generally install Reader through AcroPro.msi and keep applying the latest patch. For users who need the Pro features, they just log in with their Adobe account when they want to upgrade. If everything is done correctly, it shouldn't ask for sign-in unless they actively start the upgrade process. I manage the updates by manually pushing Reader's updates to all devices, except for those assigned Pro versions, which get the specific pro updates. Keeping track of registry customizations is crucial, as updates might reset them, so I use remediation to maintain those settings.
Here’s what worked for me: I made a custom package via the Adobe Admin Console. You can go with their pre-packed options as well. Applying the Acrobat Customization Wizard helped me set options like suppressing the sign-in requirement and enabling silent installs. You can also push key registry values to disable upsell messages from appearing. I recommend including these changes in your deployment also to keep things seamless for the users.
You can install Pro and then tweak a registry key to activate Reader mode by default. Specifically, set HKEY_LOCAL_MACHINESOFTWAREPoliciesAdobeAdobe AcrobatDCFeatureLockDown:"bIsSCReducedModeEnforcedEx"=dword:0000001. This way, it functions as Reader unless a licensed user signs in. Make sure to check out each installer option on Adobe's website too, as they have resources that can help you set this up properly.
Honestly, this has been a challenge in our organization as well. For now, we deploy Reader and let users who qualify for Pro download it through self-service. I make it a point to uninstall any existing Adobe installations before proceeding, but I too have struggled with getting the unified installer to function correctly. It seems the goal of simplifying the process with a single installer is tougher than expected.
I came across a thread that might help you out—check it out! It appears someone figured out a workaround that might just do the trick.
Right, and don't forget there's another important registry key to manage. You should also set HKEY_LOCAL_MACHINESOFTWAREPoliciesAdobeAdobe AcrobatDCFeatureLockDowncIPM to ensure proper messaging is set up.