W2K term server in 2003 AD domain

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We are currently running 2 W2K servers in terminal services application mode.
One of these W2K term servers is our term services license server with 150
licenses configured. It has worked just fine for a few years.

We are upgrading our NT4 domain to Active Directory. Our AD servers will be
running Windows 2003. Will this in any way effect our terminal server
licensing?

Will we need to move the term server license server to a Windows 2003 server
or can the license server remain on the Windows 2000 server that it currently
resides on?

Thanks for any insight on ts licensing in AD.

JT
 
Yes, you'll have to move the TS Licensing Server to a Domain
Controller.
A W2K TS Licensing Server must run on a DC, only exception is when
the W2K LS is a member server in a NT4 domain or a standalone
server in a workgroup (that's why it has been working in your
current environment).
As soon as you move the W2K member server into a 2003 AD domain,
the W2K Licensing Server won't start any more, so you'll have to
move your LS to a 2003 DC.

277917 - Terminal Server Licensing Service Failure
http://support.microsoft.com/?kbid=277917

Also check:
Q. How do I move my licenses from one licensing server to another?

from the Microsofts Terminal Services FAQ at
http://www.microsoft.com/windowsserver2003/community/centers/termin
al/terminal_faq.asp
 
On last question.....

Do we need to move the terminal server licenses immediately after upgrading
to our 2003 AD domain? Is there any 'grace' period that will allow the W2K
license server to work or will it immediately fail as soon as we upgrade to
2003 AD?

We are planning our AD upgrade soon and I need to know if we should build
that license server move task in to the upgrade weekend's work or if it is
something that we can do shortly thereafter? Thank-you?

JT
 
The W2K Licensing Server will fail to start immediately when you
move it into the new domain, so I would install and activate your
new LS on a 2003 DC prior to that.
This will take care of all your W2K Pro and XP Pro clients, since
the 2003 LS also contains the built-in "Existing 2000 Per Device TS
CALs".
If you also have other clients, which need a purchased 2000 TS CAL,
you will have to move these licenses. That involves calling the
Clearinghouse, and I'm not sure if they can be reached during the
weekend (depends on where you live as well). But this doesn't mean
that your clients can't connect anymore. Most of them will still
have a valid license, and as long as their license hasn't expired,
they will be able to connect.

And a last tip: maybe you have hardcoded the address of the current
W2K Licensing Server into the registry of your Terminal Servers,
thereby overruling the automatic discovery process. If so, remove
that registry entry again, or hardcode the new LS (shouldn't be
necessary when the new LS runs on a DC).

239107 - Establishing Preferred Windows 2000 Terminal Services
License Server
http://support.microsoft.com/?kbid=239107

Recommended reading (contains lots of examples of mixed 2003 LS and
2000 TS):
Windows Server 2003 Terminal Server Licensing White paper
http://www.microsoft.com/windowsserver2003/techinfo/overview/termse
rvlic.mspx
 
Thank-you

Vera Noest said:
The W2K Licensing Server will fail to start immediately when you
move it into the new domain, so I would install and activate your
new LS on a 2003 DC prior to that.
This will take care of all your W2K Pro and XP Pro clients, since
the 2003 LS also contains the built-in "Existing 2000 Per Device TS
CALs".
If you also have other clients, which need a purchased 2000 TS CAL,
you will have to move these licenses. That involves calling the
Clearinghouse, and I'm not sure if they can be reached during the
weekend (depends on where you live as well). But this doesn't mean
that your clients can't connect anymore. Most of them will still
have a valid license, and as long as their license hasn't expired,
they will be able to connect.

And a last tip: maybe you have hardcoded the address of the current
W2K Licensing Server into the registry of your Terminal Servers,
thereby overruling the automatic discovery process. If so, remove
that registry entry again, or hardcode the new LS (shouldn't be
necessary when the new LS runs on a DC).

239107 - Establishing Preferred Windows 2000 Terminal Services
License Server
http://support.microsoft.com/?kbid=239107

Recommended reading (contains lots of examples of mixed 2003 LS and
2000 TS):
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
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
Click to expand...
 
When we upgrade from our NT 4 domain to Windows 2003 AD, it will take place
on a weekend. I would prefer to have my current purchased CALS moved prior
to upgrading the domain. I would like to install the licensing service on a
2003 member server, call the clearinghouse and configure (move) existing CALS
and activate the licenses. Then on upgrade weekend, I will dcpromo that
member server to a DC. Will this work? Will the activated licenses work
after the DC promotion?

Also, what info do I need to give the clearinghouse? I will have the member
server information and my original license string from the purchased CALS.
Is that all they will need in order to give me an activation code?

Thank-you.

JT
 
Back
Top