In this article:

• Issue description

• Prerequisites

• Possible causes

• Resolution

• Related topics and articles

• When and how to contact support

Issue description:

Adaudit plus user session recording (USR) feature provides video recordings of user screen activity during administrative changes. This helps in investigating anomalies and deters malicious actions. However, USR does not record every user action—only administrative tasks.

Prerequisites:

• The target machine (where sessions are recorded) is properly configured in ADAudit Plus.

• The agent is installed on the target machine to enable user session recording.

• Ensure service account configured in ADAudit Plus has complete access over the installation directory.

• The FFmpeg file is available for video compilation.

• The ffmpeg.exe file is copied into the bin directory of the ADAudit Plus installation.

• Sufficient disk space is available for storing recorded frames.

• The frame collection frequency is set to 1 frame per second to ensure recording consistency.

• User Session Recording works only for reports containing a "Caller Machine Name".

• The Caller Machine Name appears as a hyperlink in reports. Clicking it should display the compiled video.

Possible causes:

• The machine where administrative activity was performed, and User Session Recording (USR) is being checked, may not be configured in ADAudit Plus.

• The agent may not be installed on the end machine, or there may be a lack of seamless connectivity between the ADAudit Plus server and the end machine.

• The machine may not be enabled or properly configured under the User Session Recording tab in Configuration.

• User Session Recording may not function properly due to the error:

• "FFmpeg program not found. Please copy ffmpeg.exe to the ADAudit Plus bin directory."

• Clicking the session hyperlink on the User Session Recording page may result in the error:

• "User Session Recording not found for the selected period" if no administrative activities were recorded during the specified timeframe.

• The report being accessed may not support User Session Recording (USR) by default.

• ADAudit Plus may fail to process recorded frames once they reach the installation directory.

Resolution:

Step 1: Ensure the machine is configured in ADAudit Plus  

• Log in to ADAudit Plus.

• Navigate to Domain Settings and verify that the DC where administrative activities take place is properly configured.

• If the machine is a Member Server, File Server, or Workstation, go to the respective configuration page and ensure that it is added for monitoring.

Step 2: Check agent installation and connectivity  

• Ensure that the ADAudit Plus agent is installed on the machine where session recording is required.

• Verify that the agent is running and properly communicating with the ADAudit Plus server.

• Check if the agent-installed machine is reporting any errors. If an error is reported, click here to troubleshoot agent connectivity issues.

• Confirm that there is seamless connectivity between the machine and the ADAudit Plus server.

• Ensure that sufficient bandwidth is available, as ADAudit Plus sends 20 frames per request from the agent to the server.

• The frame quality setting (default: 50%) can be adjusted to higher quality, but this may cause latency in frame collection.

• Customize USR Settings: Refer to the image below to customize User Session Recording (USR) settings;

•  Ensure that the agent installation directory has adequate disk space, as frames are temporarily stored there before being transferred to the ADAudit Plus server's installation directory.

Step 3: Verify User Session Recording configuration  

• Navigate to Configuration > User Session Recording.

• Ensure that the required machines are added and that User Session Recording (USR) is enabled for them.

• Confirm that all necessary settings, including retention policies, are properly configured.

Step 4: Resolving the FFmpeg Error  

If the FFmpeg program is missing, you may encounter the following error:

"FFmpeg program not found. Please copy ffmpeg.exe to the ADAudit Plus bin directory."

• Click here to download the ffmpeg zip file.

• Extract the downloaded zip file.

• Go to <extracted_file_path>\ffmpeg-N-104704-ge22dff43e7-win64-gpl\bin\ffmpeg, copy ffmpeg.exe, and paste it into the ADAudit Plus bin folder (<product_installation_path>\bin\).

• Restart the ADAudit Plus service for the changes to take effect.

• Since ADAudit Plus captures administrative activity frames, processes them, and compiles them into a video, it may take a few hours for USR to function as expected after restarting the service.

Step 5: Handling the "User Session Recording Not Found" Error  

If clicking the session hyperlink on the User Session Recording page results in the error:

"User Session Recording not found for the selected period", follow these steps:

• Confirm that an administrative activity was actually performed on the machine within the selected timeframe.

• Adjust the time range in the session recording view to ensure the correct period is selected.

Step 6: Ensure User Session Recording is supported for the report  

• Not all ADAudit Plus reports support User Session Recording (USR).

• USR is only available for reports that include the Caller Machine Name.

• Check whether the selected report supports USR.

• For a list of reports that support USR, contact ADAudit Plus support.

Step 7: Handling unprocessed User Session Recording data  

• If frames are not being processed after reaching the ADAudit Plus installation directory, check for:

• Insufficient storage space on the ADAudit Plus server.

• Corrupt session recording files—try restarting the ADAudit Plus service.

• Permission issues—ensure the ADAudit Plus service account has full access to the recording storage directory.

• Recording storage directories by default would be; 

 Frames folder:<installation_directory>\webapps\adap\sm\frames

Related topics and articles

• User Session Recording configuration guide

• Click here to download ffmpeg zip file  

How to contact support  

• If the issue persists, contact our support team here.