Thursday, April 19, 2012 3:13 AMWe have a system where we are using Microsoft's Multipoint server 2011. We also have a standard 2003 R2 running terminal services. We have a domain with 2 DC's. One is 2003 the other is 2008. The box running terminal services and the other running the multipoint server are not the DC's.
When a user logs on, we get the following warning:
The Remote Desktop license server cannot update the license attributes for user "alange" in the Active Directory Domain "Summit.local". Ensure that the computer account for the license server is a member of Terminal Server License Servers group in Active Directory domain "Summit.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
The license server (which is also the primary TS box) is a member of the TSLS group and it is not a domain controller.
I'm not sure why the Multipoint server is giving this error. I don't believe that the Multipoint server uses the Terminal Server Licensing Servers. They can be set up as stand-a-lones and the licensing (as far as I could tell) is activated on the Multipoint server itself.
If you have any insight into what is causing this warning, I'd really appreciate hearing.it.
Tuesday, June 12, 2012 10:05 PM
WMS 2011 should not rely on other servers for its licenses, whether domain-joined or in a workgroup. (This WMS is domain-joined though, right?)
As a troubleshooting step to rule out some legacy / migration weirdness, if you create a new user account from scratch (on the domain) do you get the same error logging into WMS?
If the new user account does not error out, check out this post:
If you still get the same error, let us know.
Tim Barrett http://www.NoGeekLeftBehind.com