Hello,
I assume you're utilizing the RDS Per Device CAL, as only the Per Device CAL offers a temporary CAL.
Here's the explicit explanation about the process of RDS per device CAL:
1.when an unlicensed client connects to a Remote Desktop Session Host (configured for "per Device" licensing) for the first time, the Remote Desktop License Server issues the client a temporary RDS CAL.
After the user has logged into the session, the RDS server instructs the License Server to mark the issued temporary RDS CAL token as being validated.
2.The next time the client connects, an attempt is made to upgrade the validated temporary RDS CAL token to a full RDS CAL token. Only after a second successful logon will a full CAL actually be assigned (preventing DoS attacks).
If no license tokens are available, the temporary RDS CAL token will continue to function for 90 days.
Clients store their license under the registry key:
[HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing]
- Every time the client device connects to an RDS Host, it presents its RDS CAL to the server.
The server checks not only whether the client device has a valid license, but also the expiration date of that license. If the expiration date of the license is within 7 days of the current date, the RDS Host connects to the License Server to renew the license for another random period of 52 to 89 days.
If the CAL requires upgrading or renewal, the RDSH will communicate with the RDLS on behalf of the client. From my understanding, there is no need to manually remove the temporary CAL; it should be automatically converted. The only requirement is to ensure seamless connectivity between the RDSH and the RDLS.
CAL assignment process:
8867.rd_5f00_licensing_5f00_flowchart.png (1722×675) (microsoft.com)
Additional settings that might require your attention :Cannot connect to RDS because no RD Licensing servers are available - Windows Server | Microsoft Learn
Regards,
Karlie