The article below describes the issues that are fixed in Update Rollup 5 for Microsoft System Center 2012 R2 Operations Manager (OpsMgr 2012 R2 UR5)
Issues that are fixed in this update rollup
Operations Manager
- Monitoringhost process crashes because of bind failures against Active Directory
- RunAs accounts cannot be edited because of "Specified cast is invalid" exceptio
- Application crashes when a search is finished without filter criteria on Distributed application designer
- MonitoringHost crashes with the exception - System.OverflowException: Value was either too large or too small for an Int32
- Support to troubleshoot PowerShell scripts
- Operational Insights through Operations Manager
- "Reset the Baseline," "Pause the baseline," and "Resume the baseline" tasks fail when they are run against an Optimized performance collection rule
- An exception occurs when you edit subscriptions that contain deleted monitors or objects
- You can't set Widget column width
- Event 4506: Data was dropped because of too much outstanding data
- Support for handling Datawarehouse time-outs
- Can't continue scan with NOLOCK because of data movement
- $ScriptContext.Context does not persist the value in PowerShell widgets
- Evaluation version alert
UNIX/Linux management pack
- Updating the UNIX/Linux agent for Operations Manager resets deep monitoring status for JEE application servers.
- By default, the rpcimap monitor for Red Hat Enterprise Linux 5 is now disabled.
- When you use the "scxadmin -log-rotate" utility, this stops logging to the agent’s log (/var/opt/microsoft/scx/log/scx.log) after log rotation is completed.
For more information, please read the Microsoft article here.
This posting is provided "AS IS" with no warranties.
No comments:
Post a Comment