Link to home
Start Free TrialLog in
Avatar of eymsIT
eymsITFlag for United Kingdom of Great Britain and Northern Ireland

asked on

Terminal Server 2008 Licensing Problem

I have a Windows 2008 Terminal server which is part of a 2003 domain which was installed 116 days ago which has been running fine. I didn't licence it when it was installed and have been using the 120 day grace period. I licenced it today with per user setting and added 15 licences which was successful.
However when I look in Terminal Services Manager there is an exclamation sign against the server, and the first attached screenprint seems to say it is not in the Terminal services group in Ad, yet the second attachment seems to show that it is.
How do I resolve the error?
TS-screenprint1.JPG
TS-screenprint2.JPG
ASKER CERTIFIED SOLUTION
Avatar of page1985
page1985
Flag of United States of America image

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
Avatar of eymsIT

ASKER

Thanks for the explanation.
The other server (buscall) is a Windows 2000 terminal server which I'm thinking of decommissioning very shortly, just leaving this (Sirius) Windows 2008 server as the only terminal server in the domain, which has the licensing server on.
Presumably in this scenario I would be safe to just do nothing?
Also, when looking in TS Manager at Sirius with the exclamation mark, under the 'Total TS Cals' column it says there are 15 cals, yet under the 'Available' column I would have expected to see 15 too, yet it just says 'generate report'. Is that because although I have added the 15 licences I still have 4 days left of the grace period and it is still handing out temporary licences?



No.  Your CAL count is unknown because you're licensing per user and not per device.  You can only get an accurate license count without querying active directory when you have per-device licensing.
Avatar of eymsIT

ASKER

There are some licensing errors in the event log (see attached screenshots). I assume these are all related? How do I resolve?
screenshot-4.JPG
screenshot-5.JPG
For the first error (Event ID 4105) you can reslove by adding the machine account in Active Directory to the Terminal Server Licensing Servers group.  I believe it's located at:
      domain.com/Built-in/Terminal Server Licensing Servers
 
And for the second error (Event ID 1004) it's entirely possible that this is a side effect of the first error.  Let's correct the first error and see if this event recurrs.
Avatar of eymsIT

ASKER

I've checked our AD and the TS is a member in the builtin\terminal server licencing group already
Avatar of eymsIT

ASKER

I appreciate your help on this one. The TS is up and running, although with still some niggles about licensing manager and AD. I may do some further digging and post another question to resolve outstanding stuff, but in the meantime thanks a lot.