SCOM 2012 Maintenance Mode Scheduler

We believe that core to any monitoring system is the ability to send out accurate alerts. SCOM sends out many valuable alerts but will flood e-mail boxes and paging systems during maintenance windows.  We set out to build a maintenance mode scheduler that anyone can quickly and easily use to prevent these floods of useless information.

Features:

  • Easily access the new web based maintenance mode scheduler from any browser.
  • End users will thank you at how easy it is to pick a computer, group, object, and even a subscription with a start time and end time. The app calculates the minutes for them and schedules a future maintenance window.
  • The manage tab will make it easy to see and manage any upcoming maintenance windows and identify any gaps.
  • The new integrated dashboards make it feel like the scheduling maintenance mode was always there.
Download Free Trial

screenshot1

Groups

Schedule a group of Computers, Databases, or any objects in the group into maintenance Mode.
image

One Click Maintenance Mode

Another great feature is the ability to do one click maintenance mode from any server.  This means is you can place the same shortcut on the desktop of your all your servers.  With one click, the IT administrator can put the server into maintenance mode.

image32

After the shortcut is clicked, the web page automatically detects what server you are on and puts the server into Maintenance Mode with no interaction.

screenshot2

Dashboards Integrated Into The SCOM Console

image

 

Subscriptions

Most organizations only use the alerts from SCOM.  Now you can schedule your complex subscriptions into maintenance mode.  You can choose to send the alerts that where queued up or discard them.

clip_image016_thumb.jpg

Manage any upcoming maintenance windows and identify any gaps

image12

 

Windows 8 App

The Windows 8 app can be download from the Windows App Store.  It uses the existing the same infrastructure and web service as the Web based version.

Download Now from the App Store

image

image

image

 

Click Here to Purchase

Any problems, bugs, or issues please e-mail:  support@scom2k7.com

 

Related Posts

SCOM 2012 Maintenance Mode Scheduler Installation Guide – http://www.scom2k7.com/scom-2012-maintenance-mode-scheduler-installation-guide/

SCOM 2012 Maintenance Mode Scheduler User Guidehttp://www.scom2k7.com/scom-2012-maintenance-mode-scheduler-user-guide/

Securing SCOM 2012 Maintenance Mode Scheduler – http://www.scom2k7.com/securing-scom-2012-maintenance-mode-scheduler/

 

Continue Reading

Alert on SQL Job Failure when SQL Agent Job Discovery is Enabled

Customer was asking why they were not getting alerts for SQL Agent Job failures.  They had enabled individual SQL Agent Job Discoveries that is talked about in Kevin’s post.

By default the Last Run Status monitor does not alert.  So they created an override to enable Generates Alert.

SQL1

 

Problem was no alerts came through.  Looking at Alert severity it says “Critical” and Alert on State it says “The monitor is in a critical health state”.  Looks good to me.

But still no alerts.

Lets take a look at the monitor.  The monitor is in a warning state.  That is weird I thought Alert severity is “Critical” from the above screenshot.
SQL2

 

 

Lets take a look at the monitor.  I right click and go to monitor properties.  There is no Critical Health State, only Warning and Healthy for this monitor.  Looks like a bug to me or bad MP practices.

SQL3

If I look back at my Overrides I can see that this monitor will only Alert On State if “Alert if it is in a Critical Health State”

SQL4

 

Well it will never go into a “Critical Health state” because it doesn’t exist.   There is no way to override the monitors health.  This is not usually an issue because most monitors are either two state Health and Critical, or three state, Healthy, Warning, and Critical.

So what to do?

The only way to get the monitor to alert is to create an override so that Alert on State is changed to Warning.

sql5

Now when the monitor changes to a “Warning state” I get an Alert.

SQL6

 

But why is it a “Warning”?  Not really sure.  The default behavior is Alert severity is “Critical”

If I create another override for “Alert severity” Critical

SQL7

 

Now I get a critical alert.

SQL8

 

 

But the monitor is still in a warning state and could be confusing to the end user.

sql9

 

I will file a bug to get this changed.

 

 

 

 

 

 

Continue Reading

Microsoft acquires BlueStripe

Today it was officially announced that Microsoft has acquired BlueStripe software, which has been a key partner for Operations Manager and Azure for monitoring application performance and availability of distributed business applications seamlessly and comprehensively.

bluestripe

You can read more of the announcement here

http://blogs.microsoft.com/blog/2015/06/10/microsoft-acquires-bluestripe-to-help-customers-improve-application-visibility-and-management-across-the-datacenter-and-cloud/

Continue Reading

Error upgrading SCOM 2012 RTM to SCOM 2012 SP1

Ran into this issue today trying to upgrade from SCOM RTM to SCOM SP1

I got the standard 1603 error in the OpsMgrSetupWizard.log

[15:44:20]: Error: :LaunchMSI: MSI D:\Setup\AMD64\Server\OMServer.msi returned error 1603
[15:44:20]: Error: :ProcessInstalls: Install Item Management Server failed to install. We did not launch the post process delegate.
[15:44:20]: Always: :SetErrorType: Setting VitalFailure. currentInstallItem: Management Server

Opening up the OMServer.log one of my colleagues Stefan Wuchenauer identified the issue.

 

MSI (s) (18:18) [15:43:33:134]: Executing op: CustomActionSchedule(Action=_Rollback_UninstallBIDMOF.DB577B04_77CF_4F29_BA24_844EA640D17E,ActionType=3393,Source=BinaryData,Target=UninstallMOF,CustomActionData=C:\Program Files\System Center 2012\Operations Manager\Server\mom_tracing.mof)
MSI (s) (18:18) [15:43:33:136]: Executing op: ActionStart(Name=_InstallBIDMOF.DB577B04_77CF_4F29_BA24_844EA640D17E,,)
MSI (s) (18:18) [15:43:33:138]: Executing op: CustomActionSchedule(Action=_InstallBIDMOF.DB577B04_77CF_4F29_BA24_844EA640D17E,ActionType=3073,Source=BinaryData,Target=InstallMOF,CustomActionData=C:\Program Files\System Center 2012\Operations Manager\Server\mom_tracing.mof)
MSI (s) (18:E8) [15:43:33:172]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIDE96.tmp, Entrypoint: InstallMOF
InstallMOF: Custom Action Data. C:\Program Files\System Center 2012\Operations Manager\Server\mom_tracing.mof
CompileMOF: CompileFile() failed. Error Code: 0x80041002. C:\Program Files\System Center 2012\Operations Manager\Server\mom_tracing.mof
MSI (s) (18:78) [15:43:33:399]: I/O on thread 1084 could not be cancelled. Error: 1168
MSI (s) (18:78) [15:43:33:399]: I/O on thread 2704 could not be cancelled. Error: 1168
MSI (s) (18:78) [15:43:33:399]: I/O on thread 3316 could not be cancelled. Error: 1168
MSI (s) (18:78) [15:43:33:399]: I/O on thread 4716 could not be cancelled. Error: 1168
MSI (s) (18:78) [15:43:33:399]: I/O on thread 2840 could not be cancelled. Error: 1168
MSI (s) (18:78) [15:43:33:399]: I/O on thread 3720 could not be cancelled. Error: 1168
MSI (s) (18:78) [15:43:33:399]: I/O on thread 2924 could not be cancelled. Error: 1168
MSI (s) (18:78) [15:43:33:399]: I/O on thread 1324 could not be cancelled. Error: 1168
MSI (s) (18:78) [15:43:33:399]: I/O on thread 4736 could not be cancelled. Error: 1168
MSI (s) (18:78) [15:43:33:399]: I/O on thread 4496 could not be cancelled. Error: 1168
MSI (s) (18:78) [15:43:33:399]: I/O on thread 4048 could not be cancelled. Error: 1168
MSI (s) (18:78) [15:43:33:399]: I/O on thread 3100 could not be cancelled. Error: 1168
MSI (s) (18:78) [15:43:33:399]: I/O on thread 1768 could not be cancelled. Error: 1168
MSI (s) (18!4C) [15:43:33:400]: Product: System Center Operations Manager 2012 Server — Error 25218.Failed to uninstall SDK MOF. Error Code: -2147217406 (IDispatch error #3586).

Error 25218.Failed to uninstall SDK MOF. Error Code: -2147217406 (IDispatch error #3586).
CustomAction _InstallBIDMOF.DB577B04_77CF_4F29_BA24_844EA640D17E returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

Here is the fix. (*Note* The blog post says SCOM 2007 but it works for SCOM 2012 as well.)

http://blogs.technet.com/b/operationsmgr/archive/2009/05/05/opsmgr-2007-error-25218-failed-to-uninstall-sdk-mof-when-installing-sp1.aspx

 

Resolution: To resolve this issue follow the steps below:

1. Open a CMD prompt and navigate to the “C:\Windows\System32\Wbem” folder.

2. Run the following command:

for /f %s in (‘dir /b *.mof *.mfl’) do mofcomp %s
for /f %s in (‘dir /b /s *.dll’) do regsvr32 /s %s

3. Try installing the SP1 upgrade again.

 

Continue Reading

Error Installing SCOM 2012 “The target principal name is incorrect. Cannot generate SSPI context”

I ran into this error today trying to install SCOM 2012.  “The target principal name is incorrect. Cannot generate SSPI context.”

The Error from the Setup Wizard was “This SQL server could not be found. Please check that this SQL server is running and that the current user has login permissions.”

Then looking at the OpsMgrSetupWizard.log located at %LocalAppData%\SCOM\LOGS\

I found this error

[17:50:31]: Always: :OpenAndTestSqlConnection: connection string – Data source=vDB01,1433;Integrated Security=true;Connection Timeout=5
[17:50:31]: Debug: :SqlConnectionReady returned False.
[17:50:31]: Info: :Info:DatabaseConfigurationPage: DB connection attempt completed.
[17:50:31]: Info: :Info:DatabaseConfigurationPage: DB connection attempt completed.
[17:50:32]: Always: :DatabaseConfigurationPage: Attempting to connect to database using server\instance vDB01. If we need it, the port is 1433
[17:50:32]: Debug: :MSSQLSERVER on server vDB01 is in a running state
[17:50:32]: Info: :Info:Opening/Testing Sql Connection on vDB01, port:
[17:50:32]: Debug: :Connection was not open. We will try to open it.
[17:50:32]: Error: :Error opening SQL connection.: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: The target principal name is incorrect. Cannot generate SSPI context.
[17:50:32]: Error: :StackTrace: at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource
1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource1 retry, DbConnectionOptions userOptions)
at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource
1 retry)
at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupValidationHelpers.OpenAndTestSqlConnection(DbConnection sqlConnection, Int32 retries)

 

After some research I concluded that is must be an SPN issue.

I am using a service account for SQL.  So I attempted to manually set the SPN for the service account.

But I ran into this issue.  “The operation failed because the SPN value provided for addition/modification is not unique forest-wide.”

SPNIssue

Turns out the computer account already had this SPN set.

So I removed the SPN for the computer account and added it to the SQL Service account.

Then the wizard let me continue.

 

 

Continue Reading

SCOM 2012 Maintenance Mode Scheduler 6

Here are the new features in V6:

  • Dedicated Linux / Unix Page –  Linux and Unix admins now have a dedicated page to schedule maintenance mode.  They can search and select multiple *NIX computers for maintenance mode.
  • Improved Classes Page – The new classes page is much faster and uses the display name of objects.  It also has search and the ability to schedule multiple objects of a class.
  • Classes Page now accepts a parameter  – When opening the classes page you can now specify an ObjectID as a parameter and it will find the object automatically for easy scheduling or integration in to other systems.

 

Download Free Trial

Dedicated Linux / Unix PageUnixLinux

 

Improved Classes Page

Class

 

Classes Page now accepts a parameter

Class2

Continue Reading