Some 3rd party Anti-Virus and Threat Detection & Prevention solutions prevent non-approved applications from accessing local system resources. This can prevent Authlogics Windows Desktop Agent (WDA) from installing or functioning correctly.
Issues can include:
- The installation program may fail to start after initially extracting files.
- Authlogics services fail to access database files or write to log files.
- Components are not able to connect to the Windows services.
- Services are unable to access certificates in the Windows Certificate Store.
Furthermore, some of these issues can appear to be intermittent.
In these situations, the Anti-Virus / Threat Detection and Prevention solution will need to be configured to allow WDA to function correctly. Issues are most commonly found with the following vendors' products, however, this is not an exhaustive list:
Configuring Exceptions in 3rd party solution
The following is a list of the Executable, DLL and .NET Framework Library files created and utilised by Authlogics Windows Desktop Agent. They will need to be "excluded" by the Anti-Virus or "white-listed" by the Anti-Virus or Threat Prevention & Detection solution:
The following folder and its subfolders:
- C:\Program Files\Authlogics Windows Desktop Agent\
Executable code and processes
Executable code and processes located within C:\Program Files\Authlogics Windows Desktop Agent\ folder (*.exe & *.dll):
.NET Framework 4.8 (or above) libraries
Some Anti-Virus or Threat Detection and Prevention solutions can also limit which applications and processes can access certificate stores. Authlogics Windows Desktop Agent requires access to the workstation's Local Computer Certificate store and must be permitted access.