SCOM Fundamentals

Here’s some notes I made on SCOM when I was talking about it to some colleagues. I am sure there is plenty more I could have said but this might serve as a good starting point for someone trying to understand the concepts.

Classes: https://technet.microsoft.com/en-gb/library/hh457568.aspx

All classes have a base class (not parent) and lead back up the tree to object:
scomclasshierarchy

Classes have the same properties of the base class plus their own. The values of the properties can of course be different.

Workflows targeted at a parent class also target the child (but not the other way round).

If a workflow is targeted at a class it will run on every agent that has an object of that class on it.

Relationships: https://technet.microsoft.com/en-gb/library/ee957027.aspx

Hosting Relationship – i.e Windows Computer hosts Logical Disk (1 to Many) – most relevant.
The hosting class is knows as the parent class.
The hosted class is known as the child class.

Containment Relationship – i.e when an object is a member of a group (Many to Many)

Reference Relationship – i.e. if a databases references another database

Workflows: http://blogs.technet.com/b/authormps/archive/2011/02/24/workflow-types.aspx

Discoveries
Monitors
Unit – Basic monitor
Rollup – Each target has Availability, Configuration, Performance and Security
Dependency – Used to rollup health across Hosting or Containment relationship
Rules can do various things including collect data, create an alert etc
Task
Diagnostic
Recovery

Other stuff:

Agents should be distributed amongst management servers.

For large environments there are guidelines on number of servers and role:

Overrides used to change the properties of a rule/monitor for a particular class, group or object. i.e disable a monitor, change the alerting threshold.

Run As Configuration – Some workflows have their own Profiles associated with them. The Profile can be populated with specific accounts otherwise the default action account is used.

Performance Counters – Create performance based collection rules to collect additional counters.

Notifications – Done through combination of channel and subscriber.

Can target only specific monitors/alerts for specific groups/people.

Data Warehouse – No datawarehouse server as such but it is a separate database.

Dashboards get data from DW performance views get data from main database.

Retention settings can be changed with a tool called dwdatarp.exe or in SQL directly.

Additional components to look at:
Distributed Applications
Service Level Tracking
Global Service Monitor (GSM)
Web Application Transaction Monitoring
Application Monitoring
.Net
Java
Monitoring Network Devices
Reporting
Adding Dashboards/Visio Diagrams to Sharepoint

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s