AD System errors

[SuperIntern]

I'm getting critical in both AD System Group discovery and AD System Discovery agent: SMS AD SD Agent reported errors for 1 Objects. DDR's were generated for 0 objects that had errors while reading non-critical properties. DDRs were not generated for 1 objects that had errors while reading critical poperties.

[waingro]

I typically see this when SCCM is scanning AD and finding machine accounts that are no longer active in AD.

[SuperIntern]

I typically see this when SCCM is scanning AD and finding machine accounts that are no longer active in AD.

 

Is there a tool to run to resolve the problem, or can i manually delete the entry.

 

Thank you

[waingro]

Verify the computer account in AD is, in deed, obsolete and delete it from AD. SCCM should pick up the change and remove it from its DB on the next scan.

 

There is also a rights issue, meaning the account (hopefully a service account) that SCCM is using to scan AD needs to be able to read the AD attributes. That could be your issue as well.

 

SMS Active Directory System Discovery Agent reported errors for "X" objects. DDR's were generated for 0 objects that had errors while reading non-critical properties. DDR's were not generated for "X" objects that had errors while reading critical properties.

 

Possible cause: The SMS Service might not have access to some properties of this object. The container specified might not have the properties available.

Solution: Please verify the Active Directory schema for properties that are not replicated or locked. Refer to the discovery logs for more information.

 

This is an error I commonly get. I believe it is due to these accounts being obsolete and have not been removed from AD yet.

 

Also this thread, http://social.technet.microsoft.com/forums/en-US/configmgrgeneral/thread/767da4d4-3054-45ff-8829-f5dbb1d1e778/, seems to point to DNS not having active records for those machines, which could also be a result of an inactive account.

[SuperIntern]

Verify the computer account in AD is, in deed, obsolete and delete it from AD. SCCM should pick up the change and remove it from its DB on the next scan.

 

There is also a rights issue, meaning the account (hopefully a service account) that SCCM is using to scan AD needs to be able to read the AD attributes. That could be your issue as well.

 

SMS Active Directory System Discovery Agent reported errors for "X" objects. DDR's were generated for 0 objects that had errors while reading non-critical properties. DDR's were not generated for "X" objects that had errors while reading critical properties.

 

Possible cause: The SMS Service might not have access to some properties of this object. The container specified might not have the properties available.

Solution: Please verify the Active Directory schema for properties that are not replicated or locked. Refer to the discovery logs for more information.

 

This is an error I commonly get. I believe it is due to these accounts being obsolete and have not been removed from AD yet.

 

Also this thread, http://social.technet.microsoft.com/forums/en-US/configmgrgeneral/thread/767da4d4-3054-45ff-8829-f5dbb1d1e778/, seems to point to DNS not having active records for those machines, which could also be a result of an inactive account.

 

Deleted the redundant record was the solution, Probably due to redeployment with a different name? Thanks for all of the help!