Re: Incomplete Network Dircovery of SMS 2003
From: kiwi_vtr (kiwivtr_at_discussions.microsoft.com)
Date: 10/06/04
- Next message: TerryM: "Re: roaming clients on SMS 2.0"
- Previous message: Rhonda C: "Re: roaming clients on SMS 2.0"
- In reply to: Cathy Moya [MS]: "Re: Incomplete Network Dircovery of SMS 2003"
- Next in thread: Cathy Moya [MS]: "Re: Incomplete Network Dircovery of SMS 2003"
- Reply: Cathy Moya [MS]: "Re: Incomplete Network Dircovery of SMS 2003"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 6 Oct 2004 09:45:05 -0700
Hi !,
We dont use MS DHCP servers and dont have snmp installed on the
workstations, how can we discover these devices ?.
We do have snmp on our server and after about 72 hours it discovered these.
The FAQ's are useless in this case.
"Cathy Moya [MS]" wrote:
> There are two FAQs about non-AD discovery
>
> Q. Why can't I configure DHCP options for network discovery? (added
> December 12, 2003)
> A. DHCP network discovery is disabled by default when the SMS site is
> running advanced security. This is by design. Advanced security relies on
> using the LocalSystem Account context to access server resources such as
> DHCP data. However, DHCP data cannot be accessed by using the LocalSystem
> Account security context. Therefore, DHCP network discovery is disabled in
> advanced security mode.
>
> For more information about choosing a discovery method, see "Appendix
> C: Client Deployment Planning" in Scenarios and Procedures for Microsoft
> Systems Management Server 2003: Planning and Deploymenton Microsoft
> TechNet.
>
> Q. Why didn't Network Discovery find my systems? (Added July 30, 2004)
> A. Network Discovery will only create a DDR for resource if it can
> positively determine the resource's subnet mask or Active Directory site.
> The subnet mask can be determined if:
>
> . The client's IP address is listed in a trusted router's ARP
> cache, and the router has only a single IP address on that interface.
>
> . The client has an SNMP agent running, and network discovery is
> configured to use the community name the client is configured for.
>
> . The client is a Microsoft DHCP client. This is not an option
> if you are using advanced security because there is no DHCP support for
> network discovery in advanced security. If you are using standard security,
> the SMS site server must have user-level security access on the DHCP servers
> to retrieve database information from those servers. The SMS Service account
> must have domain user credentials in the same domain as the DHCP server.
>
>
> --
> Cathy Moya, MCSE: Security, MCT
> Technical Writer, Enterprise Management Content Group
>
> Check out the SMS Technical FAQ:
> http://www.microsoft.com/technet/prodtechnol/sms/sms2003/techfaq/default.mspx
> This posting is provided AS IS with no warranties and confers no
> rights.
>
>
>
> "drumdave" <drumdave@discussions.microsoft.com> wrote in message
> news:EB7180D9-ADA8-4E8A-888C-8C6E02AB2E09@microsoft.com...
> > Hi,
> > This is for Cathy.
> >
> > I am having the same problem with the same domain structure. Are we better
> > just to push the client out via a login script?
> >
> > It is baffling why it will discover some staic IP's but not a whole lot of
> > others.
> >
> > What log should we look at to try and resolve this issue?
> >
> > There is tons of stuff with SMS 2003 in a AD environment. But us poor
> souls
> > with this older stuff are pretty much left in the dark.
> >
> > Any help on this issue from anyone would be appreciated.
> >
> > Regards,
> >
> > Dave
> >
> > "Lee Thomas" wrote:
> >
> > > Hi Cathy,
> > >
> > > Thanks very much for your post, I am still in the dark why some PC are
> not
> > > being discovered however. The document covered mainly AD issues.
> > >
> > > Kind Regards,
> > >
> > > Lee.
> > >
> > > "Lee Thomas" wrote:
> > >
> > > > Hi,
> > > >
> > > > I have a confusing issue with the Network Dircovery feature of SMS
> 2003.
> > > > Here's the background:
> > > >
> > > > I have SMS 2003 installed on a Windows 2003 server, however my main
> domain
> > > > controller is an NT4 server, therefore my LAN is NT4 based. My LAN is
> only
> > > > made up of one domain and has no subnets. I do make use of a DHCP
> server,
> > > > however most of my PC's have static IP address's.
> > > >
> > > > I have configured the setting of Network Discovery with the following:
> > > >
> > > > Discovery Type:
> > > > Topology, Client, and Client operating system
> > > > Subnets:
> > > > Although I have no subnets on my LAN I stll have filled in this
> section with
> > > > the normal address patten I use on the LAN apart from the last digit
> which I
> > > > inserted as 0.
> > > > Domain:
> > > > I have inserted the name of my domain
> > > > SMNP:
> > > > This is unchanged
> > > > SMNP Devices:
> > > > This is unchanged
> > > > DHCP:
> > > > This is the name of the DHCP server on my LAN.
> > > >
> > > > The problem is SMS has discovered some but not of the PC's on my LAN,
> some
> > > > of these PC's have static IP address's and some have DHCP address's.
> > > >
> > > > Please Help!
> > > >
> > > > Kind Thanks
> > > >
> > > > Lee.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > lt
> > > > --
> > > > lt
>
>
>
- Next message: TerryM: "Re: roaming clients on SMS 2.0"
- Previous message: Rhonda C: "Re: roaming clients on SMS 2.0"
- In reply to: Cathy Moya [MS]: "Re: Incomplete Network Dircovery of SMS 2003"
- Next in thread: Cathy Moya [MS]: "Re: Incomplete Network Dircovery of SMS 2003"
- Reply: Cathy Moya [MS]: "Re: Incomplete Network Dircovery of SMS 2003"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
