This 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 availability, 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.

Windows Server® 2008 Terminal Services Gateway (TS Gateway) is a role service that enables authorized remote users to connect to resources on an internal corporate or private network, from any Internet-connected device that can run the Remote Desktop Connection (RDC) client. The network resources can be terminal servers, terminal servers running RemoteApp™ programs, or computers with Remote Desktop enabled. TS Gateway encapsulates Remote Desktop Protocol (RDP) within RPC, within HTTP over a Secure Sockets Layer (SSL) connection. In this way, TS Gateway helps improve security by establishing an encrypted connection between remote users on the Internet and the internal network resources on which their productivity applications run. The procedures in this guide will help you set up a TS Gateway server, enabling remote users to access terminal servers, terminal servers running RemoteApp programs, or computers with Remote Desktop enabled on your internal corporate or private network.

This step-by-step guide will assist you in using Active Directory Rights Management Services (AD RMS) with Active Directory® Federation Services (AD FS) in a test environment. Specifically, this guide will look at how to implement AD RMS if you have also deployed AD FS in your organization and have established a trust relationship with another organization that has not deployed AD RMS. Using the information in this guide, you can extend the basic AD RMS deployment to use AD FS credentials to establish trusted user accounts. This will enable you to share access to rights-protected content with another organization without having to establish a separate trust.

This step-by-step guide illustrates how to deploy Active Directory® Group Policy objects (GPOs) to configure Windows Firewall with Advanced Security in Windows Vista® and Windows Server® 2008. Although you can configure a single server locally by using Group Policy Management tools directly on the server, that method is not consistent or efficient when you have many computers to configure. When you have multiple computers to manage, create and edit GPOs, and then apply those GPOs to the computers in your organization. The goal of a Windows Firewall with Advanced Security configuration in your organization is to improve the security of each computer by blocking unwanted network traffic from entering the computer. Network traffic that does not match the rule set of Windows Firewall with Advanced Security is dropped. You can also require that the network traffic which is allowed must be protected by using authentication or encryption. The ability to manage Windows Firewall with Advanced Security by using Group Policy allows an administrator to apply consistent settings across the organization in a way that is not easily circumvented by the user. In this guide, you get hands-on experience in a lab environment using Group Policy management tools to create and edit GPOs to implement typical firewall settings. You also configure GPOs to implement common server and domain isolation scenarios and see the effects of those settings.

Storage Manager for SANs is a Microsoft Management Console (MMC) snap-in that helps you create and manage logical unit numbers (LUNs) on Fibre Channel and Internet SCSI (iSCSI) disk drive subsystems that support Virtual Disk Service (VDS) in your storage area network (SAN). Before you deploy Storage Manager for SANs on a production server, we recommend that you use this guide to first familiarize yourself with the different LUN management options in Storage Manager for SANs by installing and running it on a test server.