SCOM: Patches to be Careful of

Having come across another patch recently which can cause critical issue with SCOM I’ve decided to create a page to record the KB numbers on as well as any relevant additional information.

1.KB2585542
2.KB2775511 

1. KB2585542 – This patch will break Unix monitoring due to  causing WS-Management connections to UNIX/Linux agents to fail.  If this patch is installed on your management servers you can either uninstall it or perform one of the following:

  • Edit the registry to add this 32bit DWORD value:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\ SendExtraRecord = 2
  • Or there is a “FixIt” package is available in the KB article under the Known Issues section that can be used to disable the security update

2.KB2775511  – Marnix Wolf has a great article on this issue. “After installing KB2775511 on Operations Manager Management Servers, agents or servers may be affected by a deadlock.
Once in deadlock, Management Servers will generate Heart Beat failures and will go into a “greyed out” state. grayed out. As a result, devices managed by these Management Servers will also go into a “greyed out” or “not monitored state.””

This patch is a combination of 89 hot fixes so ideally you want to avoid installing it.  Even though the issue doesn’t occur on all SCOM system it would be advisable to wait for an updated bulletin from the MS System Center team before installing it.

Note: Microsoft have release a hotfix to address this issue, I’d still recommend approaching with caution. Link – “SCOM 2012 or SCOM 2007 R2 throws a “Heartbeat Failure” message and then goes into a greyed out state in Windows Server 2008 R2 SP1

Leave a Reply

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

This site uses Akismet to reduce spam. Learn how your comment data is processed.