Citrix License Server Unable To Stop Vendor
When using XenDesktop 7.0 with a hosted shared desktop or app publishing scenario you will have to install a vda-agent onto the Windows Server to be able to publish apps or shared desktops.
During the install there is no check for existence of a RDS licensing server. In theory you can use the 120 day evaluation period to test with. But what when you’re done testing and want to make it permanent by adding RDS licensing?
Server hosts. XenApp 6.5 - Event Log Messages 1. EventID EventType EventSource EventLocation Description with Parameters 0 Warning CitrixHealthMon Application Recovery action was unable to stop service.
Using Windows Server 2008 R2 or earlier is pretty straightforward. Because the Windows Server 2008 R2 RDS licensing in my case already existed, even with older Windows Terminal services licensing, there was no need for a evaluation period.
- Citrix Licensing Subscribe to RSS notifications of new downloads. Version 11.15.0.0. Sign In to access restricted downloads. License Server. Version 11.14.0.1. Sign In to access restricted downloads. License Server. We are sorry! The item you are trying to access is restricted and requires additional permissions! If you think you should have.
- 2.At the license server, restart the Citrix Licensing service. 3.At the Citrix product server, point to a fictional license server and then point the product back to the actual license server. (See your product’s administrator’s guide for information about changing these settings.) 4.If the problem persists, restart the product server.
Windows Server 2012 RDS is another story, this gives some extra headaches. Because we’re using Citrix as a connection broker we don’t have a complete Microsoft Remote Desktop Services Deployment in place.
First we need to add a RD licensing server role because this is the first Windows Server 2012 RDSH in the environment. So far so good.
Second we need to activate the license server, this succeeded too.
Next we need to assign the license server to the RDSH server and make sure the right licensing mode is used (we use PerUser licensing).
Change Citrix License Server
This is where the problems arise. Microsoft assumes you use a complete Remote Desktop Services deployment including a RD broker. Therefor you cannot set the properties of a RDSH via the GUI (with Server Manager) or through command line (with PowerShell) as shown in the screenshots below.
How to solve it?
To set the correct license server and the mode it is operating in, we need to use a (local) group policy or change it directly in the registry.
The group policy setting the Remote Desktop licensing mode is located in:
Computer ConfigurationPoliciesAdministrative TemplatesWindows ComponentsRemote Desktop ServicesRemote Desktop Session HostLicensing
Install Citrix License Server
This can be configured by using either the Local Group Policy editor or the Group Policy Management console.
The other way is to manually change it on the RDSH using the following registry keys:
HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindows NTTerminal Services
| LicenseServers | <license server> |
| LicensingMode | 2 for PerDevice; 4 for PerUser |
After changing these settings, reboot your RD Session Host and you will see RD licensing is now in place and working!