Can someone else confirm what I'm seeing in 2012?

2012 AD Group discovery will now discover any machine that is part of an AD 
group even if the SCCM client isn't installed.
2012 AD Group discovery will now discover any machine that is part of an AD 
group even if that client isn't managed by the primary performing the discovery

In 2007 the following would have to be true for AD System Group discovery (this 
discovery method no longer exists in 2012) to discover the AD groups a machine 
was a member of


*         SCCM Client was installed on the machine being discovered

*         The primary performing the discovery would only discover machines 
that were assigned to that primary.  Meaning if you have 3 total clients in 
your environment each assigned to one primary (ex: S01, S02, S03) in order to 
get the AD groups the machines are members of, each primary would have to 
perform the discovery.  You would then see all the groups each client was a 
member of when looking at the info from the central site, since it would flow 
up from each primary.

What this means to me is even if we only have 1 SCCM client installed in our 
environment the 1st time AD Group discovery runs that is scoped to an OU that 
has AD groups with machines in it, you'll see those machines in the console.  
You will see client=no, but you could see thousands of devices (in our case you 
would).   We don't use system discovery at all, but by doing this its almost 
like running a stripped down version of system discovery since the machine 
record ends up in the console.

Thank you.

Robert Spinelli | CTS | GTI | 575 Washington Boulevard, Jersey City, NJ, 07310, 
United States| T: +1.201.595.6820 | C: +1.917.538.6192 | 
robert.j.spine...@jpmchase.com<mailto:robert.j.spine...@jpmchase.com>


This communication is for informational purposes only. It is not intended as an 
offer or solicitation for the purchase or sale of any financial instrument or 
as an official confirmation of any transaction. All market prices, data and 
other information are not warranted as to completeness or accuracy and are 
subject to change without notice. Any comments or statements made herein do not 
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and 
affiliates.





Reply via email to