


Microsoft KB2030310 article list 3 possible reasons for this behaviour: 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. 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. Ensure that the computer account for the license server is a member of Terminal Server License Servers group in Active Directory domain " domain.local". The Remote Desktop license server cannot update the license attributes for user "" in the Active Directory Domain "".
