Gowdhaman

  • The relationship is not required here as I’m extending an abstract class “Microsoft.SystemCenter.SyntheticTransactions.TCPPortCheckPerspective”.

    You cannot discover an instance of parent class as instance of child class in a hosting relationship. The hosting relationship implies, all instances of child class are instances of parent class but no…[Read more]

  • SCOM is exceptional tool which allows IT Administrators to customize the monitoring scenario to any extent. To have a customized monitoring solution, one must understand the authoring capabilities in SCOM, so that […]

    • thanks. great stuff. can I ask why you chose ‘hosted=True’ in the class definition? I thought this implied that the new class was hosted on another class, but I don’t see a Relationship defined anywhere in your MP.

      I have been playing around with setting up a powershell script discovery to query scom for ‘node’ instances whose ‘vendor’ is ‘ironport’ to create new instaneces of a class called ‘ironport,’ hosted by the class ‘node’, but xml hurts my eyes and silect mpauthor and the 2007 authoring console are not letting me ‘host’ a new class ‘ironport’ on the existing class ‘node’.

    • The relationship is not required here as I’m extending an abstract class “Microsoft.SystemCenter.SyntheticTransactions.TCPPortCheckPerspective”.

      You cannot discover an instance of parent class as instance of child class in a hosting relationship. The hosting relationship implies, all instances of child class are instances of parent class but not the opposite.

    • Right. The hosting class instances already exist in scom. My goal is to target the discovery at the existing class ‘node’ to discover instances of a new child class hosted on ‘node,’ called ‘IronPort’.

  • Gowdhaman changed their profile picture 3 years, 7 months ago

  • I have mentioned the reason for not discovering the services as instances in start of my post. Doing so will impact performance badly. Since we are targeting windows computer instance, a monitor would display either if all automatic services are running or not. But it cannot generate alert for each automatic service which is not  running. We n…[Read more]

  • Monitoring services in windows computers is available out of box in SCOM through Service Monitoring Template. But in a large enterprise with over 1000s of windows computers and 100s of applications, it is […]

    • Good stuff. Just curious why you chose a rule instead of a monitor. With a monitor you can track health state/availability over time. Also, what if you discovered all instances of automatic services with PowerShell, then you could use scom overrides to disable the monitoring. Having the instances in scom would allow you to target other rules and monitors at the services later if you wanted to. (full disclosure: I do happen to be looking for guidance on authoring a powershell discovery)

    • I have mentioned the reason for not discovering the services as instances in start of my post. Doing so will impact performance badly. Since we are targeting windows computer instance, a monitor would display either if all automatic services are running or not. But it cannot generate alert for each automatic service which is not  running. We need a rule to do that. Hence we can have a monitor if we need to track availability but not for alerting.

    • i have edit the path as below.

      \<hostname>ServicesExclusionListWindowsAutomaticServiceMonitoringExclusionList.csv

      inside the .csv i have add “Application Experience,ALL_COMPUTERS”
       

      and monitoring doesn’t seem working when i try manually stop one of the automatic state service.