L
lozza
Guest
Guys,
I guess this is quite a niche topic as I cant find much out there. I have
even read and re-read the SessionDirectory.doc from Microsoft and cant seem
to figure out what I am looking for... Here is my scenario.
2 TS Servers
1 Session Directory Server hosted on a Cluster
DNS Load Balancing being used at present
TS Servers are hooked into the SD... everything works great.
A given user can RDP to the Cluster name (VIP) and connect to either TS1 or
TS2. If user connects to TS1 and disconnects session this is fine as well.
When that users establishes an RDP session to the Cluster name (VIP) again,
whether he is dropped onto TS1 or TS2 for logon credentials, his disconnected
session is always re-connected via Session Directory... FANTASTIC!
So problem I am looking into is this. Given the above scenario, User
connects to the Cluster name (VIP)... establishes a connection to TS1, and
disconnects:
1) If TS1 is shutdown properly, then an event is triggered on the SD server,
to say TS1 successfully left the session directory. If the user establishes a
RDP session again to the Cluster name, then the user ends up on TS2, (as TS1
is down and SD knows about it.) logs in and starts a new session on TS2.. good
2) If TS1 is not shutdown properly i.e. if I go in and disable the NIC on
TS1 or pull the network cable, the Session Directory still thinks the user
still has a session on TS1. So what happens here is... User connects to the
Cluster name (VIP) and is directed to TS2 (fine, becuase DNS roundrobin deals
with TS1 being down)... User enter credentials on TS2, TS2 checks Session
Directory for any existing sessions. TS2 is told by Session Directory that
this user has an existing session on TS1 and directs the client to TS1... and
what happens here? you guessed it! user gets error to say 'cannot connect,
server maybe busy, check RDP is on, check network settings etc etc...'
Does this make sense...? and how do you get the Session Directory to also
poll the TS Servers to ensure that users can still have a session on the
other server if one server disappears from the network that had a session on
the this 'disappeared server' without checking in with session directory
first?
Lozza
I guess this is quite a niche topic as I cant find much out there. I have
even read and re-read the SessionDirectory.doc from Microsoft and cant seem
to figure out what I am looking for... Here is my scenario.
2 TS Servers
1 Session Directory Server hosted on a Cluster
DNS Load Balancing being used at present
TS Servers are hooked into the SD... everything works great.
A given user can RDP to the Cluster name (VIP) and connect to either TS1 or
TS2. If user connects to TS1 and disconnects session this is fine as well.
When that users establishes an RDP session to the Cluster name (VIP) again,
whether he is dropped onto TS1 or TS2 for logon credentials, his disconnected
session is always re-connected via Session Directory... FANTASTIC!
So problem I am looking into is this. Given the above scenario, User
connects to the Cluster name (VIP)... establishes a connection to TS1, and
disconnects:
1) If TS1 is shutdown properly, then an event is triggered on the SD server,
to say TS1 successfully left the session directory. If the user establishes a
RDP session again to the Cluster name, then the user ends up on TS2, (as TS1
is down and SD knows about it.) logs in and starts a new session on TS2.. good
2) If TS1 is not shutdown properly i.e. if I go in and disable the NIC on
TS1 or pull the network cable, the Session Directory still thinks the user
still has a session on TS1. So what happens here is... User connects to the
Cluster name (VIP) and is directed to TS2 (fine, becuase DNS roundrobin deals
with TS1 being down)... User enter credentials on TS2, TS2 checks Session
Directory for any existing sessions. TS2 is told by Session Directory that
this user has an existing session on TS1 and directs the client to TS1... and
what happens here? you guessed it! user gets error to say 'cannot connect,
server maybe busy, check RDP is on, check network settings etc etc...'
Does this make sense...? and how do you get the Session Directory to also
poll the TS Servers to ensure that users can still have a session on the
other server if one server disappears from the network that had a session on
the this 'disappeared server' without checking in with session directory
first?
Lozza