Hi All,

I wonder if anybody could assist with an issue I am having with SCCM, I have tried searching for this but cannot find anything specific enough?

We have User Discovery enabled and a delta discovery configured for every 15 mins. The delta discovery runs fine and mostly returns the expected results but on EVERY delta discovery the built-in administrator account is discovered even though no changes have been made. The account itself is disabled (verified this in AD) which results in this message being generated every time the delta discovery runs

WARN: CADSource::ProcessUserInfo: ignoring Administrator user, account disabled.

That would be fine, but it puts the User Discovery component into a warning state by 00:15 each morning and then into a critical state by 12:30 every day (critical is 50 warnings).

I have verified that in AD there are several hundred other user accounts that are also disabled, in OU's that are discovered, but these never show in the delta discovery (as expected).

Does anybody know of a way I can resolve this issue or possibly tune the alert so warnings are not generated just for this one user?

Thank you

Hmm.. haven't seen this, although the discovery is configured so that the OUs configured for user discovery do not contain any disabled users, maybe a solution for you too?

You can "suppress" the warning by increasing the threshold value for warnings on component SMS_AD_USER_DISCOVERY_AGENT.

Administration workspace -> Site Configuration -> Sites. Select the site to configure -> Status Summarizers in the ribbon.

Hi both,

Thanks for replying but unfortunately I don't think either of these will resolve our issue.

I can't modify the User Discovery as we have users in the same OU as this one problematic user that we do need to discover.

I have looked at the thresholds and this doesn't allow me to specify how many users can fail before a warning is generated. I can just specify how many errors generate a warning and rollout to a critical. I do want the alerts to stay at the same threshold so I would get alerted if there was a genuine error.

I think my best course of action is to wait until after we have upgraded to SP1 (planned in the near future) and then see if this error still exists or if gets resolved with the SP.

Thanks you for time in the meantime though