Skip to content

Commit

Permalink
Add password hash sync
Browse files Browse the repository at this point in the history
  • Loading branch information
@zhiweiwangmsft
zhiweiwangmsft committed Mar 29, 2018
1 parent 2c031ed commit ebbfdf1
Showing 1 changed file with 8 additions and 2 deletions.
10 changes: 8 additions & 2 deletions ...ve-directory/connect-health/active-directory-aadconnect-health-alert-catalog.md
View file
Expand Up @@ -21,6 +21,12 @@ Azure AD Connect Health service send alerts indicate that your identity infrastr
Error, Warning, and Prewarning are three stages of alerts that are generated from Connect Health service. We highly recommend you take immediate actions on triggered alerts. <br />
Azure AD Connect Health alerts get resolved on a success condition. Azure AD Connect Health Agents detect and report the success conditions to the service periodically. For a few alerts, the suppression is time-based. In other words, if the same error condition is not observed within 72 hours from alert generation, the alert is automatically resolved.

## General Alerts

| Alert Name | Description | Remediation |
| --- | --- | ----- |
| Health service data is not up to date | The Health Agent(s) running on one or more servers is not connected to the Health Service and the Health Service is not receiving the latest data from this server. The last data processed by the Health Service is older than 2 Hours. | Ensure that the health agents have outbound connectivity to the following service end points. [Read More](active-directory-aadconnect-health-data-freshness.md) |

## Alerts for Azure AD Connect (Sync)

| Alert Name | Description | Remediation |
Expand All @@ -31,10 +37,10 @@ Azure AD Connect Health alerts get resolved on a success condition. Azure AD Con
| Export to Active Directory failed | The export operation to Active Directory Connector has failed. | Investigate the event log errors of export operation for further details. |
| Import from Active Directory failed | Import from Active Directory failed. As a result, objects from some domains from this forest may not be imported. | <li>Verify DC connectivity</li> <li>Rerun import manually</li> <li> Investigate event log errors of the import operation for further details. |
| Export to Azure Active Directory failed | The export operation to Azure Active Directory Connector has failed. As a result, some objects may not be exported successfully to Azure Active Directory. | Investigate the event log errors of export operation for further details. |
| Password Synchronization heartbeat was skipped in last 120 minutes | Password Synchronization has not connected with Azure Active Directory in the last 120 minutes. As a result, passwords will not be synchronized with Azure Active Directory. | Restart Microsoft Azure Active Directory Sync Services:</b><br> Any synchronization operations that are currently running will be interrupted. You can choose to perform below steps when no synchronization operation is in progress.<br> 1. Click <b>Start</b>, click <b>Run</b>, type <b>Services.msc</b>, and then click <b>OK</b>.<br> 2. Locate <b>Microsoft Azure AD Sync</b>, right-click it, and then click <b>Restart</b>. |
| Password Hash Synchronization heartbeat was skipped in last 120 minutes | Password Hash Synchronization has not connected with Azure Active Directory in the last 120 minutes. As a result, passwords will not be synchronized with Azure Active Directory. | Restart Microsoft Azure Active Directory Sync Services:</b><br> Any synchronization operations that are currently running will be interrupted. You can choose to perform below steps when no synchronization operation is in progress.<br> 1. Click <b>Start</b>, click <b>Run</b>, type <b>Services.msc</b>, and then click <b>OK</b>.<br> 2. Locate <b>Microsoft Azure AD Sync</b>, right-click it, and then click <b>Restart</b>. |
| High CPU Usage detected | The percentage of CPU consumption crossed the recommended threshold on this server. | <li>This could be a temporary spike in CPU consumption. Check the CPU usage trend from the Monitoring section.</li><li>Inspect the top processes consuming the highest CPU usage on the server.<ol type="a"><li>You may use the Task Manager or execute the following PowerShell Command: <br> <i>get-process \| Sort-Object -Descending CPU \| Select-Object -First 10</i></li><li>If there are unexpected processes consuming high CPU usage, stop the processes using the following PowerShell command: <br> <i>stop-process -ProcessName [name of the process]</i></li></li></ol><li>If the processes seen in the above list are the intended processes running on the server and the CPU consumption is continuously near the threshold please consider re-evaluating the deployment requirements of this server.</li><li>As a fail-safe option you may consider restarting the server. |
| High Memory Consumption Detected | The percentage of memory consumption of the server is beyond the recommended threshold on this server. | Inspect the top processes consuming the highest memory on the server. You may use the Task Manager or execute the following PowerShell Command:<br> <i>get-process \| Sort-Object -Descending WS \| Select-Object -First 10</i> </br> If there are unexpected processes consuming high memory, stop the processes using the following PowerShell command:<br><i>stop-process -ProcessName [name of the process] </i></li><li> If the processes seen in the above list are the intended processes running on the server, please consider re-evaluating the deployment requirements of this server.</li><li>As a failsafe option, you may consider restarting the server. |
| Password Synchronization has stopped working | The Password Synchronization has stopped. As a result passwords will not be synchronized with Azure Active Directory. | Restart Microsoft Azure Active Directory Sync Services: <br /> Any synchronization operations that are currently running will be interrupted. You can choose to perform below steps when no synchronization operation is in progress. <br /> <ol> <li>Click <b>Start</b>, click <b>Run</b>, type <b>Services.msc</b>, and then click <b>OK</b>.</li> <li>Locate the <b>Microsoft Azure AD Sync</b>, right-click it, and then click <b>Restart</b>.</li> </ol> </p> |
| Password Hash Synchronization has stopped working | The Password Hash Synchronization has stopped. As a result passwords will not be synchronized with Azure Active Directory. | Restart Microsoft Azure Active Directory Sync Services: <br /> Any synchronization operations that are currently running will be interrupted. You can choose to perform below steps when no synchronization operation is in progress. <br /> <ol> <li>Click <b>Start</b>, click <b>Run</b>, type <b>Services.msc</b>, and then click <b>OK</b>.</li> <li>Locate the <b>Microsoft Azure AD Sync</b>, right-click it, and then click <b>Restart</b>.</li> </ol> </p> |
| Export to Azure Active Directory was Stopped. Accidental delete threshold was reached | The export operation to Azure Active Directory has failed. There were more objects to be deleted than the configured threshold. As a result, no objects were exported. | <li> The number of objects are marked for deletion are greater than the set threshold. Ensure this outcome is desired.</li> <li> To allow the export to continue, please perform the following steps: <ol type="a"> <li>Disable Threshold by running Disable-ADSyncExportDeletionThreshold</li> <li>Start Sychronization Service Manager</li> <li>Run Export on Connector with type = Azure Active Directory</li> <li>After successfully exporting the objects, enable Threshold by running : Enable-ADSyncExportDeletionThreshold</li> </ol> </li> |

## Alerts for Active Directory Federation Services
Expand Down

0 comments on commit ebbfdf1

Please sign in to comment.