SCOM 2012 Maintenance Mode Scheduler 4

Here are the new features in V4:

  • Multi-select Computers  This has been the most requested feature as end users often want to schedule multiple computers at a time without having to create groups.
  • Multi-select Computers in Integrated dashboard  Now you can select multiple computers in the dashboards without getting an error
  • New Search in Computers and Groups  Now instead of scrolling up in down the list you can just start to type in the name of the group or computer and results will be filtered.
  • One Click MM now accepts parameters   Some environments One Click MM was not working as the client security was high or there were DNS issues.  Now you can just add the computer as a parameter.
  • New Configuration backup tool for easier upgrades  Now you can back your configuration and upgrade to the latest version of SCOM 2012 Maintenance Mode Scheduler with have to reconfigure all of your settings.
Download Free Trial

Multi-select Computers

Now you can select multiple computers at a time for maintenance mode.

image

Multi-select Computers in Integrated dashboard

image

New Search in Computers and Groups

image

One Click MM now accepts parameters

image

New Configuration backup tool for easier upgrades

image

Continue Reading

Discovery bug in MP Author SP2 when discovering the 32-Bit registry keys

There is a bug in Silects MP Author SP2 tool.  If you select a 32-Bit registry key for discovery.

image

 

When you save the MP it will automatically remove the Wow6432Node

image

Most 32-Bit applications don’t write to multiple locations so It won’t discover anything.

image

 

**As pointed out by Kevin Holman there is an XML element called <registryview>32bit</registryview> that will accomplish the same thing but will work with 32-bit servers and 64-bit servers.**

Open up the XML and add the <registryview>32bit</registryview>

My XML would look like this.

<RegistryAttributeDefinition>
<AttributeName>ConfigProductCode</AttributeName>
<Path>SOFTWARE\Research In Motion\BlackBerry Enterprise Server\Setup\ConfigProductCode</Path>
<PathType>1</PathType>
<AttributeType>0</AttributeType>
<RegistryView>32bit</RegistryView>
</RegistryAttributeDefinition>

More info on this can be found here.  http://michielw.blogspot.ca/2010/01/scom-registry-discovery-on-64-bit-os.html

 

The following workaround will work as well, but is not perfect as you might have apps installed on both 32-bit and 64-bit servers.

Open up the XML and edit it back to what it should be.

image

image

 

I have reported this to Silect.  Hopefully they will fix it in the next version.

Continue Reading

Creating a Process Monitoring Recovery Task

Creating a Process Monitoring Recovery Task to stop a process that has been running too long.

I already created the monitor using the Process Monitoring template.

image

 

image

 

image

 

To create the recovery task.

I right click on the process monitor I created.

Choose View Management Pack Objects, Monitors.

image

 

 

The I expand down ProcessFiles, Entity Health, Availability.

I right click on Process Running Time Monitor and click Properties

image

 

 

I choose the Diagnostic and Recovery Tab.

Then under Configure recovery tasks.  I choose Recovery for critical health state.

image

 

 

I click Run Command

image

 

Give it a Recovery Name

image

 

 

Full path to file:

%windir%\system32\taskkill.exe

 

Parameters:

/F /IM processfiles.exe

image

 

Click Create

Continue Reading

Fixing the Operations Manager Shell (PowerShell Interface for SCOM)

 

I go to a lot of customers where when I launch the Operations Manager Shell (PowerShell Interface for SCOM) the shortcut is broken.

image

 

This is often caused by a user installing SCOM to a drive other then the C drive.  I’m sure there a many other possible reasons but lets just focus on fixing it.

First I Open up a new PowerShell Command Prompt as administrator.

Then I run $env:PSModulePath

image

 

Then I run the same command on my SCOM Management Server that I know that the Operations Manager Shell works.

I notice a big difference in the modules listed for my PowerShell environment.

image

I can manually fix the Environment Variable by going to the Advanced System Settings

image

image

**Note you will have to reboot after fixing this as its not the running config**

Just like there is no crying in football there is no GUIs in PowerShell so I wrote this PowerShell script to fix it..

Here is the script I wrote to fix it with comments

image

Now when I run the shell it works.

image

You can download the script here.  http://www.scom2k7.com/downloads/FixOMShell.txt

Continue Reading