When are New Client Sessions Started?

By default, a Client monitoring session is started automatically as soon as any user logs in to a Client machine, and the session continues until the user logs out, at which time the session is then terminated automatically.

Also, whenever any user is still logged in at midnight, their session is also terminated automatically by the system at this time, and a new session is started either immediately or when the user performs an action (depending on the Client operating system), as follows:

NOTE: As shown in the last column in the table above (depending on the Client operating system), if an idle event was registered before midnight (i.e. with the user not performing any actions until midnight), when the new session is started after midnight, the same idle event is registered in the new session.

Example: If 5 users log in (or the same user logs in) to 5 different Client computers, then 5 sessions are started, and if in 2 of these sessions the user has performed (at least) one action, then at midnight these 2 sessions are terminated automatically, and 2 new corresponding sessions are then started automatically. However, in the other 3 sessions (i.e. where the user has not performed any actions since logging in), then at midnight these sessions will automatically be terminated (as normal), and then:

• For Windows Clients:

- 3 new sessions are then started automatically.

- If the Register IDLE event when user is inactive parameter is enabled, both the old and new sessions display any idle event (i.e. the same idle event).

• For macOS Clients:

- 3 new sessions are not started until the appropriate users performs an action.

• For Linux Clients:

- 3 new sessions are not started until the appropriate users performs an action.

NOTE: Tasks performed automatically by the system (e.g. running a background script) are not considered as user actions by Syteca (since they are not performed by the user), and are therefore not recorded. This means (for Windows and for macOS Clients, if the Register Idle Event parameter is enabled) that an idle event will still be registered if the user does not perform any actions for the specified period, even if a task is automatically performed by the system during this time.

NOTE: If any monitoring filters are configured (e.g. Application/URL Filtering, User Filtering, Monitoring Time Filtering, Remote Host IP Filtering, Keystroke Filtering), sessions are started as normal, but session recording will only take place whenever a specific filter is triggered.