System Center 2012 Update Rollup 3 (UR3) Released!

System Center 2012 Update Rollup 3 (UR3) Released!

  • Comments 3
  • Likes

We are pleased to announce that System Center 2012 Update Rollup 3 (UR3) has been released.  Keeping with our currently schedule of releasing update rollups quarterly, Update Rollup 3 provides updates for issues that have been reported to Microsoft.

This update contains updates for Service Manager, Data Protection Manager, and Operations Manager.  This also marks the first time that Data Protection Manager and Operations Manager updates have been released via Microsoft Update (MU).

clip_image002

 

Issues that are fixed in Update Rollup 3 for System Center 2012

Update Rollup 3 for System Center Data Protection Manager 2012 (KB2751230)

Issue 1
After you upgrade System Center Data Protection Manager 2010 to System Center Data Protection Manager 2012, the tape management report does not display overdue tapes.
Issue 2
System Center Data Protection Manager 2012 Client Protection does not scale to the limits that are expected.
Issue 3
When you try to specify a client computer name in the DPMServerName attribute by using Windows PowerShell, Windows PowerShell crashes.
Issue 4
When the name of a Microsoft SharePoint site collection contains a space, and you perform a SharePoint item-level recovery operation in System Center Data Protection Manager 2012, the operation fails.
Issue 5
After you rename a SharePoint site in System Center Data Protection Manager 2012, you cannot restore the site.
Issue 6
The SharePoint Recovery Point Status Report displays incorrect data in System Center Data Protection Manager 2012.
Issue 7
A bare metal recovery fails in certain situations.

Update Rollup 3 for System Center Operations Manager 2012 (KB2750631)

Issue 1
When you use the 32-bit version of Windows Internet Explorer to start a web console, the Microsoft.EnterpriseManagement.Presentation.Controls.SpeedometerGaugeUIController controller does not work correctly.
Issue 2
When you run a Windows PowerShell cmdlet, you receive the following error message: 

Get-BPAModel is not recognized as the name of a cmdlet.

Issue 3
When you try to change a URL in the "web application availability monitoring" template instance, the change is not applied.

Update Rollup 3 for System Center Service Manager 2012 (KB2750615)

Issue 1
When you open or close the Incident form in the System Center Service Manager 2012 console, a memory leak occurs.
Issue 2
When form control objects are rooted in the Garbage-Collected (GC) Heap, the System Center Service Manager 2012 console crashes, and you receive an OutOfMemoryException exception.
Issue 3
After you change the SharePoint site language to Turkish in the System Center Service Manager 2012 portal, the display strings are displayed in English unexpectedly.
Issue 4
When you open the System Center Service Manager 2012 console by using a Citrix application, and then you open the Incident form, you experience slow performance.

 

You can find more details and instructions for obtaining and installing the update rollup on the associated KB article here:

http://support.microsoft.com/kb/2756127

 

Thank you all for your feedback on these issues.  Please continue to create support cases for issues that you encounter so they can be triaged for inclusion in future cumulative updates or service packs.

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

    It would be helpful if the installation instructions listed the servers that the rollup should be applied to and if it should be installed on client machines with the SCSM console installed.

    when including the SMPortal servers I have 7 servers in my environment and I would prefer to know ahead of time which ones need to be updated.

  • Glad to see performance enhancements for the SCSM 2012 client.  I've seen the client fail to close after exiting (process stays resident), I wonder if this might help.

  • The install for the update rollup 3 is throwing an error at the "Finalize" step: "An error ocurred while executing a custom action:RollbackCleanup"

    at this point, the install ends with a failure. any thoughts?