I have been tasked doing some work on an Ops Mgr 2007 R2 (Version 6.1.7221.0), all the dynamic groups except the default ones, have no members. Various MPs have been added, one is the SCVMM 2008 MP, another is the Exchange 2010 MP, etc. None of the MP dynamic groups populate. If I create a new group and use a dynamic query then this does populate, I am unable to override any alert by group and as the Exchange 2010 MP causes all systems to show as having errors then this is an issue. Any help would be greatly appreciated. Lee

Hi Lee, Can u pls give some examples of exactly which "dynamic" groups you are referring to that have no members, and how you have configured the groups i.e. what parameters you have set for the discoveries? Thx, John Bradshaw

The MP defined groups typically require that "allow agent proxy" setting on each agent involved. Have you checked that?Microsoft Corporation

Hi, John, If you go into Authoring -> Groups the groups that appear in there are mostly Dynamic groups and it's those that aren't populating with members, the standard ones, i.e. Agent Managed Systems, Network Devices, etc, all populate with system names but the groups for the management packs don't populate. Dan, I am going through setting the 'Allow Agent Proxy" on all clients, is there a way to automate this? Regards and thanks, Lee

Hi Lee, If u r specifically referring to the Exchange 2010 groups, then the MP guide tells you how to enable discovery. Most of that MP comes default turned off. Hth, John Bradshaw

to mass enable proxy settings to enabled, run the three lines of code in the opsmgr poweshell console. change 'domainname' to 'the name of your domain' $agents = get-agent | where {$_.domain -match 'domainname'} $agents | foreach {$_.ProxyingEnabled = $true} $agents | foreach {$_.ApplyChanges()} Hope this helpsScott Moss MVP (Operations Manager) | President - System Center Virtual Users Group | Vice President - Atlanta Southeast Management Users Group (ATL SMUG)

Thanks for all the help, I have now sorted this, it was due to the client agents not being proxy enabled. Scott, the powershell has been turned into a script and runs as an automated process now. Thanks again. Lee