So at this point, we’ve covered Part 1 of the Skills Measure “Configure Data Center Process Automation”. Now we will cover Part 2 “Deploy Resource Monitoring”.

I figured that I would break this into a series, covering each of the higher-level categories/areas and their sub topics.

So, to start let’s cover the second category: Deploy Resource Monitoring.


2.0 – Deploy Resource Monitoring


2.1 – Deploy End-To-End Monitoring

  • Deploy agents
  • Discover and deploy network device monitoring
  • Import and configure management packs
  • Deploy and configure monitoring of a heterogeneous virtualization infrastructure


2.1.1 – Deploy Agents

This topic is a little vague. Which agents is it referring to? Almost every System Center component has an Agent (i.e. SCOM, SCCM, VMM, DPM). How do you deploy these Agents? There are several ways, including command line, through the various consoles, even through GPOs for some of them.

For reference, here are some TechNet articles that review how to install the various Agents:


2.1.2 – Discover and Deploy Network Device Monitoring

I previous wrote an article on monitoring SNMP devices (i.e. network devices like gateways and routers), with SCOM.

Check out the article here: SCOM SNMP Monitoring


2.1.3 – Import and Configure Management Packs

I previously wrote a Configuration Guide on Importing Management Packs, so take a look at that for a reference (it also has video walkthroughs, but no audio commentary).

As for the part about configuring Management Packs, that is unique to each MP. However, as a general example, MPs are made up of Rules and Monitors. If you want to configure (i.e. change from their default settings) the Rules and Monitors from a Management Pack, navigate to the Authoring workspace, and expand Management Pack Objects. There will be a separate selection for Monitors and for Rules.

Configure MPs

You may have to scope the view to the MP you are interested in, and then find the Monitor/Rule you are looking to configure.

Scoped Monitors

When you find the Monitor/Rule that you want to change, you need to right-click on it and choose Override. You can then change the default configuration(s) as desired.

Override Example


2.1.4 – Deploy and Configure Monitoring of a Heterogeneous Virtualization Infrastructure

For heterogeneous environments, that usually refers to UNIX/Linux systems together with Windows. I’ve already written a Configuration Guide  on Configuring Computers and Devices to Manage (aka. installing the SCOM Agent).

I’ve also written an article on Monitoring Linux with SCOM. I haven’t done much by way of modifying/configuring Linux monitoring, but I’m sure it is a similar process as already described.


2.2 – Configure End-To-End Monitoring

  • Configure overrides
  • Create synthetic transactions
  • Configure Outside-In monitoring
  • Configure application performance monitoring (APM)
  • Create distributed application models
  • Integrate the monitoring infrastructure with Global Service Monitor (GSM)


2.2.1 – Configure Overrides

This definitely has to do with SCOM, and instead of just repeating myself, please refer to the Import and configure management packs section on this page since it covers the overrides element.


2.2.2 – Create Synthetic Transactions

Here is a link to additional information:

There are multiple types of transactions that can be created, including Web Site, Database, and TCP Port.

If you navigate to the Authoring workspace, expand Management Pack Templates and right-click on any of the entries, and choose “Add Monitoring Wizard”. You will have several options to choose from.

Add Monitoring Wizard - Monitoring Type

You can also take a look at my article on SCOM Synthetic Transactions.


2.2.3 – Configure Outside-In Monitoring

This statement is rather vague, however, the first thing I think of is Global Service Montior (GSM). I haven’t personally used this feature before, but I understand its premise.

Here is an official description from Microsoft: “System Center Global Service Monitor is a cloud service that provides a simplified way to monitor the availability of external-web-based applications from multiple locations around the world. Importantly, Global Service Monitor monitors applications from the perspective of the customers who use them. Because Global Service Monitor monitors from locations that are correlated to customer geographies, application owners can gain insight into customer experiences in addition to the separate problems related to external factors, such as Internet or network problems, from application or service problems. The Global Service Monitor monitoring experience focuses on the application instead of the infrastructure or individual URL. Global Service Monitor integrates with the Operations Manager console so that you can monitor external- and internal-facing web applications in the same place you monitor other applications.

Here is a link to “Getting Started with Global Service Monitor”:


2.2.4 – Configure Application Performance Monitoring (APM)

I have not setup this feature in my lab environment, but for a good walk-through, take a look at the following article:


2.2.5 – Create Distributed Application Models

Here is some starting information on Distributed Applications (DA’s):

In the Authoring workspace, right-click on Distributed Applications, and choose New Distributed Application.

This will open the Distributed Application Designer. This is where you can collect the various components that make up the application model, and connect those components together through Relationships.

SCOM Distributed Application Designer

Here is an additional series that provides good information:


2.2.6 – Integrate the Monitoring Infrastructure with Global Service Monitor (GSM)

Here are some useful links about GSM. Like I have already mentioned, I haven’t really had an opportunity to work directly with this functionality.

Here is a link to “Getting Started with Global Service Monitor”:

Global Service Monitor:


2.3 – Create Monitoring Reports and Dashboards

  • Implement service-level tracking
  • Implement reports, including chargeback reports and System Center Manager data warehouse reports
  • Implement dashboards


2.3.1 – Implement Service-Level Tracking

Service Level Tracking is done via SCOM, and is usually tied to a Distributed Application Model which represents your application.

Here’s a link to some information:

However, Service Level Tracking can also relate to Service Manager, in reference to SLAs concerning Incident, Problem, and Service Request management.

Here is a link to some information on this, specific to SCSM:


2.3.2 – Implement Reports Including Chargeback Reports and System Center Manager Data Warehouse Reports

Reporting in System Center is available for almost all components of the suite. Operations Manager (SCOM), Configuration Manager (SCCM), Data Protection Manager (SCDPM), Service Manager (SCSM), Virtual Machine Manager (SCVMM), all have reporting features.

Some of these components, like Virtual Machine Manager, have their reporting feature directly tied into Operations Manager; while others, like Service Manager, have independent reporting features.

As for ‘chargeback’ reports specifically, this type of report is available through Service Manager, but it requires Operations Manager and Virtual Machine Manager to fully utilize.

Here is a link to some information to get you started on Chargeback reporting in System Center:


2.3.3 – Implement Dashboards

Dashboards are mainly a SCOM thing. Here is a link to a TechNet blog post about the SCOM dashboards:


Well, that’s it for this section. Next we will review the items covered in the next Skills Measured – Part 3: Configure and Maintain Service Management.