..:::: Anand ::::..

Lion Sleeps in IT Department

SCOM: “Critical hotfixes required for reliable operation of the Exchange Server 2010”–alerts on wrong servers

Posted by anandthearchitect on April 2, 2011


Whenever I install SCOM agent on new server, I get this alert.

Alert description: Critical hotfixes required for reliable operation of the Exchange Server 2010 and other management packs are not installed on this server. Please see the appropriate KB article for more information, and to download the required hotfix

Why would SCOM barking on a wrong tree? None of them are Exchange servers.

After staring at the alert for a minute and checked the SCOM monitor properties, I found this monitor is targeting Health Service that mean all monitored servers. a..ah! Bug in Exchange 2010 management pack!!!

image

Now how to fix it? Disable this monitor for all Servers and  target this alert only to Exchange servers. Follow the steps below to do that.

  1. Open SCOM Console and go to Authoring section.
  2. Select Monitors Node. Select the scope to “Health Service”.
  3. Search for “required SCOM hotfixes” image
  4. Right click on “The required SCOM hotfixes for Exchange MP are not installed” monitor, Select Overrides –> Override this Monitor –> For all objects of class: Health Service.image
  5. Check the box for Enabled and select False in Override Value column.  Optional: Select a custom management pack created by yourself on the bottom. Click OK to disable for monitor. image
  6. Right click on the same monitor again and select Overrides –> Override this Monitor –> For a Group..
  7. image

  8. Type Exchange in the search box and select “Microsoft Exchange 2010 All Servers Computers” and click OK.image
  9. Monitor may be already enabled since we only selected Exchange servers only. You may change any alert priority or severity. Click OK.image

That’s All. No more false alarms. Enjoy. Smile

11 Responses to “SCOM: “Critical hotfixes required for reliable operation of the Exchange Server 2010”–alerts on wrong servers”

  1. nick said

    Thankyou! This was very helpful :)

  2. Christoph said

    Thank you. I just ran into this issue after this bug triggered my main SQL server to go into red. Now it’s all good. I appreciate you posting the detailed steps.

  3. mike said

    Thanks for the quick and easy instructions !

  4. Jason Legendre said

    Thanks for this, it was driving me crazy! Appreciate your post.

  5. michael said

    the single most helpful post i’ve found on SCOM07!!! THANK YOU

  6. hussain said

    Thanks alot

  7. kerem said

    thanks a lot

  8. Teboho said

    Much appriciated

  9. R.Clarke said

    Thanks for the fix!
    Was wondering why by branch file servers were reporting this!!

  10. Reblogged this on remigiooscariglesias and commented:
    SCOM 2007 y Exchange 2010.

  11. Tsai said

    Very Helpful.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Connecting to %s

 
Follow

Get every new post delivered to your Inbox.