Time quotas
You can define a 'Time quotas' policy for user members of a 'Protected account'. The principle is simple: a maximum period of time connected to the network during a recurring period for specified session types. This option is set to 'Not configured' by default.
A specific Use case is available here and will give you a step-by-step guide on how to assign a logon time quota.
You just have to set the drop-down list option to 'Enabled' to defined a 'Time quotas' policy:
- Click on 'Add' to create a 'Time quota'.
- Choose the period of time: a day, a week, a month, a quarter, a semester or a year.
- Set the desired number of hours.
-
Define which types of session will be targeted: all session types, workstation,
terminal, interactive (workstation + terminal), Wi-Fi/VPN and/or IIS.
You can create as many quotas as desired for the same 'protected account' with different time periods or session types.
The 'Consumed time' per user member of the 'protected account' can be displayed and managed from the 'User sessions' view.
Please note:
- The notification period warning users about 'Time quotas' is defined in the 'General' section of the UserLock server 'Properties'.
- A user can be a member of several permanent and/or temporary protected accounts (user, group or organizational unit). UserLock determines which rules to apply based on certain priorities. These priorities are described in the section named 'Priority management'.
-
Example of a behavior that could be counterproductive:
8 hour day time quota.
Alice does not work in the morning for any reason.
She logs on at 04:30 PM.
She forgets to log off.
At midnight, consumed time reset to 0.
At 08:00 AM, 8 hour day time quota is consumed. Session is automatically logged off.
At 08:30 AM, she tries to log on. Denied because time quota is already consumed.
If the "Maximum session length" or "Maximum locked time" restriction is set to 8 hours for example, this behavior will not occur, or will be mostly prevented.