Support Tip: OpsMgr 2012 console issues fixed in Update Rollup 4 for System Center 2012 Service Pack 1

Support Tip: OpsMgr 2012 console issues fixed in Update Rollup 4 for System Center 2012 Service Pack 1

  • Comments 9
  • Likes

ToolsJust a quick note to let you know about a couple issues you may see with the System Center 2012 Operations Manager (OpsMgr 2012) admin console when installed on Windows 7 x64 (64-bit) with .Net 4.5 or .Net 4.5.1. Both of these are fixed in Update Rollup 4 for System Center 2012 Service Pack 1.

What happens is that the console installs fine and appears to be working until you try to create a new dashboard or view performance data while changing the time range. The exact issues you may experience include the following:

1. Templates are missing when creating a new dashboard view from the Dashboard and Widget Wizard.  The templates may appear the first time but disappears if you cancel and then retry.

2. The console temporarily stops responding (hangs) when trying to view performance data while changing the selected time range (e.g. viewing the DC Performance data for % Processor Time of the LSASS process from the Microsoft Windows Active Directory Management Pack and changing the time range from 1 day to 5 days).  The Microsoft.ExterpriseManagement.Montioring.Console.exe process will ultimately consume 1 to 2 GB of memory before the console eventually responds with the requested data. 

As mentioned, both of these issues are fixed in UR4 for System Center 2012 SP1 which can be found here:

KB2879276 - Description of Update Rollup 4 for System Center 2012 Service Pack 1 (http://support.microsoft.com/kb/2879276)

J.C. Hornbeck | Solution Asset PM | Microsoft GBS Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

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/

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Why UR4 for SP1 when R2 is out? Is this fixed in R2?

  • UR4 for SP1 and R2 RTM were out roughly at the same time: like some other bugs, I believe this was fixed in R2 first and the fix back-ported to SP1.

  • This issue still exist with SP1 UR4. I am going to try upgrading to R2 RTM to see if that helps.

  • Correction: Works fine...forgot to update the standalone console to UR4. :) Thanks!