Overview
This article provides the procedure to resolve false positive alerts for "AD connector is not connected" in environments where the user provisioning method has been changed to SCIM, Azure AD, or Google Directory.
Cause
These alerts are typically generated due to stale entries from a previous AD/LDAP configuration that was not properly decommissioned. If an old AD/LDAP connector configuration remains in the Druva console after migrating to a new provisioning method, the system may continue to monitor its status, leading to false alerts.
Procedure to Remove Stale AD Connector Entries
Prerequisites
This procedure applies only if a stale AD connector or AD Account is still visible on the Druva Cloud Settings page under the AD/LDAP tab.
You must have Druva Cloud administrator permissions to access the required settings.
Steps
Navigate to Druva Cloud Settings > AD/LDAP Connectors page. Check if any old connectors are listed, particularly if the Upgrade option is grayed out.
On a local machine (a server machine is not required), download and install a new AD connector application from the Druva console or Druva Download
From the AD/LDAP page in the console, generate a new registration key and use it to activate the new connector application you just installed.
Once the registration is successful, refresh the AD/LDAP page in the console. The new connector should now be listed.
The Upgrade option for the old, stale connector should now be active. Proceed with the upgrade. After the process completes, only the single new AD connector should remain listed.
If there was an existing AD Account linked to the old connector, it should now appear linked to the new connector.
To delete the final connector, you must first remove its dependencies. Select the AD Account that is linked to the new connector and delete it from the Accounts tab.
Once the AD Account is deleted, you can proceed to delete the new AD Connector from the console.
Finally, you can uninstall the AD Connector application from the local machine where it was installed.
Resolution
After performing these actions, the false positive alerts for "AD connector is not connected" should stop. If the alerts persist, please contact Druva Support to investigate if other stale entries are causing the issue.
See also