Message

The Remote Desktop Licensing service has started.

Message

The Remote Desktop Licensing service has paused.

Message

The Remote Desktop Licensing service has resumed running.

Message

The Remote Desktop Licensing service has stopped.

Message

The Remote Desktop Licensing service has been activated

Message

This Remote Desktop license server is too busy to notify other Remote Desktop license servers about the number of licenses 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.

Message

This Remote Desktop license server cannot communicate with other Remote Desktop license servers about the number of licenses that it has in its database. The license server will attempt to communicate with other Remote Desktop license servers later.

Fields

Message

The RD Licensing database file is not valid. This file has been renamed to "%1", and the license server will start up with an empty database file. To resolve this issue, ensure that the required groups are granted the correct permissions to the LServer directory, and then reinstall the licenses. If the problem persists, rebuild the RD Licensing database and call the Microsoft Clearinghouse. When you call the Clearinghouse, ensure that your License Purchase Agreement information is readily available.

Fields

Fields

Message

All requests for licenses will be denied due to an initialization error in policy module "%1".

Fields

Fields

Message

The default policy module for RD Licensing (Tls236.dll) will be used for all license requests to the policy module "%1".

Fields

Fields

Message

The Remote Desktop license server cannot detect locally installed licenses 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

Fields

Message

This Remote Desktop license server could not notify other Remote Desktop license servers that new licenses 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.

Fields

Message

The Remote Desktop license server could not return an expired license to the available pool of licenses because of following error: %1.

Fields

Fields

Message

One or more of the RD Licensing certificates on the Remote Desktop license server "%1" are corrupted. Therefore, the Remote Desktop license server will only issue temporary licenses until it is reactivated.

Fields

Fields

Message

The Remote Desktop license server "%1" has not been activated and therefore will only issue temporary licenses. To issue permanent licenses, the Remote Desktop license server must be activated.

Fields

Fields

Message

One or more RD Licensing certificates on the Remote Desktop license server "%1" are corrupted. The Remote Desktop license server is switching to a backup certificate.

Fields

Message

The Remote Desktop license server "%1" does not have a sufficient number of permanent licenses for product "%3". Only %2 permanent licenses remain. To resolve this problem, purchase and install additional licenses as needed for this license server.

Fields

Fields

Message

The Remote Desktop license server "%1" does not have any remaining permanent licenses of the type "%2". As a result, the Remote Desktop license server cannot issue licenses of the type "%2" to the Remote Desktop Session Host or Remote Desktop Virtualization Host server "%3". To resolve this problem, verify that the Remote Desktop licensing mode configured on the RDSH or RDVH server matches the type of licenses installed on the Remote Desktop license server. If required, purchase and install additional licenses as needed for this Remote Desktop license server.

Fields

Fields

Message

The Remote Desktop license server "%1" does not have any licenses installed and registered with the Microsoft Clearinghouse for product "%2". Therefore, the Remote Desktop license server cannot issue licenses of the type "%2" to the Remote Desktop Session Host or Remote Desktop Virtualization Host server "%3". To resolve this problem, install additional licenses as required.

Fields

Message

The RD Licensing database is not consistent. All licenses will be removed. To resolve this issue, rebuild the RD Licensing database and call the Microsoft Clearinghouse. When you call the Clearinghouse, ensure that your License Purchase Agreement information is readily available.

Message

The RD Licensing database does not belong to this Remote Desktop license server. The Remote Desktop license server will update the database table to take ownership of the database and all licenses will be removed.

Fields

Message

All available "%1" licenses for product "%2" on Remote Desktop license server "%3" have been removed. Use RD Licensing Manager to re-register the licenses.

Fields

Message

The Remote Desktop Licensing service is unable to connect to the Service Control Manager.

Message

The Remote Desktop Licensing service is unable to report status to the Service Control Manager.

Message

The Remote Desktop Licensing service could not create the service initialization thread.

Message

The Remote Desktop Licensing service could not start due to a lack of system resources.

Fields

Message

The Remote Desktop Licensing service cannot start. The following error occurred: %1

To resolve this issue, ensure that required groups are granted the correct permissions to the TermServLicensing registry key and that the value of the DBPath registry key matches the location of the LServer directory. If the problem persists, shut down and then restart the Remote Desktop license server.

Fields

Fields

Message

The Remote Desktop license server cannot issue a license to the client because of following error: %1

Fields

Fields

Message

New public/private keys could not be generated because of following error: %1.

Fields

Fields

Message

A certificate could not be installed for this server because of following error: %1.

Fields

Fields

Message

The policy module could not be initialized because of the following error: %1.

Fields

Fields

Message

An error occurred in policy module "%1".

Fields

Fields

Message

The following general database error has occurred: "%1"

Fields

Message

The Remote Desktop license server cannot communicate with another Remote Desktop license server because of the following error: %1.

Fields

Fields

Message

One or more RD Licensing certificates has expired. Please re-register.

Fields

Fields

Message

The RD Licensing database is corrupt. RD Licensing could not rename the RD Licensing database file "%1" to create a backup. Rename the file manually and restart the Remote Desktop Licensing service. To reinstall the licenses, you will need to call the Microsoft Clearinghouse. When you call the Clearinghouse, ensure that your License Purchase Agreement information is readily available.

Fields

Message

The Remote Desktop Licensing service is starting up with a restored database file.

Fields

Message

The restored RD Licensing database file "%1" cannot be moved to the database directory. The Remote Desktop license server will use an empty database file. Ensure that the required groups are granted the correct permissions to the LServer directory. Rebuild the RD Licensing database and call the Microsoft Clearinghouse. When you call the Clearinghouse, ensure that your License Purchase Agreement information is readily available.

Fields

Message

A backup copy of the RD Licensing database cannot be created and the restored database file will be ignored. The Remote Desktop license server will start up with the existing database file.

Fields

Message

The existing RD Licensing database file has been saved as "%1". The Remote Desktop Licensing service has started with the restored database file.

Fields

Message

The existing RD Licensing database cannot be restored from its backup copy. To resolve this issue, ensure that the required groups are granted the correct permissions to the LServer directory, and then reinstall the licenses. If the problem persists, rebuild the RD Licensing database and call the Microsoft Clearinghouse. When you call the Clearinghouse, ensure that your License Purchase Agreement information is readily available.

Fields

Message

Key-pack decryption failed with Win32 error code %1. Use the Telephone method to install the licenses.

Fields

Fields

Message

The certificate chain verification failed with Win32 error code %1. Use the Telephone method to install the licenses.

Fields

Fields

Message

The key-pack hash validation failed with error %1. Please use Telephone method for license installation.

Fields

Message

The Remote Desktop license server has been published in Active Directory Domain Services.

Message

The Remote Desktop license server has been unpublished from Active Directory Domain Services.

Message

The Remote Desktop license server role has been successfully changed.

Message

The Terminal Server Computers local group cannot be created.Win32 error code: {param1}

Fields

Message

The Terminal Server Computers local group cannot be deleted.Win32 error code: {param1}

Fields

Message

The computer account for this Remote Desktop license server or Network Service account has been added to the Terminal Server License Servers group in Active Directory Domain Services.

Message

The computer account for the Remote Desktop license server has been removed from the Terminal Server License Servers group in Active Directory Domain Services.

Fields

Message

One license of product "%1" issued to computer "%2" has been successfully revoked.

Fields

Fields

Message

The license issued to "%1" could not be revoked because the revocation limit for the product "%2" is reached. %3 of the installed %4 licenses are already revoked. The license revocation of this product type will be allowed after %5.

Fields

Message

The "%1"  %2 belonging to computer "%3" has been upgraded to "%4" %5.

Fields

Message

The Remote Desktop license server has been registered as a service connection point in Active Directory Domain Services.

Message

The Remote Desktop license server has been removed as a service connection point in Active Directory Domain Services.

Message

The Remote Desktop license server could not be registered as a service connection point in Active Directory Domain Services (AD DS). Ensure that there is network connectivity between the license server and AD DS. To register the license server as a service connection point in AD DS, use Review Configuration in the RD Licensing Manager tool.

Message

The Remote Desktop license server could not be removed as a service connection point in Active Directory Domain Services.

Message

The licenses have been successfully installed onto the Remote Desktop license server.

Message

The RD Licensing database has been successfully rebuilt.

Fields

Message

The licenses have been successfully removed from the source Remote Desktop license server %1.

Fields

Fields

Message

The licenses on the source Remote Desktop license server %1 could not be removed during the migration. Use WMI to manually delete the licenses from %1 or ensure that %1 is no longer used as a license server with the same licenses that were migrated.

Fields

Fields

Message

The migration of licenses has completed. Because the source Remote Desktop license server %1 is running an operating system that does not support the deletion of licenses, ensure that %1 is no longer used as a license server with the same licenses that were migrated.

Fields

Fields

Message

The migration of licenses has completed. Because the source Remote Desktop license server %1 was not available on the network during the migration, you will either have to delete the licenses from %1 by using WMI (if %1 is running at least Windows Server 2008 R2) or you need to ensure that %1 is no longer used as a license server with the same licenses that were migrated.

Fields

Message

The migration of licenses 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 licenses that were migrated.

Fields

Message

The policy module could not be initialized because of the following error: %1.

Fields

Fields

Message

An error occurred in policy module "%1".

Fields

Message

Internal Error in server.

Message

An error occurred during the Remote Desktop license server initialization phase.

Message

The license server was unable to enumerate the existing reports.

Message

The RD Licensing database might be corrupted. To resolve this issue, ensure that the required groups are granted the correct permissions to the LServer directory. If the problem persists, rebuild the RD Licensing database and call the Microsoft Clearinghouse. When you call the Clearinghouse, ensure that your License Purchase Agreement information is readily available.

Fields

Message

CAL reporting: %1

Fields

Message

The certificate cannot be installed on the Remote Desktop license server. This issue might be due to a problem connecting to the Microsoft Clearinghouse over HTTPS. To resolve this issue, try reactivating the Remote Desktop license server. If the problem persists, identify and resolve any possible network connectivity issues.

Message

The remote procedure call (RPC) port is not listening.

Fields

Message

The Remote Desktop license server cannot update the license attributes for user "%1" in the Active Directory Domain "%2". Ensure that the computer account for the license server is a member of Terminal Server License Servers group in Active Directory domain "%2".
If the license server is installed on a domain controller, the Network Service account also needs to be a member of the Terminal Server License Servers group.
If the license server is installed on a domain controller, after you have added the appropriate accounts to the Terminal Server License Servers group, you must restart the Remote Desktop Licensing service to track or report the usage of RDS Per User CALs.
Win32 error code: %3

Fields

Fields

Message

CAL reporting: %1

Fields

Fields

Message

The Remote Desktop license server failed to query Active Directory Domain Services for user information.
Win32 error code: %1

Fields

Fields

Message

The Remote Desktop license server failed to generate the report.
Win32 error code: %1

Fields

Message

RD Licensing has experienced a general initialization failure.

Message

RD Licensing is unable to allocate the required system memory to perform the operation.

Message

A backup copy of the certificate for this Remote Desktop license server could not be created.

Message

Incompatible version or data detected.

Message

The Local Security Authority (LSA) has returned an invalid data version.

Fields

Message

A license could not be issued to "%1" because it is not a member of the RDS Endpoint Servers group.

Fields

Message

A security descriptor cannot be set. As a result, Remote Desktop Session Host or Remote Desktop Virtualization Host servers might not be able to connect to Remote Desktop license servers. Restart the Remote Desktop Licensing service.

Message

The Remote Desktop license server has successfully issued a %1 to user %2 in the domain %3.

Fields

Message

The Remote Desktop license server has successfully upgraded the %1 to a %2 for user  %3 in the domain %4.

Fields

Message

The %1 for user %2 in the domain %3 has been renewed.

Fields

Message

The %1 for computer %2 has been renewed.

Fields

Message

The Remote Desktop license server has successfully issued a %1 to computer %2.

Fields

Message

The Remote Desktop license server has issued a %1 to computer %2 while accessing %4. Please refer %3 to know about the different licenses that can be used to access the %4.

Fields

Message

The Remote Desktop license server has issued a %1 to computer %2 which is not the most appropriate CAL for this connection request. Please refer %3 for more information.

Fields

Fields

Message

Conversion of %1 failed because of following error. %2 
Win32 error code: %3

Fields

Fields

Message

%1 %2 from KeyPackID %3 have been successfully converted to %4 with KeyPackID %5.

Fields

Fields

Message

%1s have been reorganized across keypacks to maintain consistency in installed and issued license count.

Fields

Fields

Message

The Remote Desktop license server could not be published in Active Directory Domain Services during the installation of RD Licensing. The action failed with Win32 error code %1.

Fields

Message

The Remote Desktop license server was successfully published in Active Directory Domain Services during the installation of RD Licensing.

Fields

Message

The computer account for the Remote Desktop license server could not be added to the Terminal Server License Servers group in Active Directory Domain Services during the installation of RD Licensing. The action failed with Win32 error code %1.

Fields

Message

The computer account for the Remote Desktop license server was successfully added to the Terminal Server License Servers group in Active Directory Domain Services during the installation of RD Licensing.

Fields

Message

The RD Licensing database path could not be set to "%1" during the installation of RD Licensing.
Win32 error code: %2

Fields

Message

The RD Licensing database path was successfully set during the installation of RD Licensing.

Message

The Remote Desktop license server is not installed on a Domain Controller and hence would not be auto-discoverable by down-level Remote Desktop Session Host servers.

Fields

Message

An attempt to access a report with an invalid path occurred: %1

Fields

Message

Database was created by different version of License Server.

Message

Database was created by beta version of License Server.

Message

A license could not be issued to '{param1}' because it is not a member of the Terminal Server Computers group.

Fields

Message

The Remote Desktop license server cannot update the license attributes for user '{param1}' in the Active Directory Domain '{param2}'. Ensure that the computer account for the license server is a member of Terminal Server License Servers group in Active Directory domain '{param2}'.If the license server is installed on a domain controller; the Network Service account also needs to be a member of the Terminal Server License Servers group.If the license server is installed on a domain controller; after you have added the appropriate accounts to the Terminal Server License Servers group; you must restart the Remote Desktop Licensing service to track or report the usage of RDS Per User CALs.Win32 error code: {param3}

Fields

Message

CAL reporting: {param1}

Fields

Message

The Remote Desktop license server failed to query Active Directory Domain Services for user information.Win32 error code: {param1}

Fields

Message

The Remote Desktop license server failed to generate the report.Win32 error code: {param1}

Fields