RE: Second TS

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Patrick Rouse [MVP] (anonymous_at_discussions.microsoft.com)
Date: 03/06/04 

Date: Sat, 6 Mar 2004 13:21:07 -0800

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 servers
http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/ts_pln_c_060.asp

Designing, Deploying, and Managing a Load Balanced Terminal Server Farm
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/introduction/virtualconf/deploy/vcon91.mspx

Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com
     
     ----- 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
     
     

Relevant Pages

  • RE: Second TS
    ... We have a WIN2000 Member Server running TS. ... there is a built-in Network Load Balance check box on each ... Terminal Server Farm ... > RDP client to point to the IP Address of the new TS ...
    (microsoft.public.win2000.termserv.clients)
  • Re: Citrix vs Teminal Service
    ... As for "not as secure as Citrix" comment, if you were to install a Citrix ... Secure Gateway for users to access the terminal servers over SSL, ... Windows CALs and Terminal Server CALs. ... Load balance your server farm based on metrics like CPU Load, ...
    (microsoft.public.windows.terminal_services)
  • Re: Questions
    ... Session Directory and Load Balancing Using Terminal Server White ... >> To load balance the TSs you can use NLB for sure but as I said, ...
    (microsoft.public.windows.terminal_services)
  • Re: Load balancing roaming profiles
    ... Microsoft MVP - Terminal Server ... Does anyone know of a way to load balance or split up the load on the ...
    (microsoft.public.windows.terminal_services)