Copy link to clipboard
Copied
Hello all, there is an issue that has been elusive for me and others with Adobe support commonly telling you to repackage the software to resolve Adobe Acrobat to not function as both pro and reader with one app deployment. However, I've found out recently that this can be resolved by editing the following registry key to a value of 1 instead of 0.
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Adobe Acrobat\DC\FeatureLockDown\
Key = bIsSCReducedModeEnforcedEx
Value = 0
CHANGE TO
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Adobe Acrobat\DC\FeatureLockDown\
Key = bIsSCReducedModeEnforcedEx
Value = 1
I will note that we stumbled upon this because we ran into an issue after swapping our licenses to enterprise-based licenses, which caused two Adobe accounts to be created, thus defaulting to the personal account that had NO Adobe Pro access instead of their enterprise account that did have the correct licensing.
Appropriately we plan to either delete the personal accounts or configure SSO to resolve this matter in its entirety. However, we found we had to toggle this key to 1 to get prompted to use the correct account after clearing the credential manager and resigning into Adobe.
Have something to add?
Find more inspiration, events, and resources on the new Adobe Community
Explore Now