The Session Directory server can be any Windows Server 2003-based computer that is visible on the network and that is running the Terminal Services Session Directory service. As a best practice, the Session Directory server should be a highly available network server that is not a terminal server.
There are two methods you can use to configure Session Directory settings:
Use Group Policies (Best Practice)
- Click Start, click Run, type gpedit.msc, and then press ENTER.
- Double-click the following items, and then enable the Session Directory Active policy:
- Computer Configuration
- Administrative Templates
- Windows Components
- Terminal Services
- Session Directory
- Enable the Session Directory Server policy, and then type the name of the server where the Terminal Services Session directory service is running in Session Directory Server.
- Enable the Session Directory Cluster Name policy, and then type the name of the cluster to which the Terminal Server belongs in Session Directory Cluster Name.
Use the Terminal Services Configuration Tool
- Click Start, point to Administrative Tools, and then click Terminal Services Configuration.
- In the console tree, click Server Settings.
- In the Details pane, right-click Session Directory, and then click Properties.
- Click to select the Join session directory check box.
- In the Cluster name box, type the name of the terminal server cluster for this terminal server.
- In the Session directory server name box, type the DNS name or IP address of the domain server where the Terminal Services Session Directory service is running. Note that the server name must be a valid server name, and you cannot leave this box empty. Also, the server name cannot be localhost or 127.0.0.1.