Hi.SMS Active Directory Security Group Discovery Agent failed to bind to container LDAP://DC=scm,DC=local. Error: The specified domain either does not exist or could not be contacted.. Possible cause: The AD container specified earlier might be invalid now. The Domain Controller is inaccessible.Solution: Please verify that the AD container paths specified are valid. Confirm accessibility of the site server to the Domain Controller to be queried.

Hi,It looks like you have configured the AD system group discovery to search for a container that dosn't any longer exists. Is the path pointing to the local domain or a remote domain? It could be that the site server computer account dosn't have read permissions to the specified container. Can you tell a little more about your problem?Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products

no i gave full controll on system management container than still this problem runnigplz help me

a container that dosn't any longer exists. That would be the entire domain in that case ("LDAP://DC=scm,DC=local"). So I don't think that the whole domain is gone ... ;-)jigneshvaghasiya: does your siteserversucceed in pinging scm.local?

yes i can ping my domain controllerbut still this issu runnig plz help me

How about the other AD discovery methods? Are they working as intended?Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products

I am having the same exact problem for discovery methods. May I revive this post?-Alex

I am having a similar problem. All other OU's setup for System Discovery are working fine. We have an OU named "Domain Controllers" under our domain. The OU is there, it shows in ADSI and Active Directory Users and Computers but it's not discovering any objects inside that OU. OU=Domain Controllers,DC=ourdomain,DC=com Full error in SCCM is: SMS Active Directory System Discovery Agent failed to bind to container LDAP://OU=DOMAIN CONTROLLERS,DC=OURDOMAIN,DC=COM. Error: The specified directory service attribute or value does not exist. Possible cause: The AD container specified earlier might be invalid now. The Domain Controller is inaccessible. Solution: Please verify that the AD container paths specified are valid. Confirm accessibility of the site server to the Domain Controller to be queried.