HOME


© 2018 Adobe Inc. All rights reserved.

Updated Nov 20, 2019.

Windows Virtual Deployment Overview

This document is designed for enterprise IT professionals who have already configured the installer and are ready to deploy the product in a virtual environment.

Licensing support on VMs

Organizations must have a valid Acrobat software license for every user that has access to Acrobat on a server. For more information, refer to the Software license terms.

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.

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. For example, you may need font pack or spelling pack installers.