Re: Clients not in AD aren't discovered

• Previous message: Joseph Calabig [MSFT]: "Re: Clients not in AD aren't discovered"
• In reply to: Joseph Calabig [MSFT]: "Re: Clients not in AD aren't discovered"
• Next in thread: Kelly Bubach: "Re: Clients not in AD aren't discovered"
• Messages sorted by: [ date ] [ thread ]

Date: Wed, 23 Jun 2004 12:18:02 -0700

I did make a change yesterday and enabled the Subnet that this server sits on in Network Discovery, and it found all of the systems i was missing and they now show up in the All Systems collection , I was just trying to discover it via Domain discovery, seems that the subnet must be enabled in NetDisc, along with the Domain added into the Domain search list.

The systems were not even being discovered, there was an entry in the one of the logs saying that the resource was located, but not in an AD Site. Now I have to work out the issues with installing legacy clients assigned to Secondary sites using push installation (which is not supported). grr.

"Joseph Calabig [MSFT]" wrote:

> I'll give this a shot, though I'm not well versed in this area.
> So the machine is discovered (as being included in a collection) but not
> assigned to the site?
> Is AXCS13's subnet (130.29.152.0) part of you site boundaries? Is it also a
> part of the subnets for your AD site/s?
> --
> Thanks,
> Joseph Calabig
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Kelly Bubach" <Kelly Bubach@discussions.microsoft.com> wrote in message
> news:A48C5381-A367-4AEC-8C3E-9F0C63680D56@microsoft.com...
> > SMS 2003 implementation, most of our systems are in a single 2000 domain,
> > there are a few that are in resource domains we are slowly deleting, but
> > in the meantime I need to pick them up with SMS to manage them.
> >
> > We are dealing only with Server OS here, NT4 and W2K, no "client OS"
> > versions, hence I have limited discovery to an OU in our AD, and limited
> > the network discovery to certain NT 4 domains that contain only Servers,
> > mainly NT4. I have set up site boundaries with IP subnets and AD Sites for
> > the mixed environment.
> >
> > In the netdisc.log I get the following info:
> >
> > AXCS13 is not in any AD Site. SMS_NETWORK_DISCOVERY 6/22/2004 12:18:03 PM
> > 4168 (0x1048)
> > ** DDR creation record **~Filename:
> > F:\SMS\inboxes\ddm.box\9cz7qe0z.DDR~Device: System~Device info: NetBIOS
> > Name AXCS13~Resource Domain OR Workgroup am-exch~Operating System Name and
> > Version Microsoft Windows NT Advanced Server 4.0~~IP Addresses
> > 130.29.152.142~IP Subnets 130.29.152.0~Resource Names AXCS13~MAC Addresses
> > 00:D0:B7:06:ED:92 SMS_NETWORK_DISCOVERY 6/22/2004 12:18:03 PM 4168
> > (0x1048)
> > ExportDevice <130.29.152.141 255.255.255.0> SMS_NETWORK_DISCOVERY
> > 6/22/2004 12:18:03 PM 4168 (0x1048)
> >
> > I have a number of systems in 3 resources domains that i am having the
> > same issue with, any help is appreciated. I have enabled Network Discovery
> > (limited subnets enabled, added in the Resource Domains) , Heartbeat
> > Discovery and AD System Discovery.
> >
>
>
>

• Previous message: Joseph Calabig [MSFT]: "Re: Clients not in AD aren't discovered"
• In reply to: Joseph Calabig [MSFT]: "Re: Clients not in AD aren't discovered"
• Next in thread: Kelly Bubach: "Re: Clients not in AD aren't discovered"
• Messages sorted by: [ date ] [ thread ]