Terminalservices Licensing 4105

Posted By admin On 26/01/22

Source: Microsoft-Windows-TerminalServices-Licensing Event ID: 4105 Level: Warning User: N/A Computer: Description: The Terminal Services license server cannot update the license attributes for user in the Active Directory Domain. Ensure that the computer account for the license server is a member of. TerminalServices-Licensing 4105 – The Terminal Services license server cannot update the license attributes for user “ ” in Active Directory Domain “ ” Symptoms. You may see the following Warning event on a computer that is running Remote Desktop Licensing (RD Licensing), formerly Terminal Services Licensing (TS Licensing). If the Terminal services are installed on a server that will act as a Domain Controller also, then first install the Active Directory Domain Service (AD DS) role service and promote the Server to a Domain Controller, before installing the Remote Desktop Session Host (RDSH) role service (Terminal Service). TerminalServices-Licensing 4105 – The Terminal Services license server cannot update the license attributes for user “” in Active Directory Domain.

Last updated on July 1st, 2019

This article contains step by step instructions on how to install and configure the Remote Desktop Services on a Windows Server 2016 or 2012. In Windows Server 2016 & 2012 the Terminal Services role has been replaced by the Remote Desktop Session Host (RDSH) role service and is part of Remote Desktop Services (RDS). A Remote Desktop Session Host (RDSH) server, provides to remote users the ability to access the applications on the RDS host server and the company resources from anywhere by using an RDP client.

In this tutorial you ‘ll learn how to setup and configure a Windows Server 2016 or 2012 as a Remote Desktop Session Host (Terminal) server, in order to provide remote desktop sessions, based on the number of Remote Desktop Services client access licenses (RDS CALs) installed on the RDSH server.

How to Setup and Configure a Windows Server 2016/2012 as a Remote Desktop Session Host Server (Terminal Server).

Notes:
1. The mentioned steps below, can be applied either on a Domain Controller or in a standalone server 2016/2012.
2. If the Terminal services are installed on a server that will act as a Domain Controller also, then first install the Active Directory Domain Service (AD DS) role service and promote the Server to a Domain Controller, before installing the Remote Desktop Session Host (RDSH) role service (Terminal Service).
3. Keep in mind that the below configuration does provide access to RemoteApp programs or the RDWeb site, because the Remote Desktop Connection Broker role service will not be installed.

Step 1. Install Remote Desktop Services on Server 2016/2012.
Step 2. Activate the Remote Desktop License Server.
Step 3. Install Licenses on the Remote Desktop License Server.
Step 4. Configure RD Session Host role to use the local Remote Desktop Licensing server & Set the Remote Desktop licensing mode.
Step 5. Add RD Clients (Users) to the Remote Desktop Users Group.
Step 6. Allow the log on through remote desktop Services.
Step 1. Install Remote Desktop Licensing and Remote Desktop Session Host role services.

1. Open ‘Server Manager’ and click on Add Roles and Features.

2. At the first screen of ‘Add Roles and Features wizard’ leave the Role-based or feature-based installation option and click Next.

3. At the next screen, leave the default option “Select server from the server pool” and click Next.

4. Select the Remote Desktop Services and click Next.

5. Leave the default settings and click Next at Features and Remote Desktop Services screens.
6. At Role Services screen, select the Remote Desktop Licensing role service and then click Add Features.

7. Then select the Remote Desktop Session Host role service and click Add Features again.

8. When done, click Next to continue.

9. Finally click Install to install the Remote Desktop Services: Remote Desktop Licensing and Remote Desktop Session Host.

10. When the installation is completed close the ‘Add Roles and Features Wizard’ and restart your server.

Step 2. Activate the Remote Desktop License Server.

1. Simultaneously press the Windows + R keys to open run command box.
2. Type licmgr.exe and press Enter to open the RD Licensing Manager *

* Note: Alternately, you can launch the RD Licensing Manager, from Control Panel –> Administrative Tools –> Remote Desktop Services –> Remote Desktop Licensing Manager.

3. At the right pane, right click on the server name and select Activate Server.

4. Click Next at the Welcome screen and then click Next again at Connection method options.

5. At ‘Company Information’ window, fill the required fields and click Next twice to activate your License Server.

6. When the activation is completed, leave checked the ‘Start Install Licenses Wizard’ checkbox and click Next.

7. Continue to next step.

Step 3. Install Licenses on the Remote Desktop License Server.

1. At ‘Welcome to the install licenses wizard’, click Next

Terminalservices Licensing 4105

2. On the License Program page, select the appropriate program through which you purchased your RDS CALs, and then click Next.

3. According the License Program you selected on the previous page, type either the license code or the agreement number provided when you purchased your RDS CALs and then click Next.

4. On the Product Version and License Type page, select the appropriate product version, license type, and the quantity of the RDS CALs based on your RDS CAL purchase agreement, and then click Next.

5. When the RDS CALs installed on the server, click Finish.

Step 4. Configure RD Session Host role to use the local Remote Desktop Licensing server & Set the Remote Desktop licensing mode.

1. Open Group Policy Editor. To do that:

1. Simultaneously press the Windows + R keys to open run command box.
2. Type gpedit.msc and press Enter.

2. In Group Policy Editor navigate to:

  • Computer ConfigurationAdministrative TemplatesWindows ComponentsRemote Desktop ServicesRemote Desktop Session Host Licensing

3. At the right pane, double click at Use the specified Remote License Servers.

4. Click Enabled, and then at ‘License server to use‘ field, type the RDS license server name and click OK.

5. Then open the Set the Remote Desktop licensing mode setting.

6. Click Enabled and then specify the licensing mode (Per User or Per Device) for the RDS host server and then click OK again.

7.Close Group Policy Editor.
8. Verify the RD Licensing configuration, by going to: Windows Control Panel –> Administrative Tools –> Remote Desktop Services –> RD Licensing Diagnoser.

Step 5. Add RD Clients (Users) to the Remote Desktop Users Group.

1. Open Server Manager.
2. From Tools menu, select Active Directory Users and Computers. *

* Note: If the RD Session Host Service is not installed on the Domain Controller, use the ‘Local Users and Groups’ snap-in or the ‘Remote’ tab in the ‘System Properties’ on the RDS host server, to add the remote desktop users.

3. Double click at your domain on the left and then select Builtin.
4.
Open Remote Desktop Users on the right pane.

5. At Members tab, click Add.

6. Type the name(s) of the users that you want to give Remote access to the RDS Server and click OK.

7. After selecting the remote desktop users, click OK again to close the window.

8. Continue to step-6 below.

Step 6. Allow the log on through remote desktop Services.

1. Open the Local Group Policy Editor. To do that:

Terminal Services Licensing Error 4105

1. Simultaneously press the Windows + R keys to open run command box.
2. Type gpedit.msc and press Enter.

2. In Group Policy Editor navigate to: Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment.

3. At the right Pane: double click at Allow log on through Remote Desktop Services.

4. Click Add User or Group.

5. Click Object Types, check all the available objects (Users, Groups, & Built-in security principals) and then click OK.

6. Type remote desktop users and then click OK.

Terminalservices-licensing 4105 Windows Server 2012

7. Finally click OK again and close Group Policy Editor.

8. Now you ‘re ready to connect to the Remote Desktop Session Host Server 2016/2012 from any Remote desktop client.

That’s it! Let me know if this guide has helped you by leaving your comment about your experience. Please like and share this guide to help others.

If this article was useful for you, please consider supporting us by making a donation. Even $1 can a make a huge difference for us in our effort to continue to help others while keeping this site free:
If you want to stay constantly protected from malware threats, existing and future ones, we recommend that you install Malwarebytes Anti-Malware PRO by clicking below (we
do earn a commision from sales generated from this link, but at no additional cost to you. We have experience with this software and we recommend it because it is helpful and useful):

By visiting our site, you agree to our privacy policy regarding cookies, tracking statistics, etc. Read more

Terminalservices-licensing Id 4105

Background

  • Windows Server 2008 R2 Domain
  • Windows Server 2008 R2 Remote Desktop Server with following roles:
    • Remote Desktop Session Host
    • Remote Desktop Licensing (User CALs)
    • Remote Desktop Web Access

Issue

Every time non-administrator user logs on via Remote Desktop connection, following Warning is logged in System Logs:

Event ID: 4105
Level: Warning
Description:
The Remote Desktop license server cannot update the license attributes for user '<user.name>' in the Active Directory Domain '<domain.local>'. Ensure that the computer account for the license server is a member of Terminal Server License Servers group in Active Directory domain 'domain.local'.
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: 0x80070005

Cause

Microsoft KB2030310 article list 3 possible reasons for this behaviour:

  1. The license server is not a member of the Terminal Server License Servers group in the domain in which the users reside.
  2. The license server is installed on a domain controller, and the Network Service account is not a member of the Terminal Server License Servers group.
  3. If the user accounts existed before the domain was upgraded to Windows Server 2003, the Terminal Server License Servers group might be missing in the discretionary access control list (DACL) of the user objects in Active Directory directory service. Or, the group is in the DACL, but the group does not have permissions to update the Terminal Services Licensing information for the user account.

After checking that first 2 reasons do not apply I assumed that issue was cased by domain existence prior to Windows Server 2003.

Resolution

Issue was resolved by adding read/write permissions to the Terminal Server License Servers group for all users.

  • Open Active Directory Users and Computers
  • Right click on the domain > Delegate Control > Next
  • Add Terminal Server License Servers group > Next
  • Select Create a custom task to delegate > Next
  • Select Only the following objects in the folder, scroll down and check User objects > Next
  • Check General, scroll down and check Read and Write Terminal Server license server > Next > Finish
View the discussion thread.