Re: Licensing

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

comments inline.

=?Utf-8?B?TWFyYyBT?= <MarcS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 27
mar 2008 in microsoft.public.windows.terminal_services:

(1) Wow. Thanks for all that info. Where did you find all that
information?

I've worked with TS for many years. You can test this scenario by
simply taking your LS offline and try to connect with a couple of
clients with and without licenses. Microsoft also has a huge amount
of information. See my website for links.

(2) If I have (as an emergency measure) to install and activate
a 2nd LS on another server, and then my primary license server
comes back online, is there a problem if there are "two"
licensing servers running at the same time (on two separate
servers). Or can there only be one LS? If the Primary comes
back online, do I need to de-activate the 2nd LS.

No, you can have multiple activated Licensing Servers. It's
actually recommended, for redundancy reasons.

(3) Do I install the LS from Add/Remove Windows Components?
This was previously installed by consultants. Or is there a
download?

No download, just install from Add Windows components.

(4) Does the LS have to be on a DC? From my reading, it seems
to be the preferred way.

It doesn't have to be on a DC (assuming we are talking about
Windows 2003 or 2008). The LS role doesn't take much resources, so
you can put it on any server you like, unless you have thousands of
clients, in which case a dedicated LS could be wise.

(5) Once installed a LS, does Microsoft have to be called to
activate, if only using temporary licenses in the beginning.

No, you can activate the LS over the Internet.

Thanks.

You're welcome!

"Vera Noest [MVP]" wrote:

When your LS is offline, this is what will happen:

a. clients with an existing permanent TS CAL will be able to
connect until their license expires
b. clients with an existing temporary TS CAL will be able to
connect until their license expires
c. clients without any TS CAL will not be able to connect
d. clients with an expired TS CAL (permanent or temporary) will
not be able to connect

Permanent TS CALs expire after 52-89 days, and the clients
attempts to renew it 7 days prior to expiration. So if most of
your clients connect every day, you have 7 days to get your LS
online again. Temporary licenses expire after 90 days. A client
can never get a second temporary TS CAL.

If your only LS goes offline, you can (as an emergency measure)
install and activate a LS on another server. Even if you don't
install any TS CALs on it, it will issue a temporary license to
new clients (see group c. above). That leaves only group d. as
an immediate problem, but they should be few.

No, when you enable Terminal Services, you loose the 2 free
connections.
You have still one free connection left, though, by connecting
to the console of the server, with mstsc /console, or mstsc
/admin from a Vista SP1 or XP SP3 client.
_________________________________________________________
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?TWFyYyBT?= <MarcS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on
26 mar 2008 in microsoft.public.windows.terminal_services:

If I have two Terminal Servers. Both Windows 2003 Standard.
The Licensing Server is on a separate 3rd Server that is one
of our Domain Controllers.

If that Licensing Server is shut down for a while, and
someone tries to log onto either of the Terminal Servers,
what happens?

1. Are they temporarily issued a temporarily TS license?
How long does that license last?

2. Even if the TS is set for "per Device" mode, can it allow
2 simultaneous connections like the Remote Desktop for
Administrators...or are the two simultaneous ONLY for Remote
Desktop for Administrators.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
.

Relevant Pages

  • Re: Terminal Server 2000 in Workgroup to 2003 Domain
    ... state office kept logging on without pulling CALS or Built In Licenses. ... The MS Support person was not able to fix the problem of XP Pro clients ... Now we have an existing client with a temporary license. ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • RE: Event 1004 Terminal Server Cannot issue a client license
    ... by default Windows 2000 client/XP does not require license to connect ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Per User TS CALs, so don't buy those. ... is issued to the client, which is good for 30 days. ...
    (microsoft.public.win2000.termserv.apps)
  • Re: Terminal Service License Server in sbs 2003
    ... You can also get free TS CALs for 2003 for every XP Pro for which ... a Terminal Server running windows 2000 without have to have purchase a TS ... temp license expires, which is why your clients work...for now. ...
    (microsoft.public.windows.server.sbs)
  • Re: Problems with the Windows 2003 License Server
    ... CALs Tokens)". ... since you have no clients who need them. ... server) is started. ... I got a temporary license on the Windows 2003 Server, ...
    (microsoft.public.windows.terminal_services)
  • Re: Licensing
    ... a 2nd LS on another server, and then my primary license server ... clients, in which case a dedicated LS could be wise. ... Permanent TS CALs expire after 52-89 days, ...
    (microsoft.public.windows.terminal_services)