what's the easiest way to move the Terminal Services (TS) License Service (TSLS)...

what's the easiest way to move the Terminal Services (TS) License Service (TSLS)...

Post by pau » Fri, 19 Apr 2002 21:41:24



what's the easiest way to move the Terminal Services (TS) License
Service (TSLS)...

currently have a single NT4 domain with a w2k member server running TS
which also has the TSLS installed and activated. I haven't yet
installed any TSCALs but have had a few w2k clients connect.

as the plan is to migrate to w2k domain and TSLS needs to be on a
Domain Controller, I want to move it off the existing TS server to a
new w2k member server which can be made into a DC.

my approach was simply going to be to install/activate TSLS on the new
box and deactivate on the old box - there shouldn't be a need to
actually uninstall the TSLS although if I can I'd prefer to.

I can't see that this has any implications for the existing licences
as they are 'built-in' to the clients that have connected so far. When
they first connect to the new TSLS the entries should be re-created.

What I'm not clear about is whether the TS writes a token back to the
w2k clients, and if so how this would be interpreted by the new TSLS.

Also, do I need to inform MS Clearinghouse that old TSLS has been
deactivated and get rid of the certificate?

TIA
pet

 
 
 

what's the easiest way to move the Terminal Services (TS) License Service (TSLS)...

Post by Cláudio Rodrigue » Fri, 19 Apr 2002 21:50:30


If you have no licenses installed, no big deal. Do exactly what you
described and no need to tell MS you will get rid of your first LS.

--
Cludio Rodrigues, MVP
Windows 2000/NT Server
Terminal Services

Check my website at http://www.terminal-services.NET
for information on Training, Services, Contracts and Free Support.
Also, if you need ThinPrint, get a quote with us!

Do NOT email me directly UNLESS YOU KNOW ME or you are a Microsoft
MVP/Employee.
Use my support page on my website to submit your questions directly.

And my book is coming!


Quote:> what's the easiest way to move the Terminal Services (TS) License
> Service (TSLS)...

> currently have a single NT4 domain with a w2k member server running TS
> which also has the TSLS installed and activated. I haven't yet
> installed any TSCALs but have had a few w2k clients connect.

> as the plan is to migrate to w2k domain and TSLS needs to be on a
> Domain Controller, I want to move it off the existing TS server to a
> new w2k member server which can be made into a DC.

> my approach was simply going to be to install/activate TSLS on the new
> box and deactivate on the old box - there shouldn't be a need to
> actually uninstall the TSLS although if I can I'd prefer to.

> I can't see that this has any implications for the existing licences
> as they are 'built-in' to the clients that have connected so far. When
> they first connect to the new TSLS the entries should be re-created.

> What I'm not clear about is whether the TS writes a token back to the
> w2k clients, and if so how this would be interpreted by the new TSLS.

> Also, do I need to inform MS Clearinghouse that old TSLS has been
> deactivated and get rid of the certificate?

> TIA
> pet


 
 
 

1. Terminal Services Licensing and Activation, Terminal Services Licensing and Ac

Hi,

I have a client that has already purchased 10 Windows 2000
Terminal Services CALS through Open License Program (OLP
NL).

He installed and activated the 10 licenses in its
corporate lan.

Now he wants to built 10 more small networks with:
1x Windows 2000 Server
3x Windows 2000 CALS
3x Windows 2000 Terminal Services CALS
3x Thin Clients as Terminals

Every network will be autonomous with no connection to
the corporate lan, its own Terminal Services License
Server and own small Active Directory.

My question: Which is the right way for purchasing the
additional Terminal Services Licenses?

1. A single order for 30 additional TS CALS (OLP NL)
2. Multiple orders for 10x3 additional TS CALS (OLP NL)

Thanks in advance,

Christos

----------------

When using Thin Clients you have to buy TS CALS.

The setup for every-one of the small networks
will be the following:


3x Windows 2000 CALS OLP NL
3x Windows 2000 Terminal Services CALS OLP NL
3x Windows Based Terminals (Thin Clients) as Desktop
Devices

Servers will have installed their own Active Directory,
TS License Server.

Every TS License server must have activated 3 tokens,
each for every seat. A total of 3 License Tokens for
every of the 10 networks = 30 TS Licences/TS License
tokens.

My question: Which is the right way for purchasing the
30 additional Terminal Services Licenses and Activate
the tokens?

1. With a single order for 30 additional TS CALS (OLP NL)?
2. With multiple orders for 10x3 additional TS CALS (OLP
NL)?

2. How to connect a Sun monitor to VGA card?

3. Terminal Services Licensing and Activation:::::Terminal Services Licensing and A

4. Exchange mailing list

5. The Terminal Services Licensing service terminated with service-specific error 3221291009.

6. New AT&T Calling Card PIN

7. Terminal Service Licensing Service don't work

8. The Pawn Walkthru 3 of 4

9. Terminal Services License Server on same box as Terminal Services?

10. Can Terminal Service, but Can't Terminal Service out

11. Urgent: How do I move the TS licensing service from one DC to another?

12. Win2k Cluster Service 'Service Account' 'Log on a as a service"

13. terminal services licensing service