[System Center 2012 SP1] L’Update Rollup 8 de System Center 2012 SP1 (OM, DPM)

Microsoft vient de publier l’Update Rollup 8 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 R2 Operations Manager (KB2991997)

• Un redémarrage du HealthService est causé par une utilisation élevée de la mémoire dans le processus MonitoringHost.

• La resynchronisation de toutes les entités gérées à partir de la base de données opérationnelle vers le Data Warehouse engendre des entrés dupliquées et l’exception suivante :

  Description:

  Data was written to the Data Warehouse staging area but processing failed on one of the successive operations.

  Exception 'SqlException': Sql execution failed. Error 2627, Level 14, State 1, Procedure ManagedEntityChange, Line 367, Message: Violation of UNIQUE KEY constraint 'UN_ManagedEntityProperty_ManagedEntityRowIdFromDAteTime'. Cannot insert duplicate key in object 'dbo.ManagedEntityProperty'..

• L'importation de Visualization.component.library et les fichiers binaires Visualization.library (.mpb) échoue. L'importation réussit après un essai supplémentaire.

• Les agents System Center Operations Manager font un time out au hasard lors de l'authentification à la gateway ou Management Server en raison de contrôleur de domaine ou des problèmes de performance du réseau. La valeur time-out avait été fixé à 1 seconde. Un correctif a été fait pour augmenter le temps pour les serveurs d’infrastructure à 20 secondes et le temps pour les clients à 5 minutes.

System Center 2012 R2 Data Protection Manager (KB2991995)

• Item-level recovery does not restore custom permissions when Microsoft SharePoint is running localized language packs.
  For example, assume that you try to back up a SharePoint server that has various files together with custom access permission settings and that is using a non-English locale for SharePoint sites. When you try to recover the files, item-level recovery recovers the data successfully. However, the custom permissions might be lost. Therefore, some users may no longer access the file until permissions are restored by SharePoint administrators.

• An instance of SQL Server is missing when you try to create a protection group.
  Consider the following scenario:

  • You have a default instance of SQL Server and another instance (for example, it is named as "domaininstance").

  • You create a database, and you name it "domainins" in the default SQL instance.

  • You try to create or change a protection group.

    In this scenario, the "domaininstance" instance of SQL Server is not displayed in the Create Protection Group Wizard.

• Assume that there are several virtual machines on the Hyper-V host that are physically removed. When you try to stop protection of these virtual machines, the DPM user interface crashes.

  Consider the following scenario:

  • You protect an SQL database by using a long-term protection on a tape.

  • The SQL logs are moved to a different disk volume.

  • You back up the database for the first time after you move the logs.

    In this scenario, the DPM service crashes, and a NullReferenceException exception is thrown.

• Scheduled backup to tape runs on a wrong date for quarterly, semi-annually and yearly backups. Additionally, you may see that the schedule runs before the specific date.

• When you try to change protection groups, the DPM service crashes, and you receive the following error message:

  Connection to the DPM service has been lost. (ID: 917)

• The DPM service crashes, and you receive error 999.

Télécharger :

• Update Rollup 8 for System Center 2012 Data Protection Manager SP1

• Update Rollup 8 for System Center 2012 Operations Manager Service Pack 1