I have a queston about the mechanics of System Group Discovery with SCCM 2007 R2. Normally I would lab something like this out, but I don't have access to that today. The question is, when I have client systems that are added to a group in AD, I know I have to run AD System Group Discovery in the target primary site. Do I also have to run AD System Discovery in that site in order to enumerate group memberships? This has an effect on whether we use AD Groups for software distribution target collections or use a less easy to manage solution such as updating collections directly. Thanks, DW

Hi, AD System group discovery will not discover new ressources, only add information to computers that are already in the database. If you only run AD system group discovery then it wont work.Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products

To expand on that, you could get away with only two discovery methods: Heartbeat: so that active clients send a Heartbeat DDR occasionally to indicate they are alive. AD System Group Discovery. Since the Resource exists in the database (from the Heartbeat), then there is something for the System Group DDR to attach to. I know this works because that's exactly what we do. We don't use System Discovery at all. Standardize. Simplify. Automate.