Windows Security Software Whitelist Configuration
Add VCA to security software whitelist in enterprise environments to ensure proper system operation.
Overview
In Windows enterprise environments, security software may flag certain VCA operations as suspicious and block them. VCA uses UI Automation technology to control meeting applications, including detecting meeting status, automating button clicks, and simulating keyboard/mouse input, which may trigger security software protection mechanisms.
This document is intended for enterprise IT administrators. Configuring whitelists requires system administrator privileges.
Files to Add to Whitelist
VCA includes the following executable files. It is recommended to add all of them to your security software's trusted list:
| File Name | Path | Description |
|---|---|---|
vca.exe | C:\Program Files\VCA\vca.exe | Main application |
nanomq.exe | %APPDATA%\VCA\nanomq\nanomq.exe | Local MQTT Broker |
vca_daemon.exe | %APPDATA%\VCA\daemon\vca_daemon.exe | Daemon process for automatic recovery |
vca_ax_worker.exe | %APPDATA%\VCA\vca_ax_worker.exe | RPA control process for meeting automation |
%APPDATA% typically points to C:\Users\<username>\AppData\Roaming
Behavior Types Requiring Exceptions
The following VCA operations may be blocked by security software:
- UI Automation Access: Accessing interface elements of other applications
- Keyboard/Mouse Simulation: Simulating user input operations
- Window Operations: Automatically switching and managing meeting application windows
- Inter-Process Communication: Collaboration between multiple VCA processes
Common Enterprise Security Software Configuration
Windows Defender
Open "Windows Security"
Select "Virus & threat protection"
Click "Manage settings"
Scroll down to "Exclusions" and click "Add or remove exclusions"
Click "Add an exclusion" and select "Folder"
Add the following folders:
C:\Program Files\VCA%APPDATA%\VCA
Symantec Endpoint Protection
Open Symantec Endpoint Protection management console
Navigate to "Policies" → "Application and Device Control"
Add VCA executable file paths in "Application Exceptions"
Add VCA installation directory in "Behavior Monitoring Exceptions"
McAfee Endpoint Security
Open McAfee ePO console
Navigate to "Policy" → "Threat Prevention"
Add VCA installation directory and executables in "Exclusions"
Add exceptions for VCA processes in "Access Protection Rules"
Kaspersky Endpoint Security
Open Kaspersky Security Center
Select "Policies" → "Application Control"
Add VCA executables to "Trusted Applications" list
Add VCA installation directory in "Exclusions"
Trend Micro Apex One
Open Apex One management console
Navigate to "Policies" → "Approved Program List"
Add VCA executables to approved list
Add VCA installation directory in "Scan Exclusions"
General Configuration Principles
If your security software is not listed above, please refer to the following general configuration principles:
-
Add File/Folder Exclusions
- Add the entire
C:\Program Files\VCAfolder to scan exclusions - Add the entire
%APPDATA%\VCAfolder to scan exclusions
- Add the entire
-
Add Process Exceptions
- Add
vca.exe,nanomq.exe,vca_daemon.exe,vca_ax_worker.exeto trusted process list
- Add
-
Allow Behavior Monitoring Exceptions
- Allow VCA processes to access interface elements of other applications
- Allow VCA processes to simulate keyboard and mouse input
- Allow VCA processes to perform window operations
Verify Configuration
After configuration, use VCA Host's built-in "System Diagnostics" feature to verify:
Open VCA Host application
Go to "Settings" → "System Diagnostics"
Click "Start Diagnostics"
Check diagnostic results to ensure no security software-related warnings or errors
Common Issues
| Issue | Possible Cause | Solution |
|---|---|---|
| VCA exits immediately after startup | Main program blocked by security software | Add vca.exe to whitelist |
| Meeting app control fails | RPA process blocked | Add vca_ax_worker.exe to whitelist |
| Unstable connection | MQTT Broker blocked | Add nanomq.exe to whitelist |
| No automatic recovery after crash | Daemon process blocked | Add vca_daemon.exe to whitelist |
If issues persist, please contact VCA technical support and provide the system diagnostics report and security software logs.
References
This document references the following industry best practices: