The Problem
Control R15.2 applied a new default of 15 minutes to the "Connected Idle Timeout" parameter. This default is used only when no Time Limits policy has been applied to a pool.
Unfortunately, unlike most of the other parameters, "Connected Idle Timeout" takes effect on every kind of pool: persistent as well as non-persistent, consumption billing vs. legacy, and hourly vs monthly/annual.
The default of 15 minutes is appropriate for hourly, non-persistent pools, where it disconnects the user as the first stage of a two-stage timeout process (the second being "Disconnected Timeout." But for every other kind of pool, it's inappropriate as a default, and "None" is the right value.
(Pools that can use pause/resume have a similar but different parameter, "Disconnect on Idle," that is used instead. Legacy pools should not have idle timeouts suddenly applied by default. In both cases, "Connected Idle Timeout" should be "None."
The Upcoming Fix
This will be backed out around May 18 and the default value of "Connected Idle Timeout" will be "None" for all pools. This will remove the idle disconnect from hourly/non-persistent pools, but is appropriate for all other pools.
Customers with hourly/non-persistent pools should apply a custom Time Limits policy that specifies reasonable values.
The Workaround
For persistent/non-hourly pools, the workaround is to define a Time Limits policy that sets "Connected Idle Timeout" to "None." The other parameters can be set to sensible values. These will be ignored on non-consumption-billing pools, anyway. See the procedure for persistent pools in Time Limit Policies and change the "Connected Idle Timeout" to "None" instead of what it recommends.
Steps To Complete The Work Around:
For Persistent Desktop Pools
Sign into Workspot Control as an Administrator and navigate to "Policies > Add a New Policy."
Fill out the "Add a New Policy" form. The forms are different for persistent and non-persistent target pools.
Policy Name. Enter a name in the "Policy Name" field.
Policy Type. Select "Time Limits" from "Policy Type" dropdown.
Resource. Select "VDI" as the "Resource." ("VDI" is another term for "desktop pool.")
Pool Usage Type. Select "Named" as the "Pool Usage Type." ("Named" is another term for "persistent pool.")
Desktop Availability Scheduling. All but one of the settings for persistent pools are in the "Desktop Availability Scheduling" section.
Shift Duration. This is typically set to the user's standard shift length (clock-in to clock-out). Leave at its default of nine hours.
Minimum Time Between Shifts. This gives the shortest amount of time between the end of one shift and the start of another. At first glance, this would be (24 hours - Shift Duration), but to accommodate users signing in earlier on some days than others, it should be less. Leave at its default value of twelve hours.
Disconnect on Idle. The TCP connection is closed once the desktop is idle (no keyboard or mouse activity) for this period. The state of the desktop is unchanged: the user can reconnect and continue as before. Valid settings are between five and thirty minutes. A two-minute warning is given before disconnecting, giving the user time to provide input to keep the connection going. Set this to a value that causes few user complaints.
Sleep after Disconnect. The desktop is put to sleep after the session has been disconnected for this period. Sleep puts the desktop into a deep power-saving mode. Valid settings are between two and thirty minutes. Users will experience a brief delay when the desktop wakes, after which they continue working as before. Set this value high enough that users who were disconnected accidentally are not inconvenienced.
Time Limits. Set "Connected Idle Timeout" to "None".
Save Policy
For Non-Persistent Desktop Pools:
Policy Name. Enter a name in the "Policy Name" field.
Policy Type. Select "Time Limits" from "Policy Type" dropdown.
Resource. Select "VDI" as the "Resource." ("VDI" is another term for "desktop pool.")
Pool Usage Type. Select "Concurrent" as the "Pool Usage Type." ("Concurrent" is another term for "non-persistent pool.")
Desktop Availability Scheduling. Ignore this section.
Time Limits. The settings for non-persistent pools are in this section.
Active Time Limit (optional). This sets the maximum time a desktop session can be active, preventing sessions from lasting indefinitely. The time limit is measured from when the user signs in. The user is signed out when this limit is reached, without being given the option to continue. They are warned that sign-out will happen soon. Valid values range from "None" (forever) to 24 hours.
This is not an idle time limit: user activity has no effect on the timer; neither does time spent disconnected. The only thing that resets this timer is signing out.
Example: if some users have noisy mice whose apparent movements prevent the idle timeouts from working, setting an Active Time Limit to 12 or will sign these users out anyway. This would save money with hourly desktops.Connected Idle Timeout. Set to "None".
Save Policy
Applying a Time Limit Policy to a Desktop Pool
After creating a Time Limits policy, go to the Add/Edit Pools page and select it from the Time Limits Policy pulldown menu.
Please see Control: Time Limit Policies
for more information on Time Limit Policies.
If you have any questions or concerns, please open up a support ticket with Workspot Support through your Control Support Portal.