Greetings, New to SCOM. Trying to understand the difference between creating Monitoring for Windows Service via the Windows Service MP Template Wizard and creating a Unit Monitor of type Basic Service Monitor.
It seems that (along with additional ability to monitor Performance) the former creates [an instance of?] Basic Service Monitor within its own newly created class (or object? still shaky on terminology) making it a Monitor Target of this Basic Service Monitor; and the latter creates only Basic Monitor targeting existing class\object. Please confirm or correct if that's accurate. The main benefit of the Template for me is that I am able to drill down to the Service Monitor in a Diagram View and (for example) place only it in Maintenance Mode, while still monitoring the rest of the Windows Server/Computer object; as opposed to in the case of having only Basic Service Monitor manually created under say Windows Server target I am unable to operate on it separately and am forced to place the whole Windows Server object into Maintenance Mode. Also, a product like SAVISION Live Maps is unable to "see" Basic Service Monitor as an element to be dragged onto a map; whereas it is able to "see" the class\object created by the Template as a separate element. Now if the above is more or less true, than does it mean that if I want to monitor say 5 Windows Services in a way where I am able to operate on them independently of the Windows Server object - they each must be defined as an object of its own class? Observation: After creating Windows Service Monitor via the Template Wizard I ended up with 2 "Service Running State" monitors. One - Inherited From "Windows Service" of Management Pack "Windows Service Library"; and the second - Not inherted and is of the Management Pack which I defined as destination MP during one of the configuration steps. I also targeted a specific Group to narrow down the scope of the monitor. The first monitor which is inherited from the Windows Service has a number of "Enable" parameter Overrides applied to it targets of which include the object itself and the DNS name of a server contained within the targeted Group - that is to say this monitor is "not monitoring"; why does it get inherited or instantiated at all? And lastly does running Windows Service Monitors created via the Template Wizard have a greater performance impact on the SCOM system, as opposed to Basic Service Monitors created manually, considering that I am not using the Performance counters of the former? -- Make note of my new Email address: [email protected]
