Unsolved
This post is more than 5 years old
16 Posts
0
10034
February 24th, 2011 10:00
'Reconnect if connection is dropped', SessionRoamingMode and fDisableAutoReconnect
Hi all,
I am trying to understand the relationship between the following
'Reconnect if connection is dropped' (Web Access EOP setting)
SessionRoamingMode (Connection Broker registry value)
fDisableAutoReconnect (Virtual Machine registry value)
Questions i have
1. If there is a break in the TCP connection between a Client and a Virtual Machine, will pntsc try to reconnect to the same Virtual Machine if 'Reconnect if connection is dropped' is enabled and if so for how long (and is this configurable)?
2. If pntsc reconnect has a timeout, then if this occurs and a user clicks on the same Computer Group icon on their Web Access page (without logging out), will they get a session to a different Virtual Machine if SessionRoamingMode is not set to 1?
3. How is 'Reconnect if connection is dropped' related to the HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\fDisableAutoReconnect registry value on the Virtual Machine; does it set this registry value or does it set the property to automatically reconnect within the connection file?
All replies gratefully received
DELL-Andrew W1
378 Posts
0
March 2nd, 2011 13:00
1. This is the same idea as in MSTSC | Options | Experience | Reconnect if the connection is dropped. It should try to reconnect to the same vdi.
2. The CB should check for disconnected sessions and reconnect the user to their old session
3. So, the option listed in question 1 is client side. The option listed here in 3 is server side. Server side will override Client side.
Hope this helps,
Andrew.