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

To install the update for Data Protection Manager, follow these steps:

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 orderWe recommend that you install the update rollup package in the following 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.

Notes

• 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 informationTo download the update rollup package and extract the files that are contained in the update rollup package, follow these steps:

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

For information about how to import a management pack from a disk, go to the following Microsoft TechNet website:

How to Import an Operations Manager Management PackNote 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

Uninstall informationTo uninstall an update, run the following command:

msiexec /uninstall PatchCodeGuid /package RTMProductCodeGuidNote In this command, the placeholder RTMProductCodeGuid represents one of the following GUIDs.

Component	RTMProductCodeGuid
Server	{8070C91C-7D7C-4DAD-88B1-0966EEA9A8FE}
Console (AMD64)	{5142AB0B-73E3-4AD3-9D0F-65B3D9026769}
Console (x86)	{358C8AF0-25BB-425A-A4E6-7ADE54ED4736}
Reporting	{A2D27C0E-181D-4955-B95D-D3FB651E6AF7}
WebConsole (AMD64)	{5ED945BA-2BDD-4567-804E-8D3D2DB5CC9B}
ACS	{770A7E3C-8574-4769-8D92-9ADED98C0777}
Agent (AMD64)	{8B21425D-02F3-4B80-88CE-8F79B320D330}
Agent (x86)	{387306D9-78CE-4E0E-B952-28A50CC8B3EE}
Agent (IA-64)	{F3DDB021-89BC-464F-9107-69E2547D08FD}
Gateway	{80C2A57A-4193-4800-AA27-CD79553FE9DF}
SCX-ACS (AMD64)	{B30F4F71-2AF3-4542-855B-E1C7A31AC9A5}
SCX-ACS (x86)	{B30F4F71-2AF3-4542-855B-E1C7A31AC9A5}

Additionally, the placeholder PatchCodeGuid represents one of the following GUIDs.

PatchCodeGuid	Component	CPU	Local
{94507D95-B735-48EE-B846-BFC7A0517C86}	Agent	AMD64	EN
{498BB1A1-F078-4455-A1D8-311A8AF33531}	Server	AMD64	EN
{A8887D87-0810-49D1-9AF1-645DD4BF82CC}	Gateway	AMD64	EN
{869C94D0-6701-4A5D-8289-278DBF3B7BB0}	WebConsole	AMD64	EN
{9917D98F-A39B-4EEC-8D6B-428EDEDDFF5A}	Agent	IA-64	EN
{684570C2-1470-4C7D-98CB-96EE8E8644F2}	Agent	x86	EN
{D0B4D96E-D045-4FD9-8813-D72466A10FE2}	WebConsole	AMD64	CN
{2BE683F8-98A8-4CDF-810F-2251C75B6D7E}	WebConsole	AMD64	CS
{1A5A2A56-7E4F-49F3-AB2F-828133423796}	WebConsole	AMD64	DE
{5A609F86-F3F3-432B-8BE5-D5E02C9D0487}	WebConsole	AMD64	ES
{9034EF70-5C23-47F1-A284-EF531A0F4AFB}	WebConsole	AMD64	FR
{85C7A3FB-9C4F-4B74-901E-E07ECBFFEFC5}	WebConsole	AMD64	HU
{AFDFC8EC-F7A9-4F73-995E-6A74CD0FD045}	WebConsole	AMD64	IT
{2E6017D8-68F7-4A87-8B45-D712748691FC}	WebConsole	AMD64	JA
{E8685F8C-90F4-4FED-A49E-E3F1678CADC2}	WebConsole	AMD64	KO
{B30464F5-85CC-4416-9F49-E0E041A67FB7}	WebConsole	AMD64	NL
{552AD353-C75E-4C4F-BC53-890FE8C99F3D}	WebConsole	AMD64	PL
{995CF39A-160D-44D4-9DAB-40B53093D7B0}	WebConsole	AMD64	PT-BR
{421F2011-D239-4280-A509-1A0937654BF2}	WebConsole	AMD64	PT-PT
{E277AA19-7641-4760-8230-A95DD1BB7404}	WebConsole	AMD64	RU
{0D2A9F5C-6A7B-494E-A193-0F3B1964D0C2}	WebConsole	AMD64	SV
{A4DD746E-8977-48B0-9341-975040083EFA}	WebConsole	AMD64	TR
{D6DFEBCC-6E86-40DA-89F4-B1DB03C8EC89}	WebConsole	AMD64	TW
{8083D6AD-FD12-4049-83A4-A5250E606942}	WebConsole	AMD64	ZH-ZK

To install the updated monitoring packs and agents for UNIX and Linux operating systems, follow these steps:

1. Download the updated management packs from the following Microsoft website:

   System Center Monitoring Pack for UNIX and Linux Operating Systems

2. Install the management pack update package to extract the management pack files.

3. 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

4. Import the updated management pack for each version of Linux or UNIX that you monitor in your environment.

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:

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

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)

Files that are changed	File size	Version
Microsoft.SystemCenter.CloudManager.Providers.Vmm.exe	499,344	1.0.1601.0
Microsoft.SystemCenter.CloudManager.Providers.Azure.exe	750,736	1.0.1601.0

Files that are changed	File size	Version
AMTE.dll	283,000	4.1.3322.0
CPWrapper.dll	1,104,000	4.1.3322.0
Dpmac.exe	2,063,000	4.1.3322.0
DPMRA.exe	6,264,000	4.1.3322.0
MsdpmDll.dll	544,000	4.1.3322.0
Utils.dll	1,195,000	4.1.3322.0
Inspect.dll	167,000	4.1.3322.0

Files that are changed	File size	Version
Microsoft.Mom.Modules.ClientMonitoring.dll	458,752	7.0.9538.1005
Microsoft.EnterpriseManagement.Modules.PowerShell.dll	90,112	7.0.9538.1005
Microsoft.EnterpriseManagement.Modules.Apm.AlertAttachment.ComponentTasks.dll	40,960	7.0.9538.1005
Microsoft.EnterpriseManagement.OperationsManager.Apm.Instrumentation.dll	520,192	7.0.9538.1005
Microsoft.EnterpriseManagement.Core.dll	4,046,848	7.0.9538.1003

Files that are changed	File size	Version
Web.config	941	Not applicable
Global.asax	142	Not applicable
Newtonsoft.Json.dll	368,128	4.5.1.14720
System.Net.Http.Formatting.dll	159,328	4.0.20505.0
System.Web.Http.dll	360,032	4.0.20505.0
System.Web.Http.WebHost.dll	65,632	4.0.20505.0
Microsoft.SystemCenter.Foundation.Usage.dll	24,232	7.1.3226.0
Microsoft.SystemCenter.Foundation.Billing.dll	62,608	7.1.3226.0
Microsoft.SystemCenter.Foundation.EndpointCommon.dll	46,224	7.1.3226.0
Microsoft.SystemCenter.Foundation.SpfDbApi.dll	95,912	7.1.3226.0
Microsoft.SystemCenter.Foundation.SPFData.dll	55,440	7.1.3226.0
Microsoft.SystemCenter.Foundation.Common.dll	39,568	7.1.3226.0
Microsoft.SystemCenter.Foundation.Cmdlet.dll	197,264	7.1.3226.0
Microsoft.SystemCenter.Foundation.ETW.dll	169,104	7.1.3226.0
Microsoft.SystemCenter.Foundation.dll	55,440	7.1.3226.0
Microsoft.IdentityModel.dll	1,103,256	6.1.7600.16394
EntityFramework.dll	1,060,640	4.3.20217.0
System.Net.Http.dll	181,856	1.0.0.0
addNewUserToUsageGroups.bat	65	Not applicable
SPFUsageFeatureUpdate.sql	5,251	Not applicable
Supplemental Notices for SC 2012 SP1 - Orchestrator Update Rollup 1.docx	25,863	Not applicable
OnEndCreateSession.ps1	18,720	Not applicable

Files that are changed	File size	Version	Language ID
Engine.Deployment.dll	547,008	3.1.6018.0	Not applicable
Errors.dll	3,848,376	3.1.6018.0	Not applicable
Errors.resources.dll	1,326,248	3.1.6018.0	2052
Errors.resources.dll	1,648,296	3.1.6018.0	1036
Errors.resources.dll	1,676,456	3.1.6018.0	1031
Errors.resources.dll	1,555,112	3.1.6018.0	1040
Errors.resources.dll	1,844,392	3.1.6018.0	1041
Errors.resources.dll	1,562,280	3.1.6018.0	1046
Errors.resources.dll	2,207,936	3.1.6018.0	1049
Errors.resources.dll	1,604,776	3.1.6018.0	3082
Errors.resources.dll	1,344,704	3.1.6018.0	1028
Errors.resources.dll	1,636,016	3.1.6018.0	1042
Errors.resources.dll	1,344,680	3.1.6018.0	3076
Errors.resources.dll	1,557,672	3.1.6018.0	1029
Errors.resources.dll	1,526,976	3.1.6018.0	1043
Errors.resources.dll	1,687,720	3.1.6018.0	1038
Errors.resources.dll	1,611,968	3.1.6018.0	1045
Errors.resources.dll	1,580,736	3.1.6018.0	2070
Errors.resources.dll	1,494,696	3.1.6018.0	1053
Errors.resources.dll	1,513,640	3.1.6018.0	1055
ImgLibEngine.dll	3,142,848	3.1.6018.0	Not applicable
Microsoft.SystemCenter.VirtualMachineManager.dll	1,796,264	3.1.6018.0	Not applicable
Microsoft.SystemCenter.VirtualMachineManger.PowerShell.CmdletWrappers.dll	1,494,696	3.1.6018.0	Not applicable
Microsoft.VirtualManager.UI.AddIns.Management.dll	96,424	3.1.6018.0	Not applicable
Microsoft.VirtualManager.UI.Pages.Settings.dll	168,104	3.1.6018.0	Not applicable
Microsoft.VirtualManager.UI.VMWizards.dll	213,160	3.1.6018.0	Not applicable
Microsoft.VirtualManager.UI.VMWizards.resources.dll	65,728	3.1.6018.0	2052
Microsoft.VirtualManager.UI.VMWizards.resources.dll	67,752	3.1.6018.0	1036
Microsoft.VirtualManager.UI.VMWizards.resources.dll	67,264	3.1.6018.0	1031
Microsoft.VirtualManager.UI.VMWizards.resources.dll	67,776	3.1.6018.0	1040
Microsoft.VirtualManager.UI.VMWizards.resources.dll	68,288	3.1.6018.0	1041
Microsoft.VirtualManager.UI.VMWizards.resources.dll	67,264	3.1.6018.0	1046
Microsoft.VirtualManager.UI.VMWizards.resources.dll	71,352	3.1.6018.0	1049
Microsoft.VirtualManager.UI.VMWizards.resources.dll	672,40	3.1.6018.0	3082
Microsoft.VirtualManager.UI.VMWizards.resources.dll	65,704	3.1.6018.0	1028
Microsoft.VirtualManager.UI.VMWizards.resources.dll	67,240	3.1.6018.0	1042
Microsoft.VirtualManager.UI.VMWizards.resources.dll	65,704	3.1.6018.0	3076
Microsoft.VirtualManager.UI.VMWizards.resources.dll	67,776	3.1.6018.0	1029
Microsoft.VirtualManager.UI.VMWizards.resources.dll	67,240	3.1.6018.0	1043
Microsoft.VirtualManager.UI.VMWizards.resources.dll	67,776	3.1.6018.0	1038
Microsoft.VirtualManager.UI.VMWizards.resources.dll	67,240	3.1.6018.0	1045
Microsoft.VirtualManager.UI.VMWizards.resources.dll	67,240	3.1.6018.0	2070
Microsoft.VirtualManager.UI.VMWizards.resources.dll	66,728	3.1.6018.0	1053
Microsoft.VirtualManager.UI.VMWizards.resources.dll	66,752	3.1.6018.0	1055
Remoting.dll	832,168	3.1.6018.0	Not applicable
Supplemental Notices for SC 2012 SP1 - Virtual Machine Manager Update Rollup 1.rtf	141,687	Not applicable	Not applicable
Utils.dll	751,288	3.1.6018.0	Not applicable
VirtualizationInterfaces.dll	86,696	3.1.6018.0	Not applicable
VMWareImplementation.dll	2,051,752	3.1.6018.0	Not applicable
VSImplementation.dll	99,496	3.1.6018.0	Not applicable
WSManAutomation.dll	34,984	3.1.6018.0	Not applicable
WsManWrappers.dll	3,208,896	3.1.6018.0	Not applicable

Files that are changed	File size	Version	Language ID
Engine.Deployment.dll	546,984	3.1.6018.0	Not applicable
Errors.dll	3,848,376	3.1.6018.0	Not applicable
Errors.resources.dll	1,326,248	3.1.6018.0	2052
Errors.resources.dll	1,648,320	3.1.6018.0	1036
Errors.resources.dll	1,676,456	3.1.6018.0	1031
Errors.resources.dll	1,555,112	3.1.6018.0	1040
Errors.resources.dll	1,844,416	3.1.6018.0	1041
Errors.resources.dll	1,562,280	3.1.6018.0	1046
Errors.resources.dll	2,207,912	3.1.6018.0	1049
Errors.resources.dll	1,604,800	3.1.6018.0	3082
Errors.resources.dll	1,344,680	3.1.6018.0	1028
Errors.resources.dll	1,636,032	3.1.6018.0	1042
Errors.resources.dll	1,344,680	3.1.6018.0	3076
Errors.resources.dll	1,557,688	3.1.6018.0	1029
Errors.resources.dll	1,526,968	3.1.6018.0	1043
Errors.resources.dll	1,687,744	3.1.6018.0	1038
Errors.resources.dll	1,611,944	3.1.6018.0	1045
Errors.resources.dll	1,580,712	3.1.6018.0	2070
Errors.resources.dll	1,494,696	3.1.6018.0	1053
Errors.resources.dll	1,513,664	3.1.6018.0	1055
ImgLibEngine.dll	3,142,824	3.1.6018.0	Not applicable
Microsoft.SystemCenter.VirtualMachineManager.dll	1,796,264	3.1.6018.0	Not applicable
Microsoft.SystemCenter.VirtualMachineManger.PowerShell.CmdletWrappers.dll	1,494,720	3.1.6018.0	Not applicable
Microsoft.VirtualManager.UI.AddIns.Management.dll	96,424	3.1.6018.0	Not applicable
Microsoft.VirtualManager.UI.Pages.Settings.dll	168,128	3.1.6018.0	Not applicable
Microsoft.VirtualManager.UI.VMWizards.dll	213,160	3.1.6018.0	Not applicable
Microsoft.VirtualManager.UI.VMWizards.resources.dll	65,720	3.1.6018.0	2052
Microsoft.VirtualManager.UI.VMWizards.resources.dll	67,776	3.1.6018.0	1036
Microsoft.VirtualManager.UI.VMWizards.resources.dll	67,264	3.1.6018.0	1031
Microsoft.VirtualManager.UI.VMWizards.resources.dll	67,776	3.1.6018.0	1040
Microsoft.VirtualManager.UI.VMWizards.resources.dll	68,264	3.1.6018.0	1041
Microsoft.VirtualManager.UI.VMWizards.resources.dll	67,264	3.1.6018.0	1046
Microsoft.VirtualManager.UI.VMWizards.resources.dll	71,336	3.1.6018.0	1049
Microsoft.VirtualManager.UI.VMWizards.resources.dll	67,240	3.1.6018.0	3082
Microsoft.VirtualManager.UI.VMWizards.resources.dll	65,704	3.1.6018.0	1028
Microsoft.VirtualManager.UI.VMWizards.resources.dll	67,240	3.1.6018.0	1042
Microsoft.VirtualManager.UI.VMWizards.resources.dll	65,704	3.1.6018.0	3076
Microsoft.VirtualManager.UI.VMWizards.resources.dll	67,752	3.1.6018.0	1029
Microsoft.VirtualManager.UI.VMWizards.resources.dll	67,240	3.1.6018.0	1043
Microsoft.VirtualManager.UI.VMWizards.resources.dll	67,752	3.1.6018.0	1038
Microsoft.VirtualManager.UI.VMWizards.resources.dll	67,264	3.1.6018.0	1045
Microsoft.VirtualManager.UI.VMWizards.resources.dll	67,240	3.1.6018.0	2070
Microsoft.VirtualManager.UI.VMWizards.resources.dll	66,728	3.1.6018.0	1053
Microsoft.VirtualManager.UI.VMWizards.resources.dll	66,728	3.1.6018.0	1055
Remoting.dll	832,184	3.1.6018.0	Not applicable
Supplemental Notices for SC 2012 SP1 - Virtual Machine Manager Update Rollup 1.rtf	141,687	Not applicable	Not applicable
Utils.dll	751,296	3.1.6018.0	Not applicable
VirtualizationInterfaces.dll	86,696	3.1.6018.0	Not applicable
VMWareImplementation.dll	2,051,752	3.1.6018.0	Not applicable
VSImplementation.dll	99,520	3.1.6018.0	Not applicable
WSManAutomation.dll	35,008	3.1.6018.0	Not applicable
WsManWrappers.dll	3,208,896	3.1.6018.0	Not applicable

Files that are changed	File size	Version	Language ID
Engine.Adhc.Operations.dll	1,064,616	3.1.6018.0	Not applicable
Engine.Deployment.dll	546,984	3.1.6018.0	Not applicable
Engine.Placement.ResourceModel.dll	306,856	3.1.6018.0	Not applicable
Engine.VmOperations.dll	1,134,248	3.1.6018.0	Not applicable
Errors.dll	3,848,376	3.1.6018.0	Not applicable
Errors.resources.dll	132,6248	3.1.6018.0	2052
Errors.resources.dll	1,648,320	3.1.6018.0	1036
Errors.resources.dll	1,676,456	3.1.6018.0	1031
Errors.resources.dll	1,555,112	3.1.6018.0	1040
Errors.resources.dll	1,844,416	3.1.6018.0	1041
Errors.resources.dll	1,562,280	3.1.6018.0	1046
Errors.resources.dll	2,207,912	3.1.6018.0	1049
Errors.resources.dll	1,604,800	3.1.6018.0	3082
Errors.resources.dll	1,344,680	3.1.6018.0	1028
Errors.resources.dll	1,636,032	3.1.6018.0	1042
Errors.resources.dll	1,344,680	3.1.6018.0	3076
Errors.resources.dll	1,557,688	3.1.6018.0	1029
Errors.resources.dll	1,526,968	3.1.6018.0	1043
Errors.resources.dll	1,687,744	3.1.6018.0	1038
Errors.resources.dll	1,611,944	3.1.6018.0	1045
Errors.resources.dll	1,580,712	3.1.6018.0	2070
Errors.resources.dll	1,494,696	3.1.6018.0	1053
Errors.resources.dll	1,513,664	3.1.6018.0	1055
ImgLibEngine.dll	3,142,824	3.1.6018.0	Not applicable
Remoting.dll	832,184	3.1.6018.0	Not applicable
Supplemental Notices for SC 2012 SP1 - Virtual Machine Manager Update Rollup 1.rtf	141,687	Not applicable	Not applicable
Utils.dll	751,296	3.1.6018.0	Not applicable
ViridianImplementation.dll	218,792	3.1.6018.0	Not applicable
ViridianImplementationV2.dll	359,616	3.1.6018.0	Not applicable
VirtualizationInterfaces.dll	86,696	3.1.6018.0	Not applicable
VMWareImplementation.dll	2,051,752	3.1.6018.0	Not applicable
VSImplementation.dll	99,520	3.1.6018.0	Not applicable
WSManAutomation.dll	35,008	3.1.6018.0	Not applicable
WsManMIWrappers.dll	133,824	3.1.6018.0	Not applicable
WsManWrappers.dll	3,208,896	3.1.6018.0	Not applicable
XenImplementation.dll	173,248	3.1.6018.0	Not applicable