• After you select the appropriate object you will see the override properties page. There may be as few as one rule to multiple rules that you can modify. Here you are going to need detailed knowledge about the technology that you are monitoring.
• At the bottom of this page you will need to select the management pack to save the override to. DO NOT USE THE “DEFAULT MANAGMENT PACK”!
• If you don’t have a custom management pack to save it to you can create one from this window. Just follow the dialog boxes.
• When you are done say ok and the changes will be saved.
• This article will show the basics of how to create an override
• This will not show the values to use. For this product knowledge of the technology being monitored will be required as well as some research.
• Never use the “Default Management Pack” it is selected by default, so be careful to change it to a custom management pack. This creates other potential problems later on. When installing OpsMgr service packs the “Default Management Pack” can be overwritten causing us to lose all changes.
• Never disable a monitor. This can be done as an override. When you disable a monitor it is automatically saved to the “Default Management Pack”.

how-to-move-the-operations-manager-2007-reporting-server

here are the two variables you will be adding to the monitor

parameter name: EventDescription

Alert description: $Data/EventDescription$

1. When you are creating the Event Expression click on insert, then click on button “…: under parameter name

2. Select Use Parameter Name not specified above and enter EventDescription

$Data/EventDescription$

Select an Event Property-EventDescription

3. change your operator to Contains

4. under the Value, enter the words you want to find in the desction field.

Build Event Expresion - operator and value

THIS IS NOT DONE!!!!

5. Continue to build your rule until you arrive at the Configure Alerts page. Enter the value $Data/EventDescription$ in the Alert description window. If you do not you will receive errors.

6. Create the rule, and refresh how ever you like. When i am in a hurry i will restart the health service on the server that I am monitoring.

7. To test your rule the OpsMgr Event Creator tool is not going to work. It does not allow you to create custom descriptions. Log onto the server that you want to monitor and open a command window. Using the eventcreate command type the following

eventcreate /t error /ID 1000/d “fieldxu.exe THIS IS JUST A TEST BY Brad Hearn”

/t sets as an error

/ID is the event id

/d is what will be placed into the description field. Remeber to place quotes around your text.

The alerts will look something like this.

Hope this helps out.

Follow the following steps to monitor a service and have it restarted automatically by SCOM if it fails.

Steps

Create a management pack to store the monitor in

Create a group that the monitor will be applied against

Create a monitor that watches the service

Create overrides (apply to group)

Create the recovery task

Step 1: Create the Management Pack

In the managment console under Administration right click on Management Packs and select “Create Management Pack”. Give this new MP a meaningfull name and continue.

Step 2: Create the Group

• In the Authoring Pane right click on “create new group” Give this new group a meaningful name. A description. And select the management pack that you created.

Important: Do not use the default management pack. You can do it. But this will create problems when trying to remove MP in the future. Always use Custom MP’s.

• Say next. Click on Add/remove objects on the Explicit Group Members. Enter a server name and search. Select your computer object and say ok. You can now add dynamic and exclusions. I am not going into that on this post so except all defaults.

Step 3: Create the Monitor

• In the Authoring Pane right click on monitors and select Create a monitor, then Unit Monitor.

• Expand Windows Services, and select “Basic Service Monitor”. Select the custom management pack.

• Provide a name for the monitor. I am going to create this monitor to watch Windows Update services. Select the monitor target as windows Server Operating System. Select the Parent Monitor as Availability.

• Next Browse to the server, or any server with the service running. and select the service.

• The next window shows how the monitor sees the health state. Accept the default.

• The last window is how the alerts are configured.

• uncheck the “Generate alerts for this monitor:” for now. This will prevent any unwanted alerts until we are ready.

Step 4: Apply to group

Lets apply this MP against the group that we created earlier and disable it for all other servers.

Fist disable the rule for all servers

• Find the new rule under Authoring\monitors. The easiest way to do this is to change your scope. Click on the Change scope in the top right corner
• Look for windows server operating System and select it and say ok.

• Expand the monitor, right click on it and select properties.

• Select Disable and “For all objects of type: windows Server Operating System”

• Next Right click on the same monitor and select override, Override the Monitor, for a group

• Start to type the name of the group you created and select it.
  
• Place a check beside “Parameter name”. Change the override setting to True. This will enable the rule for the group.

• Say OK to save.

STEP 5: Create Recovery Task

• In the Authoring Pane right click on monitors and select the monitor you created by right clicking on it and select properties.
• Click on the Diagnostic and Recovery Tab
• Under the configure recovery Tasks select Add… and choose “Recovery for Critical Health State”
  
• Select Run command
• Provide a meaningful name and description
• Select the recovery target as Windows server operating system
• Check run recovery automatically and recalculate monitor state.

• Next, for the full path to the file type C:\WINDOWS\system32\net.exe This will spawn the net command
• for the parameters type start service name. We are starting windows update service. Here is the best way to find the service name. Open services by opening the run box and type services.msc

• now that you have the actual service name lets enter it in the parameters field. so you would type “Start wuauserv”

• Once you have clicked on create you are done.

Symptom 1: During the pre-requisite check you receive notification that ASP.net is not started but the service is running.

Symptom 2: During setup you receive the “srs server validation” error  

To fix this

• Of course confirm that ASP is installed. If it is then do the following.
• Open the command prompt go to

C:\windows\Microsoft.NET\Framework\v2.0.50727

• Run the following command

aspnet_regiis /i

Resolution is to fix WMI. And here is exactly how I did it.

Well almost exactly. You will need to send me an email for the files required to do this.

On effected server

1. copy mom_tracing.mof to any location on the server. I used c:\downloads

 2. open the command prompt and navigate to c:\downloads and
run the following command without the quotes.

 ”mofcomp mom_tracing.mof”

 This will most likely lead to an error looking for the EventTrace class in WMI which the mom_tracing.mof is dependent upon. (This can be verified by running wbemtest connecting to Root\WMI and doing a recursive Enum of the classes and looking for EventTrace as a class, if necessary).

To fix the error proceed to step 3

3. Copy the contents of the mof folder (email me for this folder) to c:\%SystemDirectory%\system32\wbem
4. Open command prompt and navigate to c:\%SystemDirectory%\system32\wbem
Run the following command without the quotes.

“For /f %s in (‘dir /b *.mof *.mfl’) do mofcomp %s”

Restart WMI services.

Install SCOM agent from file://scomserver/agent/i386

And that’s it. The entire process should take less then a few minutes.

Brad Hearn

Enterprise Server Analyst

http://bradstechblog.com/