StepbyStepGuideforConfiguringNetworkLoadBalancingwithTerminalServicesinWindowsServer2.docx

1、StepbyStepGuideforConfiguringNetworkLoadBalancingwithTerminalServicesinWindowsServer2Step-by-Step Guide for Configuring Network Load Balancing with Terminal Services: Windows Server 2008Microsoft CorporationPublished: March2008Author: Susan BoherEditor: Ronald LoiAbstractThis step-by-step guide prov

2、ides the instructions necessary to configure Network Load Balancing (NLB) with Terminal Services for the WindowsServer2008 operating system. This guide also includes instructions on installing and configuring NLB and setting up a terminal server.Information in this document, including URL and other

3、Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product

4、, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retr

5、ieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectua

6、l property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. 2008 Microsoft Corporation

7、. All rights reserved.Microsoft, MS-DOS, Windows, WindowsNT, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.This product contains graphics filter software; this software is based in part on the work of the Indepe

8、ndent JPEG Group.All other trademarks are property of their respective owners.ContentsStep-by-Step Guide for Configuring Network Load Balancing with Terminal Services in Windows Server 2008 5NLB with Terminal Services overview 5Terminal Services components 6Terminal Services Session Broker service 6

9、Terminal Services Configuration snap-in 7Requirements for using NLB with a terminal server 7Steps for configuring NLB with Terminal Services 7Step 1: Set up a terminal server farm with TS Session Broker 8Step 2: Install NLB 10Step 3: Create an NLB cluster 10Logging bugs and feedback 12Additional res

10、ources 12Step-by-Step Guide for Configuring Network Load Balancing with Terminal Services in Windows Server 2008This step-by-step guide provides instructions for configuring Network Load Balancing (NLB) with Terminal Services.Using NLB with Terminal Services offers the benefits of increased availabi

11、lity, scalability, and load-balancing performance, as well as the ability to distribute a large number of Terminal Services clients over a group of terminal servers.NLB with Terminal Services overviewNLB distributes traffic across several servers by using the TCP/IP networking protocol. You can use

12、NLB with a terminal server farm to scale the performance of a single terminal server by distributing sessions across multiple servers. Terminal Services Session Broker (TS Session Broker), included in Windows Server 2008 Standard, Windows Server 2008 Enterprise, and Windows Server 2008 Datacenter, k

13、eeps track of disconnected sessions on the terminal server farm, and ensures that users are reconnected to those sessions. Additionally, TS Session Broker enables you to load balance sessions between terminal servers in a farm. This functionality is provided by the TS Session Broker Load Balancing f

14、eature. However, this session-based load balancing feature requires a front-end load balancing mechanism to distribute the initial connection requests to the terminal server farm. You can use a load balancing mechanism such as DNS round robin, NLB or a hardware load balancer to distribute the initia

15、l connection requests. By deploying NLB together with TS Session Broker Load Balancing, you can take advantage of both the network-based load balancing and failed server detection of NLB, and the session-based load balancing and per server limit on the number of pending logon requests that is availa

16、ble with TS Session Broker Load Balancing.Note To use the TS Session Broker Load Balancing feature, all terminal servers in the farm must be running Windows Server 2008. For more information about the TS Session Broker Load Balancing feature, see the Windows Server 2008 TS Session Broker Load Balanc

17、ing Step-by-Step Guide.When deploying a terminal server farm by using NLB, each server needs to serve all users. To facilitate this, you must store per-user information, system information, and common data in an accessible place, such as a back-end file server.Terminal Services componentsTerminal Se

18、rvices has two components that are important for establishing load balancing: the Terminal Services Session Broker service and the Terminal Services Configuration snap-in.Terminal Services Session Broker serviceThis service maintains a database that keeps track of terminal server sessions in a load-

19、balanced terminal server farm and provides information to the terminal server, which is used to connect users to existing sessions.When the Terminal Services Session Broker service starts, it creates the Session Directory Computers local group. By default, this group is not populated. You must choos

20、e the individual terminal servers or groups that you want to participate in the Terminal Services Session Broker service, and then manually change group memberships to the Session Directory Computers group.The Terminal Services Session Broker service starts automatically after you install the TS Ses

21、sion Broker role service on the server that you want to use to track user session information for a load-balanced terminal server farm. You can use a single TS Session Broker server to track user sessions across multiple farms because there is minimal performance overhead.When you install the TS Ses

22、sion Broker role service, the following changes occur on the local computer: The Terminal Services Session Broker service is installed. By default, the service is set to Started and to Automatic. The Session Directory Computers local group is created.Installation prerequisites The server where you i

23、nstall the TS Session Broker role service must be a member of a domain. The Windows Server2008-based server where you install the TS Session Broker role service does not have to be a terminal server or have Remote Desktop enabled.Note If you install the TS Session Broker role service on a domain con

24、troller, the Session Directory Computers group will be a domain local group, and it will be available on all domain controllers.Installation procedureIf you do not have any of the Terminal Services role services installed, use the following procedure to install the TS Session Broker role service.To

25、install the TS Session Broker role service1. Click Start, point to Administrative Tools, and then click Server Manager.2. Under Roles Summary, click Add Roles.3. In the Add Roles Wizard, review the Before You Begin page, and then click Next.4. On the Select Server Roles page, select the Terminal Ser

26、vices check box, and then click Next.5. On the Terminal Services page, click Next.6. On the Select Role Services page, select the TS Session Broker check box, and then click Next.7. On the Confirm Installation Selections page, confirm that TS Session Broker is listed, and then click Install.8. On th

27、e Installation Results page, click Close.Terminal Services Configuration snap-inThis snap-in is included on each terminal server. Terminal servers that comprise the terminal server farm communicate with TS Session Broker to ensure that users are transparently reconnected to the original server hosti

28、ng their disconnected sessions. The process is:1. When the user logs on to the terminal server farm, the terminal server receiving the initial client logon request sends a query to the TS Session Broker server. 2. The TS Session Broker server checks the user name against its database and sends the r

29、esult to the requesting server. One of the following occurs: If the user has no disconnected sessions, logon continues at the server hosting the initial connection. If the user has a disconnected session on another server, the client session is passed to that server and logon continues.Requirements

30、for using NLB with a terminal serverTo use NLB, a computer must have: At least one network adapter for load balancing. Only TCP/IP used on the adapter for which NLB is enabled. Do not add any other protocols (for example, IPX) to this adapter. All hosts in the NLB cluster must reside on the same sub

31、net. Ensure that the clusters clients are able to access this subnet. All terminal servers in the terminal server farm should be joined to the same domain.Steps for configuring NLB with Terminal ServicesTo configure NLB with Terminal Services, complete the following steps:Step 1: Set up a terminal s

32、erver farm with TS Session Broker.Step 2: Install NLB.Step 3: Create an NLB cluster.Step 1: Set up a terminal server farm with TS Session BrokerFor a terminal server to use TS Session Broker, you must add the computer account for the terminal server to the Session Directory Computers local group on the TS Session Broker server.Important You must perform this procedure on the server where you installed the TS Session Broker role service.To add a terminal server to the Session Directory C