"Now to just explain to the user community why there will be 100k+ clients in the console when we haven’t even rolled out one SCCM 2012 client yet." As Jason already mentioned: discovery has nothing to do with the client being installed or not.
This is where the confusion is coming from: "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" That's not true. The client did not have to be installed. AD system grp discovery in CM07 also added group and OU information to resources with client=0. The only change between CM07 and CM12 is: AD group discovery can now also add resources, not only update existing ones. 2013/8/1 chris catlett <[email protected]> > I view “discovery” as FIND ALL THE THINGS. ;)**** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Spinelli, Robert J > *Sent:* Wednesday, July 31, 2013 5:20 PM > *To:* [email protected] > *Subject:* [mssms] RE: AD Group Discovery - SCCM 2012**** > > ** ** > > We never liked system discovery since it always discovered computer > objects that no one cleaned up, so you had thousands of dead machines in > the console. I know you can know filter out stale objects, which is > great. **** > > ** ** > > So the behavior I’m seeing is to be expected. Now to just explain to the > user community why there will be 100k+ clients in the console when we > haven’t even rolled out one SCCM 2012 client yet.**** > > ** ** > > 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 | > [email protected]**** > > ** ** > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Jason Sandys > *Sent:* Wednesday, July 31, 2013 3:09 PM > *To:* [email protected] > *Subject:* [mssms] RE: AD Group Discovery - SCCM 2012**** > > ** ** > > Don’t mix up AD System Group discovery in 2007 with AD Group Discovery in > 2012. They are two completely different things. AD Group Discovery in 2012 > is the evolution of AD Group Discovery in 2007, not System Group Discovery. > **** > > ** ** > > Thus, just like with System Discovery, the presence/existence of the > client agent makes no difference.**** > > ** ** > > Yes, some folks are now using AD Group Discovery as a way to target their > discoveries without having to rely on their OU structure which may not > match up to their management intentions (although that’s odd because by > definition that’s how your AD OUs are supposed to be, but that’s a whole > separate conversation).**** > > ** ** > > J**** > > ** ** > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Spinelli, Robert J > *Sent:* Wednesday, July 31, 2013 2:01 PM > *To:* [email protected] > *Subject:* [mssms] AD Group Discovery - SCCM 2012**** > > ** ** > > 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 | > [email protected]**** > > ** ** > > 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. This transmission may contain > information that is privileged, confidential, legally privileged, and/or > exempt from disclosure under applicable law. If you are not the intended > recipient, you are hereby notified that any disclosure, copying, > distribution, or use of the information contained herein (including any > reliance thereon) is STRICTLY PROHIBITED. Although this transmission and > any attachments are believed to be free of any virus or other defect that > might affect any computer system into which it is received and opened, it > is the responsibility of the recipient to ensure that it is virus free and > no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and > affiliates, as applicable, for any loss or damage arising in any way from > its use. If you received this transmission in error, please immediately > contact the sender and destroy the material in its entirety, whether in > electronic or hard copy format. Thank you. Please refer to > http://www.jpmorgan.com/pages/disclosures for disclosures relating to > European legal entities. **** > > ** ** > > ** ** > > 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. This transmission may contain > information that is privileged, confidential, legally privileged, and/or > exempt from disclosure under applicable law. If you are not the intended > recipient, you are hereby notified that any disclosure, copying, > distribution, or use of the information contained herein (including any > reliance thereon) is STRICTLY PROHIBITED. Although this transmission and > any attachments are believed to be free of any virus or other defect that > might affect any computer system into which it is received and opened, it > is the responsibility of the recipient to ensure that it is virus free and > no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and > affiliates, as applicable, for any loss or damage arising in any way from > its use. If you received this transmission in error, please immediately > contact the sender and destroy the material in its entirety, whether in > electronic or hard copy format. Thank you. Please refer to > http://www.jpmorgan.com/pages/disclosures for disclosures relating to > European legal entities. **** > > ** ** > >
