Advanced Monitoring with System Center Operations Manager 2007 and System Center Virtual Machine Manager : Capabilities

Microsoft Hyper-V Server R2 Limits

walterch — Mon, 20 Apr 2009 23:49:44 GMT

Monitoring Windows 7 (Beta)

walterch — Fri, 09 Jan 2009 20:09:53 GMT

This blog is just to share some fun an unexpected results I had this morning. I was working on some ADI stuff and didn't exclude 'clients'. 25 minutes later, my newly provisioned, Windows 7 Beta Client was being monitored by OpsMgr. Although no MP is available, you can readily whip up some of your own rules if you choose to.

Windows 7 Beta is a Hyper-V Guest and OpsMgr correctly identified.

At first glance, AD Client Monitoring works just fine:

Lastly, a few performance collection rules came on-line nicely:

So all in all , nothing really new but for us OpsMgr guys its nice to know monitoring Windows 7, not withstanding a official MP, will be attainable and easy to demonstrate if required.

OpsMgr R2 - Process Monitoring

walterch — Mon, 08 Dec 2008 19:33:44 GMT

With the anticipated release of R2, the current beta has revealed some very simple, yet highly effective improvements. My favorite is the addition of the Process Monitoring Management Pack Template. Although the functionality is reproducible in SP1, it is far easier to configure. One particular problem I always encounter by end-users is the presence of the cscript.exe process. Sometimes 1 instance, sometimes 4. The variability, depending on deployed management packs, always has and still makes many server owners and security personnel nervous. We now can monitor it. Below I quickly demonstrate how fast and it easy to monitor a particular process and target all Windows Servers:

1. Launch the Operations Console and go to Authoring / Management Pack Templates / Process Monitoring:

2. Right-click and choose 'Add Monitoring Wizard' and choose 'Process Monitoring' then click Next:

3. Fill in all General Properties:

4. You can monitor expected processes or for the presence of process you don't want running. In this example we will monitor for a known process, cscript.exe:

5. Next you can define when an Alert is generated, either on the number of processes, maximum and minimums or for duration. The latter is excellent for diagnosing out favorite generic Alert that a script field :-) In the example below, we want an alert generated if any cscript.exe process runs for more than 120 seconds:

6. Next we can define what performance data is collected:

7. After reviewing the summary, click Create.

Simple, flexible and powerful! Excellent for monitoring non-Microsoft processes.

Monitoring Windows Server 2008 with OpsMgr 2007

walterch — Fri, 24 Oct 2008 16:58:00 GMT

Gotta' give credit where credit is due.....nice write up Pete!

http://technet.microsoft.com/en-us/magazine/cc974507.aspx