How to Deploy Adobe Reader and Acrobat Standard on a Terminal Server
Question details
The user needs to configure a shared terminal server so that authorized users can access Adobe Acrobat Standard while the rest use Adobe Reader, with Reader remaining the default system PDF application. The user is also seeking clarity on AppLocker rules and licensing compliance.
- Product
- Adobe Reader and Acrobat Standard
- Device & OS
- Windows Server
- Scenario
- Deploying multiple PDF applications on a shared Remote Desktop Session Host (RDSH) while restricting premium features to specific users and maintaining compliance.
- Observed behavior
- Needs a deployment strategy that legally balances Adobe's EULA requirements with technical restrictions (like AppLocker and Group Policy) to control application access and default file handlers.
Before making changes to your Terminal Server, carefully review your current Adobe Enterprise License Agreement (EULA). Standard retail licenses prohibit server deployment, so ensure you have the appropriate named-user or enterprise licensing required for Remote Desktop Services (RDS).
Use Official Adobe Enterprise Deployment Methods
To avoid EULA violations, deploy Acrobat using Adobe's official enterprise methods and proper per-user licensing rather than relying solely on AppLocker.
Using a retail version of Adobe Acrobat on a shared server usually violates the End User License Agreement (EULA). You must implement an enterprise deployment using Adobe's administrative tools to legally assign access to specific users.
While Windows AppLocker can technically prevent execution, Adobe auditing requires official Named User Licensing or Shared Device Licensing configurations.
Log in to your Adobe Admin Console to confirm your organization possesses a Volume License or Enterprise Term License Agreement (ETLA) that explicitly permits Terminal Server deployments.
Open an elevated Command Prompt and run 'change user /install' to put the Terminal Server into install mode before running any executable files.
Download and utilize the Adobe Customization Wizard to generate a pre-configured transform (.mst) file that suppresses the EULA prompt and optimizes settings for a multi-user environment.
Follow the latest Adobe IT deployment guides to implement Named User Licensing. This ensures only authenticated, licensed users can run Acrobat Standard on the server.
Configure Default PDF File Associations via Group Policy
Use Windows Group Policy to ensure Adobe Reader remains the default PDF viewer for all users on the server, even with Acrobat Standard installed.
Deploy WPS Office for Simplified Enterprise PDF Management
Juggling complex Adobe licenses, Customization Wizards, and AppLocker rules on a Terminal Server can be a massive administrative burden. WPS Office offers an integrated suite with a powerful built-in PDF reader and editor. It provides a highly compatible, lightweight, and cost-effective alternative for multi-user environments.
- 1. Download the enterprise installer: Obtain the WPS Office installer suitable for business and multi-user RDS environments from the official website.
- 2. Install on the server: Place your Terminal Server into install mode via the command line, then run the WPS Office setup.
- 3. Assign user permissions: Use standard Windows Active Directory policies to manage access to the suite without complex third-party license servers.
- 4. Set as the default handler: Use Group Policy or Windows Settings to assign WPS PDF as the default .pdf application for all remote desktop users.
Frequently Asked Questions
Can I use AppLocker to restrict Adobe Acrobat to specific server users?
Yes, you can use AppLocker or specific Group Policy restrictions to limit the Acrobat executable to a specific security group. However, doing so does not replace Adobe's requirement for you to hold proper enterprise Named-User or concurrent licensing.
Why shouldn't I use a retail license of Adobe Acrobat on a shared server?
Adobe's End User License Agreement (EULA) strictly prohibits installing standard retail versions on a centralized server for remote access. You must use an Enterprise Term License Agreement (ETLA) or Volume License to remain legally compliant.
How do I force Adobe Reader to be the default instead of Acrobat Standard?
The most reliable method in an RDSH environment is to configure an XML default file association that prioritizes Adobe Reader, and deploy it via Group Policy under Computer Configuration > Administrative Templates > Windows Components > File Explorer.
Will 2011 Adobe deployment instructions work on modern Windows Servers?
Most likely not. Adobe has drastically changed its licensing models (shifting from serial numbers to Named User Licensing) and deployment tools. Always consult the current Adobe Enterprise Administration Guide for modern Windows Server compatibility.
