Link to home
Start Free TrialLog in
Avatar of TCS-tech
TCS-tech

asked on

How do I resolve Event ID 4105 with source Microsoft-Windows-TerminalServices-Licensing?

Log Name:      System
Source:        Microsoft-Windows-TerminalServices-Licensing
Date:          12/21/2010 7:55:23 AM
Event ID:      4105
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      bkupsrv.domain.local
Description:
The Remote Desktop license server cannot update the license attributes for user "UserName" 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.

The License server is the Domain Controller and it assigns licenses properly to users that are located in the default Users container in ADU&C.  However, the users located in a separate OU container receive this license.  How can we get the License server to assign user licenses to users in the non-default User containers.  Of course, the above conditions have been met.  Thanks for your help.
Avatar of Sajid Shaik M
Sajid Shaik M
Flag of Saudi Arabia image

am sure u saw this but event though have a look once...

http://technet.microsoft.com/en-us/library/cc775179(WS.10).aspx

all the best
Avatar of TCS-tech
TCS-tech

ASKER

Thanks the link.  

Yes, I have done that, and it works great with the default Users container.  When I use the built-in diagnostic for licensing, it says that everything is configured properly.  

I just came across a link that suggests that I need to "add read\write permissions to the terminalServer attribute or to the Terminal Server License Server attribute of the “user object” by the Terminal Server License Servers group."   I am going to try that and see if that will resolve the issue.
ASKER CERTIFIED SOLUTION
Avatar of TCS-tech
TCS-tech

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
The problem has been resolved as noted.
I was unable to see a 'Read TerminalServer' or 'write TerminalServer' permission.  Are these the exact names?
Hello,  I am having this issue on a 2008 Terminal server environment.  Following the steps above to delegate control I also do not have "Read Terminal Server" and Write Terminal server" permissions as an object to select.  I have numerous objects that start with Read and Write msTS...  For example, "Read msTSMaxidleTime".  Does any one have more specific information about the exact permission name?

Thanks.
"Read and write Terminal Server license server" is the exact permission name. The list is not ordered and this permission is at the top, approx. 20 items down.