Common settings

The most important options in this tab:

Store reports no more then N-days
Indicate users' reports retrospective saving to the database and to folders (incl. shadowcopy folder). Do not indicate too big value in order not to occupy to much space on SQL server and the disk.
If you specify 0, cleaning will not be performed!

Store journal no more then N-days
The same option for Journal.

Daily database optimization
Optimization refers to the process of deleting old records from the database in acc. with prev. retrospective option.
It is recommended to perform during off-hours the minimum load on the database.
For the multi-server mode (several servers connected to one database), only the server that is selected as the main one will perform optimization (see server settings).

Reindex base
The re-indexing operation is optional and can improve database query performance.
Otherwise, the features of this option are similar to the previous one.

Keep reports for user _LOGOFF_ (logged off session state)
If checked it will be possible to see the user with the name _LOGOFF_ in BOSS-Online.

Optimization: ignore computer name for domain users
It makes sense to turn on this option in large companies where domain users can work on different computers. In this case, the list of users in BOSS-Offline can be very large and this will adversely affect the performance when building reports. With this option computer name for each user in the list will be replaced by _ANYPC_, this will reduce their total count.
After enabling the option, the old entries (with real computer names) in BOSS-Offline will remain and will be gradually deleted in accordance to the retrospective of reports storage.

Traffic limitation
Warning! Use small values with great caution!
Set 0 to cancel restrictions.

Storage on clients
If any of the three options is enabled and the corresponding problem occurs, then the clients will be notified by the server about the occurrence of such an event and will stop transmitting the intercepted monitoring data to the server. In this case, no data separation is performed. For example, if only the shadow copy folder is unavailable and the sensitivity is set to this event, but the monitoring data does not contain shadow copies, then they will still not be transferred to the server! Conversely, if only the database is unavailable, then even shadow copies will not be transferred.
The data on the clients is stored in this case as standard in the local storage.
This status is polled by clients approximately once per minute.
If the options are not used, then all data will be transmitted to the server even if there are problems, and in this case:
- if the shadow copy folders are unavailable, the transferred shadow copies will be destroyed by the server;
- if the database is unavailable, the packets will be delayed in the server's RAM (and after it is full, data is no longer accepted from clients at the TCP protocol level).

Max. number of attempts to enter an incorrect password
If you specify a non-zero number, and the number of consecutive failed login attempts to the BOSS web console equals this number, the account will be blocked during N-minutes (next parameter)!
If the block duration is set to zero, only the administrator can unlock it by resetting the password on the "Database Users" page (for SQL accounts) or by deleting/creating an account (for accounts from the Active Directory).