Re: Active Directory System Discovery

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Adam Barker (adam_barker_at_cable.comcast.com)
Date: 08/24/04 

Date: Tue, 24 Aug 2004 11:45:03 -0700

I am receving a whole bunch of unable to resolve errors. See below
Unable to resolve CCH-006728~ $$<SMS_AD_SYSTEM_DISCOVERY_AGENT><Tue Aug 24
14:27:27.036 2004 Eastern Daylight Time><thread=3844 (0xF04)>
Unable to resolve CCH-031385~ $$<SMS_AD_SYSTEM_DISCOVERY_AGENT><Tue Aug 24
14:27:29.301 2004 Eastern Daylight Time><thread=3844 (0xF04)>
Unable to resolve CCH-N000013~ $$<SMS_AD_SYSTEM_DISCOVERY_AGENT><Tue Aug 24
14:27:31.582 2004 Eastern Daylight Time><thread=3844 (0xF04)>
Unable to resolve CCH-005064~ $$<SMS_AD_SYSTEM_DISCOVERY_AGENT><Tue Aug 24
14:27:33.879 2004 Eastern Daylight Time><thread=3844 (0xF04)>
Unable to resolve CCH-006051~ $$<SMS_AD_SYSTEM_DISCOVERY_AGENT><Tue Aug 24
14:27:36.160 2004 Eastern Daylight Time><thread=3844 (0xF04)>
Unable to resolve CCH-005489~ $$<SMS_AD_SYSTEM_DISCOVERY_AGENT><Tue Aug 24
14:27:38.473 2004 Eastern Daylight Time><thread=3844 (0xF04)>
Unable to resolve CCH-008802~ $$<SMS_AD_SYSTEM_DISCOVERY_AGENT><Tue Aug 24
14:27:40.754 2004 Eastern Daylight Time><thread=3844 (0xF04)>
Unable to resolve CCH-006782~ $$<SMS_AD_SYSTEM_DISCOVERY_AGENT><Tue Aug 24
14:27:43.035 2004 Eastern Daylight Time><thread=3844 (0xF04)>
Unable to resolve CCH-008778~ $$<SMS_AD_SYSTEM_DISCOVERY_AGENT><Tue Aug 24
14:27:45.566 2004 Eastern Daylight Time><thread=3844 (0xF04)>
Unable to resolve CCH-008724~ $$<SMS_AD_SYSTEM_DISCOVERY_AGENT><Tue Aug 24
14:27:47.957 2004 Eastern Daylight Time><thread=3844 (0xF04)>

I was unaware SMS tried to resolve the names before importing them into SMS.

"Stan White [MS]" wrote:

> There is no need to extend the schema to discover resources - the two are
> unrelated.
> Extending the schema is for publishing server location information for
> sites.
> You will want to review the adsysdisc.log to see why not all computers were
> discovered.
>
>
> --
> --
> Stan [MSFT]
> --
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> --
> --
>
> "Adam Barker" <adam_barker@cable.comcast.com> wrote in message
> news:B6EA1C9C-F7CC-4AB8-9487-DCA411DE346D@microsoft.com...
> > If you have not extended the AD Schema are you still able to poll
> > information using AD system, user, system group discovery?
> >
> > If yes im having issues to where SMS collections/ All systems has 486
> > computers but AD computer container has 784 computers why am i missing 300
> > computers???
> >
> > Help????
>
>
>

Relevant Pages

  • Computers not removed from AD dynamic query collection
    ... I have enabled Active Directory System Group Discovery on my SMS2003 server. ... I have created a single AD container which points to a group for SMS to ... If I add computers to the AD group, ...
    (microsoft.public.sms.swdist)
  • Re: What part of SMS inventories the OU-path for computers?
    ... They have been visible in SMS all the time as Unassigned and without Client. ... The computers that got the sms-clients have been in AD for months so you'd think that the OU-path would be in SMS by now. ... All computers appeared in SMS within an hour which they should since I run the 'Active Directory System Discovery' method every five hours on five Primary Site Servers so information should be collected into SMS every hour. ...
    (microsoft.public.sms.admin)
  • Re: What part of SMS inventories the OU-path for computers?
    ... It takes a long time for the OU-path to appear connected to the client in SMS. ... If you need this for non-clients you might want to take a look at the enhanced system discovery plugin. ... The computers that got the sms-clients have been in AD for months so you'd think that the OU-path would be in SMS by now. ...
    (microsoft.public.sms.admin)
  • Re: What part of SMS inventories the OU-path for computers?
    ... I didn't understand that the System Group Discovery *only* discovers data for the computers in in its own site even if you point out the top of the Active Directory as search path for each site. ... Clients in other sites than the site running the SGD aren't detected/added until the SGD is run for that particular site That is why our clients didn't get their OU-path in SMS until the discovery was run for that particular site. ...
    (microsoft.public.sms.admin)
  • Re: What part of SMS inventories the OU-path for computers?
    ... They have been visible in SMS all the time as Unassigned and without Client. ... The computers that got the sms-clients have been in AD for months so you'd think that the OU-path would be in SMS by now. ... All computers appeared in SMS within an hour which they should since I run the 'Active Directory System Discovery' method every five hours on five Primary Site Servers so information should be collected into SMS every hour. ...
    (microsoft.public.sms.admin)