Migrating the Terminal Licensing Server

[tnt]

Guys,

We are looking to replace our Domain Controller which also have Terminal
Licenseing Server. Any methods/ways I can use to perform the procedure?

Here is my brief Domain Controller plan for a background of what I am doing.
I am not sure about the Terminal Licensing Server.

Thanks,
Tnt.
---------------------------------------------------------------------------
Guys,

I am looking to get ideas/opinions on the best approach to promote a 2003
(Enterprise) Server to a domain controller.

Right now, we have two domain controllers (ad1 & ad2) in our live
environment. Both are also dns servers (replication of each other). On ad1,
we have terminal licensing server as well.

We are looking to replace ad1 because we are having hardware issue (no
longer have raid1 and hardware is old).

I am looking for the safest and least downtime if possible. Not sure what
or how to move this licensing server since it factors into this equation.

I do want the new server having the same name "ad1". Could I bring the new
ad into production as "ad3_temp" and in a few days, bring the old ad1 down
and changing the name of the new AD to "ad1"?

Thanks a lot.

Tnt.

 

[Vera Noest [MVP]]

From
http://ts.veranoest.net/ts_faq_licensing.htm#move_LS

Q: How do I move my TS licenses to a new TS Licensing Server?

A: Here are the steps to move your TS CALs from one TS Licensing
Server to another:

1. install the Terminal Server Licensing component on the
new server
2. activate the TS Licensing Server on the new server
3. install your TS CALs on the new server. Since licenses cannot
be installed more than once, you will have to call the Microsoft
Clearinghouse to get them re-issued:
* make sure that you have all the paperwork for the licenses at
hand (purchase contracts, licensing agreements, etc)
* start the Terminal Services Licensing tool, right-click the
server, choose Properties, choose "Telephone" on the
"Connection Metod" tab, choose your country or region, click
"OK".
Right-click the server again, choose "Install licenses", click
"Next".
* call the regional Clearinghouse telephone number they will
guide you through the rest of the installation process
4. verify that your Terminal Server(s) can locate the new TS
Licensing Server
5. deactivate the TS Licensing Server on the old server
6. uninstall the TS Licensing Service from the old server
_________________________________________________________
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?dG50?= <tnt@discussions.microsoft.com> wrote on 06 aug
2007 in microsoft.public.windows.terminal_services:

> Guys,
>
> We are looking to replace our Domain Controller which also have
> Terminal Licenseing Server. Any methods/ways I can use to
> perform the procedure?
>
> Here is my brief Domain Controller plan for a background of what
> I am doing.
> I am not sure about the Terminal Licensing Server.
>
> Thanks,
> Tnt.
> -----------------------------------------------------------------
> ---------- Guys,
>
> I am looking to get ideas/opinions on the best approach to
> promote a 2003 (Enterprise) Server to a domain controller.
>
> Right now, we have two domain controllers (ad1 & ad2) in our
> live environment. Both are also dns servers (replication of each
> other). On ad1, we have terminal licensing server as well.
>
> We are looking to replace ad1 because we are having hardware
> issue (no longer have raid1 and hardware is old).
>
> I am looking for the safest and least downtime if possible. Not
> sure what or how to move this licensing server since it factors
> into this equation.
>
> I do want the new server having the same name "ad1". Could I
> bring the new ad into production as "ad3_temp" and in a few
> days, bring the old ad1 down and changing the name of the new AD
> to "ad1"?
>
> Thanks a lot.
>
> Tnt.

 

[tnt]

Vera,

Thanks you for your response.

From your response, I am assuming that MS allows you to get the new licenses
issued while the old ones are in the production server?

This way, less downtime is needed

Are the Clearhouse open weekend?

Thanks,
Tnt

"Vera Noest [MVP]" wrote:

> From
> http://ts.veranoest.net/ts_faq_licensing.htm#move_LS
>
> Q: How do I move my TS licenses to a new TS Licensing Server?
>
> A: Here are the steps to move your TS CALs from one TS Licensing
> Server to another:
>
> 1. install the Terminal Server Licensing component on the
> new server
> 2. activate the TS Licensing Server on the new server
> 3. install your TS CALs on the new server. Since licenses cannot
> be installed more than once, you will have to call the Microsoft
> Clearinghouse to get them re-issued:
> * make sure that you have all the paperwork for the licenses at
> hand (purchase contracts, licensing agreements, etc)
> * start the Terminal Services Licensing tool, right-click the
> server, choose Properties, choose "Telephone" on the
> "Connection Metod" tab, choose your country or region, click
> "OK".
> Right-click the server again, choose "Install licenses", click
> "Next".
> * call the regional Clearinghouse telephone number they will
> guide you through the rest of the installation process
> 4. verify that your Terminal Server(s) can locate the new TS
> Licensing Server
> 5. deactivate the TS Licensing Server on the old server
> 6. uninstall the TS Licensing Service from the old server
> _________________________________________________________
> 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?dG50?= <tnt@discussions.microsoft.com> wrote on 06 aug
> 2007 in microsoft.public.windows.terminal_services:
>
> > Guys,
> >
> > We are looking to replace our Domain Controller which also have
> > Terminal Licenseing Server. Any methods/ways I can use to
> > perform the procedure?
> >
> > Here is my brief Domain Controller plan for a background of what
> > I am doing.
> > I am not sure about the Terminal Licensing Server.
> >
> > Thanks,
> > Tnt.
> > -----------------------------------------------------------------
> > ---------- Guys,
> >
> > I am looking to get ideas/opinions on the best approach to
> > promote a 2003 (Enterprise) Server to a domain controller.
> >
> > Right now, we have two domain controllers (ad1 & ad2) in our
> > live environment. Both are also dns servers (replication of each
> > other). On ad1, we have terminal licensing server as well.
> >
> > We are looking to replace ad1 because we are having hardware
> > issue (no longer have raid1 and hardware is old).
> >
> > I am looking for the safest and least downtime if possible. Not
> > sure what or how to move this licensing server since it factors
> > into this equation.
> >
> > I do want the new server having the same name "ad1". Could I
> > bring the new ad into production as "ad3_temp" and in a few
> > days, bring the old ad1 down and changing the name of the new AD
> > to "ad1"?
> >
> > Thanks a lot.
> >
> > Tnt.
>

 

[Vera Noest [MVP]]

There's no downtime at all, the whole process doesn't take more
than half an hour, and you can be several days without an LS
without any downtime.
Remember that clients that already have a valid license (permanent
or temporary) will be able to connect normally, even when the LS is
offline.
The only problem you could have is when a completely new client
wants to connect, or when an existing client needs to renew its
license. But since clients start to renew their licenses 7 days
before they actually expire, you have theoretically a week's time
before this becomes a problem (assuming that all clients connect
each day).
And the Clearinghouse doesn't actually remove your production
licenses from the old LS, they issue you a new license pack for
installation on the new LS.

I have no idea about the opening hours of the Clearinghouse. Those
could well differ between different countries, regions and states.

_________________________________________________________
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?dG50?= <tnt@discussions.microsoft.com> wrote on 09 aug
2007 in microsoft.public.windows.terminal_services:

> Vera,
>
> Thanks you for your response.
>
> From your response, I am assuming that MS allows you to get the
> new licenses issued while the old ones are in the production
> server?
>
> This way, less downtime is needed
>
> Are the Clearhouse open weekend?
>
> Thanks,
> Tnt
>
> "Vera Noest [MVP]" wrote:
>
>> From
>> http://ts.veranoest.net/ts_faq_licensing.htm#move_LS
>>
>> Q: How do I move my TS licenses to a new TS Licensing Server?
>>
>> A: Here are the steps to move your TS CALs from one TS
>> Licensing Server to another:
>>
>> 1. install the Terminal Server Licensing component on the
>> new server
>> 2. activate the TS Licensing Server on the new server
>> 3. install your TS CALs on the new server. Since licenses
>> cannot
>> be installed more than once, you will have to call the
>> Microsoft Clearinghouse to get them re-issued:
>> * make sure that you have all the paperwork for the licenses
>> at
>> hand (purchase contracts, licensing agreements, etc)
>> * start the Terminal Services Licensing tool, right-click
>> the
>> server, choose Properties, choose "Telephone" on the
>> "Connection Metod" tab, choose your country or region,
>> click "OK".
>> Right-click the server again, choose "Install licenses",
>> click "Next".
>> * call the regional Clearinghouse telephone number they
>> will
>> guide you through the rest of the installation process
>> 4. verify that your Terminal Server(s) can locate the new TS
>> Licensing Server
>> 5. deactivate the TS Licensing Server on the old server
>> 6. uninstall the TS Licensing Service from the old server
>> _________________________________________________________
>> 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?dG50?= <tnt@discussions.microsoft.com> wrote on 06
>> aug 2007 in microsoft.public.windows.terminal_services:
>>
>> > Guys,
>> >
>> > We are looking to replace our Domain Controller which also
>> > have Terminal Licenseing Server. Any methods/ways I can use
>> > to perform the procedure?
>> >
>> > Here is my brief Domain Controller plan for a background of
>> > what I am doing.
>> > I am not sure about the Terminal Licensing Server.
>> >
>> > Thanks,
>> > Tnt.
>> > --------------------------------------------------------------
>> > --- ---------- Guys,
>> >
>> > I am looking to get ideas/opinions on the best approach to
>> > promote a 2003 (Enterprise) Server to a domain controller.
>> >
>> > Right now, we have two domain controllers (ad1 & ad2) in our
>> > live environment. Both are also dns servers (replication of
>> > each other). On ad1, we have terminal licensing server as
>> > well.
>> >
>> > We are looking to replace ad1 because we are having hardware
>> > issue (no longer have raid1 and hardware is old).
>> >
>> > I am looking for the safest and least downtime if possible.
>> > Not sure what or how to move this licensing server since it
>> > factors into this equation.
>> >
>> > I do want the new server having the same name "ad1". Could I
>> > bring the new ad into production as "ad3_temp" and in a few
>> > days, bring the old ad1 down and changing the name of the new
>> > AD to "ad1"?
>> >
>> > Thanks a lot.
>> >
>> > Tnt.

 

[tnt]

Vera,

Thanks again.

I am assuming once I renamed the new Domain Controller's name to the old
server (perfom all necessary steps), the existing clients will know where to
look for when it is renewing the licenses?

Thanks,
Tnt





"Vera Noest [MVP]" wrote:

> There's no downtime at all, the whole process doesn't take more
> than half an hour, and you can be several days without an LS
> without any downtime.
> Remember that clients that already have a valid license (permanent
> or temporary) will be able to connect normally, even when the LS is
> offline.
> The only problem you could have is when a completely new client
> wants to connect, or when an existing client needs to renew its
> license. But since clients start to renew their licenses 7 days
> before they actually expire, you have theoretically a week's time
> before this becomes a problem (assuming that all clients connect
> each day).
> And the Clearinghouse doesn't actually remove your production
> licenses from the old LS, they issue you a new license pack for
> installation on the new LS.
>
> I have no idea about the opening hours of the Clearinghouse. Those
> could well differ between different countries, regions and states.
>
> _________________________________________________________
> 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?dG50?= <tnt@discussions.microsoft.com> wrote on 09 aug
> 2007 in microsoft.public.windows.terminal_services:
>
> > Vera,
> >
> > Thanks you for your response.
> >
> > From your response, I am assuming that MS allows you to get the
> > new licenses issued while the old ones are in the production
> > server?
> >
> > This way, less downtime is needed
> >
> > Are the Clearhouse open weekend?
> >
> > Thanks,
> > Tnt
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> From
> >> http://ts.veranoest.net/ts_faq_licensing.htm#move_LS
> >>
> >> Q: How do I move my TS licenses to a new TS Licensing Server?
> >>
> >> A: Here are the steps to move your TS CALs from one TS
> >> Licensing Server to another:
> >>
> >> 1. install the Terminal Server Licensing component on the
> >> new server
> >> 2. activate the TS Licensing Server on the new server
> >> 3. install your TS CALs on the new server. Since licenses
> >> cannot
> >> be installed more than once, you will have to call the
> >> Microsoft Clearinghouse to get them re-issued:
> >> * make sure that you have all the paperwork for the licenses
> >> at
> >> hand (purchase contracts, licensing agreements, etc)
> >> * start the Terminal Services Licensing tool, right-click
> >> the
> >> server, choose Properties, choose "Telephone" on the
> >> "Connection Metod" tab, choose your country or region,
> >> click "OK".
> >> Right-click the server again, choose "Install licenses",
> >> click "Next".
> >> * call the regional Clearinghouse telephone number they
> >> will
> >> guide you through the rest of the installation process
> >> 4. verify that your Terminal Server(s) can locate the new TS
> >> Licensing Server
> >> 5. deactivate the TS Licensing Server on the old server
> >> 6. uninstall the TS Licensing Service from the old server
> >> _________________________________________________________
> >> 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?dG50?= <tnt@discussions.microsoft.com> wrote on 06
> >> aug 2007 in microsoft.public.windows.terminal_services:
> >>
> >> > Guys,
> >> >
> >> > We are looking to replace our Domain Controller which also
> >> > have Terminal Licenseing Server. Any methods/ways I can use
> >> > to perform the procedure?
> >> >
> >> > Here is my brief Domain Controller plan for a background of
> >> > what I am doing.
> >> > I am not sure about the Terminal Licensing Server.
> >> >
> >> > Thanks,
> >> > Tnt.
> >> > --------------------------------------------------------------
> >> > --- ---------- Guys,
> >> >
> >> > I am looking to get ideas/opinions on the best approach to
> >> > promote a 2003 (Enterprise) Server to a domain controller.
> >> >
> >> > Right now, we have two domain controllers (ad1 & ad2) in our
> >> > live environment. Both are also dns servers (replication of
> >> > each other). On ad1, we have terminal licensing server as
> >> > well.
> >> >
> >> > We are looking to replace ad1 because we are having hardware
> >> > issue (no longer have raid1 and hardware is old).
> >> >
> >> > I am looking for the safest and least downtime if possible.
> >> > Not sure what or how to move this licensing server since it
> >> > factors into this equation.
> >> >
> >> > I do want the new server having the same name "ad1". Could I
> >> > bring the new ad into production as "ad3_temp" and in a few
> >> > days, bring the old ad1 down and changing the name of the new
> >> > AD to "ad1"?
> >> >
> >> > Thanks a lot.
> >> >
> >> > Tnt.
>

 

[Vera Noest [MVP]]

To avoid any misunderstandings:
I have *not* checked the rest of your domain migration plan at all,
I'm just commenting on moving the TS LS role.

The clients never communicate directly with a TS Licensing Server.
All communication is between the TS LS and the terminal Servers.
If they will autodetect the new LS depends on a couple of things:
Enterprise or Domain Licensing Server, installed on DC or member
server, if the current LS is hardcoded in the registry, etc.

But you can easily point each Terminal Server to the correct TS
Licensing Server, in Terminal Services Configuration - Server
Settings, or in a Group Policy.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?dG50?= <tnt@discussions.microsoft.com> wrote on 10 aug
2007:

> Vera,
>
> Thanks again.
>
> I am assuming once I renamed the new Domain Controller's name to
> the old server (perfom all necessary steps), the existing
> clients will know where to look for when it is renewing the
> licenses?
>
> Thanks,
> Tnt
>
>
>
>
>
> "Vera Noest [MVP]" wrote:
>
>> There's no downtime at all, the whole process doesn't take more
>> than half an hour, and you can be several days without an LS
>> without any downtime.
>> Remember that clients that already have a valid license
>> (permanent or temporary) will be able to connect normally, even
>> when the LS is offline.
>> The only problem you could have is when a completely new client
>> wants to connect, or when an existing client needs to renew its
>> license. But since clients start to renew their licenses 7 days
>> before they actually expire, you have theoretically a week's
>> time before this becomes a problem (assuming that all clients
>> connect each day).
>> And the Clearinghouse doesn't actually remove your production
>> licenses from the old LS, they issue you a new license pack for
>> installation on the new LS.
>>
>> I have no idea about the opening hours of the Clearinghouse.
>> Those could well differ between different countries, regions
>> and states.
>>
>> _________________________________________________________
>> 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?dG50?= <tnt@discussions.microsoft.com> wrote on 09
>> aug 2007 in microsoft.public.windows.terminal_services:
>>
>> > Vera,
>> >
>> > Thanks you for your response.
>> >
>> > From your response, I am assuming that MS allows you to get
>> > the new licenses issued while the old ones are in the
>> > production server?
>> >
>> > This way, less downtime is needed
>> >
>> > Are the Clearhouse open weekend?
>> >
>> > Thanks,
>> > Tnt
>> >
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> From
>> >> http://ts.veranoest.net/ts_faq_licensing.htm#move_LS
>> >>
>> >> Q: How do I move my TS licenses to a new TS Licensing
>> >> Server?
>> >>
>> >> A: Here are the steps to move your TS CALs from one TS
>> >> Licensing Server to another:
>> >>
>> >> 1. install the Terminal Server Licensing component on the
>> >> new server
>> >> 2. activate the TS Licensing Server on the new server
>> >> 3. install your TS CALs on the new server. Since licenses
>> >> cannot
>> >> be installed more than once, you will have to call the
>> >> Microsoft Clearinghouse to get them re-issued:
>> >> * make sure that you have all the paperwork for the
>> >> licenses at
>> >> hand (purchase contracts, licensing agreements, etc)
>> >> * start the Terminal Services Licensing tool, right-click
>> >> the
>> >> server, choose Properties, choose "Telephone" on the
>> >> "Connection Metod" tab, choose your country or region,
>> >> click "OK".
>> >> Right-click the server again, choose "Install
>> >> licenses", click "Next".
>> >> * call the regional Clearinghouse telephone number they
>> >> will
>> >> guide you through the rest of the installation process
>> >> 4. verify that your Terminal Server(s) can locate the new TS
>> >> Licensing Server
>> >> 5. deactivate the TS Licensing Server on the old server
>> >> 6. uninstall the TS Licensing Service from the old server
>> >> _________________________________________________________
>> >> 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?dG50?= <tnt@discussions.microsoft.com> wrote on 06
>> >> aug 2007 in microsoft.public.windows.terminal_services:
>> >>
>> >> > Guys,
>> >> >
>> >> > We are looking to replace our Domain Controller which also
>> >> > have Terminal Licenseing Server. Any methods/ways I can
>> >> > use to perform the procedure?
>> >> >
>> >> > Here is my brief Domain Controller plan for a background
>> >> > of what I am doing.
>> >> > I am not sure about the Terminal Licensing Server.
>> >> >
>> >> > Thanks,
>> >> > Tnt.
>> >> > -----------------------------------------------------------
>> >> > --- --- ---------- Guys,
>> >> >
>> >> > I am looking to get ideas/opinions on the best approach to
>> >> > promote a 2003 (Enterprise) Server to a domain controller.
>> >> >
>> >> > Right now, we have two domain controllers (ad1 & ad2) in
>> >> > our live environment. Both are also dns servers
>> >> > (replication of each other). On ad1, we have terminal
>> >> > licensing server as well.
>> >> >
>> >> > We are looking to replace ad1 because we are having
>> >> > hardware issue (no longer have raid1 and hardware is old).
>> >> >
>> >> > I am looking for the safest and least downtime if
>> >> > possible. Not sure what or how to move this licensing
>> >> > server since it factors into this equation.
>> >> >
>> >> > I do want the new server having the same name "ad1". Could
>> >> > I bring the new ad into production as "ad3_temp" and in a
>> >> > few days, bring the old ad1 down and changing the name of
>> >> > the new AD to "ad1"?
>> >> >
>> >> > Thanks a lot.
>> >> >
>> >> > Tnt.