Remote Desktop Services Client Access License (RDS CAL) Availability
Applies To: Windows Server 2008 R2
When a client—either a user or a device—connects to a Remote Destkop Session Host server, the RD Session Host server determines if a Remote Desktop Services client access license (RDS CAL) is needed. The RD Session Host server then requests an RDS CAL from a Remote Desktop license server on behalf of the client attempting to connect to the RD Session Host server. If an appropriate RDS CAL is available from a license server, the RDS CAL is issued to the client, and the client will be able to connect to the RD Session Host server.
RDS CALs are installed onto a license server by using the Remote Desktop Licensing Manager tool.
Events
| Event ID | Source | Message |
|---|---|---|
Microsoft-Windows-TerminalServices-Licensing |
This Remote Desktop license server is too busy to notify other Remote Desktop license servers about the number of Remote Desktop Services client access licenses (RDS CALs) that it has in its database. It will attempt to notify other Remote Desktop license servers later. If the problem persists, free up available memory if memory is low on the Remote Desktop license server, and identify and resolve any issues with network connectivity, specifically with firewall configuration. Problems with remote procedure calls (RPCs) might also cause this issue. | |
Microsoft-Windows-TerminalServices-Licensing |
This Remote Desktop license server cannot communicate with other Remote Desktop license servers about the number of Remote Desktop Services client access licenses (RDS CALs) that it has in its database. The license server will attempt to communicate with other Remote Desktop license servers later. | |
Microsoft-Windows-TerminalServices-Licensing |
All requests for Remote Desktop Services client access licenses (RDS CALs) will be denied due to an initialization error in policy module "%1!s!". | |
Microsoft-Windows-TerminalServices-Licensing |
The Remote Desktop license server cannot detect locally installed Remote Desktop Services client access licenses (RDS CALs) or communicate with other Remote Desktop license servers. To resolve this issue, identify and resolve any network connectivity issues. If the problem persists, restore the licensing database from backups or contact the Microsoft Clearinghouse. The following error occurred: %1!s! |
|
Microsoft-Windows-TerminalServices-Licensing |
This Remote Desktop license server could not notify other Remote Desktop license servers that new Remote Desktop Services client access licenses (RDS CALs) have been installed and added to its licensing database. If the problem persists, free up available memory if memory is low on the Remote Desktop license server, and identify and resolve any network connectivity issues, specifically with firewall configuration. Problems with remote procedure calls (RPCs) might also cause this issue. | |
Microsoft-Windows-TerminalServices-Licensing |
The Remote Desktop license server could not return an expired Remote Desktop Services client access license (RDS CAL) to the available pool of RDS CALs because of following error: %1!s!. | |
Microsoft-Windows-TerminalServices-Licensing |
The Remote Desktop license server "%1" does not have a sufficient number of permanent Remote Desktop Services client access licenses (RDS CALs) for product "%3". Only %2 permanent RDS CALs remain. To resolve this problem, purchase and install additional RDS CALs as needed for this license server. | |
Microsoft-Windows-TerminalServices-Licensing |
The Remote Desktop license server "%1" does not have any remaining permanent Remote Desktop Services client access licenses (RDS CALs) of the type "%2". As a result, the Remote Desktop license server cannot issue RDS CALs of the type "%2" to the Remote Desktop Session Host server "%3". To resolve this problem, verify that the Remote Desktop licensing mode configured on the RD Session Host server matches the type of RDS CALs installed on the Remote Desktop license server. If required, purchase and install additional RDS CALs as needed for this Remote Desktop license server. | |
Microsoft-Windows-TerminalServices-Licensing |
The Remote Desktop license server "%1" does not have any Remote Desktop Services client access licenses (RDS CALs) installed and registered with the Microsoft Clearinghouse for product "%2". Therefore, the Remote Desktop license server cannot issue RDS CALs of the type "%2" to the Remote Desktop Session Host server "%3". To resolve this problem, install additional RDS CALs as required. | |
Microsoft-Windows-TerminalServices-Licensing |
All available "%1!s!" Remote Desktop Services client access licenses (RDS CALs) for product "%2!s!" on Remote Desktop license server "%3!s!" have been removed. Use RD Licensing Manager to re-register the RDS CALs. | |
Microsoft-Windows-TerminalServices-Licensing |
The Remote Desktop license server cannot issue a Remote Desktop Services client access license (RDS CAL) to the client because of following error: %1!s! | |
Microsoft-Windows-TerminalServices-Licensing |
The Remote Desktop license server cannot communicate with another Remote Desktop license server because of the following error: %1!s!. | |
Microsoft-Windows-TerminalServices-Licensing |
Key-pack decryption failed with Win32 error code %1!s!. Use the Telephone method to install the Remote Desktop Services client access licenses (RDS CALs). | |
Microsoft-Windows-TerminalServices-Licensing |
The certificate chain verification failed with Win32 error code %1!s!. Use the Telephone method to install the Remote Desktop Services client access licenses (RDS CALs). | |
Microsoft-Windows-TerminalServices-Licensing |
The key-pack hash validation failed with error %1!s!. Please use Telephone method for CAL installation. | |
Microsoft-Windows-TerminalServices-Licensing |
One Remote Desktop Services client access license (RDS CAL) of product "%1" issued to computer "%2" has been successfully revoked. | |
Microsoft-Windows-TerminalServices-Licensing |
The Remote Desktop Services client access license (RDS CAL) issued to "%1" could not be revoked because the revocation limit for the product "%2" is reached. %3 of the installed %4 RDS CALs are already revoked. The RDS CAL revocation of this product type will be allowed after %5. | |
Microsoft-Windows-TerminalServices-Licensing |
The "%1!s!" %2!s! belonging to computer "%3!s!" has been upgraded to "%4!s!" %5!s!. | |
Microsoft-Windows-TerminalServices-Licensing |
The Remote Desktop Services client access licenses have been successfully installed onto the Remote Desktop license server. | |
Microsoft-Windows-TerminalServices-Licensing |
The Remote Desktop Services client access licenses (RDS CALs) have been successfully removed from the source Remote Desktop license server %1!s!. | |
Microsoft-Windows-TerminalServices-Licensing |
The Remote Desktop Services client access licenses (RDS CALs) on the source Remote Desktop license server %1!s! could not be removed during the migration. Use WMI to manually delete the RDS CALs from %1!s! or ensure that %1!s! is no longer used as a license server with the same RDS CALs that were migrated. | |
Microsoft-Windows-TerminalServices-Licensing |
The migration of Remote Desktop Services client access licenses (RDS CALs) has completed. Because the source Remote Desktop license server %1!s! is running an operating system that does not support the deletion of RDS CALs, ensure that %1!s! is no longer used as a license server with the same RDS CALs that were migrated. | |
Microsoft-Windows-TerminalServices-Licensing |
The migration of Remote Desktop Services client access licenses (RDS CALs) has completed. Because the source Remote Desktop license server %1!s! was not available on the network during the migration, you will either have to delete the RDS CALs from %1!s! by using WMI (if %1!s! is running at least Windows Server 2008 R2) or you need to ensure that %1!s! is no longer used as a license server with the same RDS CALs that were migrated. | |
Microsoft-Windows-TerminalServices-Licensing |
The migration of Remote Desktop Services client access licenses (RDS CALs) has completed. During the migration, the source Remote Desktop license server was specified as no longer functioning. Ensure that it is no longer used as a license server with the same RDS CALs that were migrated. |