OpsMgr 2012 SP1 User Experience Issues Resolved with UPDATE ROLLUP 2

OpsMgr 2012 SP1 User Experience Issues Resolved with UPDATE ROLLUP 2

  • Comments 3
  • Likes

With the latest update rollup we resolved 2 major user experience issues customers have given us feedback on.


1. Hostname\Display Name in “Object by Performance” widget is empty

I am happy to announce that we addressed the issue where the display name in Object By Performance widget was never returned. I showed that we fixed this issue at my MMS 2013 dashboarding session last Tuesday and all 850 people that attended applauded. I know this was a big hurdle for most of you and I apologize in any delay in getting this issue resolved.


 2. OpsMgr Web Console Performance Improved

We have made some significant web console performance improvements with this update rollup in particular view load times. We made some changes in the code which now helps views like the alert view loads in a couple of seconds. This is another big customer request where we have addressed with this update.

You can download the update from here: http://support.microsoft.com/kb/2802159

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Hi Satya,

    I noticed in my lab that the path still does not show in the "object by performance" widget when it's accessed from the SCOM Web Console. Do you confirm this ?

  • Philippe you are right the "Display Name” fix for Obj by Perf widget worked in the SCOM desktop console but does not populate in the SCOM Web Console for some reason. I am having the devs take a look at this issue and we hope to have it resolved for you as part of SP1 Update Rollup 3.

    Thanks for notifying us. We appreciate it.

  • We have found a temporary workaround for this issue which involves:

    Copying the “Microsoft.EnterpriseManagement.Presentation.DataProviders.Library” and “Microsoft.EnterpriseManagement.Monitoring.DataProviders” DLLs found in the OM desktop console folder \OperationsManager\Console and replacing the DLLs in the WebConsole Server folder WebConsole\WebHost\bin.

    This fixes the issue straightaway.