Update Release 2 available for System Center 2012 Service Manager SP1 and R2

Last week the Service Manager Engineering Team announced the release of  Update Rollup for both System Center 2012 Service Manager SP1 and R2 – the set of fixes between the two versions is going to be identical, except for a fix in MP Importer, a feature which is only applicable to the R2 release.

Console fixes:

  1. For users who have both SMTP and SIP endpoints, Service Manager always picks up the Lync “sip” endpoint, even when emailing users from the console.
  2. After selecting Service Requests with Service Level Warning, an error message stating a “FullAdapter” exception occurs about one hour later.
  3. After selecting the Assigned to me view, an error message stating a “FullAdapter” exception occurs about one hour later.
  4. Service Manager console maximized window fixes:
    1. When maximized, the console is slow or unresponsive and has up to 30% CPU utilization.
    2. Context menus in the console don’t render where expected — instead, they appear at the top-right corner of the window.
    3. Work item scroll bars in the preview pane do not render properly when running in full screen mode. When they do appear, they are inactive and cannot be used.
    4. Forms and wizards don’t always render properly and only the left navigation pane renders with the right area blank.
    5. When editing or creating request offerings, user prompts do not render properly.
  5. Concurrent PowerShell workflows fail to run, although they show as successful in the console.
  6. An error appears in the console when you try to open an attachment in a work item form that was already opened.
  7. The attachment and its associated details of the release record cannot be retrieved after it is marked as Closed.
  8. The request offering form takes a long time to render when you create service requests from request offerings.
  9. Console crashes when attempting to use an SR Template with an assigned analyst..
  10. Creating a service request can cause a NullReferenceException error and crashes the console.
  11. SM console shows a generic SQL exception instead of the detailed Data Collision exception when running in a non-English environment.

Platform fixes:

  1. When grooming of the Database the p_DataPurging stored procedure does not complete and SQL registers an error with event ID 8623 stating that the query processor ran out of internal resources and could not produce a query plan
  2. Adding multiple RegEx’s to a group definition causes a SQL error when you add or execute the group.
  3. The Configuration Manager connector does not handle updates to DeviceHasSoftwareItemInstalled correctly. This causes a divergence in the data that is synchronized between the Service Manager and Configuration Manager databases.
  4. MPImporter does not import management packs from Operations Manager if Service Manager has any management packs from a previous version already present.

The news of the pending release is definitely a welcome sign and shows that Microsoft truly is intent on keeping the product around. In early February Microsoft had to take the blog wires to assure customers that Service Manager was not a dead product due to rumors and due to limited improvements to the product over a long span.

An Update Rollup is a single installation that contains all the fixes and updates provided since either the last major product update or since the last Update Rollup was released. The Update Rollup is expected to be available for download via the Download Center today.

The Update Rollup 2 for System Center 2012 R2 Service Manager can be downloaded here

Sources:

http://blogs.technet.com/b/servicemanager/archive/2014/04/18/upcoming-fixes-in-the-april-ur2.aspx

http://windowsitpro.com/service-manager/update-rollup-service-manager-due-tuesday

It's only fair to share...Tweet about this on TwitterShare on LinkedIn0Share on Google+0Share on Facebook0