Re: Active Directory Discovery

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

The area is a leased out area and we do not want to even be discovered, do
not want people to remoting this PC's nor do we want to take any chance of
things getting pushed out to them.

"Kim Oppalfens <MVP>" wrote:

But what is the reason not to discover them.
Discover doesn't install anything at all on the client. I can see the
argument for not making them sms clients.
We can exclude machines from installing the client, excluding them from
discovery is much trickier.

Kim Oppalfens
MVP SMS

"Jowest" <Jowest@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6C24356C-1689-4524-B75C-935DC180615A@xxxxxxxxxxxxxxxx
We have installed clients on machines that we do not want discovered by
adding our active directory site to our site boundaies, all of these PC's
are
in a specific subnet within our domain. We did not see a way in site
boundaries to exclude a subnet.

"Kim Oppalfens <MVP>" wrote:

Erm,

You can't create exclusions in discovery methods. Discovery methods are
configured by including stuff.
May I ask what you are trying to accomplish?

I have heard of people wanting to exclude machines from becoming clients,
never heard of anyone insisting on machines NOT being discovered.

Kim Oppalfens
MVP SMS


"Jowest" <Jowest@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3624D025-C7E4-4AC0-B0BF-7A792AD72589@xxxxxxxxxxxxxxxx
How do we exclude a subnet from being discovered in SMS 2003 SP2 with
the
following discovery methods enabled:

Windows user account discovery
Windows user Group Discovery
Heartbeat Discovery
Network discovery
AD system discovery
AD user Discovery
AD System Group Discovery.


We have one domain and the subnet that we want to exclude is also an OU
in
Active Directory. SMS has already discovered the workstations in this
subnet
through a combination of discovery methods and we are not sure how to
go
about getting rid of the unwanted workstations. Do we have to make
exclusion
in each discovery method? Is there an easier way to do this in one
location
with the site/roaming boundaries?

Thanks for your help.




.

Relevant Pages

  • Re: Preventing SMS Management of XPEmbedded Devices
    ... But you can exclude them from installation unless you have ... client pushinstallation enabled for your site. ...
    (microsoft.public.sms.admin)
  • Re: Active Directory Discovery
    ... Discover doesn't install anything at all on the client. ... We can exclude machines from installing the client, ... You can't create exclusions in discovery methods. ...
    (microsoft.public.sms.setup)
  • Re: SMS 2003 Network Discovery
    ... the subnet mask, we aren't creating the DDR. ... Network discovery works best when it is hitting the DHCP server. ...
    (microsoft.public.sms.admin)
  • Re: client assignment
    ... clients unless you ahve configured your AD sites with IP subnets. ... Discovery and therefore we pull there IP information. ... > As I said this a test environment with AD and the subnet is 192.168.2.0 ... > I know the first thing you do when see an assignment problem is check the ...
    (microsoft.public.sms.setup)
  • Re: sms2003 network discovery
    ... just enter the subnets on the Subnets tab of the Network Discovery ... If I leave the client push installation disabled initially, ... > push the client per the discovered resources, basically subnet by subnet. ...
    (microsoft.public.sms.admin)