IMPORTANT: HP-UX PA-RISC computers monitored by Operations Manager will experience heartbeat and monitoring failures after an upcoming Windows update

Microsoft is preparing to strengthen Windows security by allowing only RSA keys that are more or equal of 1024 bits. As SCOM uses 512 bit key for monitoring HP-UX PA-RISC this will break communication between such servers. Read more about the problem and how to implement workarounds here.

Update Rollup 2 for System Center 2012

This is a big update for System Center 2012 product family. This update rollup includes fixes for all System center components with the exception for Configuration Manager. Here are the fixes provided in this update:

App Controller (KB2721175)

Issue 1
When you view a service on System Center 2012 App Controller as a self-service user, you receive the following warning message:

Retrieved data is incomplete

For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base: 2709415 Viewing a service on System Center 2012 App Controller as a self-service user may fail with a "Retrieved data is incomplete" warning

Issue 2
When you view a service diagram on System Center 2012 App Controller, you receive the following error message:

Category: Critical
Description: App Controller has encountered an error and needs to restart. App Controller will restart when you click Close.
Details: The given node belongs to different graph and therefore it cannot be added to the collection.

Issue 3

When you try to change a service on Windows Azure, the change is not saved, and you receive the following error message:

The specified configuration settings for Settings are invalid. Verify that the service configuration file is a valid XML file, and that role instance counts are specified as positive integers. (StatusCode: BadRequest)
The remote server returned an error: (400) Bad Request. (Status Code: System.Net.Exception)


Data Protection Manager (KB2706783)

Issue 1
After you upgrade from System Center Data Protection Manager 2010, Microsoft SharePoint backups fail if the SharePoint database has a nondefault collation.
Issue 2
A backup of encrypted files fails silently when the self-signed certificate Group Policy Object is disabled.
Issue 3
In the About Microsoft Data Protection Manager dialog box, the Version label is displayed. However, the version number is not displayed.
Issue 4
On the Action menu, the Help command is displayed two times. This issue occurs because you can now access Help for DPM by using the DPM Help command. The Help item on the Action menu refers to Microsoft Management Console (MMC) help.
Issue 5
In the DPM console view menu, the Expand All and Collapse All menu commands are displayed multiple times.
Issue 6
The Windows PowerShell cmdlet to query licenses that are being used is added.
Issue 7
A DPM backup may fail for a SharePoint farm with a mirrored content database whose mirrored server name starts with the principal server name. For example, this issue may occur when the principal server name is "MachineName," the mirrored server name is "MachineName1," and the content database resides on a nondefault instance of Microsoft SQL Server.
This issue may occur when a consolidated backup failure warning is raised for all the mirrored databases that satisfy the previous conditions.
When this failure occurs, you may receive the following error message:

Prepare for backup operation for SQL Server database CONTENT_DB_NAME (mirrored between – SQL PRINCIPAL and SQL MIRROR ) on SQL-PRINCIPAL.FQDN has been stopped because this operation depended on another backup operation which failed or was cancelled. (ID 30200)

Issue 8
Expiry dates for valid datasets that are already written to tape are changed when the retention range is changed during a protection group modification.
For example, a protection group is configured for long-term tape recovery points with custom long-term recovery goals. Recovery Goal 1 has a smaller retention range than other recovery goals. In this configuration, if a protection group is changed to remove Recovery Goal 1 and to keep other recovery goals, the datasets that were created by using Recovery Goal 1 have their retention range changed to the retention range of the other recovery goals.
To work around this problem, create the IsDatasetExpiryDateChangeInModifyPgAllowed DWORD under the following subkey, and then set its value to 0:

HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Data Protection Manager\Configuration\MediaManager

Issue 9
Tapes are marked as reusable on the next day after the date of expiry as DPM runs a reclamation job only at midnight. If you want the tape to be reusable on the same date as it is expired, create the ExpireDatasetOnDayStart 32- bit DWORD, and set its value to 1 under the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Data Protection Manager\Configuration\MediaManager

Issue 10
DPM does not enable browsing of a protected folder on a protected server that has an invalid created date and time.
Issue 11
A tape backup of millions of files fails, and you receive the following error message:

ID 998
Details: The parameter is incorrect (0x80070057).

 

Operations Manager (KB2731874)

Issue 1
The Windows PowerShell module runspace configuration cache grows indefinitely. This causes memory usage to increase.
Issue 2
The Set-SCOMLicense cmdlet fails if the management group evaluation expiration time-out has expired.

Operations Manager – UNIX and Linux Monitoring (Management Pack Update)

Issue 1
The System Center Operations Manager agent may crash on Oracle Solaris root zones that are configured to use a range of dedicated CPUs.
Issue 2
The UNIX/Linux agent process provider may not enumerate running processes if a process has arguments that include non-ASCII characters. This prevents process/daemon monitoring.
Issue 3
The .rpm specification file for the agent for Red Hat Enterprise Linux does not specify the distribution.

Orchestrator (KB2702112 – Runbook Designer (x86), Runbook Server (x86))

Issue 1
A System Center Orchestrator Runbook that uses the "Run Program" activity to execute an application on a system that is running Windows Server 2008, Windows Vista, or an earlier version of Windows may return a failed status for the "Run Program" activity together with the following content in the Error Summary Text published data:

Could not start Orchestrator Run Program Service service on computer_name – The service did not respond to the start or control request in a timely manner. (code 1053)

On the remote computer on which the service is trying to start, the following event is captured in the Application log:

Log Name: Application
Source: Application Error
Event ID: 1000
Level: Error
Description:
Faulting application OrchestratorRunProgramService.exe, version 0.0.0.0, time stamp 0x4f44a324, faulting module KERNEL32.dll!SetProcessPreferredUILanguages, version 6.0.6002.18005, time stamp 0x49e03824, exception code 0xc0000139, fault offset 0x0006f04e,
process id 0x76c, application start time 0x01cd134f73ced65a.

 

Service Manager (KB2719827)

Issue 1
The URL links to incidents or activities in the Notification Templates are incorrect. For more information about this issue, go to the following Microsoft TechNet website:

Including Links to Incidents or Activities in Notification Templates (SCSM 2012)

Issue 2
The time stamp for incidents that are created by using the SMTP connector are incorrect.
Issue 3
If you change the SharePoint site language in the Service Manager portal, an incorrect language may be displayed.
Issue 4
Service Manager does not generate an incident for alerts that are created by Operations Manager rules.

 

Virtual Machine Manager (KB2724538 – Console, KB2724539 – VMM Server, KB2725034 – Self-Service Portal)

Issue 1
After a VMM update is installed, a physical-to-virtual (P2V) conversion may fail with error 413 because the version that is listed in the AgentVersion registry value is incorrect.
Issue 2
A virtual machine has a status of "Unsupported VM Configuration" if the virtual machine was configured to use an ISO and if the Share image file instead of copying it option is selected. For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base:

2690619 Virtual machine configured to use an ISO has a status of Unsupported VM Configuration in System Center 2012 Virtual Machine Manager

Issue 3
Power optimization powers off the host computer instead of shutting it down.
Issue 4
When you view checkpoints for a VMware virtual machine, the VMM Console may crash. Additionally, you receive the following error message:

Value of ‘0’ is not valid for ‘Value’. ‘Value’ should be between ‘Minimum’ and ‘Maximum’.

Issue 5
Virtual machine placement may provide the same host rating even though available memory between the hosts is different.
Issue 6
You cannot log on to App Controller because VMM does not support domains that have a one-way trust.
Issue 7
Text is truncated on PRO tip warnings.
Issue 8
Images (or logos) within PRO tips are not displayed when integrating with System Center 2012 Operations Manager.
Issue 9
The VMM Console can take several minutes to load in environments that have several hundred hosts.
Issue 10
Virtual machine placement can require up to 30 seconds per host.
Issue 11
VMM Console performance decreases in large environments.
Issue 12
VMM does not recognize third-party disk resource types that are used in a Hyper-V failover cluster.
Refresh host cluster jobs may fail, and you receive the following error message:

Warning (13926)
Host cluster cluster.contoso.com was not fully refreshed because not all of the nodes could be contacted. Highly available storage and virtual network information reported for this cluster might be inaccurate.

Virtual machines that have a status of "Unsupported Cluster Configuration" may fail, and you receive the following error message:

Error (13924)
The highly available virtual machine (VMname) is not supported by VMM because the virtual machine uses non-clustered storage.

 

 

The update for the different components can be downloaded from these links:

Full description on the update and instructions for installation can be found in the knowledge base article.

Cumulative Update 4 for System Center Service Manager 2010 SP1 is available

Another hotfix for a product of System Center family. This cumulative update contains only one fix for System Center Service Manager 2010 SP1:

  • This update fixes an issue in which the wrong time stamp is used for incidents that are created by the Simple Mail Transfer Protocol (SMTP) connector.

Full instructions on installing the update are here.

The update file is located here.

QFE Rollup Package 6 for System Center Data Protection Manager 2010 is released

Microsoft released a new hotfix for SCDPM 2010. This hotfix resolves several issues:

  • DPM backup fails for a Microsoft SharePoint farm together with a mirrored content database if the mirrored server name starts with the same name as the principal server name. For example, this issue occurs if the principal server name is "MachineName," the mirrored server name is "MachineName1," and the content database is on a nondefault instance of Microsoft SQL Server. 
    Additionally, you receive the following error message:

    Prepare for backup operation for SQL Server database CONTENT_DB_NAME (mirrored between – SQL PRINCIPAL and SQL MIRROR ) on SQL-PRINCIPAL.FQDN has been stopped because this operation depended on another backup operation which failed or was cancelled. (ID 30200)

  • Expiry dates for valid datasets that are already written to tape are changed when the retention range is changed during a protection group modification.
    A protection group is configured for long-term tape recovery points together with custom long-term recovery goals. Recovery Goal 1 has a smaller retention range than the other recovery goals. In this configuration, if the protection group is changed to remove Recovery Goal 1 and to keep other recovery goals, datasets that were created by Recovery Goal 1 have their retention range changed to the retention range of the other recovery goals.
    To avoid this problem, create the IsDatasetExpiryDateChangeInModifyPgAllowed DWORD value under the following registry key, and then set its value data to 0:

    HKLM\Software\Microsoft\Microsoft Data Protection Manager\Configuration\MediaManager

  • Tapes are not reusable until the day after the day of expiry. This is true because DPM waits until midnight to run the reclamation job that marks tapes as reusable. If a user wants a tape to be reusable on the same day on which it expires, the user should follow these steps: 
    1. Create the following registry key:

      HKLM\Software\Microsoft\Microsoft Data Protection Manager\Configuration\MediaManager

    2. Create the ExpireDatasetOnDayStart 32-bit DWORD value, and then set its value data to 1.
  • DPM does not enable browsing of protected folders on a protected server that has an invalid created date and time.
  • A tape backup of millions of files fails, and you receive the following error message: 

    ID 998 Details: The parameter is incorrect (0x80070057).

  • Tape colocation that has a high expiry tolerance mixes retention ranges. This causes tapes to expire earlier than expected.
    Full information and instructions for implementing about this hotfix can be found here.
    The update itself can be downloaded from here.

KB: Adding a Citrix XenServer host on System Center 2012 Virtual Machine Manager fails with error 2916 (0x8033810f)

In this Microsoft knowledgebase article can be found solution to the issue.