Consolidating License Servers

[Guest]

Archived from groups: microsoft.public.windowsnt.terminalserver.setup (More info?)

I have recently been tasked with "Cleaning up" my company's Terminal Server
environment. I will admit that I haven't worked with Terminal Service much
and that this has definitely been a learning experience. My current
Challenge is this:

We have a Windows 2000 License Server and a Windows 2003 License Server.
The 2000 server is due to go off-lease and my company has not plans to
replace it. I would like to migrate the licenses from this server to the
2003 Licensing server. What would be the best way to accomplish this? What
are some of the things a need to think about for a smooth transition?

Our Network is configured as such:

Servers:
---------
NT 4.0 Domain (I know ... we are also working to get that upgraded as well
.... that's another email for another group)
NT/2k/2003 Member servers
2 - 2k Terminal Servers (they are pulling licenses from the 2k Licensing
server)
2- 2003 Terminal Servers (they are pulling their licenses from the 2003
Licensing server)


Clients Connecting to Terminal Servers:
----------------------------------------

A few NT 4.0 Workstation
Mainly 2000 Professional
Very Few XP

Thanks for any help that can be provided!

 

[Guest]

Archived from groups: microsoft.public.windowsnt.terminalserver.setup (More info?)

There is no real method to "move" TS licenses from one LS to
another. What you have to do is to phone the Clearinghouse, They
will issue new licenses, which you can install on your 2003 LS.

This should be an painless operation. Since your existing clients
already have a TS CAL, which is stored locallly on the client, you
have a time period of 7 days to make the move

There's only one thing that you should verify: if you ever run out
of Windows 2000 TS CALs, but have still 2003 TS CALs available,
the 2003 LS issues a 2003 TS CAL to a client which only connects
to a 2000 TS. Whether this is what you want or not is up to you to
decide, but you can configure this behaviour a "Prevent License
Upgrade Policy", located here:

Computer Configuration/Administrative Templates/Windows
Components/Terminal Services/Licensing

Note that this only applies when your 2003 TS CALs are Per Device
CALs. This (and other scenarios where a 2003 LS handles both 2000
and 2003 TS CALs) is described in the

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

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

"John Benefield" <john.benefield@eds.com> wrote in
news:uAl9yRhfEHA.3428@TK2MSFTNGP11.phx.gbl:

> I have recently been tasked with "Cleaning up" my company's
> Terminal Server environment. I will admit that I haven't worked
> with Terminal Service much and that this has definitely been a
> learning experience. My current Challenge is this:
>
> We have a Windows 2000 License Server and a Windows 2003 License
> Server. The 2000 server is due to go off-lease and my company
> has not plans to replace it. I would like to migrate the
> licenses from this server to the 2003 Licensing server. What
> would be the best way to accomplish this? What are some of the
> things a need to think about for a smooth transition?
>
> Our Network is configured as such:
>
> Servers:
> ---------
> NT 4.0 Domain (I know ... we are also working to get that
> upgraded as well ... that's another email for another group)
> NT/2k/2003 Member servers
> 2 - 2k Terminal Servers (they are pulling licenses from the 2k
> Licensing server)
> 2- 2003 Terminal Servers (they are pulling their licenses from
> the 2003 Licensing server)
>
>
> Clients Connecting to Terminal Servers:
> ----------------------------------------
>
> A few NT 4.0 Workstation
> Mainly 2000 Professional
> Very Few XP
>
> Thanks for any help that can be provided!