• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 343
  • Last Modified:

Session Directory on Terminal Servers

I have created a 2 sever network load balanced terminal server cluster.  Both have Windows 2003 Enterprise and I have created a Session Directory on a third server.  I used a GPO and have done all of the preliminary work such as adding these servers to the Session Driectory group and have started the session directory service on the 3rd server holding the database.  Each server reports in the event viewer that it has joined the Session Directory successfully.  This morning I connected to the cluster, opened a word document and started typing an example and after confirming which server I actually connected to I unplugged the network cable to that server.  When I tried to connect to the cluster again it would not let me connect.  I was under the impression that a session directory setup would provide high availabilty by allowing me to reconnect to another server in the cluster and putting me back into my word document or whatever else I was doing when the server "wnet down".  Not only did it not do that, I was prevented from connecting to the cluster as that user because it still saw my session as being open.  Am I missing something or is this how it's supposed to work?  If that's the case what is the real benefit of using a session directory on top of using network load balancing?  It seems like the session directory is working against me in this scenario as I am unable to get back to any server in the cluster.  Any thoughts or comment would be much appreciated.
1 Solution
Cláudio RodriguesFounder and CEOCommented:
Session directory simply allows you to RECONNECT to the correct server in case YOUR PC goes down for some reason and you come back later.
Imagine having 5 TSs and you are on TS1. If you get disconnected on the client side (network issue on the client end) when you reconnect, how they know on which TS you were on? This is what Session Directory is for, to find where your session is and to reconnect you there. Nothing else.
It is not supposed to create a 'cluster' of servers and replicate their memory/disk contents so if TS1 crashes your 'session' continues running on a different server.
There is NO SUCH solution for Terminal Services or Citrix.
And by the way, avoid Session Directory. Not only it does not work properly, it does require Enterprise (as you realize, at 4x the cost of regular standard). You are much better off something like 2X LoadBalancer.


Cláudio Rodrigues
Microsoft MVP
Windows Server - Terminal Services
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now