Contents I. Microsoft Windows Terminal Services. What Is Windows Terminal Services? Citrix MetaFrame Presentation Server. Project Management Considerations. Network Planning. Client Hardware and Software Planning. Terminal Server Hardware Planning. Server and Application Software Planning. Server Installation and Management Planning. Service Pack and Hotfix Management. Installing Windows Terminal Services. Terminal Services Configuration and Tuning.
Licensing Service Installation and Configuration. MetaFrame Presentation Server Installation. When using Windows NLB, all servers must be on the same subnet. A portion of the incoming network traffic can be received by the host. Windows Network Load Balancing works at the network level by distributing the network client request between hosts. Windows NLB is limited to a maximum number of 32 possible hosts in any one cluster.
Also, as its name implies, Windows Network Load Balancing is only able to determine which server is the least-busy based on network load. If one server has failed but is still responding to the network, the NLB system will continue to send users to it. One major limitation of Windows Network Load Balancing is that you can only use it to load balance 32 servers. If you need more than 32 servers in your cluster, you must implement one of the following options:. Make sure that each cluster has the same number of servers, or adjust your round robin ratio accordingly.
At this point you may be thinking that a DNS round robin solution could suffice for simple load balancing. However, a DNS round robin scheme will continue to send connections to the server that has failed until a change is manually made to the DNS entry. This article is not meant to an exhaustive study of Windows Network Load Balancing. In an ideal world, each of your Terminal Servers within in the cluster would have two network cards. There are several configuration options to understand when using NLB in a Terminal Server environment.
These should be the same on all Terminal Servers in the cluster. Both unicast and multicast modes have benefits and drawbacks.
One benefit of unicast mode is that it works out of the box with all routers and switches since each network card only has one MAC address. For reference and comparison with Remote Desktop Services, details of how the naming of components changed can be found here. Load balancing Microsoft Terminal Services.
Useful resources blog deployment guide manual. Example deployment showing load balanced Terminal Servers. In the Properties dialog, set Startup Type to Automatic. Click Start. Double-click Server Settings in left pane to expand it. Double-click Session Directory. In the Cluster name field, enter a cluster name.
You must use the same cluster name on every server. Windows Server will sometimes try to reconnect to the farm using the loopback adapter. Instead, it must always use the real interface. Setting a high value for the interface metric field of the loopback adapter of each Real Server will ensure the real interface is used. It is recommended that you do these steps if you have Windows Server or Windows Server installed. On each Real Server, reprioritize the interface so that the loopback adapter is not used for reconnection: On the Control Panel, click Network and Sharing Center.
Click Manage network connections. Right-click the loopback adapter and then click Status. On the loopback Status dialog, click Properties. On Windows Server , double-click IPv4. Click Advanced At the bottom of the page, clear the Automatic metric check box. In the Interface metric field enter Restart the Real Server to make it rejoin the farm. View the Terminal Services event log to verify reconnection. Click Terminal Services. An Event indicates a successful connection. An error indicates a failure to connect to the server farm.
Click System to see all events. An Event with a source of TermServJet indicates a successful connection.
0コメント