How to Fix Acrobat Pro 2017 Sign-In Prompt on Cloned Virtual Machines
Question details
Standard users are unexpectedly prompted to sign into Acrobat Pro 2017 on cloned vSphere virtual machines after volume serialization.
- Product
- Adobe Acrobat Pro 2017
- Device & OS
- not provided
- Scenario
- Using volume serialization on a master image to deploy PDF software across multiple cloned vSphere virtual machines.
- Observed behavior
- Standard users receive a sign-in prompt upon opening the software, while local administrators do not face this activation loop.
Ensure you have administrative access to the master vSphere virtual machine image and have the Adobe Provisioning Toolkit Enterprise Edition (PRTK) available for configuration.
Verify Provisioning Commands and Registry Permissions on the Master Image
Re-applying the volume serialization commands and ensuring standard users have the required registry and file-system permissions can resolve the continuous sign-in prompt.
This issue typically occurs because the volume licensing entitlement is not properly written to standard user profiles, or standard users lack read/write permissions to specific licensing directories in the Windows Registry and file system.
On the master image, open Command Prompt as an administrator and execute the Adobe Provisioning Toolkit (PRTK) volume serialization command to apply the license globally across all profiles.
Use the Adobe Customization Wizard to configure the installation package. Under the 'Personalization Options' menu, ensure you check 'Suppress display of End User License Agreement (EULA)' and 'Disable registration'.
Open the Registry Editor (regedit) and navigate to the Adobe software keys under HKEY_LOCAL_MACHINE and HKEY_CURRENT_USER. Right-click the keys, select 'Permissions', and ensure that the 'Users' group has 'Read' access.
Navigate to the Adobe PCD and SLCache folders (usually located in the ProgramData directory). Right-click the folders, open 'Properties', go to the 'Security' tab, and verify that standard users have the correct permissions to read the license cache files.
Deploy PDF Software Easily with WPS Office
If enterprise deployment and volume licensing for Acrobat Pro are causing persistent sign-in loops, consider switching to WPS Office. It provides a lightweight, highly compatible alternative with a built-in PDF editor, making mass deployment across virtual machines seamless without complex licensing hurdles.
Frequently Asked Questions
Why does Acrobat Pro 2017 only prompt standard users for sign-in?
Local administrators automatically have read/write access to the machine-level licensing directories and registry keys (like the Adobe PCD folder). Standard users may lack these permissions, causing the software to fail to read the volume license and prompt for a sign-in.
Can I fix the sign-in loop without recreating the master VM image?
Yes, you can deploy a startup script via Group Policy (GPO) that runs the Adobe PRTK serialization command with elevated privileges, which re-applies the license for standard users on the existing clones.
What Adobe tool is recommended for applying volume serials on VMs?
The Adobe Provisioning Toolkit Enterprise Edition (PRTK) is the standard command-line tool used to serialize Adobe products across enterprise environments and cloned virtual machines.
Does WPS Office support volume deployment on virtual machines?
Yes, WPS Office offers enterprise deployment tools that allow IT administrators to silently install and activate the software across multiple virtual machines without triggering user-level activation prompts.
