Active Directory Group Populator Management Pack214610

This management pack creates tree of organizational units and groups in OpsMgr Groups like in Active Directory. Before import Discovery Management Pack you must change “distinguishedName” property in Discovery rule “Discover Active Directory Root Organizational Unit” and enable it, or import all packs (sealed library and unsealed discovery mp) and override these properties in authoring pane. All groups will be populated with Microsoft.Windows.Computer and Microsoft.SystemCenter.HealthServiceWatcher classes where Display Names of objects equal name of computer objects in Active Directory group.

All OU will be discovered recursively, all Groups will be discovered recursively!

This management pack uses PowerShell cmdlets of OpsMgr 2007 R2 and not tested with OpsMgr 2012!

Update 08/29/2013 (Version

– Fixed error when OU not discovered if it doesn’t have Child OU;

– Now module GroupPopulator.ActiveDirectory.TimedPowerShell.DiscoveryProvider.GroupPopulator works with Operations Manager 2012;

– Now all 3 modules returns DisplayName property;

– ” – Organizational Unit” and ” – Group” was removed from DisplayName property;

– Other cosmetic changes;

14 thoughts on “Active Directory Group Populator Management Pack214610

  1. Joseph


    I am relatively new to SCOM and stumbled across this management pack, which would make my life alot easier as monitoring needs to be done by the groups we have in AD.

    However I cannot seem to get it to work properly. I get the distinguished name set up correctly and add the management pack in, it will create the folder trees alright, although it still has “organizational unit” in the name, but it will not populate the trees with the computers. I feel like I am missing a step or misinterpreting what this pack does.

    I would be grateful for any clarification,


  2. Pete Zerger

    If you post a question in our OpsMgr forum with a link to this page and some detail of the steps you have tried and any error message you are receiving, we will definitely do our best to help.

  3. John

    This MP Does work great but I would suggest the discovery of multiple domains.  I work in an environment that has multiple domains but I am only able to define one domain in the “distinguishedName” property.  Any chance you would add this feature?


  4. Tobi

    This is a great MP and works as a charm. The only missing feature is to support multiple domains.

    Thank you very much!

  5. Bobgreen Post author

    Thanks! If your domains are trusted, then you can add more similar discovery rules.

    Thank you! This management pack should have access to management server shell. If you have trusts between another domains then you can add these domains using this management pack. Anyway, I will investigate how to achieve it without trusts, but I will write new MP only for OpsMgr 2012 and greater.

  6. koxa

    After installation of your MP all groups have been discovered successfully but just a couple of groups has members the other groups are empty. Could you help me please where to find the cause of issue.

  7. hmarcia

    I’ve added a new Discover Active Directory Root Organizational Unit Discovery rule, target a trusted Domain OU and works great. Now I can create dynamic groups from two different forests.

    Thanks for the great work Bob.

    Copy of Bob’s modified GroupPopulator.ActiveDirectory.Discovery MP can be downloaded from here (excuse the shorten link…testing it)

    Modifications needed highlighted below





  8. Ray

    After installation of this management pack it discovered the groups successfully and most have members but a few of the larger groups are empty.  Are there any known issues with groups containing more than 200 members?  I’ve already tried clearing the console cache using the /clearcache switch.

  9. Kele

    Imported into SCOM 2016 CU3 with no issues and works well.
    Our groups are under 200 for now.
    Thankyou very much!

  10. Elmer Luriz

    Is this supported on SCOM 2016 RU3?


    We have 2 SCOM Environment 2012 and 2016, the group were populated on both versions however when I view the Group Members in 2016 Ru3 it is blank.


    Also if I update or add a group members in AD, how can I force the sync of the group?

  11. Bobgreen Post author

    Elmer Luriz

    I didn’t test it with SCOM 2016 but there is no reasons why it shouldn’t work. I have plans to write new managed module with LDAP authentication but it’ll work only with SCOM 2012 and greater without backward compatibility with SCOM 2007 R2.

  12. Bobgreen Post author


    About 200+ instances. I think it’s a limitation of DataItem and MOMScriptAPI. I hope that managed modules can reach this limitation.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.