Maybe that's a newbie questions, but I'm a newbie. Now that you know what NLB means and how it works, it is time to add another Microsoft tool to the picture: Session Directory. Microsoft Network Load Balancing (NLB) with Session Directory. The target is to provide a good performance and save costs using servers just when they are needed. The recommmended scenario for enabling the BIG-IP WTS persistence feature is to create a load balancing pool that consists of servers running Windows. If you missed the previous article in this series please read Load Balancing Terminal Services: All you wanted to know but were afraid to ask (Part 1).
Is it possible to move their sessions between the servers to be able to shut them down? Or do we have to wait until midnight when they all finished their work to be able to shut them down? Now 10 users of Server 1 and 10 users of Server 2 are finishing their work and in total we have 30 sessions left. 2X LoadBalancer for Terminal Services / Citrix allows you to load balance RDP/ICA sessions between Terminal Servers and provide fault tolerance. But how to proceed with the reduction of the load. Since Microsoft Terminal Services Servers support many users, it's important to ensure that each Terminal Server is fully redundant and that the load is distributed between servers ensuring optimal service quality for users. If the maximum is exceeded, a second server is to be added and so on. Means: Up to 20 sessions, only one server exists. The environment is to be migrated to the Google Cloud and provide server power as needed. During the rush hour its about ~25 sessions per server. I'm pretty new in the cloud technology and have some general questions for my understanding and maybe you can share your experience with me.Ĭurrently 3 windows virtual machines are running and providing users access to it via Citrix to be able to work with an installed software.
0 kommentar(er)
