Remote licensing server

To complete the license installation process, you need the license server ID that is displayed in the Remote Desktop Licensing Manager tool. Additionally, you need to provide one of the following items: a license code from retail product packaging, license and authorization numbers from an Open License confirmation, or a Microsoft Select, Enterprise, Campus, School, or Services Provider License enrollment or agreement number.

Please rate your experience Yes No. Any additional feedback? Module: RemoteDesktop. Forces the command to run without asking for user confirmation. Submit and view feedback for This product This page. Clients cannot connect to Remote Desktop Services, and they display messages that resemble the following:.

Look for messages like the following:. In this case, check the RD Licensing configuration. Such problems tend to be associated with user messages, such as the following:.

Because of a security error, the client could not connect to the Terminal server. After making sure that you are signed in to the network, try connecting to the server again. In this case, refresh the X Certificate registry keys. Verify the following:. For more information about this configuration, see Activate the Remote Desktop Services license server. For more information about this configuration, see Install RDS client access licenses on the Remote Desktop license server.

No trusts exist One-way or Two-way trust between these forests. In Windows , you can create a registry key to override the discovery of the licensing server.

For more information, please refer the article How to override the license server discovery process in Windows Server Terminal Services In Windows R2, automatic license server discovery is no longer supported for RD Session Host servers. It can be either Forest Trust or External Trust. You can do it through RDS host configuration snap-in or through a group policy. Need more help? Expand your skills.