Second TS

[College Guy]

We are going to be adding about 20 extra TS users to our
environment in the next three weeks. Our current TS could
not handle this extra load. So, we have been given the
green light to purchase a second Server and the additional
licenses for these 20 extra TS users.

So, here is my newbie question: how do I set it up when
adding the second TS to our environment? The 20 current
users will use the existing TS and the 20 new users will
use the new TS? We are currently using RDP ( for both
internal and external access ). Am I making this more
difficult than I need to? Just configure the new users
RDP client to point to the IP Address of the new TS
internally seems clear. But what about externally?

And my biggest fear is when Frank ( one of the existing
users ) uninstalls his RDP client at home, reinstalls it
and then calls Bob ( one of the new users ) for the
settings. Frank needs to access the old TS, not the new
TS.

Sonny

 

[Guest]

What most people do is load balance the servers and let people connect to whichever machine is most available. So long as they have the same software loaded and users have Roaming Terminal Server Profiles, the user doesn't know or care which server they connect to

Claudio Rodrigues makes an excellent, intelligent RDP Load balancer called WTSGateway Pro, which is available from http://www.terminal-services.net. This allows you to load balance 2 or more Windows Servers w/o having to purchase Windows Server Enterprise Edition

The other ways to load balance TS are the bulit-in Microsoft way

Load balancing and terminal server
http://www.microsoft.com/resources/.../2003/standard/proddocs/en-us/ts_pln_c_060.as

Designing, Deploying, and Managing a Load Balanced Terminal Server Far
http://www.microsoft.com/technet/pr...03/introduction/virtualconf/deploy/vcon91.msp

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co

----- College Guy wrote: ----

We are going to be adding about 20 extra TS users to our
environment in the next three weeks. Our current TS could
not handle this extra load. So, we have been given the
green light to purchase a second Server and the additional
licenses for these 20 extra TS users

So, here is my newbie question: how do I set it up when
adding the second TS to our environment? The 20 current
users will use the existing TS and the 20 new users will
use the new TS? We are currently using RDP ( for both
internal and external access ). Am I making this more
difficult than I need to? Just configure the new users
RDP client to point to the IP Address of the new TS
internally seems clear. But what about externally

And my biggest fear is when Frank ( one of the existing
users ) uninstalls his RDP client at home, reinstalls it
and then calls Bob ( one of the new users ) for the
settings. Frank needs to access the old TS, not the new
TS

Sonny

 

[College Guy]

Patrick,

Thank you for the tips. I have looked them over and have
a question or two for you. Please excuse my ignorance as
I am somewhat new to all of this.

Q #1: We have a WIN2000 Member Server running TS. This is
a good thing ( in that it is not a DC ). We will be
adding a second WIN2000 Member Server. How do I
accomplish this Network Load Balancing?


Q #2: I was playing with WIN2003 Enterprise Edition this
weekend ( have the evauluation copy ). It looks like
there is a built-in Network Load Balance check box on each
network card's properties. This seems really nice. My
confussion is this: if there are two member servers
running TS in the environment how would I do
the "cluster"? If 192.168.0.10 is the DC on which I have
the service running and 192.168.0.12 and 192.168.0.13 are
the two member servers where TS is running which IP
Address do I add on the Cluster Parameters tab? I assume
that I would have to give both hosts the same Priority (
on the Host Parameter tab ) so that we have true network
load balancing?

I have looked at the Help but this does not clarify things
for me.

Thanks,

Sonny

-----Original Message-----
What most people do is load balance the servers and let

people connect to whichever machine is most available. So
long as they have the same software loaded and users have
Roaming Terminal Server Profiles, the user doesn't know or
care which server they connect to.

Claudio Rodrigues makes an excellent, intelligent RDP

Load balancer called WTSGateway Pro, which is available
from http://www.terminal-services.net. This allows you to
load balance 2 or more Windows Servers w/o having to
purchase Windows Server Enterprise Edition.

 

[Matthew Harris [MVP]]

answers are inline...

-----Original Message-----
Q #1: We have a WIN2000 Member Server running TS. This is
a good thing ( in that it is not a DC ). We will be
adding a second WIN2000 Member Server. How do I
accomplish this Network Load Balancing?

I would look up network load balancing on the
knowledgebase. As far as I know, Windows 2000 only
supports NLB with the Advanced Server version only. This
might be incorrect, so please verify this.

Q #2: I was playing with WIN2003 Enterprise Edition this
weekend ( have the evauluation copy ). It looks like
there is a built-in Network Load Balance check box on each
network card's properties. This seems really nice. My
confussion is this: if there are two member servers
running TS in the environment how would I do
the "cluster"? If 192.168.0.10 is the DC on which I have
the service running and 192.168.0.12 and 192.168.0.13 are
the two member servers where TS is running which IP
Address do I add on the Cluster Parameters tab? I assume
that I would have to give both hosts the same Priority (
on the Host Parameter tab ) so that we have true network
load balancing?

When you load balance each load balanced server gets the
same virtual IP address which you can then use to connect
to the cluster. When you connect to that virtual ip
address, the load balancer then figures out which server
needs to get the connection, and forwards your connect to
the particular server.

-M