In this article  :

• Issue description

• Prerequisites

• Possible causes

• Resolution

• Related topics and articles

• How to reach support

Issue description

The User Work Hours report is generated by correlating local events such as login, logout, computer locked, unlocked, screensaver invoked and dismissed (if configured). The user's workstation or machine must be configured with ADAudit Plus for the data to show up in the report.

Prerequisites

1. The end user's workstation should be configured under ADAudit Plus > Configuration.

2. The required audit policies should be configured as per the document.

Possible causes

1. The user's workstation is not configured.

2. The required audit policies are not enabled.

3. The user's crunch schedule has not been initiated.

Resolution

1. Workstation configuration

1. Log in to ADAudit Plus.

2. Navigate to Configuration > Workstations.

3. Check if the workstation is configured. If not, then follow the steps in Configuring Windows workstations.

2. Audit policy check

1. Log in to the workstation in question.

2. Open Command Prompt as an administrator and execute: auditpol /get /category:*

3. Check if the required audit policies are applied, especially the Logon/Logoff category, to register all the correlation events. If not configured, please configure the required policies and check if the User Work Hour report shows the upcoming data.

3. User crunch schedule

1. Log in to ADAudit Plus.

2. Navigate to Active Directory > Local Logon-Logoff > User Work Hours.

3. In the top information bar, click Run now and check if the User Work Hour report has the data updated. .

How to reach support

If the issue persists, contact our support team here.