SessionLimit v2
  • Infrastructure Documents
  • Overview
    • What is SessionLimit
    • FAQs
    • Road Map
    • Licensing
  • Planning
    • POC Requirements
    • Supported Configurations
    • Windows Server Requirements
    • SQL Server Requirements
    • Agent Requirements
      • .Net Framework 4.7.2
    • Other Requirements
    • Network Considerations
    • Design
      • Single Deployment
      • Distributed Deployment
  • Deployment
    • GMSA Account for Application Pool
    • DNS Service Record for Agent Autodiscovery
    • Installing Microsoft SQL Server
    • Internet Information Service Installation
    • .NET Core 8.0 Download and Install
    • .Net Framework 4.7.2 Download and Install
    • HTTPS Certificate
    • Installing SessionLimit 2.0
    • Upgrading SessionLimit
      • Upgrading SessionLimit 2.0.12 to 2.0.13
      • Upgrading SessionLimit 2.0.13 to 2.0.14
      • Upgrading SessionLimit to 2.0.15
      • Upgrading SessionLimit to 2.0.16
      • Upgrading SessionLimit to 2.0.17
      • Upgrading SessionLimit to 2.0.18
      • Upgrading SessionLimit to 2.1
      • Upgrading SessionLimit to 2.1.2
      • Upgrading SessionLimit to 2.1.3
      • Upgrading SessionLimit to 2.1.4
    • First Time Wizard
    • Agent Deployment
  • Managing
    • Logging to SessionLimit 2.0
    • Dashboard (Home)
      • General Dashboard
      • My Dashboard
      • Agents Dashboard
    • Policy
      • Session Protection Policy
      • 2FA Policy
    • Limitations
    • Endpoint Management
      • Users
      • Computers
    • Settings
      • General
        • Server Settings
        • LDAP Settings
        • Notification Settings
          • General Notification
          • E-Mail
          • SMS
        • Syslog Settings
        • Syslog Message Settings
      • Advanced Settings
      • 2FA
      • Agent
    • Events
    • Reports
    • Role Management
    • License Management
      • Online License
    • Syslog
      • Logon Operations
  • Agent
    • Session Control
    • 2FA
  • Tips&Tricks
    • SQL Express Usage
    • Fixing 500.19 web.config error
    • Enable HTTPS Redirection in IIS with HSTS
    • Using GMSA Account in Application Pool
    • Give Database Access for GMSA Account
    • What are the SessionLimit protection states?
    • Securing Windows Server
Powered by GitBook
On this page
  • Settings
  • Data Age (Day)
  • Period (Minute)
  • Number of Records to be Deleted
  • Disabled
  1. Managing
  2. Settings
  3. General

Server Settings

Scope: SessionLimit 2.0

PreviousGeneralNextLDAP Settings

Last updated 10 months ago

This screen contains grooming settings. With the grooming settings, it is determined how long the logs, events and session records accumulated in the database will be stored. By default, this setting is off and never deletes old records.

In the recommended configuration, this setting is turned on and the duration of storage is determined in line with legal limits.

Settings

Data Age (Day)

It is determined how long the data will be kept. It can be set to minimum 10 and maximum 4000. The default value is 400 days.

Period (Minute)

It determines the period in which the grooming process will run. This is an important setting to prevent the database from being busy with constant data deletion. It should be adjusted in accordance with the number of records to be deleted simultaneously.

It can be set to minimum 60 and maximum 1440 minutes. The default value is 60 minutes.

If a lot of records are to be deleted during the grooming process, the time should be increased; if the records are to be deleted little by little, the time can be shortened. Otherwise, unwanted clogging and performance loss may occur in the database.

Number of Records to be Deleted

Determines the number of rows to be deleted in each period. It ensures gradual deletion of data held in the database. It is erased from old to new.

It can be set to minimum 60 and maximum 1440 minutes. The default value is 60 minutes.

If a lot of records are to be deleted during the grooming process, the time should be increased; if the records are to be deleted little by little, the time can be shortened. Otherwise, unwanted clogging and performance loss may occur in the database.

Disabled

It is used to turn grooming settings on and off. It is closed when Disabled and open when Enabled. When it is on, data is automatically deleted for a specified period of time.