2008 TS Session Broker

[BridgeRE]

Anyone using it? I've read about it, but is there an advatage to using it? or not using it?

 

[kmcferrin]

IIRC, all it does it keeps track of which server each session is connected to so that in the event of a disconnect they can be re-connected to their running session. If you have a single terminal server then you wouldn't need it.

________________________________________
CompTIA A+, Network+, Server+, Security+
MCSE:Security 2003
MCITP:Enterprise Administrator

 

[BridgeRE]

Actually I run 5 Terminal Servers, but only is 2008 so far. So I don't think I really care if a user gets their same session or not, sso I gues I'll pass, thanks.

 

[kmcferrin]

Just keep in mind that if people have a tendency to close out of terminal sessions instead of logging out, the session will stay logged in and disconnected until you log them off manually (unless you have set idle timeouts).

________________________________________
CompTIA A+, Network+, Server+, Security+
MCSE:Security 2003
MCITP:Enterprise Administrator

 

[BridgeRE]

Yes, I have a GPO that has the timeouts set. And our home grown app had has logoff.exe as the last statement after the click exit.

 

[w33mhz]

Well I have read that it will only work if you have W2k8 Enterprise or Datacenter. I haven't actually tested it to see if it will work with standard. It will let you configure it in std.

 

[BridgeRE]

I run ENT. But I think I'm going to pass for now, until I see something that's "cool" about it.

 

[w33mhz]

well it keeps the user session alive if they get disconnected. But the kicker is that if you are doing loadbalancing it will push that session to a different server.

 

[BridgeRE]

I believe the session broker will always try to give a user the same session on the same server, unless the server is down, at that time it will connect them to another server in the farm.