Creating Groups of Health Service Watcher Objects based on other Groups

<!--[if lt IE 9]>


Comments (23)
  1. Kevin Holman says:

    @ Yaniv –

    Easy. Create a state view. Scope it to class of Windows Server OS, then filter it by the custom group.

  2. Kevin Holman says:

    @Rupert – yes – I think you are oversimplifying. The customer in this case wanted to specifically create a group of HSW instances ONLY, for the purposes of availability reporting. They did not want computers and HSW’s, hence this example, which is something completely different.

  3. Kevin Holman says:

    Oh, I see. That’s weird – and you are right there must be some relationship that does this. I’d have to play around. It is a pity that our group criteria does not support "anding" of multiple object types instead of the way it is, with only being able
    to select OBJECT (all) or a single specific class.

  4. Rupert S says:

    Am I missing something? Can’t this also be achieved by creating a group with dynamic membership based on server name, for example, that adds both the Computer object and the HSW object?

  5. Frikkie says:

    @Kevin – I would just like to esquire about the code. Is it specifically for the 2012x system or can it be used on 2007 as well?

  6. Yaniv says:

    Hi Kevin. I want to create a group which will have Windows Server Operating System objects (and not the Windows Computer objects) based on OU (Organizational Unit) and their related Health Service Watcher (which I know will have to come from Windows Computer
    objects…). Well I succeeded, but the thing is when I create a new State view based on that group, I see also the Health Service objects.. How can I eliminate them?


  7. Yaniv says:

    @ Kevin :-),

    he he … Yes I know that…

    Maybe I skipped some details: I created a custom group to have Windows Server OS + Health Service Watcher objects. When I go to SCOM Console -> Authoring -> Groups -> MyCustomGroup -> View Members, I get what I asked and that is both, Windows Server OS and
    Health Service Watcher objects. Great. Now, I created new State view and left in "Show data related to:" OBJECT. In "Show data contained in a specific group:" I targeted to MyCustomGroup (which gave me WSOS + HSW objects…). Now I am expecting to see ONLY
    WSOS + HSW objects BUT I see also "Health Service" objects. I want to get rid of the Health Service objects… Is it possible (since there is a relationship defined between HSW and HS classes…) ?

    My apologies for the looooong explaination 🙂


  8. Yaniv says:

    Hi Kevin. Do you any new insights here?

  9. Gopal says:

    Hi Kevin, I have created a custom group. I could see the members of the custom group. But when i check for reporting, the custom group is not getting listed. I found that, the group is not listed in DataWarehouse also. Its been a week after creating the
    group. Please help what could have gone wrong and what needs to be done to fix this?

  10. In response to the question by Yaniv – one solution is to use the state view widget in a Dashboard.

    We see the behaviour in the state views as Yaniv has correctly stated the health service rolls up to health service watcher. When we only want to scope on one class then we can scope by "Show data related" to a specific class so as not to see the objects that
    roll up to our class.

    But if we have multiple class types in the group, we can’t scope by multiple classes in the State View. We need to use a dashboard instead and just scope to our group.

  11. Anonymous says:

    The SQL 2014 Management Packs have fundamentally changed the way that SQL Server classes are scoped.

  12. Pavithra says:

    Hi Kevin, We have checked the "Health Service Watcher Group/Microsoft.SystemCenter.AgentWatchersGroup" – group for alert forwarding from SCOM 2012 on the connector. Though this default group is enabled for alert forwarding, not all alerts are forwarding.
    Is there anything that has been missed along with group enabling?

  13. Kevin Holman says:

    Why would you filter anything on that default group?

    If you want HSW alerts – I’d filter for the computer down and HB failure monitors specifically, or the HSW class instance.

  14. Anonymous says:

    SCOM can be quite complicated!
    One of the biggest confusions is around why agents go gray, why you

  15. How can I create one Dynamic SCOM Group that only show members with a specific Health State? For example one group for SQL databases that not show “Health State = Not monitored”.

  16. esky says:

    is it possible to create a group of just temperature sensors ? eg – temp monitor from ups and temp monitor from nas in the same group ?

  17. Kapil D says:

    Hello Kevin, I have similar requirement for a client of mine and I need to have the health service object for ALL windows computers as well as unix computers. This is to calculate availability for reporting purpose. Any help will be greatly appreciated.
    Kapil D

  18. Jorique says:

    Hi Kevin,
    longtime listener, first time caller… I am absolutely certain this is the solution to my conundrum, but I don’t know how to alter the code to fit my environment. Can you help me understand how to get this working?

    1. Kevin Holman says:

      Well, what are you trying to do?

      1. Jorique says:

        I have created a group specifically for windows computers and I would like to populate the complimentary HSW group. I was parsing through the XML, but admittedly I am a novice, so I’m not sure what variables need to be altered to reflect my environment. Also, I noticed that the libraries in use by your sample are not the same as in my group, despite leveraging what I thought to be similar objects. e.g. System Health Library. I’m not sure if I should be replacing existing code in my current XML with this code or supplementing. I realize I might be clear as mud, but I hope that helps you understand where I’m coming from.

  19. Gr8lemon says:

    Hey Kevin,

    Thanks for everything you do for the SCOM community! I’m hoping this will solve a long standing frustration I’ve been having, however when I go to import it I get this error:

    Error 1:
    Found error in 1|Microsoft.Windows.Server.Custom||UINameSpacec68c38acf2ae45d689fb7bfe26eca849.Group.DiscoveryRule/GroupPopulationDataSource|| with message:
    The configuration specified for Module GroupPopulationDataSource is not valid.
    : Cannot find specified MPElement SC!Microsoft.SystemCenter.HealthServiceWatcher in expression: $MPElement[Name=”SC!Microsoft.SystemCenter.HealthServiceWatcher”]$
    Cannot resolve identifier SC!Microsoft.SystemCenter.HealthServiceWatcher in the context of management pack Microsoft.Windows.Server.Custom. Unknown alias: SC

    Any ideas on what’s wrong?

    Thanks again!!

    1. Kevin Holman says:

      You simply need to update your reference. In my example code – i reference the system center library with “SC!” however since you are doing this in an MP that you likely created using the console – you have some other Reference Alias for the Microsoft.SystemCenter.Library. You just need to update all the places using “SC!” in the new code you are adding – to use the existing alias for that MP which you will find in your manifest.

      1. Gr8lemon says:

        That worked perfectly, thank you!

Comments are closed.

Skip to main content