Terminalservices Licensing 4105



  1. Terminalservices-licensing 4105 Windows Server 2012
  2. Terminal Services Licensing Error 4105
  3. Terminal Services Licensing 4105 Community Care
  4. Terminal Services Licensing 4105 Number
  5. Terminal Services Licensing 4105

Source: Microsoft-Windows-TerminalServices-Licensing Date: 14:43:08 Event ID: 4105 Task type: None Level: Warning Keyword: Classic User: Missing Computer: MDC.XXXX.cn Description: The remote desktop authorization server cannot update the license attribute of the user 'Administrator' in the Active Directory domain 'XXXX.cn. Make sure that the. After the user has logged on, check the event logs of the server, there should not be a event id 4105 Warning for the user in the System log, and there should be a event id 4143 Information entry for the user under Microsoft-Windows-TerminalServices-Licensing/Admin log. Univention Bugzilla – Bug 31088. Event 4105: The Remote Desktop license server cannot update the msTSExpireDate attribute for user objects. Last modified: 2013-04-19 12:45:56 CEST.

  1. Therefore, the Terminal Services license server cannot issue TS CALs of the type 'Windows Server 2003 - Terminal Server Per Device CAL Token' to the terminal server 'IP of a TS'. To resolve this problem, install additional TS CALs as required.
  2. TerminalServices-Licensing 4105. The Terminal Services license server cannot update the license attributes for user g h in Active Directory Domain g h Ώې i FWindows Server 2008 Datacenter without Hyper-V, Windows Server 2008 Enterprise without Hyper-V, Windows Server 2008 R2 Datacenter, Windows Server 2008 R2 Datacenter.

Heya!

Today I will tell you about issue I discovered recently with terminal license server. It was windows 2012R2 with 100 per user licenses installed. I configured license usage report for it which was described here. For about 1 year it was showing usage of about 10 from 100 licenses. That was confusing so I started investigation. First I checked license usage report from RD Licensing Manager and noticed there:

Failed Per User License Issuance Detail

Terminalservices-licensing 4105 Windows Server 2012

User,CAL Version,CAL Type,Tried Issuance On

ddc.comm_okla,Windows Server 2012,RDS Per User CAL,”den 7 april 2017 14:00:10″

ddc.comm_dvbl,Windows Server 2012,RDS Per User CAL,”den 7 april 2017 14:00:20″

ddc.comm_lpdn,Windows Server 2012,RDS Per User CAL,”den 7 april 2017 16:06:33″

ddc.comm_opda,Windows Server 2012,RDS Per User CAL,”den 10 april 2017 09:44:58″

Terminalservices Licensing 4105

ddc.comd_elam,Windows Server 2012,RDS Per User CAL,”den 10 april 2017 09:48:33″

Failed Per User License Issuance Summary

4105

DomainName,FailedPerUserLicenseIssuanceCount

ddc.com,5

First I checked logs on server and there were no any recent events regarding terminal licenses. So I asked a question on MS support forums and got reply to search for event 4105 in windows application log.

2016

I searched and found a lot of such events. So this issue is about permissions for RD License server on user accounts in AD. You can check this permissions on security tab of user account in AD, but before you need to enable “Advanced Features” in AD Users and Computers

In our case “Terminal Server License Servers” group was added as Allow entry in users ACL, but did not had any permissions on user account at all.

It should be “Read/Write Terminal Server license server”

First I was planning to write some script to update permissions for each user object, but then I found this article from MS. It is not stated there that it applies for windows 2012 and windows 2012R2, but it does 🙂

Terminal Services Licensing Error 4105

I used both methods from scenario #2 and each of them worked.

Terminal Services Licensing 4105 Community Care

4105

Terminal Services Licensing 4105 Number

1 warning here. Permissions for “Terminal Server License Servers” group will not be updates, new ACL entry will be added for each user object instead. So keep it in mind when checking results, just look at all ACL entries to make sure it worked.

Terminal Services Licensing 4105

After correct permissions were applied license usage increased twice during 1 day only!





Comments are closed.