ExchangeRequiredHotfixesNotInstalled with SCOM 2012

There is a bug in the current version ( of the Exchange 2012 SCOM Management Pack with when using SCOM 2012


You may get an error like this Operations Manager failed to start a process

The process started at 2:03:25 PM failed to create System.PropertyBagData. Errors found in output:

C:\Program Files\System Center Operations Manager\Agent\Health Service State\Monitoring Host Temporary Files 19\1725\HotFixValidation.vbs(117, 10) Microsoft VBScript runtime error: Subscript out of range: ‘count’

Command executed: "C:\Windows\system32\cscript.exe" /nologo "HotFixValidation.vbs"

Working Directory: C:\Program Files\System Center Operations Manager\Agent\Health Service State\Monitoring Host Temporary Files 19\1725\

One or more workflows were affected by this.
Workflow name: ExchangeRequiredHotfixesNotInstalled
Instance name:
Instance ID: {A22EB582-0426-DDC4-8C78-EEB5EBDBFA42}
Management group: AMTMTECH


The reason is that the script tries to check for a particular Cumulative Update on SCOM 2007.  The script doesn’t account for the version of SCOM 2012



So fix this we just need to disable the rule that does the check.

So I grab the workflow name from the error

Workflow name: ExchangeRequiredHotfixesNotInstalled

Being this is the Exchange MP we want to disable the monitor not the rule. So I do a search for the monitor.



Now I create an override to disable it [For All Object of Class: Agent.  I store the override in my Exchange Customizations MP.

Now I close the rule an make sure it doesn’t come back.

4 comments on “ExchangeRequiredHotfixesNotInstalled with SCOM 2012

  1. I love it when I see ‘fixes’ like this. Something screaming with errors or warrnings? Disable it – Done, its fixed! This is not an error, it’s a warrning, there is a difference. Also this doesn’t prevent any functionality of the agent or actions, just logs a warning. What would be more useful would be to edit the script to detect the 2012 version, updates, etc.

    1. Marius, I would have to disagree:

      Firstly it is not the workflow itself logging a warning. The agent version check workflow fails due to a bug and a separate generic workflow detects a SCOM workflow has failed and raises an alert to tell you. There is no value in cluttering up your console with these alerts.

      Regarding fixing the bug, it is a script contained in a sealed management pack. Therefore you still have to disable this monitor even if you choose to later to write your own with a bug fix.

      Lastly this check is failing because it is looking for scom 2007 agent versions and doesn’t expect the 2012 version. In a scom 2012 management group, you can’t have any agents which don’t meet the minimum required version and therefore in this environment it is completely redundant.

      Best all round just to disable it.

  2. Yeah, but in reality when you are in a huge production environment a “fix” like this helps, especially since I dont want to go reengineering what msfot screws up

  3. 3yrs on and this post still delivers. Thanks again – I just resolved this issue in a new SCOM 2012 R2 environment monitoring Exchange 2010.

Leave a Reply

Your email address will not be published. Required fields are marked *