Can you offer up some suggestions regarding the following System log events? We are seeing these errors frequently on the Windows Server 2012 R2 server which is hosting the Remote Desktop license server.
1. Are these warnings and errors concerning and require action to correct? If so what steps?
2. What end user experience symptoms (other than the posted messages to System log) would we expect to see?
Log Name: System Source: Microsoft-Windows-TerminalServices-Licensing Date: 4/29/2019 11:12:28 AM Event ID: 4105 Task Category: None Level: Warning Keywords: Classic User: N/A Computer: MSRDSLIC.mydomain.com Description: The Remote Desktop license server cannot update the license attributes for user "useraccountname" in the Active Directory Domain "mydomain.com". Ensure that the computer account for the license server is a member of Terminal Server License Servers group in Active Directory domain "mydomain.com". 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
Log Name: System Source: Microsoft-Windows-TerminalServices-Licensing Date: 4/30/2019 5:51:17 AM Event ID: 44 Task Category: None Level: Error Keywords: Classic User: N/A Computer: MSRDSLIC.mydomain.com Description: The following general database error has occurred: "ESE error -1003 JET_errInvalidParameter, Invalid API parameter."
Log Name: System Source: Microsoft-Windows-TerminalServices-Licensing Date: 5/1/2019 11:46:41 AM Event ID: 4106 Task Category: None Level: Warning Keywords: Classic User: N/A Computer: MSRDSLIC.mydomain.com Description: CAL reporting: Windows Server 2012 : RDS Per User CAL - Installed: 850, Issued: 881
In addition, I can confirm that, per instructions in event 4105, the license server is not a domain controller and the computer account is a member of the built-in "Terminal Server License Servers" group.
A similar question TechNetForumTopic, TechNetForumQuestion, SysAdminTipBlog, and MsITprosBlog refers to a solution involving old accounts for long-term employees who are appearing in event 4105. I have validated that many of them are old enough that they likely existed back when this domain was at the 2003 functional level (it is now at the 2012 level). However, these users are not reporting any symptoms, so the event 4105 seems to not cause any downside other than logging the event. (Which goes back to my original questions, what symptom effect should we be seeing?)
Thanks in advance for your assistance.