Overview

The information in the historic scan reports tends to be inaccurate, as the report occasionally claims the services are removed or the program uninstalled when they still exist on the system. 

Solution

The security scan history reports show the difference between two scan states, and the reporting issues described can be caused by periodic scanning errors, access problems preventing LanGuard from collecting the correct information, or database issues while saving the scan results.

Ensure firewall and antivirus exclusions

Make sure you have all the necessary firewall and antivirus exclusions for successful LanGuard operations.

Scans might encounter errors due to the requirements not met.

Verify the Required Settings are met in your environment in general and with the affected machines in particular. Be thorough - all of these settings are equally important; without them, operations may fail. Pay extra attention to all the required services on the client machines and the Required Network Connectivity and Security Permissions - these are the most common root causes for the LanGuard operations issues.

Also, ensure the remote computers are reachable through Remote Procedure Calls (RPC), as registry checks for the installed applications and services rely on RPC.

Maintain the backend scan results database.

Scan results are saved to the database, and LanGuard uses this data for reports. If there are problems with the database, the results would be unreliable. For example, if the SQL Express database has reached its maximum capacity, scan results just won't be saved for the LanGuard to analyze them. Maintain the Scan Results Database backend in good shape to avoid database size issues or corruption.

Testing

Rerun the usual scans at least twice successfully and compare the results. If the issue persists, contact GFI LanGuard Support.