Re: Old NetBIOS names in SMS

hmmm that ought to be taking care of the obsolete clients. You could see if
those machine names are still being picked up from DNS or if they're still
registered in DHCP since you're using network discovery.
--
Jeff Gilbert, MCSE
Technical Writer | Windows & Enterprise Management Division
Microsoft Corporation

This posting is provided "AS IS" with no warranties and confers no rights.

"John" <John@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9C0F9C6D-AC16-4481-8FCE-21E299687561@xxxxxxxxxxxxxxxx
Delete Obsolete Client Discovery Data = 7 days

John



"Jeff Gilbert [MSFT]" wrote:

I'm sure of your exact network configuration, but scheduling AD system
discovery every 15 minutes seems pretty aggressive to me. Not enabling
DNS
scavenging has been known to cause issues similar to this, and enabling
it
may help you.

What is your schedule for the delete obsolete client discovery data
maintenance task set to?
--
Jeff Gilbert, MCSE
Technical Writer | Windows & Enterprise Management Division
Microsoft Corporation

This posting is provided "AS IS" with no warranties and confers no
rights.

"John" <John@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A2653C86-126F-4126-999D-01FF32314F03@xxxxxxxxxxxxxxxx
Jeff,

If all our Delete Aged tasks are configured, what do you think could be
another issue? Would we have to clean up stale DNS?

Thanks,
John



"Jeff Gilbert [MSFT]" wrote:

This can occur if the systems are still registered in DNS. AD system
discovery checks for active computer accounts and then bounces those
off
of
DNS for IP resolution. This can usually be traced to DNS scavenging
issues.
The delete aged data maintenance tasks should take care of the old
data
according to the schedule you've set for them.

Hope this helps,

Jeff Gilbert, MCSE
Technical Writer | Windows & Enterprise Management Division
Microsoft Corporation

This posting is provided "AS IS" with no warranties and confers no
rights.

"John" <John@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:26CEB15B-4737-42F7-9F09-3DF25E3EBC14@xxxxxxxxxxxxxxxx
AD System = 15 minutes
AD User = 1 Day (for what this my be worth)
AD System Group = 10 minutes

John


"Steve Thompson" wrote:

"John" <John@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:FA0FABD1-6C1F-4905-946F-B95B97C82F38@xxxxxxxxxxxxxxxx
Yep. We are running Discovery Methods.
Heartbeat = 1 hour
Network = 2 hours.

What about AD discovery?

ST











.

Relevant Pages

  • Re: Old NetBIOS names in SMS
    ... What is your schedule for the delete obsolete client discovery data ... Would we have to clean up stale DNS? ... This can usually be traced to DNS scavenging ...
    (microsoft.public.sms.inventory)
  • Re: SMS System Discovery Not Listing All Systems - Suggestions?!
    ... Are you using MS DNS or Other DNS? ... I've recently setup SMS on our ... domain and using AD Discovery methods. ... Do the systems have to be online ...
    (microsoft.public.sms.setup)
  • Re: AD System Discovery, Multiple Domains and DNS
    ... There A record in DNS will be different, ... > The problem has to do with trying to setup SMS to manage systems on ... > Discovery method to get those systems into your collection. ... > systems were only being discovered in our parent domain, ...
    (microsoft.public.sms.setup)
  • Re: AD System Discovery, Multiple Domains and DNS
    ... There A record in DNS will be different, ... > The problem has to do with trying to setup SMS to manage systems on ... > Discovery method to get those systems into your collection. ... > systems were only being discovered in our parent domain, ...
    (microsoft.public.sms.admin)
  • Re: Decommission a server with AD installed
    ... you need to get DNS running on another server. ... > Third, if you don't care where the FSMO roles wind up, you can simply run ...
    (microsoft.public.win2000.setup)
Loading