Hi all
Currently running in Per User licensing mode. The RDS platform is within the license grace period, however via RDS Manager added license server and activated by clearing house. No valid licenses added as yet, so running in temp license allocation mode. Confirmed RDSH is configured to use RDSL by using RD Licensing Diagnoser.
With reference to: https://technet.microsoft.com/en-gb/library/cc725933.aspx and considering Per User mode.
My understanding is that the RDSH MUST be able to contact an RDSL, but only when the RDSH deems applicable - so perhaps this transaction is instigated upon a new client not seen on the RDSH before? However during testing new clients don't appear to trigger the RDSH to RDSL connection and can still run published apps .
- RDSL service running and RDS Manager configured for Per User mode. Using RD Licensing Manager I can see 2012 R2 licenses issued for each new user - all ok so far.
- I disable RSDL licensing service - previously connected users can still connect and I assume RSDH validates license and doesn't need to contact RDSL at this point - not sure when in the future it will though?
Are there reg keys defining this cached information, can they be deleted forcing the RDSH to contact the RDSL again as if it's a new user not seen before?
Here's the weird part - new users never seen on the RDSH before can still open applications! No licenses appear on the License Manager (obviously as the service is stopped).
But why can new users connect successfully?
I'm wondering if its due to the Grace period? - A permanent RDS CAL is issued by a license server to a client connecting to the RD Session Host server.
- The number of days in the grace period is exceeded
You must configure RD Licensing correctly in order for your RD Session Host server to accept connections from clients. To allow ample time for you to deploy a license server, Remote Desktop Services provides a licensing grace period for the RD Session Host server during which no license server is required. During this grace period, an RD Session Host server can accept connections from unlicensed clients without contacting a license server. The grace period begins the first time the RD Session Host server accepts a client connection. The grace period ends after whichever of the following occurs first:
Re the bullets above, I'm wondering that as I'm currently using temp licenses that the RDSH reverts to the grace period functionality when it cannot communicate with the RDSL, hence my users are still able to connect when teh RDSL service is stopped?
- If I delete c:\windows\laserver\*.* on the RDSL to clear the previously issued license list, I note the RDSH servers do not request licenses for users previously connected.
How can I delete the RDSH license cache? - I note several
articles pointing to issues when the grace period expires even though a RDSL is configured, this CONCERNS me significantly as we shall be rolling out the LIVE platform soon. The previous PoC remained in grace period throughout its testing life so
I'm unsure how this will pan out.
In order to resolve articles point to simply deleting the reg key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod, however doesn't this simply reset the grace period?
The RDSH connects to the RDSL and obtains a new temp license upon every new user, but when the RDSL service is disabled why do I see new users still connecting?
HELP!
And thanks
Lea