Thanks for the info, think we have gotten to the bottom of this. We had some Terminal Services GPOs deploying some settings (maximum connections and the like), but it seems as though it had previously been used to set disconnection settings on the ICA-TCP connection, and removing this configuration in the GPO has not removed the settings (as sometimes they are prone to). Unlinking these GPOs and forcing an update appears to have gotten rid of the settings.
I thought it was going to be a setting on the thin clients via Xcalibur, but as usual, it pays to try and cover all of your bases :-) Cheers, 2009/3/11 Webster <carlwebs...@gmail.com> > *From:* James Rankin [mailto:kz2...@googlemail.com] > *Subject:* Re: Citrix with Chip PC thin clients > > > > I meant the Keep-Alive interval > > > Session Reliability is at five minutes last I checked > > Then you have to wait 301 seconds before checking. Session Reliability say > to wait 300 seconds for the same client ID to reconnect. At 301 seconds > attempt to break down the session connection. > > Have you seen the massive flowchart for Citrix logoffs and disconnects? > > > http://www.brianmadden.com/blogs/brianmadden/archive/2006/10/09/the-excruciating-detail-of-the-citrix-logoff-process.aspx > > Webster > > 2009/3/11 Webster <carlwebs...@gmail.com> > > *From:* James Rankin [mailto:kz2...@googlemail.com] > *Subject:* Re: Citrix with Chip PC thin clients > > > > We have Session Reliability at 30 seconds, and when the 30 seconds elapses, > they just go straight to a *Down* (reset) status > > Not to be rude, but what is the point then of using Session Reliability? > Do you understand the intentions behind Session Reliability? > > Webster > > > > > > > > > > > > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
