© 2017 Adobe Systems, Inc. All rights reserved.

Updated Dec 04, 2017.


Supported products

In addition to this overview page, refer to the following for deployment details:


Adobe requires that organizations have a valid Acrobat software license for every user that has access to Acrobat on a server. For more information, see http://www.adobe.com/legal/licenses-terms.html.

Supported activation methods
Product Serialized? Named user? Notes
Citrix XenApp Supported Supported (Jan, 2017) The activation count is increased by one for each server. Admins can control user access by specifying groups. Named user deployment is only supported on Citrix Xenapp and Xendesktop 7.6 and above.
Windows Terminal Server Supported Supported (Nov, 2017)  
Microsoft App-V Supported Supported The activation count is equal to the number of clients on which a package is published. Admins can pre-serialize the package or allow users to activate with an ID.
VMware Horizon Supported Supported (Jan, 2017) Named user deployment is only supported on VMware Horizon 6.2 and above.

Named user deployments

Named user deployments do not use serial numbers for licensing: the end user simply “activates” Acrobat by logging in. Some virtual environments require that you serialize and deploy Acrobat DC with a serial number.

  • Named user deployment is always supported on dedicated virtual desktops (also known as VMs) because this is similar to deploying on a local machine, and users can sign in with their Adobe ID or Enterprise ID.
  • This feature is not supported for trial installs.


Some purchasing plans (such as the Adobe Value Incentive Plan) don’t have access to serial numbers.

Product tuning

In addition to the best practices described on the deployment pages, you may want to tune Acrobat products if you experience performance issues. Additionally, you may want to disable features and behaviors that should not be accessible to end users in an IT-managed environment.

  • The Updater should be disabled as described in this guide and the Preference Reference.

  • Accept the EULA on behalf of all users by setting the appropriate registry key.

  • For multilanguage installations (MUI), set the preferred language for all users via the SUPPRESSLANGSELECTION property or registry settings described in the Preference Reference.

  • Deploy enterprise files to the product’s directories (rather than per-user directories) so they are available to all users.

  • There are over 500 documented settings. Refer to the Preference Reference for complete registry and plist details.

  • Disable the Help > Repair Acrobat Installation menu by setting:

    • 32 bit machines: [HKLM\SOFTWARE\Adobe\(product name)\(version)\Installer] "Disable_Repair"
    • 64 bit machines: [HKLM\SOFTWARE\Wow6432Node\Adobe\(product name)\(version)\Installer] "Disable_Repair"

Scrolling performance

If scrolling performance is poor in graphic intensive documents, try the following:

  1. Go to Edit > Preferences > Rendering.
  2. Uncheck Smooth line art and Smooth images. Alternatively, you can set these preferences during pre-deployment configuration:
HKCU\Software\Adobe\Adobe Acrobat\10.0\Originals\bAntialiasGraphics: 0x00000000
HKCU\Software\Adobe\Adobe Acrobat\10.0\Originals\bAntialiasImages: 0x00000000

Distiller performance

  • In some environments, Distiller performance may suffer if the messages.log file becomes too large after a number of Distiller operations. Delete this file periodically. It is located at \Application Data\Adobe\Acrobat\Distiller <version>\messages.log.
  • Remove unused fonts from the Windows installation.

Folder permissions

Protected Mode will only work when the USERS group has the following permissions on the product installation folder: Read and execute, List folder contents, Read. For a default installation, the path might be C:\Program Files (x86)\Adobe\Acrobat Reader DC.

Resource planning

Note the following:

  • Acrobat products leverage Windows’ User Profiles feature to provide end users with a custom experience with respect to settings and files. Follow standard VMware’s methodologies for mapping user resources across one or more servers:

    • Registry: Registry preferences to control the UI and application behavior. Follow the VMware recommendations when planning for registry configuration and deployment.
    • Files: The application creates and writes to files automatically, but end users can also store information such as signature appearances, contacts, templates, and so on. Follow the VMware recommendations for setting up file I/O.
  • Separate installers: When enterprise workflows require components that use separate installers, run those installers at deployment time. End users without admin privileges on the server won’t be able to install components if their workflow suddenly requires them. The following items requires running an additional installer: