Terminal Server License Key
To give you a more consistent licensing experience across multi-cloud environments, we transitioned from processor-based licensing to core-based licensing for Windows Server 2019 Datacenter and Standard editions. For specific pricing, contact your Microsoft reseller. Hi Derek, You have 2 options. 1 - Volume License Office 2016 ProPlus (you require a license for each user of the terminal server who could use the software, even if they don't intend to use it it must still be licensed if they could get access to it). If the server that has Terminal Server enabled is member of a Windows Server-based domain, there are three methods that you can use to discover a Terminal Services Licensing server. After a Terminal Services Licensing server is located, the discovery process stops. Method 1: LicenseServers Registry Key Query.
- Terminal Server Licensing Registry
- Recover Terminal Server License Key
- 2008 R2 Terminal Server License Key
- Terminal Server License Reg Key
- Windows Terminal Server License Key
Add 'Terminal Server' & Terminal Server Licensing' Default licensing mode is per device as we will need to for actiivation 2. SERVER Start Terminal Server Licensing (Start Control Panel Administrative Tools Services Terminal Server Licensing) if it is not started 3. SERVER Go to the Terminal Server Licensing, Right-click on Terminal Server. I need my license key for terminal services but cannot access the eopen with my old email address from Jan. 2003 which is when I received my acceptance. I have my a licence number, authorization number but no key.
This document describes deployment via Remote Desktop Services, including RemoteApp and Terminal Server, (formerly Windows Terminal Server).
System requirements¶
Deploy on one of the following:
Windows Server 2019
Windows Server 2016, Windows 10
Windows Server 2012 R2 standard
Windows Server 2008 R2
User profile data in the
<user>/appdata/Roaming
folder and the HKCU hive should roam with user so that they are synced on the server instance where the user logs in. Administrators can use any available technique for profile redirection such as folder redirection or other profile management tools.Trial deployments are unsupported.
Tested environments¶
Adobe validates all Acrobat DC products in a Windows Terminal Server environment.
The environments used for validation were set up in the following ways:
Acrobat DC:
Windows Server 2016, Windows 10
Windows Server 2008 R2 Enterprise Edition 64bit, Windows Server 2012 64bit & Windows Server 2012 R2 64bit
Client operating systems: Windows 7 (32-bit and 64-bit), Windows 8 (32 and 64-bit) and Windows 8.1 (32 and 64-bit)
RemoteApp and Remote Desktop Web Access
Tuning for virtual envs¶
Yodot recovery software mac crack. Tune the installer prior to imaging and deployment.
Tuning helps mitigate performance issues, simplifies the end user experience, and allows you to disable features and behaviors that should not be accessible to end users in an IT-managed environment.
Honestech tvr 3.0 serial key. Install the latest product.
Disable the updater.
Accept the EULA on behalf of all users by setting the appropriate registry key.
Use SUPPRESSLANGSELECTION on the command line at install time to disable user’s ability to change the language.
If the product language should be different than the OS languages, set the language.
Supress registration (there are multiple ways: Wizard, cmd line property, PRTK tool).
Disable push notifications: Set bToggleNotifications to 0.
Disable the Help > Repair Acrobat Installation menu by setting:
32 bit machines:
[HKLMSOFTWAREAdobe(productname)(version)Installer]'Disable_Repair'
64 bit machines:
[HKLMSOFTWAREWow6432NodeAdobe(productname)(version)Installer]'Disable_Repair'
Scrolling performance
If scrolling performance is poor in graphic intensive documents, try the following:
Terminal Server Licensing Registry
Go to Edit > Preferences > Rendering.
Uncheck Smooth line art and Smooth images. Alternatively, you can set these preferences during pre-deployment configuration:
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
ApplicationDataAdobeAcrobatDistiller<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:ProgramFiles(x86)AdobeAcrobatReaderDC
.
Other settings
There are over 500 other registry preferences documented in the Preference Reference . Use the Wizard or manual/scripted methods to customer the product.
Licensing¶
Only licensed users should have access to the virtual Acrobat instance. For more information, refer to the Software license terms.
RDS deployments support the following licensing options:
Serial numbers
Named user licensing
Feature restricted licensing
For details, see http://www.virtualizationadmin.com/articles-tutorials/citrix-articles/installing-and-configuring-citrix-xenapp-xendesktop-76-part4.html
Named user licensing¶
Named user licensing (NUL) is the preferred activation method.
DC products support NUL and user management via the Admin Console. The Console supports managing single user and group entitlements for all Adobe products as well as Single Sign-On. It also provides tools for managing software, users, and devices and support multiple ID types. With NUL, end users simply “activate” Acrobat by logging in to any VM or machine. License-related data is saved in the <user>/AppData/Roaming/Adobe/
folder which is synced to the VM on login.
Note
Trial installs and the Classic track do not support named user licensing.
Image-based deployment¶
Set up profile redirection. User profile data in
<user>/AppData/Roaming/Adobe/
as well as the HKCU hive must sync to the VM instance on which the user logs in. Admins should ensure that such data is saved on user logout or disconnect. Some systems provide VM tools; for example, Citrix (Citrix Profile Management) and VMware Horizon (View Personal Management). At a minimum, sync the following:
Folders
C:Users<User>AppDataRoamingAdobeOOBE
C:Users<User>AppDataRoamingAdobeSLData
C:Users<User>AppDataRoamingAdobeAdobe User Info
HKCUSoftware registries:
Adobe
MicrosoftInternet ExplorerToolbarWebBrowser{47833539-D0C5-4125-9FA8-0819E2EAAC93}
MicrosoftInternet ExplorerMenuExt
Wow6432NodeGoogleChromeExtensionsefaidnbmnnnibpcajpcglclefindmkaj
Wow6432NodeGoogleChromeNativeMessagingHostscom.adobe.acrobat.chrome_webcapture
Log in to master image.
(Optional) Customize the installer with the Customization Wizard.
Install Acrobat on the master image by calling the default exe or the one you modified with the Wizard. Use the following command:
Verify the following registry keys are present and the string
(REG_SZ)
values are 1 on the master image. If not, create the key and set the value as 1.
If you are using a Federated ID or connectors (like Dropbox), enable third party cookies:
Choose Internet Explorer > Settings > Internet Options > Privacy > Advanced.
For First-party cookies, choose Accept.
For Third-party cookies, choose Accept.
Shut down the master image.
Take a snapshot of the master image.
Update all VM desktops with the new snapshot.
Note
Unlike serialized deployments, do not launch Acrobat on the master image.
Serialized deployments¶
Note
On November 30, 2019, some customers may see their serial numbers expire. To avoid interruption and to access the latest versions of the apps, migrate to named user licensing or update your serial number.
To image a machine with Acrobat, first generate a prov.xml file on an online machine and then create a permanent offline exception that is not machine specific. Note the following:
Supported for volume licenses only.
Acrobat need not be installed.
The target machine must be online.
Steps:
Download the latest Adobe Provisioning Toolkit Enterprise Edition.
Open an elevated prompt (run as administrator).
Generate a prov.xml file on any machine connected to the internet using the following APTEE tool command line with the following options:
serial
: The serial numberregsuppress=ss
: Optional (but recommended); suppresses registrationeulasuppress
: Optional; suppresses the EULA promptlocales
: Optional; specify from the limited list of locales in the formal xx_XX or ALLprovfile
: Optional; path of the folder where prov.xml is created. If this parameter is not specified, prov.xml is created in the folder in which APTEE resides.LEID
:DC Continuous Track: V7{}AcrobatCont-12-Win-GM
Classic Track 2020: V7{}AcrobatESR-20-Win-GM
Classic Track 2017: V7{}AcrobatESR-17-Win-GM
Classic Track 2015: V7{}AcrobatESR-12-Win-GM
Install Acrobat on the master image.
On the master image, copy the prov.xml file created above.
Serialize and activate Acrobat using the following APTEE tool command line:
For Acrobat Classic 2020 deployments, create and set
IsAMTEnforced
to 1.
Launch Acrobat once for about a minute and close.
Note
Granting an offline exception using the Customization Wizard for an imaged OS deployment method is not supported. Use the PRTK tool.
Feature Restricted Licensing¶
Acrobat supports Feature Restricted Connected and Offline Licensing (FRL) in most virtual environments, including Citrix, VMWare, RDS/WTS, and App-V. Use this package type for end-users who:
Cannot adopt named user licensing since they are not allowed to use online services.
The users are periodically connected to the Internet (FRL connected).
Restricted environment with no internet (FRL offline).
Support is limited to:
FRL offline
These high level steps do not supersede the details on the FRL page or the deployment steps below, but in general, use the Admin Console to create an FRL-enabled Acrobat package:
Create license-only package from the Admin Console and deploy Acrobat from a standalone installer, OR
Create an FRL package that embeds Acrobat.
Then, deploy as usual:
(Optional) Customize the installer with the Customization Wizard.
Log in to the master image.
Install the package on the master image. If you have created a license-only package, first run the Acrobat installer followed by the license-only package.
Shut down the master image.
Take a snapshot of the master image, and update all VM desktops.
Troubleshooting steps:
Verify that FRL package is applied properly on the master image.
Validate that ASNP, Certificates and Operating Configuration folders are present at
C:ProgramDataAdobe<folder>
on the master image.If present, remove
HKLMSOFTWAREWOW6432NodeAdobeAdobeAcrobatDCActivationIsAMTEnforced
.
Shared Device Licensing¶
Acrobat does not support Shared Device Licensing (SDL) in virtual environments.
However, SDL may prove useful to you in other business contexts. SDL is a licensing model to deploy and manage Adobe applications in labs and shared device setups, where multiple users use the devices and applications. The software license is assigned to a device or computer instead of an individual. SDL is ideal for computers in labs or classrooms, but is not designed for use on machines used by dedicated users. For dedicated users, we recommend you deploy named-user licenses. For more detail, see https://helpx.adobe.com/enterprise/using/sdl-deployment-guide.html
Terminal Server deployment¶
You must install applications by using Add or Remove Programs on the RDS server.
To install Acrobat products:
Choose Start > Settings > Control Panel > Add or Remove Programs.
Choose Install.
Auto clicker download mac free. Choose Next > Browse to locate the installer.
Choose Finish.
Note
Some users have experienced issues where Anti Virus software conflicts with Acrobat’s licensing components (e.g. PDApp.exe). If you are experiencing problems, try disabling the software temporarily.
Known issues common to virtual installs¶
Push notifications to specific users are unsupported.
If users sign in on both a virtual environment and a physical machine, then they may be randomly signed out from a physical machine. This is because users can activate Acrobat on multiple virtual machines while only two activations are allowed per user. The current implementation provides an over activation workflow for these environments which does not force users to see or interact with any dialogs.
Volume licenses are deleted when multiple users launch the product simultaneously before it is activated.
In the Help menu, signed-in users are not shown as signed-in on subsequent sessions.
Users may appear as signed-in on the Help menu even if they are signed out from the Creative Cloud Desktop application or signed out of the current session.
Signing in with IDs having no subscriptions may result in random failures.
Why do I see an error that my license is expired or not activated?
Users must launch Acrobat prior to using “Print to PDF”, the Microsoft Office Acrobat plugin, or any other PDF Maker features.
RDS-specific issues¶
Signing in with an Adobe ID on both RDS environments and non-RDS environments may result in random sign outs from non-RDS environments.
Tech Level: 1
When using Citrix or RDP, a user might experience the following message upon connection:
Recover Terminal Server License Key
'The remote session was disconnected because there are no Terminal Service License Servers available to provide a license. Please contact your server administrator.'
This issue can be resolved typically by removing a registry key and reconnecting to the RDP or Citrix server.
3 Steps total
Step 1: Open the registry editor
While logged in as an administrator, click 'start'> 'run'
In the 'open' field, type 'regedit.exe' and click 'ok.'
Step 2: Locate and delete the MSLicensing registry key
Navigate to HKLMSoftwareMicrosoft key. Export this key for backup purposes.
Find the 'MSLicensing' subkey and delete it.
Step 3: Retry your connection to Citrix/RDP
2008 R2 Terminal Server License Key
Once the key has been deleted, you can try to open the Citrix/RDP session in question again. Note that you do not have to close Internet Explorer (if accessing via this method).
If the problem persists, check the remote end to ensure there is a valid terminal services licensing server online and available.
These steps can also be performed remotely, pending you have admin rights, using a remote registry connection via regedit.
References
- Removing Terminal Server licenses from an RDP client
Terminal Server License Reg Key
1 Comment
Windows Terminal Server License Key
- PimientoAlbert6697 Sep 28, 2016 at 04:12pm
I ran into this issue because I installed the RDS role for testing on the server I was attempting to connect to and after the allotted period of time (60 or 90 days) I had to have RDS licensing so it blocked any incoming connections due to licensing. I simply removed the role, rebooted and was able to log in via RDP.