Return
-
Title
ADPro: The Agent's not checking in after cutover to the target domain -
Description
The ADPro agents have stopped checking in after cutover, and user log into the device.
We are performing a cutover with a new test user
Ran a ReACL all is communicating properly
We see the ReACL logs and State file.
The machine is communicating after cutover but we found it stopped when we logged into the device. The agent is missing along with the folders and logs. the ReACL logs and State file are missing. -
Cause
GPO is deleting the BT ADPro Agent. This can be verified by viewing the application Event Log. The log entry will state a GPO deleted the agent.
-
Resolution
This is a non-product issue. Please work with the administrators to prevent any GPO from removing or altering the product agent.