• Management Pack:  SCOM 2016
  • MP Version:  1.0
  • Released:  10/19/2018
  • Publisher:  Microsoft

AD Agent Assignment: Unable to bind to domain Rule

  • ID:  Microsoft.SystemCenter.ADAssignment.UnabledToBindToDomain.Alert
  • Description:  Unable to bind to domain
  • Target:  AD Assignment Resource Pool
  • Enabled:  Yes

Overridable Parameters

Parameter Name Default Value Description Override
Priority 1  
Severity 2  

Run As Profiles

Name
Default

Alert Details

Message Priority Severity
AD Agent Assignment: Unable to bind to the specified domain Medium Critical

Rule Knowledgebase

Summary

This alert indicates that an AD Integration agent assignment rule failed to complete successfully because it cannot bind to the specified domain. Agents will not find out which server they should report to until this problem is resolved.

Causes

The agent assignment rule is unable to bind to Active Directory. This may have been caused by:

1. AD may have become inaccessible.

2. The run as profile (default = Active Directory Based Agent Assignment Account) used by the rule does not have a valid run as account that can access the management group container in the domain.

3. The run as account associated with the run as profile has wrong user name or password.

Resolutions

1. Make sure all servers in the AD Assignment resource pool are able to access the domain.

2. If the Run As Account is a domain user account, make sure the username and password is valid.

3. If all else fails, then try deleting the Management Group container in the domain, using "MOMADAdmin -d {Management Group Name} {Domain}", and re-run MOMADAdmin.exe to prepare the domain again.

External References
This rule does not contain any external references.

See Also for SCOM 2016 Management Pack


Downloads for SCOM 2016 Management Pack

AZURE OPTIMIZATION ASSESSMENT GET STARTED
MIGRATION TO AZURE GET STARTED
SYSTEM CENTER MIGRATION TO AZURE GET STARTED
MIGRATION TO AZURE FOR SQL AND WINDOWS 2008 GET STARTED