To perform this procedure, you must have membership in the local Administrators group on the license server and membership in the Enterprise Admins group in AD DS, or you must have been delegated the appropriate authority. Publish the license server by using Remote Desktop Licensing Manager To perform these tasks, refer to the following sections. You can publish the license server in AD DS either by using Remote Desktop Licensing Manager or by using ADSI Edit. To resolve this issue, publish the Remote Desktop license server in Active Directory Domain Services (AD DS). Publish the license server in Active Directory Domain Services To register the license server as a service connection point in AD DS, use Review Configuration in the RD Licensing Manager tool. Ensure that there is network connectivity between the license server and AD DS. The Remote Desktop license server could not be registered as a service connection point in Active Directory Domain Services (AD DS). Microsoft-Windows-TerminalServices-Licensing To configure forest discovery scope, you must be logged on as an enterprise administrator to the forest in which the license server is a member.
If you configure forest discovery scope, RD Session Host servers, without any additional configuration, can automatically discover a license server in the same forest, because the license server is published in Active Directory Domain Services. The recommended discovery scope for a license server is forest discovery scope. If the RD Session Host server cannot discover a license server, client connections may fail. Remote Desktop license server discovery is the process by which a Remote Desktop Session Host (RD Session Host) server contacts an available license server to request Remote Desktop Services client access licenses (RDS CALs) for the clients that are connecting remotely to the RD Session Host server. Event ID 85 - Remote Desktop License Server Discovery