Hello, maybe I missed some part in the documentation, but it is not clear to me how to build a dynamic group, which only contains the FSMO role "PDC Emulator". While there is an attribute "PDC Emulator" after importing the ADMP, I can use this attribute only on the left side of a formula and it doesn't conain a single value like "1" or "True", but instead holds the FQDN of the DC wich is assinged the role. Regards Carsten

Hello, maybe I missed some part in the documentation, but it is not clear to me how to build a dynamic group, which only contains the FSMO role "PDC Emulator". While there is an attribute "PDC Emulator" after importing the ADMP, I can use this attribute only on the left side of a formula and it doesn't conain a single value like "1" or "True", but instead holds the FQDN of the DC wich is assinged the role. Regards Carsten I don't recall if this FSMO role information is available through WMI or registry or if you have to script it but in any case to satisfy this scenario you could create an custom extended attribute. The attribute is targeted towards "Domain Controller" or another class that suits your needs and uses the registry,wmi, or a script to populate the attribute value. This isn't the actual solution just a concept you could use developing one

While the PDC Emulator could be queried through WMI (I use it in group policies), this is not what I intend - or to use your words: I am looking for a solution (if there is any), rather than a concept. For the concept is already there: it is the dynamic groups and attributes SCOM offers. The situation is: the AD Management Pack brings an attribute PDC Emulator, and also brings some code, that fills this attribute. After importing the ADMP, you will have the name of the DC, which holds the PDC Emulator role in this attribute. The quest is: can I use this attribute to create a dynamic group in SCOM, so that I can do a monitor override just for this group. Or to say it in a different way: the override should only be for the DC, which holds the PDC Emulator FSMO role (say DC-1). And if this role is transferred to another DC (say DC-2), the override should reflect it and affect DC-2 then and not DC-1 anymore. If I am still not clear in what I say, imagine a group policy, which is bound to a WMI filter. This group policy will self-adjust which computers it covers, while the results of the WMI query change. C.

While the PDC Emulator could be queried through WMI (I use it in group policies), this is not what I intend - or to use your words: I am looking for a solution (if there is any), rather than a concept. For the concept is already there: it is the dynamic groups and attributes SCOM offers. The situation is: the AD Management Pack brings an attribute PDC Emulator, and also brings some code, that fills this attribute. After importing the ADMP, you will have the name of the DC, which holds the PDC Emulator role in this attribute. The quest is: can I use this attribute to create a dynamic group in SCOM, so that I can do a monitor override just for this group. Or to say it in a different way: the override should only be for the DC, which holds the PDC Emulator FSMO role (say DC-1). And if this role is transferred to another DC (say DC-2), the override should reflect it and affect DC-2 then and not DC-1 anymore. If I am still not clear in what I say, imagine a group policy, which is bound to a WMI filter. This group policy will self-adjust which computers it covers, while the results of the WMI query change. C. Conceptually it would be nice to be able to fill the value field with a variable using something like the following: $Target/Host/Property[Type=” Name of class ”]/PropertyName$ In your case it would be $Target/Host/Property[Type=”Microsoft.Windows.Server.AD.DomainControllerRole”]/PDCEmulator$. However, I don't believe this will work so I believe you are stuck with trying to find another alternative which would be writing a simple custom attribute that evaluates to a true/false value.

OK, so it seems, there is some function missing. Indeed it should work as posted above: $Target/Host/Property[Type=”Microsoft.Windows.Server.AD.DomainControllerRole”]/PDCEmulator$ Maybe with OpsMgr 2012? Hop so. Regards Carsten