License Server

  • Thread starter Thread starter Hunter
  • Start date Start date
H

Hunter

Ok, I have an older W2K server that has TS in application mode. It
has the licensing server since it was the very first TS installed. I
also have 2 more servers with TS now. The first server is being
replaced with a newer box.

1. I need to change where the licensing server is (preferably the new
box which will still be W2K).
2. Remove the first TS box from the network including removing from
AD.
3. Keeping in mind that a W2003 box will probably be in this mix
sometime this summer.

Suggests, comments, things to watch for?

I can read. Kdocs would be great if you have them handy.

Thanks for your input.
 
Mmm, let me see:
W2K server, AD, TS Licensing Service. This must mean that the
server is a Domain Controller, is that correct?
If so, I would strongly suggest *not* to move all of these
functions to the new server. Running Terminal Services in
Application Server mode on a DC is not recommended, for both
performance and security reasons.
Maybe you should move the terminal server function to a new member
server, and keep the old server as a DC? Then you could also keep
the TS Licensing Service on the old server (unless it has hardware
problems, other than performance problems, that is).

Anyway, here's the FAQ on moving a TS Licensing Server:
From Microsofts Terminal Services FAQ at
http://www.microsoft.com/windowsserver2003/community/centers/termin
al/terminal_faq.asp

<quote>
Q. How do I move my licenses from one licensing server to another?

A. You should back up your Terminal Services licensing server
regularly by using the Windows Backup tool or similar. This will
help protect your licensing data from accidental loss if your
system experiences hardware or storage failure.

When backing up a Terminal Server License Server, back up both the
System State data and the folder in which the Terminal Server
License Server is installed. This ensures that data in both the
registry and the Terminal Services licensing server database is
backed up.

If you restore the System State data and the database to the
original Terminal Services licensing server computer, any unissued
licenses are restored correctly as long as you have not replaced
the operating system on the computer. Otherwise any unissued
licenses are not restored and an event will appear in the system
log providing the unissued count. You can still restore the
unissued licenses by using the TS License Manager tool with the
Telephone activation mechanism, and requesting the licenses back.
You can switch to the Telephone mechanism by right clicking on the
server in TS License Manager, and selecting properties from the
menu.
</quote>

In short: you'll have to phone the Clearinghouse.

291795 - HOW TO: Locate a Phone Number for the Microsoft
Clearinghouse
http://support.microsoft.com/?kbid=291795

About the planned addition of a 2003 Terminal Server:
this gives you a whole new set of requirements:
* a 2003 TS Licensing Server (a W2K LS cannot handle 2003 TS CALs)
* a 2003 server CAL for every device or user
* a 2003 TS CAL for every device or user

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___
 
Vera thanks for the info. While out of town, the old TS server decided
to carp out so It's physically gone anyway. That's why it took so long
to say thanks.



Mmm, let me see:
W2K server, AD, TS Licensing Service. This must mean that the
server is a Domain Controller, is that correct?
If so, I would strongly suggest not to move all of these
functions to the new server. Running Terminal Services in
Application Server mode on a DC is not recommended, for both
performance and security reasons.
Maybe you should move the terminal server function to a new member
server, and keep the old server as a DC? Then you could also keep
the TS Licensing Service on the old server (unless it has hardware
problems, other than performance problems, that is).

Anyway, here's the FAQ on moving a TS Licensing Server:
From Microsofts Terminal Services FAQ at
http://www.microsoft.com/windowsserver2003/community/centers/termin
al/terminal_faq.asp

<quote>
Q. How do I move my licenses from one licensing server to another?

A. You should back up your Terminal Services licensing server
regularly by using the Windows Backup tool or similar. This will
help protect your licensing data from accidental loss if your
system experiences hardware or storage failure.

When backing up a Terminal Server License Server, back up both the
System State data and the folder in which the Terminal Server
License Server is installed. This ensures that data in both the
registry and the Terminal Services licensing server database is
backed up.

If you restore the System State data and the database to the
original Terminal Services licensing server computer, any unissued
licenses are restored correctly as long as you have not replaced
the operating system on the computer. Otherwise any unissued
licenses are not restored and an event will appear in the system
log providing the unissued count. You can still restore the
unissued licenses by using the TS License Manager tool with the
Telephone activation mechanism, and requesting the licenses back.
You can switch to the Telephone mechanism by right clicking on the
server in TS License Manager, and selecting properties from the
menu.
</quote>

In short: you'll have to phone the Clearinghouse.

291795 - HOW TO: Locate a Phone Number for the Microsoft
Clearinghouse
http://support.microsoft.com/?kbid=291795

About the planned addition of a 2003 Terminal Server:
this gives you a whole new set of requirements:
* a 2003 TS Licensing Server (a W2K LS cannot handle 2003 TS CALs)
* a 2003 server CAL for every device or user
* a 2003 TS CAL for every device or user

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



--
 
Back
Top