How to Re-Sync Credentials from Central Server to Probe Servers

How to Re-Sync Credentials from Central Server to Probe Servers

Issue Description

  1. In Applications Manager Enterprise Edition, credentials configured on the Central Server are automatically synchronized to all associated Probe Servers. In some cases, credentials on a Probe Server may become unavailable or inconsistent due to synchronization failures, data corruption, or incomplete synchronization.
  2. This issue may result in monitor discovery failures, authentication failures, or the inability to perform credential-based monitoring operations on the affected Probe Server.
Info
Credentials added from the Central Server can be identified by a Credential ID that begins with 10000000.
To verify, navigate to Settings → Discovery and Data Collection → Credential Settings →  Credential Manager and check the Credential ID column.

Symptoms

One or more of the following symptoms may be observed. Navigate to Settings → Discovery and Data Collection → Credential Settings →  Credential Manager to verify:

  1. Credentials created on the Central Server are available on some Probe Servers but are missing on one or more Probe Servers.
  2. Newly added credentials on the Central Server are not synchronized to the affected Probe Server(s).
  3. Updates made to existing credentials on the Central Server (such as username, password, or other credential properties) are not reflected on one or more Probe Servers.
  4. Credential-based monitor authentication fails on a Probe Server even though the corresponding credentials are present and valid on other Probe Servers.

Resolution Steps

To restore credential consistency, trigger a full credential re-synchronization from the Central Server to the affected Probe Server(s) by following the steps below.

1. Identify the Probe Server ID

  1. Log in to the Applications Manager Central Server.
  2. Navigate to Probe Servers.
  3. Locate the affected Probe Server and note its Probe Server ID.
Info
If multiple Probe Servers are affected, note all corresponding Probe Server IDs.

2. Check and Configure Security Settings (If Required)

The re-synchronization requires executing an UPDATE query in the Database Summary tool. If the "Enable security constraints in Query Tool and Custom Query Report" setting is active, DML queries (INSERT / UPDATE / DELETE) are blocked and you will see the error:

Warning
Cannot execute this query since security constraints are enabled. Please disable in Settings → Security Settings and try again.
⚠️ How to temporarily disable security constraints
Notes
Perform this on the Central Server before executing the query in Step 3, then re-enable it afterwards.

  1. Navigate to Settings → Security Settings.
  2. Locate the option "Enable security constraints in Query Tool and Custom Query Report".
  3. Uncheck / Disable this option and save.
  4. After completing Step 3, return here and re-enable this option to restore the security posture.
Alert
If the security constraint setting is already disabled in your environment, you can skip the configuration above and proceed directly to Step 3.

3. Trigger Credential Re-Synchronization

On the Central Server, navigate to Settings → Support → Database Summary and execute the following query.

Replace <PROBE_SERVER_ID> with the actual Probe Server ID(s) noted in Step 1.

Query
IdeaUPDATE am_mas_comm_synchdetails SET STATUS = 'TOSYNCH' WHERE SERVERID IN (<PROBE_SERVER_ID>) AND APIURL = '/AppManager/xml/credential';
Example — Multiple Probe Servers
Query (Probe Server IDs: 2, 3, 5)
Idea
UPDATE am_mas_comm_synchdetails SET STATUS = 'TOSYNCH' WHERE SERVERID IN (2, 3, 5) AND APIURL = '/AppManager/xml/credential';
After the query executes successfully, return to Settings → Security Settings and re-enable the "Enable security constraints in Query Tool and Custom Query Report" option if it was disabled in Step 2.

4. Verify Synchronization

  1. Wait a few minutes for the synchronization process to complete.
  2. Log in to the affected Probe Server.
  3. Navigate to Settings → Credential Settings and verify that the missing credentials have been repopulated.
  4. Verify monitor authentication on the affected Probe Server(s) using the credentials added from the Central Server.
  1. InfoRestores synchronization consistency without requiring manual credential update or recreation.
  2. No service restart is required as part of this operation.



          New to M365 Manager Plus?
          New to M365 Manager Plus?
            New to RecoveryManager Plus?
            New to RecoveryManager Plus?
              New to Exchange Reporter Plus?
              New to Exchange Reporter Plus?
                New to SharePoint Manager Plus?
                New to SharePoint Manager Plus?
                  See all integrations
                  New to ADManager Plus?
                  See all integrations
                  New to ADManager Plus?

                    New to ADSelfService Plus?

                    Start your free trial
                    Start your free trial
                      Related Products