DetailPage-MSS-KB

Microsoft small business knowledge base

Article ID: 2785682 - Last Review: June 20, 2014 - Revision: 10.0

On This Page

Introduction

This article describes the installation instructions for Update Rollup 1 for Microsoft System Center 2012 Service Pack 1 and the issues that are fixed in the update rollup.

To download and install the update packages for System Center 2012 Service Pack 1, follow the installation instructions.

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

The OperatingSystemId 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

Issue 4

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:
  1. Locate the following folder:

    C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin

  2. Right-click the AddInPipeline folder, and then click Properties.
  3. On the Security tab, click Advanced, and then click Continue.
  4. Select the BUILTIN group, and then click Edit.
  5. Click the Select a principal link, type Authenticated Users, and then click OK.
  6. Click OK to close each dialog box that is associated with the properties.

How to obtain and install Update Rollup 1 for System Center 2012 Service Pack 1

The update packages for App Controller, Data Protection Manager, Operations Manager, Service Provider Foundation, and Virtual Machine Manager are available from Microsoft Update.

The UNIX and Linux Monitoring Pack update for Operations Manager is available from the following Microsoft Download Center website:
http://www.microsoft.com/download/details.aspx?id=29696 (http://www.microsoft.com/download/details.aspx?id=29696)

  • To obtain and install the update packages from Microsoft Update, follow these steps on a system that has an applicable System Center 2012 component installed:
    1. Click Start, and then click Control Panel.
    2. In Control Panel, double-click Windows Update.
    3. In the Windows Update window, click Check Online for updates from Microsoft Update.
    4. Click Important updates are available.
    5. Select the Update Rollup 1 packages that you want to install, and then click OK.
    6. Click Install updates to install the selected update packages.

  • To manually download the update packages from Microsoft Update Catalog, go to the following Microsoft websites:

    App Controller (KB2790935)
    Collapse this imageExpand this image
    Download
    Download the update package now. (http://catalog.update.microsoft.com/v7/site/Search.aspx?q=2790935)
    Data Protection Manager (KB2802095)
    Collapse this imageExpand this image
    Download
    Download the update package now. (http://catalog.update.microsoft.com/v7/site/Search.aspx?q=2802095)
    Operations Manager (KB2784734)
    Collapse this imageExpand this image
    Download
    Download the update package now. (http://catalog.update.microsoft.com/v7/site/Search.aspx?q=2784734)
    Service Provider Foundation (KB2785476)
    Collapse this imageExpand this image
    Download
    Download the update package now. (http://catalog.update.microsoft.com/v7/site/Search.aspx?q=2785476)
    Virtual Machine Manager (KB2792925 - Console, KB2792926 – VMM Server)
    Collapse this imageExpand this image
    Download
    Download the Console update package now. (http://catalog.update.microsoft.com/v7/site/Search.aspx?q=2792925)
    Collapse this imageExpand this image
    Download
    Download the VMM Server update package now. (http://catalog.update.microsoft.com/v7/site/Search.aspx?q=2792926)

    To manually install the update packages, run the following command from an elevated command prompt:
    msiexec.exe /update packagename
    For example, to install the Virtual Machine Manager Server Update (KB2792926), run the following command:
    msiexec.exe /update KB2792926-AMD64-Server.msp

Installation instructions

Installation instructions for Data Protection Manager

Collapse this imageExpand this image
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.
Collapse this imageExpand this image

Installation instructions for Operations Manager

Collapse this imageExpand this image
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  (http://support.microsoft.com/kb/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
We 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 information
To 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 Pack (http://technet.microsoft.com/en-us/library/hh212691.aspx)
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
Uninstall information
To uninstall an update, run the following command:
msiexec /uninstall PatchCodeGuid /package RTMProductCodeGuid
Note In this command, the placeholder RTMProductCodeGuid represents one of the following GUIDs.

Collapse this tableExpand this table
ComponentRTMProductCodeGuid
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.

Collapse this tableExpand this table
PatchCodeGuidComponentCPULocal
{94507D95-B735-48EE-B846-BFC7A0517C86}AgentAMD64EN
{498BB1A1-F078-4455-A1D8-311A8AF33531}ServerAMD64EN
{A8887D87-0810-49D1-9AF1-645DD4BF82CC}GatewayAMD64EN
{869C94D0-6701-4A5D-8289-278DBF3B7BB0}WebConsoleAMD64EN
{9917D98F-A39B-4EEC-8D6B-428EDEDDFF5A}AgentIA-64EN
{684570C2-1470-4C7D-98CB-96EE8E8644F2}Agentx86EN
{D0B4D96E-D045-4FD9-8813-D72466A10FE2}WebConsoleAMD64CN
{2BE683F8-98A8-4CDF-810F-2251C75B6D7E}WebConsoleAMD64CS
{1A5A2A56-7E4F-49F3-AB2F-828133423796}WebConsoleAMD64DE
{5A609F86-F3F3-432B-8BE5-D5E02C9D0487}WebConsoleAMD64ES
{9034EF70-5C23-47F1-A284-EF531A0F4AFB}WebConsoleAMD64FR
{85C7A3FB-9C4F-4B74-901E-E07ECBFFEFC5}WebConsoleAMD64HU
{AFDFC8EC-F7A9-4F73-995E-6A74CD0FD045}WebConsoleAMD64IT
{2E6017D8-68F7-4A87-8B45-D712748691FC}WebConsoleAMD64JA
{E8685F8C-90F4-4FED-A49E-E3F1678CADC2}WebConsoleAMD64KO
{B30464F5-85CC-4416-9F49-E0E041A67FB7}WebConsoleAMD64NL
{552AD353-C75E-4C4F-BC53-890FE8C99F3D}WebConsoleAMD64PL
{995CF39A-160D-44D4-9DAB-40B53093D7B0}WebConsoleAMD64PT-BR
{421F2011-D239-4280-A509-1A0937654BF2}WebConsoleAMD64PT-PT
{E277AA19-7641-4760-8230-A95DD1BB7404}WebConsoleAMD64RU
{0D2A9F5C-6A7B-494E-A193-0F3B1964D0C2}WebConsoleAMD64SV
{A4DD746E-8977-48B0-9341-975040083EFA}WebConsoleAMD64TR
{D6DFEBCC-6E86-40DA-89F4-B1DB03C8EC89}WebConsoleAMD64TW
{8083D6AD-FD12-4049-83A4-A5250E606942}WebConsoleAMD64ZH-ZK


Collapse this imageExpand this image

Installation instructions for Operations Manager UNIX and Linux monitoring packs and agents

Collapse this imageExpand this image
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 (http://www.microsoft.com/en-us/download/details.aspx?id=29696)
  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.

Collapse this imageExpand this image

Installation instructions for Service Provider Foundation

Collapse this imageExpand this image
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 (http://www.microsoft.com/hosting/en/us/services.aspx)

Collapse this imageExpand this image

Uninstall instructions for App Controller

Collapse this imageExpand this image
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)

Collapse this imageExpand this image

File information

The following files are updated in Update Rollup 1 for System Center 2012 Service Pack 1.
App Controller Update (KB2790935)
Collapse this imageExpand this image
Collapse this tableExpand this table
Files that are changedFile sizeVersion
Microsoft.SystemCenter.CloudManager.Providers.Vmm.exe499,3441.0.1601.0
Microsoft.SystemCenter.CloudManager.Providers.Azure.exe750,7361.0.1601.0

Collapse this imageExpand this image
Data Protection Manager Update (KB2802095)
Collapse this imageExpand this image
Collapse this tableExpand this table
Files that are changedFile sizeVersion
AMTE.dll283,0004.1.3322.0
CPWrapper.dll1,104,0004.1.3322.0
Dpmac.exe2,063,0004.1.3322.0
DPMRA.exe6,264,0004.1.3322.0
MsdpmDll.dll544,0004.1.3322.0
Utils.dll1,195,0004.1.3322.0
Inspect.dll167,0004.1.3322.0

Collapse this imageExpand this image
Operations Manager Update (KB2784734)
Collapse this imageExpand this image
Collapse this tableExpand this table
Files that are changedFile sizeVersion
Microsoft.Mom.Modules.ClientMonitoring.dll458,752 7.0.9538.1005
Microsoft.EnterpriseManagement.Modules.PowerShell.dll90,1127.0.9538.1005
Microsoft.EnterpriseManagement.Modules.Apm.AlertAttachment.ComponentTasks.dll 40,960 7.0.9538.1005
Microsoft.EnterpriseManagement.OperationsManager.Apm.Instrumentation.dll520,1927.0.9538.1005
Microsoft.EnterpriseManagement.Core.dll4,046,8487.0.9538.1003

Collapse this imageExpand this image
Service Provider Foundation Update (KB2785476)
Collapse this imageExpand this image
Collapse this tableExpand this table
Files that are changedFile sizeVersion
Web.config941Not applicable
Global.asax142Not applicable
Newtonsoft.Json.dll368,1284.5.1.14720
System.Net.Http.Formatting.dll159,3284.0.20505.0
System.Web.Http.dll360,0324.0.20505.0
System.Web.Http.WebHost.dll65,6324.0.20505.0
Microsoft.SystemCenter.Foundation.Usage.dll24,2327.1.3226.0
Microsoft.SystemCenter.Foundation.Billing.dll62,6087.1.3226.0
Microsoft.SystemCenter.Foundation.EndpointCommon.dll46,2247.1.3226.0
Microsoft.SystemCenter.Foundation.SpfDbApi.dll95,9127.1.3226.0
Microsoft.SystemCenter.Foundation.SPFData.dll55,4407.1.3226.0
Microsoft.SystemCenter.Foundation.Common.dll39,5687.1.3226.0
Microsoft.SystemCenter.Foundation.Cmdlet.dll197,2647.1.3226.0
Microsoft.SystemCenter.Foundation.ETW.dll169,1047.1.3226.0
Microsoft.SystemCenter.Foundation.dll55,4407.1.3226.0
Microsoft.IdentityModel.dll1,103,2566.1.7600.16394
EntityFramework.dll1,060,6404.3.20217.0
System.Net.Http.dll181,8561.0.0.0
addNewUserToUsageGroups.bat65Not applicable
SPFUsageFeatureUpdate.sql5,251Not applicable
Supplemental Notices for SC 2012 SP1 - Orchestrator Update Rollup 1.docx25,863Not applicable
OnEndCreateSession.ps118,720Not applicable

Collapse this imageExpand this image
Virtual Machine Manager - Console Update (KB2792925-x86)
Collapse this imageExpand this image

Collapse this tableExpand this table
Files that are changedFile sizeVersionLanguage ID
Engine.Deployment.dll547,0083.1.6018.0Not applicable
Errors.dll3,848,3763.1.6018.0Not applicable
Errors.resources.dll1,326,2483.1.6018.02052
Errors.resources.dll1,648,2963.1.6018.01036
Errors.resources.dll1,676,4563.1.6018.01031
Errors.resources.dll1,555,1123.1.6018.01040
Errors.resources.dll1,844,3923.1.6018.01041
Errors.resources.dll1,562,2803.1.6018.01046
Errors.resources.dll2,207,9363.1.6018.01049
Errors.resources.dll1,604,7763.1.6018.03082
Errors.resources.dll1,344,7043.1.6018.01028
Errors.resources.dll1,636,0163.1.6018.01042
Errors.resources.dll1,344,6803.1.6018.03076
Errors.resources.dll1,557,6723.1.6018.01029
Errors.resources.dll1,526,9763.1.6018.01043
Errors.resources.dll1,687,7203.1.6018.01038
Errors.resources.dll1,611,9683.1.6018.01045
Errors.resources.dll1,580,7363.1.6018.02070
Errors.resources.dll1,494,6963.1.6018.01053
Errors.resources.dll1,513,6403.1.6018.01055
ImgLibEngine.dll3,142,8483.1.6018.0Not applicable
Microsoft.SystemCenter.VirtualMachineManager.dll1,796,2643.1.6018.0Not applicable
Microsoft.SystemCenter.VirtualMachineManger.PowerShell.CmdletWrappers.dll1,494,6963.1.6018.0Not applicable
Microsoft.VirtualManager.UI.AddIns.Management.dll96,4243.1.6018.0Not applicable
Microsoft.VirtualManager.UI.Pages.Settings.dll168,1043.1.6018.0Not applicable
Microsoft.VirtualManager.UI.VMWizards.dll213,1603.1.6018.0Not applicable
Microsoft.VirtualManager.UI.VMWizards.resources.dll65,7283.1.6018.02052
Microsoft.VirtualManager.UI.VMWizards.resources.dll67,7523.1.6018.01036
Microsoft.VirtualManager.UI.VMWizards.resources.dll67,2643.1.6018.01031
Microsoft.VirtualManager.UI.VMWizards.resources.dll67,7763.1.6018.01040
Microsoft.VirtualManager.UI.VMWizards.resources.dll68,2883.1.6018.01041
Microsoft.VirtualManager.UI.VMWizards.resources.dll67,2643.1.6018.01046
Microsoft.VirtualManager.UI.VMWizards.resources.dll71,3523.1.6018.01049
Microsoft.VirtualManager.UI.VMWizards.resources.dll672,403.1.6018.03082
Microsoft.VirtualManager.UI.VMWizards.resources.dll65,7043.1.6018.01028
Microsoft.VirtualManager.UI.VMWizards.resources.dll67,2403.1.6018.01042
Microsoft.VirtualManager.UI.VMWizards.resources.dll65,7043.1.6018.03076
Microsoft.VirtualManager.UI.VMWizards.resources.dll67,7763.1.6018.01029
Microsoft.VirtualManager.UI.VMWizards.resources.dll67,2403.1.6018.01043
Microsoft.VirtualManager.UI.VMWizards.resources.dll67,7763.1.6018.01038
Microsoft.VirtualManager.UI.VMWizards.resources.dll67,2403.1.6018.01045
Microsoft.VirtualManager.UI.VMWizards.resources.dll67,2403.1.6018.02070
Microsoft.VirtualManager.UI.VMWizards.resources.dll66,7283.1.6018.01053
Microsoft.VirtualManager.UI.VMWizards.resources.dll66,7523.1.6018.01055
Remoting.dll832,1683.1.6018.0Not applicable
Supplemental Notices for SC 2012 SP1 - Virtual Machine Manager Update Rollup 1.rtf141,687Not applicableNot applicable
Utils.dll751,2883.1.6018.0Not applicable
VirtualizationInterfaces.dll86,6963.1.6018.0Not applicable
VMWareImplementation.dll2,051,7523.1.6018.0Not applicable
VSImplementation.dll99,4963.1.6018.0Not applicable
WSManAutomation.dll34,9843.1.6018.0Not applicable
WsManWrappers.dll3,208,8963.1.6018.0Not applicable


Collapse this imageExpand this image
Virtual Machine Manager - Console Update (KB2792925-x64)
Collapse this imageExpand this image


Collapse this tableExpand this table
Files that are changedFile sizeVersionLanguage ID
Engine.Deployment.dll546,9843.1.6018.0Not applicable
Errors.dll3,848,3763.1.6018.0Not applicable
Errors.resources.dll1,326,2483.1.6018.02052
Errors.resources.dll1,648,3203.1.6018.01036
Errors.resources.dll1,676,4563.1.6018.01031
Errors.resources.dll1,555,1123.1.6018.01040
Errors.resources.dll1,844,4163.1.6018.01041
Errors.resources.dll1,562,2803.1.6018.01046
Errors.resources.dll2,207,9123.1.6018.01049
Errors.resources.dll1,604,8003.1.6018.03082
Errors.resources.dll1,344,6803.1.6018.01028
Errors.resources.dll1,636,0323.1.6018.01042
Errors.resources.dll1,344,6803.1.6018.03076
Errors.resources.dll1,557,6883.1.6018.01029
Errors.resources.dll1,526,9683.1.6018.01043
Errors.resources.dll1,687,7443.1.6018.01038
Errors.resources.dll1,611,9443.1.6018.01045
Errors.resources.dll1,580,7123.1.6018.02070
Errors.resources.dll1,494,6963.1.6018.01053
Errors.resources.dll1,513,6643.1.6018.01055
ImgLibEngine.dll3,142,8243.1.6018.0Not applicable
Microsoft.SystemCenter.VirtualMachineManager.dll1,796,2643.1.6018.0Not applicable
Microsoft.SystemCenter.VirtualMachineManger.PowerShell.CmdletWrappers.dll1,494,7203.1.6018.0Not applicable
Microsoft.VirtualManager.UI.AddIns.Management.dll96,4243.1.6018.0Not applicable
Microsoft.VirtualManager.UI.Pages.Settings.dll168,1283.1.6018.0Not applicable
Microsoft.VirtualManager.UI.VMWizards.dll213,1603.1.6018.0Not applicable
Microsoft.VirtualManager.UI.VMWizards.resources.dll65,7203.1.6018.02052
Microsoft.VirtualManager.UI.VMWizards.resources.dll67,7763.1.6018.01036
Microsoft.VirtualManager.UI.VMWizards.resources.dll67,2643.1.6018.01031
Microsoft.VirtualManager.UI.VMWizards.resources.dll67,7763.1.6018.01040
Microsoft.VirtualManager.UI.VMWizards.resources.dll68,2643.1.6018.01041
Microsoft.VirtualManager.UI.VMWizards.resources.dll67,2643.1.6018.01046
Microsoft.VirtualManager.UI.VMWizards.resources.dll71,3363.1.6018.01049
Microsoft.VirtualManager.UI.VMWizards.resources.dll67,2403.1.6018.03082
Microsoft.VirtualManager.UI.VMWizards.resources.dll65,7043.1.6018.01028
Microsoft.VirtualManager.UI.VMWizards.resources.dll67,2403.1.6018.01042
Microsoft.VirtualManager.UI.VMWizards.resources.dll65,7043.1.6018.03076
Microsoft.VirtualManager.UI.VMWizards.resources.dll67,7523.1.6018.01029
Microsoft.VirtualManager.UI.VMWizards.resources.dll67,2403.1.6018.01043
Microsoft.VirtualManager.UI.VMWizards.resources.dll67,7523.1.6018.01038
Microsoft.VirtualManager.UI.VMWizards.resources.dll67,2643.1.6018.01045
Microsoft.VirtualManager.UI.VMWizards.resources.dll67,2403.1.6018.02070
Microsoft.VirtualManager.UI.VMWizards.resources.dll66,7283.1.6018.01053
Microsoft.VirtualManager.UI.VMWizards.resources.dll66,7283.1.6018.01055
Remoting.dll832,1843.1.6018.0Not applicable
Supplemental Notices for SC 2012 SP1 - Virtual Machine Manager Update Rollup 1.rtf141,687Not applicableNot applicable
Utils.dll751,2963.1.6018.0Not applicable
VirtualizationInterfaces.dll86,6963.1.6018.0Not applicable
VMWareImplementation.dll2,051,7523.1.6018.0Not applicable
VSImplementation.dll99,5203.1.6018.0Not applicable
WSManAutomation.dll35,0083.1.6018.0Not applicable
WsManWrappers.dll3,208,8963.1.6018.0Not applicable



Collapse this imageExpand this image
Virtual Machine Manager – VMM Server Update (KB2792926)
Collapse this imageExpand this image

Collapse this tableExpand this table
Files that are changedFile sizeVersionLanguage ID
Engine.Adhc.Operations.dll1,064,6163.1.6018.0Not applicable
Engine.Deployment.dll546,9843.1.6018.0Not applicable
Engine.Placement.ResourceModel.dll306,8563.1.6018.0Not applicable
Engine.VmOperations.dll1,134,2483.1.6018.0Not applicable
Errors.dll3,848,3763.1.6018.0Not applicable
Errors.resources.dll132,62483.1.6018.02052
Errors.resources.dll1,648,3203.1.6018.01036
Errors.resources.dll1,676,4563.1.6018.01031
Errors.resources.dll1,555,1123.1.6018.01040
Errors.resources.dll1,844,4163.1.6018.01041
Errors.resources.dll1,562,2803.1.6018.01046
Errors.resources.dll2,207,9123.1.6018.01049
Errors.resources.dll1,604,8003.1.6018.03082
Errors.resources.dll1,344,6803.1.6018.01028
Errors.resources.dll1,636,0323.1.6018.01042
Errors.resources.dll1,344,6803.1.6018.03076
Errors.resources.dll1,557,6883.1.6018.01029
Errors.resources.dll1,526,9683.1.6018.01043
Errors.resources.dll1,687,7443.1.6018.01038
Errors.resources.dll1,611,9443.1.6018.01045
Errors.resources.dll1,580,7123.1.6018.02070
Errors.resources.dll1,494,6963.1.6018.01053
Errors.resources.dll1,513,6643.1.6018.01055
ImgLibEngine.dll3,142,8243.1.6018.0Not applicable
Remoting.dll832,1843.1.6018.0Not applicable
Supplemental Notices for SC 2012 SP1 - Virtual Machine Manager Update Rollup 1.rtf141,687Not applicableNot applicable
Utils.dll751,2963.1.6018.0Not applicable
ViridianImplementation.dll218,7923.1.6018.0Not applicable
ViridianImplementationV2.dll359,6163.1.6018.0Not applicable
VirtualizationInterfaces.dll86,6963.1.6018.0Not applicable
VMWareImplementation.dll2,051,7523.1.6018.0Not applicable
VSImplementation.dll99,5203.1.6018.0Not applicable
WSManAutomation.dll35,0083.1.6018.0Not applicable
WsManMIWrappers.dll133,8243.1.6018.0Not applicable
WsManWrappers.dll3,208,8963.1.6018.0Not applicable
XenImplementation.dll173,2483.1.6018.0Not applicable

Collapse this imageExpand this image

Applies to
  • Microsoft System Center 2012
Keywords: 
kbfix kbqfe kbexpertiseinter kbsurveynew KB2785682
Share
Additional support options
Ask The Microsoft Small Business Support Community
Contact Microsoft Small Business Support
Find Microsoft Small Business Support Certified Partner
Find a Microsoft Store For In-Person Small Business Support