Win2003 No Licence Issued

  • Thread starter Thread starter Mike Nash
  • Start date Start date
M

Mike Nash

Hi Guys

I may be worrying about nothing but here's my story anyway.

We had a site running two servers. One SBS4.5 box and one dedicated Win2003
Terminal Server box.
Last weekend we migrated from SBS4.5 to SBS2k3. The migration appeared to go
well. With the new SBS2k3 box now in place the old Win2003 TS box needed to
find a new licensing server. So, we installed terminal server licensing on
the new SBS2k3 box, activated the server, and then added the client
licences. Sweet as! Remote users logged in to the Terminal Server via a VPN
link through the SBS2k3 box. Five users are logged in and working as we
speak

But,.... I cranked up the Terminal Server Licensing window to have a look
around and noticed that the issued licences are still set at 0....??? They
have 3 open licence packs of four users per device. ie 12 devices can grab
the licences. Before the migration you could see that the licences were
assigned to specific machines etc. Now, they don't appear to be assigned to
any device - But it's working?

Is something out of whack or is it just that 120 day grace period thing
kicking in...?
There is an Application Event log error now too.

Source: Userenv
Category: None
Event ID: 1030
Windows cannot query for the list of Group Policy objects. Check the event
log for possible messages previously logged by the policy engine that
describes the reason for this.
(What ever all that means - grin)

Any pointers will be greatly appreciated
Thanks in advance
Mike Nash
 
Are these "per user" or "per device" Terminal Server CALS?

Per user TSCALs are unmanaged, and do not get issued to specific users or
workstations.

Are there TSCALs activated on the TSLS that are the same kind as the mode
set in the Terminal Server Configuration, i.e. Per User, or Per Device

Are there errors in the TS Event log about not being able to find the TSLS?

Are computers being issued Temp Licenses (this only should happen on the
first logon)?

Have you tried querying the TSLS with the tools from the Resource Kit to
make sure a client can find the TSLS?

Did you (before the migration) have the TS hard coded via registry to find a
specific TSLS?

Did you know that the TSLS can run perfectly well on the TS with Windows
Server 2003?

http://www.workthin.com/tsls2k3.htm

Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com
 
I believe that there is no problem at all:
remember that licenses are stored on the client. All of your
clients have received a license before (in the old domain setup),
so they don't need one. That's why TS Licensing manager doesn't
list them.

You will start to see your clients when their TS CALs expire and
they have to renew them.

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*

"=?Utf-8?B?UGF0cmljayBSb3VzZSBbTVZQXQ==?="
 
Thanks Patrick (I think - grin)

Gawd, what a lot of questions. Not sure if I know all the answers though -
Here goes


Patrick Rouse said:
Are these "per user" or "per device" Terminal Server CALS?
Click to expand...

I selected per device just like they were before.
Per user TSCALs are unmanaged, and do not get issued to specific users or
workstations.

Are there TSCALs activated on the TSLS that are the same kind as the mode
set in the Terminal Server Configuration, i.e. Per User, or Per Device
Click to expand...

Not sure. I don't remember answering any mode question when setting up the
TSLS. I only saw a mode question when installing the client licences.

Are there errors in the TS Event log about not being able to find the TSLS?
Click to expand...

Not that I'm aware off. I'll have another look though later.

Are computers being issued Temp Licenses (this only should happen on the
first logon)?
Click to expand...

Don't think so. I assume that would be in the Event Logs. Didn't see
anything in there.
Have you tried querying the TSLS with the tools from the Resource Kit to
make sure a client can find the TSLS?
Click to expand...

Were do I find this resource kit. Naghhhh, don't worry about that one (grin)
Did you (before the migration) have the TS hard coded via registry to find a
specific TSLS?
Click to expand...

Pardon...? I'll pass on that one too thanks (grin)

Did you know that the TSLS can run perfectly well on the TS with Windows
Server 2003?
Click to expand...
Well, no I didn't. (But I do now) I was under the impression it had to run
on the domain contoller. Which it does just fine - I think (grin). I'm sure
it must be easier to include in the back up now too.

Sorry I sound like a right wally (which I am - grin) It's a steep learning
cure at the moment. Thanks for your comments though

All the best
Mike
 
Hi Vera
Hey, I like your answer heaps better. I can actually understand it (grin)
And, it even makes sence. Cool!
I'll keep an eye on it and see if they start popping up over time.
Thanks
All the best
Mike
 
Yes, I imagined that you would be pleased :-)
Just to be 100 % sure, keep an eye on the EventLog as well.
 
Back
Top