Error Appears in VigilEntAgent_8094.log (ERROR [Minifilter_Collector]) for Windows Machine
Installing Change Guardian Agent for Windows Fails with SMB Protocol Mismatch
Warning and Driver Initialization Errors Observed for Windows Agent
Windows Agent Goes Offline When Client Agent Manager is Uninstalled
Issue: Windows Agent VigilEntAgent_8094.log shows the error Minifilter_Collector.
Workaround: Reconfigure the agent through Agent Manager to address these errors.
Issue: Change Guardian Agent for Windows installation fails displaying the following error message in failed task logs:
Protocol negotiation failed...
The error might occur due to the following reasons:
SMB1 protocol is disabled on Change Guardian Agent for Windows.
Change Guardian server is installed on a Linux version that does not support SMB Version 2 (such as SLES 11.x or RHEL 6.x that has kernel version 2.6.x or lower), but only supports SMB Version 1. (Bug 1155405)
Workaround: Upgrade the operating system, on which Change Guardian server is running, to a version that supports SMB Version 2.
Alternatively, you can manually install the latest version of Change Guardian Agent for Windows. For more information, see Installing Change Guardian Agent for Windows.
Issue: You have a requirement to roll back to an older version of the agent package, but Agent Manager does not allow you to change the agent package version. (Bug 1155538)
Workaround: You can enable a new package, and disable the previous package by using the following file: /opt/netiq/ams/ams/repository/packageActiveStatus.new.example.
Issue: Warning statuses and driver initialization errors might be observed on the Agent Health page. However, events are forwarded to the server without any loss, and file change monitoring functions as expected. (Defect 603387)
Workaround: These messages do not affect functionality. You can safely ignore the warnings and errors and proceed with normal operations.
Issue: When the Client Agent Manager is uninstalled or removed, the windows agent stops functioning and goes offline. This issue occurs because the environment variables created during Client Agent Manager installation are deleted when Client Agent Manager is uninstalled. These environment variables are required for the agent to operate correctly. (Defect 686005)
Workaround: Reinstall or reconfigure the windows agent without uninstalling the existing agent to avoid policy reassignment. This applies to scenarios where Client Agent Manager has been uninstalled.