Jean-Sébastien DUCHENE Blog's

Actualité, Tips, Articles sur l'ensemble des Technologies Microsoft (SCCM/SMS, EMS, Microsoft Intune, Microsoft Azure, Windows 10, SCOM, MDOP...)

Microsoft vient de publier l’Update Rollup 6 pour les produits System Center 2012 SP1. Avant d’appliquer cet UR, lisez bien les articles de la base de connaissances associés. Vous pouvez les déployer manuellement en récupérant les CAB ou via Windows Update/WSUS.

Celui-ci corrige les problèmes suivants :

System Center 2012 Operations Manager SP1 (KB2929885)

  • Service Level Objectives (SLO) dashboards sometimes load in several seconds and sometimes take minutes to load. Additionally, the dashboard is empty after it loads in some cases.
  • SQL Time Out Exceptions for State data (31552 events) occur when you create Data Warehouse workflows.
  • This update rollup includes a fix for the dashboard issue that was introduced in Update Rollup 5.
  • Adding multiple regular expressions (RegEx's) to a group definition causes a SQL exception when adding or running the group.
  • The System Center Operations Manager console is slow to load views if you are a member of a custom Operator role.

System Center 2012 Operations Manager SP1 UNIX (KB2929885)

  • All IBM WebSphere application servers that run on Linux or AIX computers are not automatically discovered by the Management Pack for Java Enterprise Edition (JEE) if multiple application servers are defined in a single WebSphere profile.


System Center 2012 Service Manager SP1 (KB2904726)

  • If the Manual Activities list that is displayed in the Service Manager portal exceeds a certain limit, page loads time out and do not display correctly. This causes a blank page to be displayed.
  • Incorrect cleanup of custom related types cause grooming on the EntityChangeLog table to stall. This causes the table to grow significantly.
  • Service requests finish unexpectedly because of a race condition between workflows.
  • The console crashes when you double-click the parent incident link on an extended incident class.
  • Windows PowerShell tasks that are created by using the authoring tool do not run because of an incorrect reference to certain assemblies.
  • Exchange Management Pack gets stuck in pending association after a Management Pack sync job.
  • "Run as Accounts" is enabled for use with the release version of Exchange Connector 3.0.
  • SQL broker conversations could lead to a very large OperationsManagerDB size and TempDB size.
  • Service requests that are put on hold are evaluated incorrectly as completed.
  • File attachments are not being correctly saved in the database.
  • The RunbookMonitorWorkflow process cannot handle a failed status of runbooks (workflow).
  • After you upgrade to SP1, new "Service Dependents" entries that are created for "Business Services" cannot be seen in the console.
  • Later activities in a service request start to run even though the current activity is not yet complete.
  • The Review Activity "add reviewer" workflow cannot run.
  • Simple lists in a self-service portal do not function correctly in the shared services provider (SSP) after you upgrade to SP1.
  • Windows PowerShell tasks that are created by using the authoring tool do not run.
  • For users who have both SMTP and SIP endpoints, Service Manager detects the Lync "sip" endpoint. This occurs even when you send email messages to users from the console.
  • After you select Service Requests with Service Level Warning, you receive a "FullAdapter" exception error message about one hour later.
  • After you select the Assigned to me view, you receive a FullAdapter" exception error message about one hour later.
  • Service Manager console maximized window fixes include the following:•When maximized, the console is slow or unresponsive and has up to 30 percent CPU usage.
    • Context menus in the console do not display where they are expected. Instead, they appear at the upper-right corner of the window.
    • Work item scroll bars in the preview pane do not display correctly when you run in full-screen mode. When they do appear, they are inactive and cannot be used.
    • Forms and wizards are not always displayed correctly. Only the left navigation pane is displayed, and the right side area is blank.
  • When you edit or create request offerings, user prompts do not display correctly.
  • Concurrent Windows PowerShell workflows cannot run, although they are listed as successful in the console.
  • An error occurs in the console when you try to open an attachment in a work item form that was already opened.
  • The attachment and its associated details of the release record cannot be retrieved after it is marked as closed.
  • The request offering form takes a long time to display when you create service requests from request offerings.j. The console crashes when you try to use an SR template that has an assigned analyst.
  • Creating a service request can cause a NullReferenceException error and can cause the console to crash.
  • The Service Manager console shows a generic SQL exception instead of the detailed Data Collision exception when you run in a non-English environment.
  • When you are grooming the database, the p_DataPurging stored procedure does not finish, and SQL registers an error that occurs with event ID 8623. The error states that the query processor ran out of internal resources and could not produce a query plan.
  • Adding multiple "RegEx"es to a group definition causes a SQL error when you add or execute the group.
  • 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.

System Center 2012 Data Protection Manager SP1 (KB2958098)

  • Catalog generation fails for SharePoint 2013 sites that contain app store parts.
  • Update rollup for DPM 2012 SP1 introduces new stored procedures that have incorrect SQL permissions. This causes connectivity issues with DPM UI when opened as a non-admin user.
  • SetBackupComplete called prematurely causes SetBackupSucceeded to be called and 0x80042301 in VSS.
  • SharePoint item level recovery fails when the first part of the site URL matches another site in SharePoint.
  • Status reports says DPMDB is not being protected even though it is protected and there are valid Recovery Points on tape for it.
  • Invalid Trace Message format string causes second chance System.FormatException and termination of DPM Process.


Télécharger :


Facebook Like