Not all settings in Customization wizard are passed on to Reader DC installs

Question

I created an MST file for my company installation of Adobe Reader DC. I am installing DC using SCCM and it installs fine, but the Protected View and Privileged Locations settings do not carry over into the installation. Some settings do carry over, so I know the MST file is being read. Also, if I open the MST file in Notepad, I can see some of the Privileged Location URL's listed so I know the info is in there, but it isn't getting used during the install.

Same thing happens if I run the install from the command line, so I know SCCM is not the culprit. Anyone else have this issue?

Any ideas?

Steve Cordero · Accepted Answer

MST file is here:Dropbox - PublicI edited the MST file to take out a few of my internal server names that I didn't want public. This appears to be a UI bug. The Privileged Locations don't show up in the UI of the Acrobat Reader DC client but DO show up in the Windows Registry FeatureLockdown hive.Example:Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown\cTrustedFolders\cAlwaysTrustedForJavaScript]"t2_recursive"="K:\""t1_recursive"="G:\""t0_recursive"="F:\"

TDHCA78701 · Answer

Thank you for this message thread. I noticed this when preparing my install and I was confused why I could not see my configuration, but see the entries in the registry. How can we gain any insight into WHEN this will be fixed as I would prefer to not upgrade client systems and then have the confusion of what is already trusted and what is not?

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.