Introduction to the Service Editor

The Service Editor allows you to define how services in the service hierarchy are dependent on each other, and allows you to define rules that evaluate the severity based on the state of the contributing services. Although you can use the Service Editor to create an entire service hierarchy, it is recommended that you use the Discover Services command to create a basic hierarchy, which you can then fine tune. You can use the Service Editor to modify the status propagation so that it is tuned for your environment. You can also build on the SPI service hierarchy, using it as a building block in a larger hierarchy that you create.

1. Learn about the service hierarchy.
2. Learn how to plan a service hierarchy.
3. Learn about Service IDs.
4. Sketch out a plan for your service hierarchy that includes the high-level services that you want to monitor, for example, printing, e-mail, internet access and so on, noting the service hosting for each service.
5. Make sure that all nodes needed for the service hierarchy are configured managed nodes.
6. Execute the command Tools Microsoft Windows Discover Services.
7. Use the Service Editor to add folder-based services for all high-level services in your service hierarchy. Accept the default value propagation and calculation values. You can change these values later if you need to.
8. For each node, add a dependency from the Windows OS SPI hierarchy to all services that reside on that node.
9. Create folder-based services for any special applications or processes are monitored by your policies. Include these services in the service hierarchy. Ensure that the service IDs match those in the policies.