||The field indicates whether the preference can be
modified by through the user interface or by the administrator
at the registry level. There are a number of preference that exist
the registry, but which are application generated. For example,
tSASL_Mechanism is a server-generated
ID which is sent to the client. Values marked with a red X should be
modified as this will either
break the feature or the value will just be overwritten when the
feature is excerised.
||The preference data type; for example, boolean
or string. While Windows and Macintosh use the same data types, they are
represented differently. For an overview, see the following:
For more detail, refer to theEnterprise Administration Guide.
||The default value. Many default values can be changed by administrators or users as they excerise the user interface.
||Whether or not the preference is deprecated for this release. Deprecated preferences are not supported.
||Details should include allowable values,
interaction with other preferences, and a description of all the
preference's effects. Since this document is merely a reference, it is
often necessary to refer to additional related technical guides.
||The name of the application preference in the registry or plist
||These are paths to machine (system) level preferences that
require administrator permissions to change.
- Windows 32-bit: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\(product name)\(version)\FeatureLockDown\
- Windows 64-bit: On a 64 bit Windows system, the path to the FeatureLockdown is
- Macintosh: For 11.0 and later, preferences that are lockable on Windows may also be locked
on Macintosh. When configuring, use the same path that's used under FeatureLockdown
in the registry. The lock file is located at /Library/Preferences/com.adobe.(product name).plist/FeatureLockdown[same as Windows path]
|Maps to GUI
||Whether or not this preference maps to a graphical user interface (GUI) item.
For example, t(trusted file ID) maps to thePreferences panel > Security (Enhanced) > Add File. When a user adds a file as a privileged location, that choice is written to the registryafter the application is closed.
||The user preference path in the registry or plist to this particular preference.
These paths are for per user settings. For information about machine (system) preferences that
require administrator permissions to change, see Lock Path.
- Windows: The registry path. Preferences that can be set by
the user interface and which are user modifiable reside in HKCU. The
path varies based on the product name and product version. Lockable
preferences and a few others (such as installer preferences) reside in
HKLM and can only be modified by the administrator (See lockpath). Most
user preferences reside in HKEY_CURRENT_USER\Software\Adobe\(product
- Mac: The plist path varies by version. The filename includes the application
name and version. For 9.x versions and earlier, the filename also
includes the processor type. For example:
- 10.x /Users/(username)/Library/Preferences/com.adobe.[Acrobat.Pro or Reader].plist
- 9.x: /Users/(username)/Preferences/com.adobe.[Acrobat.Pro or Reader]_[ppc or x86]_[version].plist
||The product name must be one of the following:
- Windows: Adobe Acrobat (for all versions of Acrobat) or Acrobat Reader
- Macintosh: Acrobat.Pro or Reader
||The base version of the installed product
without any dots. For example, the value can be 8.0, 9.0, or 10.0. It
cannot be 9.1 or 8.2.5.
||Whether or not values for this
preference make the application environment more or less secure. For
application security by reducing potential surface attack areas. Of
course, such security precautions also restrict or turn off feature, and
managing for security is often a balancing act between mitigating risks
and allowing desirable features. For additional detail, see the
Application Security documentation.
||The version that the preference was introduced.
||A one sentence summary describing what the key does. The summary is used to populate the summary table.
||Whether or not the preference is visible to
the user if they examine the registry or plist. Many preferences are
"visible" but are not modifiable because they are created by the
application, server, or because changing them would break a feature.