Posts Tagged ‘SCOM’

SCOM : Open view direct in console

Written by Ingmar Verheij on April 4th, 2011. Posted in Operations Manager

System Center Operations Manager (SCOM) gives you great insights in your IT infrastructure. (Pro) active monitoring you’re environment enables you to respond quickly to alerts and (maybe) prevent outage.

One way to get informed is by hanging monitors in the “IT room” with dashboards displaying the environment. You can create a “view” in the Management Console displaying the information needed.

Ideally a dedicated machine boots up and displays the view you created. You can start the System Center Operations Manager with the option / ViewName: <viewname> to open the console and show the view.

Microsoft.MOM.UI.Console.exe

However if you start the console with the name of the view you get this error:

The view could not be found

Install SCOM 2007R2 on SQL 2008R2 (including reporting server)

Written by Ingmar Verheij on February 21st, 2011. Posted in Microsoft SQL, Operations Manager

When installing the Microsoft System Center Operations Manager (SCOM) 2007 R2 database on a Microsoft SQL Server 2008 R2 the installation failes because a prerequisite is not met:

This is caused by an outdated installer which doesn’t recoginize SQL 2008R2. Altough installing on SQL 2005 / 2008 will prevent this message there is an alternative.

Maintenance mode

Written by Ingmar Verheij on October 20th, 2010. Posted in Nagios / GroundWork, Operations Manager

Monitoring servers, services and connections is great. It enables pro-active management, notification and escalation and improves root cause analysis.

One big challenge is the number of notifications being sent and the relevance of those notifications. A well set-up environment sents notifications when problems raise or a negative trend is detected. Signals for the Administrator to get out of his lazy chair.
Most environments, however, sent more notifications then needed and are often irrelevant. This causes a negative effect, the mailbox fills up rapidly and the value of the message decrease.

An example of a not well-planned monitoring environment is a reboot schedule. Especially when terminal servers are periodically rebooted, or re-deployed, servers maybe be unreachable once in a while. The monitoring software assumes the server is in trouble and would cause an alert and sent notifications.

Donate