Adding Redundancy to Session Directory

To avoid the Session Directory from becoming a single point of failure you can configure Session Directory to run as a clustered service using Microsoft's clustering technology. You create the cluster by following these steps:

1. Set Terminal Services Session Directory Server service to Automatic.

2. Ensure that the following resources are available in the server cluster configuration:

   • Physical Disk In addition to the quorum disk, the cluster will require a shared disk for the shared data. This shared data disk must be able to failover to all nodes in the cluster that you want to be able to host the Terminal Services Session Directory database.

   • IP Address A static IP address accessible from all the terminal servers that will be configured in the load balancing cluster.

   • Network Name A name that is resolvable from all the terminal servers in the cluster. Kerberos is required for all communication between the terminal server and the Session Directory server. Make sure to select Enable Kerberos Authentication and DNS Registrations Must Succeed before bringing the network name resource online.

3. Select File, New, Resource. This will start a wizard. Enter the name and description, and set the resource type to Generic.

4. Click Next and accept the defaults.

5. Define your dependencies. Specify the Physical Disk and Network Name resources.

6. Define the Generic Service Parameters. Specify the service name, TSSDIS, in the Service Name box, and check the box next to Use Network Name for Computer Name.

7. Configure Registry Replication. Click Add and type System\CurrentControlSet\Services\Tssdis\Parameters.

8. Click Finish.

9. Bring the new service resource online.

Clustering the Session Directory Servers

You must be using Windows Server 2003 Enterprise or Datacenter edition to be able to cluster the Session Directory servers.