Cleaning the Windows Session Logon Events History

The logon cleaner in UserLock deletes session events from the database. By default UserLock keeps logon events indefinitely. Removing old logon events prevents the database from becoming too large. Deciding when to remove old logon events will depend on your organizations regulations and compliance policies.

Click on the ‘Logon Cleaner’ menu in the UserLock Windows Console.

Logon Event Cleaner

You will find on this view, different figures about the current state of the UserLock database.

Remember that the MS Access free database provided with the UserLock package has a maximum size limit of 2 GB.

If you decide that it’s time to clean your database, you can do this operation in just a few clicks.

The Logon cleaner offers two different operations.

  1. After selecting the first operation, define the time (in days) from when you want to keep your User sessions event history.
    All records generated before this date will be deleted. To confirm a delete, click on ‘Launch’.
  2. The second operation will delete all events stored in the UserLock database.
    Again, there is no possibility to cancel this action once you have validated it.

Take note that these two operations are a final deletion.

Schedule Logon Event Cleaning

To control and manage the progression of the database size, you can schedule these operations.

Configure the desired action as you want and click on the ‘Schedule’ button.

Type the name of the new scheduled task. The Windows Task Scheduler then opens.

Configure the schedule of your task by clicking on ‘new’ and choosing the time interval for your cleaning task.

You will be prompt to enter a user account that is authorized to start this task.

Once finished, the task is added in the Scheduler menu. You can edit or delete this task from this view.

UserLock will now automatically clean old user sessions activity, allowing you to keep only the pertinent history you need.

Take note that these actions will delete records in the database, but won’t reduce the database hard file size. You need to use the native database tool provided by Access or SQL Server for this operation.