Issues that are fixed in Update Rollup 1
App Controller (KB2790935)Issue 1
Copying a .vhd file between Microsoft Azure storage accounts may be unsuccessful, and you receive a "Retrieved data is complete" warning message. This issue occurs if the .vhd file already exists on the destination or if the .vhd file is mapped to an existing virtual machine.Issue 2
The importation of Virtual Machine Manager (VMM) library server certificates may be unsuccessful for VMM library servers that are clustered.
Data Protection Manager Issue 1
Client backups fail when there is a case difference between the client computer name on the computer and the client computer name that is stored in Active Directory.Issue 2
The Administrator Console may stop working when a user starts the Create Protection Group Wizard in a non-English or a non-Russian version of Data Protection Manager.Issue 3
The Agent Management Wizard may stop working in the Spanish version of Data Protection Manager.
Operations Manager (KB2784734)Issue 1
Agentless Exception Monitoring (AEM) in Operations Manager may provoke an increase in reporting threads and choke points.Issue 2
After the Alert Attachment Management Pack (Microsoft.SystemCenter.AlertAttachment.mpb) is imported, you create a dashboard that contains an alert widget. When you click an alert, the Operations Manager console may crash.Issue 3
When a Windows PowerShell module uses the Monitoringhost.exe process on an x86-based client that is running Windows 8, more than 800 megabytes (MB) of memory may be consumed.Issue 4
After an application domain is created, adding another application domain may be unsuccessful.
Operations Manager - UNIX and Linux Monitoring (Management Pack Update)Issue 1
When multiple process monitors are used to target the same computer or group, processes may incorrectly monitor some template instances. Additionally, problems with the monitored processes may not be detected. This issue occurs when each process monitor uses the same name as the process even though different argument filters are used in each process monitor.Note
After the updated Microsoft.Unix.Process.Library.mpb file is imported, all existing Process Template instances must be edited and saved for the fixed behavior to take effect.
Service Provider Foundation (KB2785476)Issue 1
property on a virtual hard disk (VHD) object is always set to NULL.Issue 2
Virtual machine usage metrics are not aggregated at hourly intervals and are missing basic usage metrics such as network sent and receive I/O operations per second (IOPS).
Virtual Machine Manager (KB2792925 - Console; KB2792926 - VMM Server)Issue 1
When a logical unit number (LUN) is unmasked on an iSCSI array, the VMM service may crash.Issue 2
When a node is put in maintenance mode, virtual machines in the cluster change to a status of "Unsupported Cluster Configuration."Issue 3
When an add-in that uses multiple DLL files is expected to be imported into the VMM console, the add-in is not imported. Additionally, you receive the following error message:
Add-in cannot be installed
When an add-in is expected to be imported into the VMM console on a server that is running Windows Server 2008 R2, the add-in is not imported.Issue 5
When an add-in is imported into the VMM console, the console may crash.Note
After Update Rollup 1 for Virtual Machine Manager is installed, you may experience one of the following issues:
- When you try to import an add-in into the VMM console, the import may be unsuccessful. Additionally, you receive the following error message:
An error occurred while trying to create an add-in folder for your account:
Access to the path: "C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\AddInPipeline\AddIns" is denied.
- When you open the VMM console, you receive the following error message:
Could not update managed code add-in pipeline due to the following error:
The required folder "C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\AddInPipeline\HostSideAdapters" does not exist.
To resolve these issues, follow these steps:
- Locate the following folder:
C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin
- Right-click the AddInPipeline folder, and then click Properties.
- On the Security tab, click Advanced, and then click Continue.
- Select the BUILTIN group, and then click Edit.
- Click the Select a principal link, type Authenticated Users, and then click OK.
- Click OK to close each dialog box that is associated with the properties.
Installation instructions for Data Protection Manager
To install the update for Data Protection Manager, follow these steps:
- Before you install this update, make a backup of the DPM database.
- Install the rollup package on the server that is running System Center 2012 SP1 - Data Protection Manager. To do this, run Microsoft Update on the server.
Note Before you install this update through Microsoft Update, the DPM Console should be closed. You may have to restart the Data Protection Manager server after you install this rollup package.
- In the DPM Administrator Console, update the protection agents. To do this, use one of the following methods.
Method 1: Update the protection agents from the DPM Administrator Console
- Open the DPM Administrator Console.
- Click the Management tab, and then click the Agents tab.
- In the Protected Computer list, select a computer, and then click Update on the Action pane.
- Click Yes, and then click Update Agents.
Note A restart may be required for Agent Upgrades.
Method 2: Update the protection agents on the protected computers
- Obtain the update protection agent package from the "<Data Protection Manager installation location>\DPM\DPM\Agents\RA\4.1.3322.0" directory on the System Center 2012 SP1 - Data Protection Manager server.
- For x86-based updates: i386\1033\DPMAgentInstaller_KB2802095.exe
- For x64-based updates: amd64\1033\DPMAgentInstaller_KB2802095_AMD64.exe
Note The DPMAgentInstaller.exe package applies to all languages.
- Run the appropriate DPMAgentInstaller.exe package on each protected computer, based on the architecture of the Agent.
- Open the DPM Administrator Console on the System Center 2012 Service Pack 1 - Data Protection Manager server.
- Click the Management tab, and then click the Agents tab.
- Select the protected computers, update the information, and then verify that the agent version is listed as 4.1.3322.0.
Installation instructions for Operations Manager
Known issues for this update
- After you install the update rollup package on all roles on the server that is running System Center Operations Manager 2012 Service Pack 1 (except on the Agent and Gateway roles), the updates do not appear in the Add or Remove Programs item in Control Panel.
- After you apply Update Rollup 1, the Operations Manager console has to be reopened in order to apply the Alert Attachment Management Pack fix.
- After you install the update rollup package, the version number of the console is not changed.
- After you install the update rollup package on a web console, you receive the following error message in Internet Explorer:
Server Error in '/OperationsManager' Application.
To resolve this issue, close and then restart Internet Explorer.
- After you uninstall the update rollup package, a System.Management.Automation.ActionPreferenceStop exception occurs in the Discover Agent Versions script, and the script fails. To resolve this issue, change the InstallDirectory value in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\System Center Operations registry subkey to the following value:
C:\Program Files\System Center 2012 SP1\Operations Manager\PowerShell
- This update rollup package is available from Microsoft Update in the following languages:
- Chinese Simplified (CHS)
- Japanese (JPN)
- French (FRA)
- German (DEU)
- Russian (RUS)
- Italian (ITA)
- Spanish (ESN)
- Portuguese (Brazil) (PTB)
- Chinese Traditional (CHT)
- Korean (KOR)
- Czech (CSY)
- Dutch (NLD)
- Polish (POL)
- Portuguese (Portugal) (PTG)
- Swedish (SWE)
- Turkish (TUR)
- Hungarian (HUN)
- English (ENU)
- Chinese Hong Kong (HK)
- Some components are language neutral, and the updates for these components are not localized.
- You must run the update rollup as an administrator.
- If you do not want to restart the computer after you apply the console update, close the console before you apply the update for the console role.
- To start a new instance of Microsoft Silverlight, clear the browser cache in Silverlight, and then restart Silverlight.
- Do not install the update rollup package immediately after you install the System Center 2012 SP1 server. Otherwise, the Health Service state may not be initialized.
- If User Account Control is enabled, run the .msp update files from an elevated command prompt.
- You must have System Administrator rights on the database instances for the Operational Database and Data warehouse to apply updates to these databases.
- Microsoft.SystemCenter.IntelliTraceProfiling.mpb is included in Update Rollup 1 but does not contain new fixes. Do not import this file.
- To enable the web console fixes, add the following line to the %windir%\Microsoft.NET\Framework64\v2.0.50727\CONFIG\web.config file:
<machineKey validationKey="AutoGenerate,IsolateApps" decryptionKey="AutoGenerate,IsolateApps" validation="3DES" decryption="3DES"/>Note Add the line under the <system.web> section as described in the following article in the Microsoft Knowledge Base:
You may receive an error message when you access ASP.NET Web pages that have ViewState enabled after you upgrade from ASP.NET 1.1 to ASP.NET 2.0
Supported installation order
We recommend that you install the update rollup package in the following order.
- Install the update rollup package on the following server infrastructure:
- Management server or servers
- Gateway servers
- Reporting servers
- Web console server role computers
- Operations console role computers
- Manually import the management packs.
- Apply the agent update to manually installed agents, or push the installation from the Pending view in the Operations console.
- Install the update rollup package on agents either before or after you install the update rollup package on the server infrastructure.
- If the Connected MG/Tiering feature is enabled, first update the top tier of the Connected MG/Tiering feature.
To download the update rollup package and extract the files that are contained in the update rollup package, follow these steps:
- Download the update packages that Microsoft Update provides for each computer. Microsoft Update provides the appropriate updates according to the components that are installed on each computer.
- Apply the appropriate MSP files on each computer.
Note MSP files are included in the update rollup package. Apply all MSP files that relate to a specific computer. For example, if the web console and console roles are installed on a management server, apply the MSP files on the management server. Apply one MSP file on a server for each specific role that the server holds.
- Import the following management pack:
For information about how to import a management pack from a disk, go to the following Microsoft TechNet website:Note
Management packs are included in the Server component updates in the following path:
%SystemDrive%\Program Files\System Center 2012 SP1\Operations Manager\Server\Management Packs for Update Rollups
To uninstall an update, run the following command:
msiexec /uninstall PatchCodeGuid /package RTMProductCodeGuidNote
In this command, the placeholder RTMProductCodeGuid
represents one of the following GUIDs.
Additionally, the placeholder PatchCodeGuid
represents one of the following GUIDs.
Installation instructions for Operations Manager UNIX and Linux monitoring packs and agents
To install the updated monitoring packs and agents for UNIX and Linux operating systems, follow these steps:
- Download the updated management packs from the following Microsoft website:
- Install the management pack update package to extract the management pack files.
- Import the following:
- The updated Microsoft.Unix.Library management pack (from the Microsoft.Unix.Library\2012 SP1 folder)
- The Microsoft.Process.Library management pack bundle
- The platform library management packs that are relevant to the Linux or UNIX platforms that you monitor in your environment
- Import the updated management pack for each version of Linux or UNIX that you monitor in your environment.
Installation instructions for Service Provider Foundation
Known issues for this update
- After you install the Update Rollup 1 package on the Service Provider Foundation server, the updates do not appear in the Add or Remove Programs item in Control Panel.
- After you install the Update Rollup 1 package on the Service Provider Foundation server, the VMM endpoint Application Pools identity will be set to Network Services. To resolve this issue, use the IIS management console to reset the VMM Application Pools identity.
- The Usage endpoint will be unable to return metered data if you specified nondefault ports for connection to your VMM instances. This is the same known issue that occurs in System Center 2012 Service Pack 1 Service Provider Foundation.
To install Update Rollup 1 for System Center 2012 Service Pack 1 Service Provider Foundation, follow these steps:
- On the Service Provider Foundation server, install the Update Rollup 1 for Service Provider Foundation package.
- Set the Application Pools identity for the Usage endpoint. To do this, follow these steps:
- Start the Internet Information Services (IIS) management console.
- Select the Usage application pool, and then select Advanced Settings.
- From the Identity list item, select the identity, and then set it to an account.
Note The account that is set for the Usage application pool will have to be added as a logon account to the SPF database and to the Operations Manager Data Warehouse databases. See the database update steps that follow.
- This account will also require permission to list all virtual machines in all instances of Virtual Machine Manager (VMM) that you have configured to use SPF. Add this account to the Administrators role in each instance of VMM.
- Specify connection strings to the Operations Manager Data Warehouse (OMDW) database, and then set up access to read from the OMDW database.
- Virtual machine usage data is collected and stored in the OMDW database. Depending on the scale of your SPF deployment, you may have multiple Operations Manager management servers that are monitoring VMM instances. You will have to specify connection strings to every OMDW database.
- Locate and open the web.config file by using Notepad from the Usage directory. By default this file is installed in the c:\inetpub\SPF\Usage directory. Locate the <connectionStrings> section in the web.config file, and add an entry for each OMDW database connection.
An example of the <connectionStrings> section with two SCOM management servers is as follows:
- On computers that are running Microsoft SQL Server where the OMDW databases reside, make sure that the Usage Application Pool account that you configured in previous step has logon rights and read permission.
- Apply the Update Rollup 1 SPF database update script. To do this, follow these steps:
- Locate the SFPUsageFeatureUpdate.sql file from the Usage directory. By default, this file is installed in the c:\inetpub\SPF\Usage\KB2875476 directory.
- Copy this file to the instance of SQL Server where the SPF database is installed, and then start SQL Server Management Studio.
- Add a logon to this instance of SQL Server by using the Usage Application Pools account that you configured in previous steps.
Grant the following permissions to the SCSPFDB for the logon account that you added. Do this unless the Usage application pool account that you specified is the same account that you specified for the VMM endpoint, as described in the Notes section. Then, move to the instance of SQL Server (click Security, and then click Logins), select the account that you have added, and include the following permissions:
Note If the application pools account that you specify for the Usage endpoint is the same account that you specified for the VMM endpoint, you have to set additional permissions for the account in the instance of SQL Server. This is true because the account that is associated with the VMM endpoint is more restricted in what it can access. Specifically, it has table-level security permissions instead of database-level permissions.
Therefore, after this update rollup is installed, you have to add table-level permissions for the following three new usage tables:
Then, add the following permissions for each table:
We recommend these permissions as best practices. The permission structure that we recommend here is the minimum set that is required. You can apply a more or less restrictive permissions scheme, depending on your security policies.
- If you are use the Service Management Portal and Service Management API with SPF to enable Infrastructure-as-a-Service scenarios, you must set up access to the SPF Usage endpoint.
- On the Service Provider Foundation server, start the Computer Management console, and then expand to view Local Users and Groups.
- The account that you will use to access the SPF Usage endpoint must belong to the Administrator group.
- The same account must be added to the SPF_Usage group.
- On the Service Management Admin site, click the VM Clouds tab. On the Quickstart page, select the Register System Center Usage Provider option. Then, enter the URL to the SPF Usage endpoint by using the credentials that you added to the SPF_Usage group.
For more information about websites, virtual machines, Service Management portals, and Service Management APIs, go to the following Microsoft website:
Uninstall instructions for App Controller
If the App Controller (KB2790935) package is uninstalled, you have to restart the following App Controller services:
- App Controller Hosted Virtual Machine Manager Provider (cmspfvmm)
- App Controller System Provider (cmsystem)
- App Controller Virtual Machine Manager Provider (cmvmm)
- App Controller Microsoft Azure Provider (cmazure)