Lots of of good fixes in the latest UR. Especially if you are using APM then this update rollup is a must for making this work. Working with Sensitive Data for .NET Applications
Issues that are fixed in update rollup 4
It takes many minutes for the Microsoft.Windows.CheckNTServiceStateMonitorType function to determine that the service is down.
An attempt to apply sensitivity rules fails, and you receive the following error message:
Exception: System.ApplicationException: Attribute ‘regexCompare’ is null
at Microsoft.EnterpriseManagement.Modules.Apm.LibraryConfigManager.Tools.XmlTools.GetMandatoryAttribute(String attributeName, XmlNode node)
at any attempt to apply sensitivity rules fails with the errorMicrosoft.EnterpriseManagement.Modules.Apm.LibraryConfigManager.Modules.ApmModule.Core.Actions.AgentHandlersConfig.HiddenRuleXmlDeserializer.Deserialize(XmlNode rowData)
GSM locations are geotagged incorrectly on Map Widget.
The MonitoringHost.exe process issues too many calls to System Center Failover Clustering.
The re-synchronization of all managed entities from Operations Manager to the Operations Manager Data Warehouse database causes duplicate entries, and an exception that resembles the following is thrown:
If data is truncated and is in Terminal status to a workflow, event ID 31551 is logged, and an exception that resembles the following is thrown:
An arithmetic overflow error occurs, and an exception that resembles the following is thrown:
You experience poor performance when Operations Manager searches for attributes. Additionally, when doing more than one search in a row, the cache file (momcache.mdb) keeps increasing.
SCX agent generates lots of warnings in the log file when a user is using Security-Enhanced Linux (SELinux).
By default, the Rpcimap monitor for Red Hat Enterprise Linux 6 is disabled.