chicken or egg?

  • Thread starter Thread starter RH
  • Start date Start date
R

RH

I'm planning on upgrading all hardware in my single
domain server farm early next year. My root domain
controller is also my terminal services license server.
When I replace this machine with a new server and install
W2K3 it will become the root domain controller in the
forest. I will then transfer the FSMO roles to this
machine, as well as export DHCP settings from the old dc
and import them to the new one after taking the old one
off-line. I then plan on installing w2K3 licensing on
this machine. Meanwhile I will have a W2K terminal
server running while rolling out the new W2K3 terminal
server. Is it okay to do it this way and apply my 150 TS
device CAL's on the licensing server and have them be
doled out to my w2K TS clients while I'm getting the new
TS ready? When the new TS is ready to put on line, can I
then "re-set" the W2K3 TS CAL's for the 2K3 box after I
take the W2K TS down? Or....
Should I put licensing for W2K on the new 2K3 DC and have
it dole out licenses until I put the 2K3 TS on-line and
then add the TS CAL's to the licensing server? Which
comes first...the chicken or the egg. Thanks for you
help. Ron
 
Since a 2003 TS Licensing server can handle both W2K and 2003 TS
CALs, I would first install the TS LS on the 2003 LS (which is
also a DC), install any 2003 TS CALs that you have boght on it,
as well as move any W2K TS CALs that you have purchased over to
this LS. Moving TS CALs involves phoning the Clearinghouse.

Then you can install new 2003 TS whenever you want.

I would read this white paper, it explains scenarios with mixed
server OSes and a 2003 LS:

Windows Server 2003 Terminal Server Licensing White paper
http://www.microsoft.com/windowsserver2003/techinfo/overview/terms
ervlic.mspx
 
Oh and watch out for the removal of the "equivalence" licence.

W2K and XP clients could use a W2K server without purchasing additional
licenses.

On W2K3 - you must license everything.

I'm still struggling to understand why a single thin client should need a
Windows Server CAL and a TS CAL. Apparantly it makes it easier for us to
understand........
 
You need a server CAL because you connect to the server for
authentication, file and print services, etc.
You need a TS CAL because you connect to a Terminal Server.
 
Back
Top