- This topic has 2 replies, 2 voices, and was last updated 5 years, 4 months ago by
.
-
Posts
-
Hi guys and Thomas,
I was wondering if you could share your experience with “Reconnect=yes” feature. The issue I’ve seen for years in different firmware versions and Wyse models is after network disruption or session disconnect happens, “Reconnect=yes” starts counting down and reconnect terminals to their sessions, however, it stops keep trying after some time, it is not doing it indefinitely.
In my environment this is problematic as if network (or any other) disruption lasts longer than 30-60min, my IT support team needs to remote to every of hundreds of the terminals and just click “OK” on whatever “Error!” is displayed on the screen. This reconnects terminals to their sessions fine. It is a manual intervention which has slowed down recovering from multiple different outages in my business which cost it lots of money.
I am missing any way to set terminals to keep trying to reconnect to their XenApp sessions indefinitely or there is a hidden timeout in the “Reconnect=yes” command?
Thank you for your help,
The only option is to use Reconnect=seconds, which seconds being between 1 and 3600.
However, this only set the amount of seconds ThinOS waits until trying to reconnect.CG
Thanks a lot Thomas.
To me it seems like 3600 seconds is the default reconnect timeout then, as this is what we experiences in production incidents we’ve had.I will speak to Wyse Support about it and request it to be changed so “Reconnect=yes” command without any timeout specified, reconnects indefinitely.
Regards,
- You must be logged in to reply to this topic.