Return
-
Title
The most common list of issues related to the Change Auditor Agent service and connectivity -
Description
The most common list of issues related to the Change Auditor Agent service and connectivity -
Resolution
These are the most common list of culprits that can hint you for any Change Auditor Agent service and connectivity issues:
1. Verify the Quest agent and the coordinator Windows services ('Logon' tab) are running as a "Local System".
2. Check if agent ports are listening if you query the coordinator server from the agent host and the other way around since it is a TCP bi-directional relation. Also, confirm that the RPC service is running.
3. Besides the agent port, ensure that the SCP and SDK ports aren't blocked either.
4. If the remote agent deployment method from the Windows Client Console does not work, try to do it manually instead by using the Agent MSI installer. Always ensure the account used for this deployment has the required permissions.
5. Check if the Change Auditor installation has the necessary license(s) active and working.
6. Make sure the agent is in the same forest and the network has no obstacles DNS nslookup and ping.
7. Ensure no Antivirus or MSFT surface attack reduction rule is blocking the agent service. Review this KB article for more information:
https://support.quest.com/kb/234488/
8. In the case of a foreign forest agent, port 88 Kerberos is required to be listening. Bi-directional opening of ports 389 and 3268 between agent and forest root AD DCs (where the coordinator resides) is also mandatory.
9. Always check if the Installation name matches
10. Make sure the service account used to install the foreign forest agent is a member of the Change Auditor Agents security group on your forest root AD.
11. Try to reinstall the CA agent by completely uninstalling it from Programs and Features, then install it by running the Agent MSI from an elevated CMD prompt.