Forum Discussion

jvmagni's avatar
jvmagni
Copper Contributor
May 08, 2024

Entra Cloud Sync agents skipping local AD config

Some of our VMs that contained Cloud Sync agents were lost. We recreated the VMs and reinstalled the Cloud Sync provisioning agent. The provisioning agent wizard is skipping the on-premises AD configuration part and going straight to the Azure AD connection configuration. This way, the cloud sync agents are in the "not configured for xxx domain" state, so we can't add new agents for redundancy. There's any way to force "local AD" connection or at least configure new agents for an already configured domain?

We are relying on a single agent. We did a test of killing this agent and reinstalling it and we were left with no agent and no possibility to create new ones. We had to restore the VM to get our synchrony back. Any help would be awesome.

1 Reply

Sort By
  • Kidd_Ip's avatar
    Kidd_Ip
    MVP
    Feb 23, 2025

    Please considering this:

     

    • Clear Previous Configuration:
      • Ensure that any remnants of the previous configuration are completely removed. This includes any old agent configurations that might be lingering in the system.
    • Reinstall the Agent:
      • When reinstalling the Cloud Sync provisioning agent, make sure to follow the steps carefully to avoid skipping the on-premises AD configuration part. 
    • Force Local AD Connection:
      • If the wizard is skipping the local AD configuration, you might need to manually configure the local AD connection. This can be done by accessing the agent configuration settings and ensuring that the local AD connection is properly set up.
    • Check for Updates:
      • Ensure that you are using the latest version of the Cloud Sync provisioning agent. Sometimes, updates can resolve issues with the configuration process.

Resources