Re: Some servers still getting temp licenses

You're welcome, Amy, I'm glad I could help.
Yes, the grace period thing isn't very widely published.
The only document that I know of which states this clearly is:

Windows Server 2003 Terminal Server Licensing White paper
http://www.microsoft.com/windowsserver2003/techinfo/overview/termse
rvlic.mspx

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?QW15?= <Amy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 09 mar
2007 in microsoft.public.windows.terminal_services:

I apologize for the confusion. What I meant was what terminal
server the user was connecting through to get to the license
server. In all of my reading I had never come across anything
that said the grace period ended as soon as the LS issued the
first permanent license, so I guess that answers all of my
questions.

I just wanted to make sure that in another month (when the 120
days would have been up) we weren't going to have quite a few
users who weren't able to connect to Terminal Server.

Thanks for your help.

"Vera Noest [MVP]" wrote:

I'm a bit confused by your post.
First: servers don't get licenses, neither temporary nor
permanent. Terminal Servers issue a license from the LS to the
clients.

But if you see a lot of temporary licenses in the TS Licensing
Server, then the Terminal Server *has* been able to locate the
TS Licensing Server, hasn't it?

Also: your grace period has already ended (it ends after 120
days OR when the first permanent license is issued by an LS).

You'll have to look a bit further at these temporary licenses
and check which clients they are issued to. My guess is that
these clients have only connected once. Maybe by users who are
not even allowed to connect to the TS? That's the reason for
the temporary license on the first connection: no unauthorized
user should be able to take up a license.

But you really need to know the whole picture (total number of
clients, issued, available, permanent/ temporary licenses,
etc.) to be able to verify that.
Also check the EventLog on the Terminal Servers for any
licensing warnings.

Again: running lsview will tell you if a TS sees the LS.
And one single GPO can point all of your TS to the LS. But I
doubt that it is necessary.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?QW15?= <Amy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 08
mar 2007 in microsoft.public.windows.terminal_services:

If that were the case, wouldn't the number of temporary
licenses go down, instead of continuing to increase?

So I guess there is no way to see which servers are getting
temporary licenses, the only option is to go hard code each
one to point to the licensing server?

"Vera Noest [MVP]" wrote:

You can run lsview from the Resource Kit on each server to
see if it can detect the LS.

Or point each TS to the LS. This can be done in Terminal
Services Configuration, but it's easiest in a GPO.

Note that each client *always* uses a temporary license on
the very first connection. On the second connection from the
same client, a permanent license should be issued. Maybe
that's what you see?

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?QW15?= <Amy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 08
mar 2007:

Is there a way to determine which servers are getting temp
licenses? There are over 2000 regular licenses obtained,
but the number of temp licenses has grown (close to 100)
and I want to get this resolved before the 120 days is up.


When we first installed this we found that no one was
getting regular licenses, and determined it was because of
this issue:

When a terminal server searches for license servers in
remote sites by using a global catalog server, the
terminal server incorrectly searches for an object that is
named TS-Enterprise-LicenseServer. The correct object is
TS-Enterprise-License-Server.

We corrected this and thought the problem was fixed, but
apparently there are still servers not discovering the
licensing server. So is there a way to determine which
servers are getting the temporary licenses?
.

Relevant Pages

  • Re: terminal server that hands out licenese to other servers..
    ... I've worked in a lot of place but have never had a reason to allow 10 admins on one server at time. ... Microsoft MVP - Terminal Server ... Does that mean you have to install all terminal services in "application mode" on all servers that will need more than two connections? ... To provide licenses for the user connections, install the Terminal Server Licensing component on a domain controller and use the Terminal Server Licensing administration tool to activate your licenses. ...
    (microsoft.public.windows.terminal_services)
  • Re: Licensing issue
    ... Is the Terminal Server set to use "Per ... I have purchased 40 per user licenses ...
    (microsoft.public.windows.terminal_services)
  • Re: 2003 Small Business Server - TS out of liscences?
    ... What OS is the Terminal Server running? ... What type of TS licenses were purchased? ... From the information that you provided, it appears that the TS CALs have not been installed on the TS Licensing server. ...
    (microsoft.public.windows.terminal_services)
  • Re: TS Licensing Server not issuing licenses
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... and a W2K TS cannot use Per User licenses at all. ... purchased and installed 80 Per User CALs for W2K3. ...
    (microsoft.public.windows.terminal_services)
  • Licenses allocated longer than 90 days
    ... I have terminal server licenses that have lifetimes as long as 439 days. ... temporary licenses issued. ...
    (microsoft.public.windows.terminal_services)
Loading