Thee ways to monitor websites with SCOM

There are three different ways to monitor a website with operations manager in SCOM.  Each of the different ways has its own pros and cons.

  1. Web Application Management Pack Template
  2. Bulk URL Editor or BUE
  3. Custom URL management pack by Russ Slaten

 

Web Application Management Pack Template

Pros:

  • Ease of Use
  • Integrated into the Console
  • Supported by MS Support

Cons:

  • Produces a lot of alerts
  • Not very scalable
  • Alerts are not very descriptive to what the actual issue is
  • Creates too many groups
  • Time consuming to setup a lot of websites

 

Bulk URL Editor

 

Pros:

  • Scales to 3,000 websites per management servers and 12,000 per management group
  • Saves time by importing a list of of multiple websites from a text file
  • Each URL creates its own instance so putting individual URLs in maintenance mode is easier
  • Less groups are created
  • Supported by MS Support

Cons:

  • Not Intuitive
  • Not integrated and requires an extra console to be copied for tool to be run
  • Produces a lot of alerts
  • Alerts are not very descriptive to what the actual issue is

 

Custom URL management pack by Russ Slaten

Pros:

  • Easy to add and remove websites
  • Reduces number of alerts by consolidating them and only alerting if website is really down.
  • Alerts are descriptive telling you exactly why the alert was created
  • Doesn’t create any extra groups
  • Doesn’t require extra console as everything is added and removed from an csv (Excel) document
  • Seems to scale well
  • Reduced administration as csv document can be modified by anyone with no knowledge of SCOM

Cons:

  • Not integrated in console
  • Initial setup of MP is more difficult
  • Logging of performance data is not possible but could be added
  • No MS Support if you have issues

 

In all actuality there is probably a ton of custom ways you can monitor a website with SCOM.  For simplicity I am just going to cover the three most common.

Continue Reading

The report server has encountered a configuration error. Logon failed for the unattended execution account.

 

I recently ran into this error. “The report server has encountered a configuration error. Logon failed for the unattended execution account.” 

Capture_error

 

A couple weeks ago I changed the passwords on all my SCOM Service Accounts.  I didn’t run any reports since then, but when I finally ran one I got the above error.

So to fix it I logged into my SQL Server and looked at Reporting Services Configuration.  I initially thought it was the service account.

svc

I changed the password and tried to run the reports but got the same error.

The looking a little further I realized the it was obviously the Execution Account as that is what was specified in the error.  

svc2

 

I then ran reports without any issues.

 

Here is the full text of the error

Date: 7/13/2011 10:10:35 AM
Application: System Center Operations Manager 2007 R2
Application Version: 6.1.7221.61
Severity: Error
Message: Cannot initialize report.

Microsoft.Reporting.WinForms.ReportServerException: The report server has encountered a configuration error. Logon failed for the unattended execution account. (rsServerConfigurationError) —> Microsoft.Reporting.WinForms.ReportServerException: Log on failed. Ensure the user name and password are correct. (rsLogonFailed) —> Microsoft.Reporting.WinForms.ReportServerException: For more information about this error navigate to the report server on the local server machine, or enable remote errors
   — End of inner exception stack trace —
   — End of inner exception stack trace —
   at Microsoft.Reporting.WinForms.ServerReport.GetExecutionInfo()
   at Microsoft.Reporting.WinForms.ServerReport.GetParameters()
   at Microsoft.EnterpriseManagement.Mom.Internal.UI.Reporting.Parameters.ReportParameterBlock.Initialize(ServerReport serverReport)
   at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ReportForm.SetReportJob(Object sender, ConsoleJobEventArgs args)
Microsoft.Reporting.WinForms.ReportServerException: Log on failed. Ensure the user name and password are correct. (rsLogonFailed) —> Microsoft.Reporting.WinForms.ReportServerException: For more information about this error navigate to the report server on the local server machine, or enable remote errors
   — End of inner exception stack trace —
Microsoft.Reporting.WinForms.ReportServerException: For more information about this error navigate to the report server on the local server machine, or enable remote errors

Continue Reading

System Center Operations Manager R2 Admin Resource Kit now available

Download: Link

The System Center Operation Manager 2007 Administration Resource Kit provides the following features to aid in management group administration:

  • Scheduled Maintenance Mode – Ability to schedule and manage maintenance mode in the management group.
  • Clean Mom – Helps remove all installed R2 components.
  • MP Event Analyzer – MP Event Analyzer tool is designed to help a user with functional and exploratory testing and debugging of event based management pack workflows like rules and monitors.

Feature Summary:

  • Ability to schedule Maintenance mode for “run once”, daily, weekly, and monthly schedules
  • Ability to removal all OpsMgr 2007 R2 files from a system
  • Ability to debug event based management pack workflows
Continue Reading

Subscription Copier

Download: SubscriptionCopier.zip

Guide: SubscriptionCopierGuide.pdf

Subscriptions copier is a simple tool for copying subscriptions and helping with alert escalation. I created this tool after multiple customers have asked me why they couldn’t copy an existing subscription.

image

I have found that customers are not using subscriptions to their full potential; most customers only setup one subscription. While this works for some, I think that all alerts should be actionable. If an alert has not had some type of action taken in a given time, the alert e-mail should be re-sent or escalated to someone who can take action on it. A ticketing system such as SCSM would also fulfill this function, but few customers have their SCOM system linked to a ticketing system.

You want to make a copy of the Windows Server Team subscription and send alerts to the Windows Server Team’s manager, if they not closed within one hour. To do this today is a very manual process. You would have to open up the subscription and take a screenshot of the configuration. Then create a new subscription with the same configuration and add the Windows Team Manager to the recipients. While this works, there is a possibility that you don’t select that exact same criteria and accidently send the windows team manager an informational alert in the middle of the night that the windows team never even saw.

So let’s show how this is done with the subscription copier tool:

As you can see we have 3 subscriptions

image

Step 1: Launch the Subscription Copier Tool
image

Step 2: Type in the name of your root management server
image

Step 3: The tool will then open

image

Step 4: Select the Subscription you would like to copy from the drop down.

image

Step 5: Select how may copies you would like to make. (In this scenario we will only create one.)

image

Step 6: Select how many minutes in between re-alerts. In this scenario we will leave it at the default of 0 (This will be used in scenario 2)

image

Step 7: Check this box if you want the copied subscription enabled. (In this scenario we are leaving it unchecked because we need to make some changes before it is enabled.)

image

Step 8: Click Create

image

Step 9: You should see a message telling you that the subscription was create successfully.

image

Step 10: Open the SCOM console and refresh the subscriptions screen. You should see the copied alert under the subscriptions screen.

image

Now back to our scenario we want to alert the windows team manager if an alert has stayed open for longer than one hour.

We go to the properties of the copied alert.

image

Change the name to “Windows Server Team (Escalated to manager after one hour)” and click next

image

As you can see all of our criteria has been copied from the original subscription.

image

Click Next

Remove the Windows Team E-Mail and add Windows Server Team Manager to the subscribers

image

On the channels screen set the alert aging to 60 minutes. This will only send alerts that have been open for longer than 60 minutes to the Windows Server Team Manager

image

On the Summary Page click “Enable this notification subscription.

image

Then click Finish

image

You want a subscription to re-alert on open alerts every 10 minutes for one hour. To do this today you would have to open up the subscription and take a screenshot of the configuration. Then create six new subscriptions with the same configuration and set the delay by adding an extra ten minutes to every subscription. This could take up to 10 minutes manually. If you were to do this for every subscription in your environment it could take many hours.

So let’s see how this is done with the subscription copier tool

Step 1: Launch the Subscription Copier Tool

Step 2: Type in the name of your Root Management server

Step 4: Select the Subscription you would like to copy from the drop down.

Step 5: Select how may copies you would like to make. In this scenario we will create six.

image

Step 6: Select how many minutes between each re-alert. In this scenario we will set it to 10 minutes.
image

Step 7: Check the enabled box to enable the 6 subscriptions we are going to create.
image

Step 8: Click Create

Step 9: It will take a short time as the copies are created. After it completes you should see a message telling you that 6 subscription copies were created at a 10 minute interval.
image

Step 10: Open the SCOM Console and refresh the subscriptions screen.
image

You should now see the copied subscriptions created by the tool.

  • When creating multiple copies with a re-alert interval. Set your subscription criteria to only include only

Reason: When your subscription criteria includes closed alerts, the closed alerts get delayed and you will get some a bunch of extra closed alerts that you won’t want.

  • If you have subscriptions with duplicate names you will get an error of “An entry with the same key already exists”.

Workaround: Delete subscription(s) with duplicate name

  • Copied subscriptions with a delay set. The delay doesn’t interval doesn’t get copied.

Workaround: Manually set the delay on copied subscriptions

Continue Reading

SCOM 2007 R2 CU4 has been released

SCOM 2007 R2 CU4 has been released to the web.  You can download it here

CU 4 contains a fix that I have been waiting for since SCOM 2007 RTM.  It has the ability for the RMS to recover from a SQL disconnect, restart, or failure.  This is obviously super important for a monitoring system.  

Automatic recovery of Health Service in a SQL Server failure scenario
After SQL Server goes offline, Health Service of Root Management Server (RMS) stops responding. For example, Health Service stops responding after SQL Server disconnects, restarts, or fails. To recover from this issue when SQL Server is available again, you must restart Health Service. 

By default, this automatic recovery feature is disabled. The DALInitiateClearPoolSeconds setting controls when RMS drops the current connection pool and when RMS tries to reestablish an SQL connection. We recommend that you set this setting to 60 seconds or more to avoid performance issues. To configure this recommended setting, set the following values:

  • SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\DAL\DALInitiateClearPool = true
  • SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\DAL\DALInitiateClearPoolSeconds = 60

*Note* To apply the DALInitiateClearPoolSeconds setting, restart Health Service of RMS.

 

Kevin Holman has done a nice job providing step-by-step instructions on CU4.  Link

Continue Reading

Testing a SCOM PowerShell script from the command line

When I wrote SCOM VBScripts in the past, it was easy to test the script and see if I was getting the right output. 

I would simply run the cscript command from the command prompt to get the output.

C:\temp2\cscript count.vbs "c:\temp2" 4

 vbscript4

But now with a similar SCOM PowerShell script I get useless output.

PS C:\temp2\ .\filecount.ps1 -Folder ‘C:\temp2’ -FCount 5

pshell

To fix this I have to add a simple line of code to the end of my PowerShell script

$api.Return($bag)

 

Now I can see the same output that my VBScripts gave me in the past.

powershell2

Don’t forget to comment the line out after you are done testing.

powershell3

Continue Reading

Installing SCOM 2007 R2 on a SQL 2008 Instance with all Windows Firewalls Enabled.

 

I decided I needed to re-install my lab environment.  I wanted to keep all of the firewalls on during the install process and only open the ports that are actually needed. I installed SQL using a named instance as many customers use a SQL 2008 cluster.

After I installed the SCOM database on the SQL 2008 server with all firewalls on.  I created a firewall rule to let port 1433 allow connections.  As specified in the Supported Configurations doc

Root management server 1433 —> OperationsManager database

1

I also setup a firewall rule to allow port 1434 back to the RMS server from the SQL Instance Server. (Also in the guide)

Root management server 1434 UDP < — OperationsManager database

2

I start the install of SCOM to the RMS server.  I unchecked Database as my database is already install the on the SQL instance.

3

I typed in my SC Database Instance Name and clicked Next

4

But I got this error “Setup cannot location the SC database”

5

So I enabled firewall logging to see what was getting dropped blocked by setting the firewall to log dropped packets.
6

 

In the SCOM setup I clicked back and then next.

I checked the firewall logs in %systemroot%\system32\Logfiles\Firewall\pfirewall.log  and it looks like UDP port 1434 is being dropped

date time action protocol src-ip dst-ip src-port dst-port size path
12/26/2010 16:56:54 DROP UDP 192.168.2.63 192.168.2.61 58321 1434 38 RECEIVE

 

I create another rule on the SQL server to enable UDP port 1434
8

 

In the SCOM setup I click back and next again.

 

Once again same failure.  “Setup cannot location the SC database”

Back to the firewall logs.  It now needs TCP port 62756 (Not in the guide)

date time action protocol src-ip dst-ip src-port dst-port size path
12/26/2010 17:12:03 DROP TCP 192.168.2.63 192.168.2.61 50503 62756 38 RECEIVE

 

 

I create another rule on the SQL server to enable TCP port 62756

7

After that rule is enabled I am able to continue on a install SCOM successfully with all of the windows firewalls still on.

Continue Reading

SCOM vNext with Vlad Joanovic

Great video from Vlad Joanovic talking about vNext

Link

About:
Vlad steps by our hallway studio to talk about the Beta version for OpsMgr v.Next. He informs us about new and rich UI and what has been done to the product to make is more easy to manage. He also tells about performance enhancements. We also discuss AviCode integration.

Continue Reading