Windows Server 2008 R2 Terminal Services Licensing Crack
Applicable Products
- XenDesktop 7.8
- XenDesktop 7.7
- XenDesktop 7.6 Feature Pack 3
- XenApp 6.5
- XenDesktop 7.1
- XenDesktop 7
- XenDesktop 7.5
- XenDesktop 7.6
Instructions 1 Restart the Windows Server 2008 computer, and log in to a Windows Server 2008 computer Administrator account. Click “Start,” and select the “Search” box.
Symptoms or Error
Solution
First the location of the RDS licence server is located here:
HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindows NTTerminal Services
HKEY_LOCAL_MACHINESOFTWAREWow6432NodePoliciesMicrosoftWindows NTTerminal Services
In 2008 R2 you can verify the RDS licence information by opening the Remote Desktop Session Host Configuration. Here you can validate the server is pointing to a RDS server and there are no issues with the RDS licensing.
In 2012 R2 the Remote Desktop Session Host Configuration does not exist but you can open “RD Licence Diagnoser” feature once installed by running the following:
%windir%system32lsdiag.msc
If it is not installed open the Server Manager which can be accessed in opening control panel and click 'Turn Windows feature on or off', 'Add role or feature', Under features 'Remote Server Administration Tools', 'Role Administration Tools', 'Remote Desktop Services Tools', 'Remote Desktop Licensing Diagnoser':
Also know Windows will require a different license file for 2012 R2 than it will for 2008 R2. While on the RD licence server run the command %windir%system32licmgr.exe to open the RD Licensing Manage.
Only having one licence type but two different version of the Operating system can cause users to say the applications or desktops will launch on a 2008 R2 VDA but not a 2012 R2 VDA or vice versa.
Most of the time if a customer opens an application with an issue with RDS licensing they will just see the Citrix Receiver launch window instantly close with no error or explanation other than an event in the System event log 1130 which can make users point to Citrix.
Citrix does not troubleshoot issues with RDS licensing, the customer will have to go to Microsoft troubleshooting however these tools should help you rule out Citrix the root cause.
Know logging into the console does not consume an RDS licence so logging on this way will bypass RDS issues. God mode windows xp.
Finally know that whether in your environment or on a customers, they should have a 120 day grace period for using RDS, however it could be extended by deleting the REG_BINARY in
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal ServerRCMGracePeriod however this is NOT a permanent solution nor recommended.
-->Terminal Services has been renamed Remote Desktop Services.
In Windows Server 2008 R2, all Remote Desktop Services role services have been renamed. The following table lists both the former name and the new name of each Remote Desktop Services role service.
Previous name | Name in Windows Server 2008 R2 |
---|---|
Terminal Services | Remote Desktop Services |
Terminal Server | Remote Desktop Session Host (RD Session Host) |
Terminal Services Licensing (TS Licensing) | Remote Desktop Licensing (RD Licensing) |
Terminal Services Gateway (TS Gateway) | Remote Desktop Gateway (RD Gateway) |
Terminal Services Session Broker (TS Session Broker) | Remote Desktop Connection Broker (RD Connection Broker) |
Terminal Services Web Access (TS Web Access) | Remote Desktop Web Access (RD Web Access) |
Terminal Services Virtualization | Remote Desktop Virtualization Host (RD Virtualization Host) |
Also, please note that a server that has the RD Session Host role service installed is now called a RD Session Host server, instead of a terminal server.