SCOM 2007: Renaming Default Management Pack display name

One of the most common frustration I face (and I’m sure I’m not alone) is the fact that from time to time there are things saved in the default management pack. It’s so easy to forget to change the destination management pack while creating rules / monitors and just click next. We all know once you’ve created the rule it’s not possible to change the management pack anymore… It’s best practice not to write anything to your default management pack but it’s always selected as default… Yet you have 2 options: Delete the rule and start all over again live with the rule residing in your default management pack which is not a good idea in case you face issues with dependencies… To avoid this common mistake / lack of attention I make a habit of renaming my default management pack display name to something eye catching so I see it before clicking next while creating a rule / monitor. Open the SCOM console...
Read More

SCOM 2007: Custom Alert Fields

Just recently I needed to connect SCOM to an in-house written Problem Management system. There was not a connector available and it was also not possible to generate tickets directly in the system itself. The only way the system is receiving input is via mail through specific keywords. Most of the keywords could be mapped to standard alert fields like severity, time raised, description…. BUT (off course there’s a but) the system also requested other fields to decide proper escalation, severity,… The previously used system onsite is MOM2005. In MOM2005 there’s an option to define globally these fields so you can use them in whatever alert you want to raise. This is in MOM2005: Open Operator Console > Administration > Global Settings > Custom Alert Fields Up to 5 Custom Fields can be named here: These fields can than be addressed in the Rules you create and can be populated with the text you define: When you select Custom Fields the labels you specified in the Custom Alert...
Read More

SCOM 2007: Dump alerts to text file and mail

Just recently I had an issue at a client where there was a need to rethink the notification possibilities due to various issues. I’ve developed a powershell script to gain more control over the notification process. Case: My Client is using an in-house developed and maintained problem management system installed on a mainframe platform. The alerts which need escalation are detected in SCOM and then sent by mail to a Lotus Notes system. The data is then read through a connector between the mainframe system and the Lotus Notes dbase. The mail is scrubbed and through a series of scripts on the mainframe the key fields of the mail are detected and filled in in the ticket…. Problem: So far so good… BUT because of the use of different systems there was an issue with encoding. The mails were sent in UTF8 encoding and correctly decoded when viewing in the Lotus Notes Client but stayed encoded in the Lotus Notes Dbase and therefore the...
Read More

SCOM 2007: Setup Command Notification Channel + Subscriber

Sometimes it’s necessary to launch a custom script or other action after an alert is detected. This can be all executable scripts or programs. In my particular case I’m using this to launch scripts when an alert is detected to properly escalate the alert and perform additional tasks on the alert. So how do you make sure that the script you intend to run will actually run when a predefined alert is raised? By creating a Command notification channel and subscription… Let’s start with setting up the command notification channel. Note: I’m using my script Create_Ticket.Ps1 as documented here. The parameters I’m passing are useful for this script but you can pass many more parameters according to your needs. First of all open the Notification Channels by opening the SCOM console > administration > Notifications > Channels Right click in the Right pane > choose New > Command… In the settings tab you need to fill in what you prefer to run: Full Path of the command file:...
Read More

SCOM 2007: Create custom Alert Resolution States

Sometimes it’s useful to make your own Custom Alert Resolution States to further classify your alerts in the console and use these states to trigger different actions using various scripts. I’ll be posting some scripts which are going to use this custom alert resolution state so therefore I’m documenting here how to configure them. Open your SCOM console, select the administration tab, settings and alerts. Click new… Type in the Resolution State display name and choose a uniqueID. Click OK. And we are done. Not much to it but it makes live a little easier when you want to classify different alerts. In the next series of blogs I’ll be frequently using this Custom Alert Resolution States to classify and report on different types of alerts....
Read More

SCOM 2007: installation bypassing the prerequisite checker

Most of the time the prerequisite checker when installing SCOM 2007 is right that there’s a prerequisite not met to install the specific role or specific item of SCOM 2007. However If you are 100% sure everything is there you can bypass the prerequisite checker by running the install with the following command: MSIEXEC /i <path>\MOM.msi /qn /l*v D:\logs\MOMUpgrade.log PREREQ_COMPLETED=1 This is however NOT supported by Microsoft. Note: in Windows Server 2008 always run commands in an elevated prompt. This should be your last resort to get things going. Most of the time there’s indeed a prerequisite not met and therefore the checker is right. If you want to double check your prerequisites you can find them here: http://technet.microsoft.com/en-us/library/bb309428.aspx A known issue with the prerequisites is that ASP.Net is not correctly detected. More info here: http://support.microsoft.com/kb/934759...
Read More
Uncategorized, Notice: Trying to access array offset on value of type bool in /customers/5/1/0/obvus.be/httpd.www/wp-content/themes/square/inc/template-tags.php on line 138

SCOM: Moving the Opsdb Datawarehouse to another drive

Recently I got a question of a customer to move the Opsdb Datawarehouse (DW) to another drive because the disk on which it was originally installed was not big enough. In fact they wanted to move the DW to an iscsi disk to boost performance. To verify whether there would be an issue or it would be a straight forward move I did some browsing on the biggest manual out there… The internet! However all that came up were actually moves from one server to another but not from one drive to another on the same server… I did some testing in my lab and thought I ‘d share the outcome with you. First of all this is your DW you are tempering about. Make sure you have proper backups of your db and read the entire blog before proceeding. Just to be on the safe side. It would be a shame that you lost...
Read More