Update Rollup 2 for Microsoft System Center 2012 Service Pack 1 (SP1) is now available and includes the following updates for OpsMgr 2012 SP1:
Issue 1: The Web Console performance is very poor when a view is opened for the first time.
Issue 2: The alert links do not open in the Web Console after Service Pack 1 is applied for Operations Manager.
Issue 3: The Distributed Applications (DA) health state is incorrect in Diagram View.
Issue 4: The Details Widget does not display data when it is viewed by using the SharePoint webpart.
Issue 5: The renaming of the SCOM group in Group View will not work if the user language setting is not "English (United States)."
Issue 6: An alert description that includes multibyte UTF-8 characters is not displayed correctly in the Alert Properties view.
Issue 7: The Chinese (Taiwan) Web Console displays the following message even after the SilverlightClientConfiguration.exe program is run: Web Console Configuration Required.
Issue 8: The Application Performance Monitoring (APM) to IntelliTrace conversion is broken when alerts are generated from dynamic module events such as the Unity Container.
Issue 9: Connectivity issues to System Center services are fixed.
Issue 10: High CPU problems are experienced in Operations Manager UI.
Issue 11: Query processor runs out of internal resources and cannot produce a query plan when you open Dashboard views.
Issue 12: Path details are missing for "Objects by Performance."
Issue 1: The Solaris agent could run out of file descriptors when many multi-version file systems (MVFS) are mounted.
Issue 2: Logical and physical disks are not discoverable on AIX-based computers when a disk device file is contained in a subdirectory.
Issue 3: Rules and monitors that were created by using the UNIX/Linux Shell Command templates do not contain overridable ShellCommand and Timeout parameters.
Issue 4: Process monitors that were created by the UNIX/Linux Process Monitoring template cannot save in an existing management pack that has conflicting references to library management packs.
Issue 5: The Linux agent cannot install on a CentOS or Oracle Linux host by using FIPS version of OpenSSL 0.9.8.
You can get all the details and a download link here:
KB2802159 - Description of Update Rollup 2 for System Center 2012 Service Pack 1 (http://support.microsoft.com/kb/2802159)
J.C. Hornbeck | Knowledge Engineer | Microsoft GBS Management and Security Division
Get the latest System Center news on Facebook and Twitter:
System Center All Up: http://blogs.technet.com/b/systemcenter/ System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/ System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/ System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/ System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm
Windows Intune: http://blogs.technet.com/b/windowsintune/ WSUS Support Team blog: http://blogs.technet.com/sus/ The AD RMS blog: http://blogs.technet.com/b/rmssupp/
App-V Team blog: http://blogs.technet.com/appv/ MED-V Team blog: http://blogs.technet.com/medv/ Server App-V Team blog: http://blogs.technet.com/b/serverappv
The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
Concerning issue 12, I've noticed that it's not solved from the Web Console point of view. My Dashboard is ok from SCOM Console, I can see the path that was previously missing. But in the same Dashboard from the Web console, the path are still missing.
Any idea why ?
Hi Philippe, thanks for the note. I'm not sure why this might be occurring but I'll get this to the product group and report back on what I find out.
I notice in the KB2802159:
Do not install the update rollup package immediately after you install the System Center 2012 SP1 server. Otherwise, the Health Service state may not be initialized.
We are currently running SCOM 2012 and going to upgrade to SP1. My question is how long time we shall wait after upgrading to SCOM 2012 SP1. And is it okay to leave the agents (Both Windows agents and Linux agents) at 2012 version and upgrade them after UR2 applied??
York - We have additional information on that here: blogs.technet.com/.../patience-is-a-virtue-with-the-system-center-2012-operations-manager-sp1-installation.aspx