Michaelgrey
asked on
VMware Idle timeout setting?
Trying to find where I can change/set the idle timeout for the thin clients. VMware3.1
in other words, if someone is logged into a wyse terminal in to their vm and they leave their machine idle for a certain amount of time, it will disconnect. I would like to know 'what' that default timeout is, and if I can change it.
thanks
in other words, if someone is logged into a wyse terminal in to their vm and they leave their machine idle for a certain amount of time, it will disconnect. I would like to know 'what' that default timeout is, and if I can change it.
thanks
Michael Worsham
Are they connecting from the thin client (i.e. WYSE Terminal) to a Windows desktop instance which is running on the VMware Server?
ASKER
Yes, that is correct. WYSE terminal to a windows instance on VMware servers. The terminals will disconnect after a certain time of idle-ness. Not exactly sure of the time but somewhere in the 30min to 45min timeframe. Not sure if this is the Wyse or VMware... but not seeing anything in the Wyse setup about idle timeouts.
Actually it's Windows that is causing it. Wyse Terminals are connecting via a RDP (Remote Desktop Protocol), thus there is a Group Policy (GPO) that is handling the timeout length.
Are the terminals connecting to a Windows XP, Server 2003 or Server 2008 instance?
Are the terminals connecting to a Windows XP, Server 2003 or Server 2008 instance?
ASKER
They are connecting to a Windows XP instance.
I did check the GPO and all those settings under both Computer Config and User Config are set to 'NOT CONFIGURED' -- is there a defaullt timeout even if the setting is 'not configured'??? Just curious.
So I 'should' be able to set the 'sets a time limit for active but idle Terminal Services Sessions' line to Enabled and then set the limit to either never or the value I chose????
If there is a default even for not-configured does anyone know what that default is??
thanks!
I did check the GPO and all those settings under both Computer Config and User Config are set to 'NOT CONFIGURED' -- is there a defaullt timeout even if the setting is 'not configured'??? Just curious.
So I 'should' be able to set the 'sets a time limit for active but idle Terminal Services Sessions' line to Enabled and then set the limit to either never or the value I chose????
If there is a default even for not-configured does anyone know what that default is??
thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
In the View client administrator gui, you can set how long the session should be valid for. Have you checked that setting? I think default it 600 minutes though...