ControlUp classifies Insights user sessions as Active or Idle. The session state is displayed, both in Insights and in the console.
When viewing user session reports in Insights, the user session state is displayed as Active or Idle. The Idle/Active status of a session is based on the time elapsed since the last user input was received in the user session.
By default, sessions are set to timeout and become idle after 30 minutes. For example:
If a session is in Active State AND the Idle Time is lower than 30 minutes, the session is considered active.
If a session is in Active State AND the Idle Time is higher than 30 minutes, the session is considered idle.
This can be modified to suit your needs as described in the section below.
In the examples below, the default setting of 30 minutes is in use.
The following is an example of how the user session state appears in Insights:
The following is an example of how the user session state and idle time are displayed in the console:
The idle timeout can be modified per machine via the machine's registry editor.
To modify the idle time timeout:
- Open Regedit.exe on an agent computer.
- From the computer's registry, locate and select the following registry entry:
- If the IdleTime value does not appear in the Registry, you need to create it by right-clicking Agent > New > DWORD, and a new value appears in the Registry.
Right-click on the new value and click Rename and rename the value IdleTime.
- Click the IdleTime value and the Edit DWORD Value popup appears.
- In the Value Data, enter the the amount of time, in minutes, you want idle sessions to timeout and set the Base to Decimal.
- Once you've entered the requested values click OK, and the new value appears in the data column.
- Restart the ControlUp Agent Windows service, and the newly set idle timeout is implemented.