Active Directory sync stuck at “Initiated” even though AD agent logs show successful connectionSolved

Hi @gareyy,

For Hexnode Active Directory sync, the administrator account configured in the AD integration must remain active, and the password saved in Hexnode must match the current password for that account.

If the account used for the integration was disabled, deleted, locked, or had its password changed, the sync can fail to complete even if the AD agent service itself is running.

Recommended checks:

1. Confirm that the AD account configured for the integration is active.
2. Verify that the password has not changed or expired.
3. If the password was changed, update the credentials in the AD integration settings.
4. Confirm that the AD agent service is running on the server where it is installed.
5. Trigger the AD sync again from the Hexnode portal.

If the agent logs show successful AD binding, OU retrieval, and successful posting to Hexnode, the local AD agent is able to communicate with both Active Directory and the Hexnode server. In that case, allow the sync process to complete and then verify whether the portal updates the last successful sync time.

Best Regards,
Isabel Lora
Hexnode UEM

We checked the configured AD account and it is still active. The password is correct as well. We also added a new sensor and updated the settings. After triggering the sync, the portal says it is syncing and asks us to wait, but it still remains in the initiating stage. The logs continue to show successful connection checks and successful posts.

We ran into something similar after changing the account used for directory sync. The agent logs looked fine, but the portal took longer than expected to reflect the completed sync. In our case, rechecking the saved credentials and retriggering the sync was enough, but the status did not update immediately.

If the AD account is active and the logs show entries similar to the following, the AD agent side is generally functioning correctly:

• Connection check completed successfully
• AD sync started
• AD server bind completed
• OU/search data retrieved
• Connection unbound cleanly
• Data posted successfully
• HTTP 200 response from the Hexnode sync endpoint

Since the credentials and agent communication are valid, the next step is to wait for the initiated sync to finish processing in the portal. If the status remains unchanged for an extended period even after a successful post, trigger the sync again after confirming that no credentials, domain settings, or selected OUs were changed incorrectly.

Best Regards,
Isabel Lora
Hexnode UEM