It can be implemented with hardware, software, or a combination of both. Load balancing means distributing the incoming terminal server connections to two or more terminal servers, transparently to your users. If you now have multiple servers, how do you tell your users which server they should connect to? Ideally this should be completely transparent. This is when Load Balancing comes to the picture. The answer, in a certain way, is simple and straight forward: simply add another server, running the same applications, and you will have redundancy.īut the answer is not that simple. After going in production with their first server, the first question that comes to their minds is, “If our TS server goes down, what will happen? How can we prevent that?”. It is that simple.Īs Terminal Services becomes mainstream (thanks to Microsoft for making it part of the Windows Server OS), pretty much every company, large or small, knows what Terminal Services is and they probably have played with it a little bit. We want our readers to simply have a better understanding of what Load Balancing is, the most common features you should look for and what your options are (with all their PROs and CONs). This article does not intend to go in depth on how you actually configure/use every single option mentioned here. If you would like to read the next article in this series please go to Load Balancing Terminal Services: All you wanted to know but were afraid to ask (Part 2).Īgain, as in most of my articles, I just want to point this one was written for all the guys out there now thinking about expanding their one server environment or even trying to find out if they could improve the way they are currently load balancing their multi-server environment.
0 kommentar(er)
