Windows 7 / Getting Started

---

Create Highly Available Terminal Services

Windows Server 2008 includes the Terminal Services Session Broker Load Balancing (TS SBLB) feature to let you create highly available TS server infrastructures. TS SBLB is performed through an integration of the Domain Name Service (DNS) with the service. Basically, you create a single entry in DNS for the TS farm. Include the IP address of each TS server in the farm into this DNS entry. Also, as seen in Table-4, configure the TS SBLB feature through Group Policy.

When users first connect to a TS session, the Session Broker will automatically connect them to the first IP address in the list, but then redirect them to a TS server with a lower workload. If the connection to the first IP address fails, the Session Broker will connect the user to the next IP address and so on.

This provides a more refined user experience and allows users to disconnect from a session and reconnect to the appropriate session in the farm. If you plan to make extensive use of Terminal Services in your network, especially if you plan to go beyond remote administration, then you should consider working with the Session Broker.

Your Terminal Services environment is now ready for production. Ensure that you use a thorough testing policy before giving users access to the applications you host on your terminal servers.

The Remote Desktop Console

One of the greatest tools you'll find in Windows Server 2008 for remote administration is the Remote Desktops console (RDC). That's because this console lets you regroup all of the RDP connections you need to manage every server in your network in one single place, providing a central location for the administration of your entire network. And, what's even better, you can save the credentials you use to log onto each server within the console, making each server only one click away.

CAUTION: The RDC is a powerful tool since it stores passwords that provide access to servers. Make sure you store the console in your profile to secure it, and make sure you lock your computer any time you leave your desk.

This console is present by default in Administrative Tools, but as you would expect, it is empty. If you want to use it to its fullest, then you need to populate it with your own list of shortcuts. This lets you build an ultimate RDC that provides a central interface and includes connections to every system you need to manage.

If you build it on a server, then you only need to add the shortcut connections. If you build it on a workstation, then you need to install the Windows Server 2008 Remote Administration Tools. Prepare your console as follows:

1. Begin by launching the console. It is located under Start Menu | Administrative Tools | Remote Desktops.
2. Save the console. By default, this console is stored within Administrative Tools, but since you will be saving your credentials with your connections to simplify server access, you should save this console in your Documents folder. This automatically secures it so that only you have access to it. To do so, use File | Save As, move to your Documents folder, name it Remote Desktops, and click Save.
3. Now you can begin to build the console. By default, this console includes one copy of the Remote Desktops snap-in. If you only have one environment to manage, that is fine. But if you build multiple environments for production, testing and you should add one Remote Desktops snap-in for each environment you need to manage. Using multiple snap-ins makes it easier to differentiate between environments. For example, you can differentiate between the resource pools and virtual service offerings by using a different snap-in for each. This makes it clearer and easier to identify the servers of each environment.
4. Then use File | Add/Remove Snap-in to open the dialog box. Select the Remote Desktops snap-in under Available Snap-ins, and click the Add button. Click the Add button as many times as you need the snap-in, once for each environment you manage. Click OK when you're done.
5. You're ready to add a connection with saved credentials for each server. Saving credentials allows you to make faster connections to the remote system. But you need to make sure the console is secure-all the more reason to put it under your Documents folder.
6. In the left pane, first select a Remote Desktops snap-in, and then right-click it to select Add New Connection. Enter the following information:
   • The server name or the IP address
   • The connection name (give a logical name that represents what this connection links to)
   • Clear Connect To Console, since this only applies to Windows Server 2003 systems.
   • Select Allow Me To Save Credentials.
   • Click OK to create the connection.
   • In order to save the credentials, you need to connect to the link. The credentials dialog box will appear. Enter appropriate credentials, and make sure you select the Remember My Credentials check box. Click OK to connect to the server. Your credentials are now saved. If you return to the Properties dialog box, you'll see that it now includes your credentials. Notice the Edit or Delete links that let you modify credentials for this connection.
   • Repeat the same steps for each connection you need in that environment. Move to a different snap-in for each different environment. Save the console again when you're done. Finally, you need to save the console settings to complete the creation of the console.
   • Click File | Options and enter the name of your console. Make sure you set the console mode to User Mode - Full Access and that Do Not Save Changes To This Console is not selected. Also, make sure that Allow The User To Customize Views is selected. Click OK when you're done. Save the console again. Now you won't be prompted to save the console each time you close it.

You're done. Now you can use your console to manage your multiple physical servers or virtual machines in a single interface. For example, an ultimate RDC console could include as many different environments as you need. Moving from machine to machine is as easy as clicking the machine name.

TIP: If the console or the connection becomes unresponsive, simply right-click the connection name and choose Disconnect. Right-click again to choose Connect, and you're right back in.

The connections contained in this console are really nifty and can save you a lot of time. Here are some tips for its use:

• To use the console, just open it and click once on the link you want to connect to.
• To break a connection, either log off from the remote server or right-click Disconnect.
• If you have already connected to a link and you are disconnected, reconnect by right-clicking the link and selecting Connect.
• You'll want to keep connection names short and make sure the tree pane is as small as possible, because Remote Desktop connections will automatically fill the details pane. Maximize the console and maximize the console window to get as much screen real estate as possible for your connections.
• Once your connections are made, you can modify their properties, including such items as screen resolution, linking your local disk drives to the remote machine and more. To make these types of modifications permanent, you need to right-click the console and select Author. This will let you modify settings and save them for next time.
• Once the console is ready, place it in your Quick Launch area. That way, you'll only be one click away from any server you need to administer.

You'll soon find that this is the most valuable console in your administrative toolkit.