While this disconnection of users happens often, it is observed that the Remote Desktop Services on the RD server also stops at the same time. This causes the failure of Remote Desktop Licensing Manager services on the server which hosts this role. One of the users who had opened a case with Microsoft had found out that the issue can be caused by the network equipment between the client connection and the server. One user has reported that turning off energy saving settings on the network cards from the client’s fixed issue, while another user had to split out the number of RDSH hosts from the connection brokers as anything more than 500 users to HA connection broker farm does not work. As said above, there could be other possible reasons as well. Here in this article, we will see few methods that might help you in fixing this issue.
Method 1: Apply Local GPO
This is one solution which is provided by Microsoft TAM. Apply a local GPO to set up a Remote Desktop Licensing mode. As it is observed that Remote Desktop Licensing Manager Service fails on the server that hosts this role, applying a local GPO setting might help. Follow below steps to apply a local GPO. Click Start -> Run -> Type gpedit.msc Browse to COMP configuration -> Admin Template -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Licensing Use the specified Remote Desktop Licensing Servers Set the Remote Desktop Licensing mode Open Command Prompt as Administrator Type gpupdate /force On the Domain Controller, add the computer account of Connection broker and licensing server to the Domain Admins Group On the Session host server, add the Computer and Network Service account to the RDS Endpoint server and RDS Management servers. Reboot the server.
Method 2: Give permissions to the “terminalServer” attribute or to the “Terminal Server License Server” attribute of the “user object” to add read/write permissions to the Terminal Server License Group
Open Active Directory User and Computers. Right-click on Domain and then click on Delegate Control. “User and Groups” dialog box will open, Click Add. Type Terminal Server License Servers and then click OK. Click Next. In the “Active Directory Object Type” dialog box, click on “Only the following objects in the folder“. Click on “User objects” in that list Click Next According to the operating system that the domain controller is running, do following For the forests that are running Windows Server 2008 or newer Schema: In the Permissions dialog box, make sure that only the “General” checkbox is selected. In the “Permissions” list, click on the “Read and Write Terminal Server license server” check box. Click Next. In the “Completing the Delegation of Control Wizard” dialog box, click Finish.
Method 3: Turn off energy saving on the network cards from the clients
One of the users has mentioned that turning off energy saving on the network cards from the clients has fixed the issue for him. To turn off power saving on the network cards, you can do below steps. Click Start -> Run Type regedit and hit Enter Registry editor will open. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class{4D36E972-E325-11CE-BFC1-08002bE10318}\DeviceNumber Note: DeviceNumber is the network adapter number. If a single network adapter is installed on the computer, the DeviceNumber is 0001. Click PnPCapabilities. On the Edit menu, click Modify. In the Value data box, type 24, and then click OK. Note: By default, a value of 0 indicates that power management of the network adapter is enabled. A value of 24 will prevent Windows 7 from turning off the network adapter or let the network adapter wake the computer from standby. Close Registry Editor
FIX: Steps to fix iPhone 6 Error 4013FIX: Steps to fix a corrupted pst or ost outlook data fileFIX: Steps to Fix Error ERR_FILE_NOT_FOUNDFix: You need to fix your Microsoft Account for apps on your other devices to be…
