Description of Update Rollup 1 for System Center 2012 Service Pack 1

1. Before you install this update, make a backup of the DPM database.
2. 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.
   
3. 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
   1. Open the DPM Administrator Console.
   2. Click the Management tab, and then click the Agents tab.
   3. In the Protected Computer list, select a computer, and then click Update on the Action pane.
   4. 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
   1. 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.
      
   2. Run the appropriate DPMAgentInstaller.exe package on each protected computer, based on the architecture of the Agent.
   3. Open the DPM Administrator Console on the System Center 2012 Service Pack 1 - Data Protection Manager server.
   4. Click the Management tab, and then click the Agents tab.
   5. Select the protected computers, update the information, and then verify that the agent version is listed as 4.1.3322.0.

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

Installation notes

• 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:
  911722 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

1. 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
2. Manually import the management packs.
3. 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.

Installation information

1. 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.
2. 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.
   
   
3. Import the following management pack:
   • Microsoft.SystemCenter.AlertAttachment.mpb

Uninstall information

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.

1. On the Service Provider Foundation server, install the Update Rollup 1 for Service Provider Foundation package.
2. Set the Application Pools identity for the Usage endpoint. To do this, follow these steps:
   1. Start the Internet Information Services (IIS) management console.
   2. Select the Usage application pool, and then select Advanced Settings.
   3. 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.
3. 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.
4. Specify connection strings to the Operations Manager Data Warehouse (OMDW) database, and then set up access to read from the OMDW database.
   1. 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.
   2. 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:
      <connectionStrings>
      <add name=”OMDWConnectionString1”
      connectionString=”Server=[server name]”;
      Database=[databasename];
      Trusted_Connection=True;
      MultipleActiveResultSets=True;”/>
      <add name=”OMDWConnectionString2”
      connectionString=”Server=[server name]”;
      Database=[databasename];
      Trusted_Connection=True;
      MultipleActiveResultSets=True;”/>
      </connectionStrings>
5. 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.
6. Apply the Update Rollup 1 SPF database update script. To do this, follow these steps:
   1. Locate the SFPUsageFeatureUpdate.sql file from the Usage directory. By default, this file is installed in the c:\inetpub\SPF\Usage\KB2875476 directory.
   2. Copy this file to the instance of SQL Server where the SPF database is installed, and then start SQL Server Management Studio.
   3. 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:
      • Connect
      • Delete
      • Insert
      • Select
      • Update
      
      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:
      • OnPremServicesCollectorSessions
      • OnPremServicesSubscriberWatermarks
      • OnPremServicesSubscriberTombstones
      
      Then, add the following permissions for each table:
      • Delete
      • Select
      • Insert
      • Update
      
      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.
      
      
   4. 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.
   5. On the Service Provider Foundation server, start the Computer Management console, and then expand to view Local Users and Groups.
   6. The account that you will use to access the SPF Usage endpoint must belong to the Administrator group.
   7. The same account must be added to the SPF_Usage group.
7. 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:
   Microsoft Hosting Solutions Services