Update Rollup 10 for System Center 2012 R2 Virtual Machine Manager

Introduction
This article describes the new features that are added and the issues that are fixed in Update Rollup 10 for Microsoft System Center 2012 R2 Virtual Machine Manager. The following updates are available for System Center 2012 R2 Virtual Machine Manager (VMM):

  • VMM Server
  • Administrator Console
  • Guest Agent
Additionally, this article contains the installation instructions for Update Rollup 10 for System Center 2012 R2 Virtual Machine Manager.

Note Upgrading from VMM 2012 R2 Update Rollup 10 (UR10) to VMM 2016 Technical Preview 5 (TP5) is not supported because UR10 was released after TP5. If you plan to upgrade to TP5, we recommend that you do not install UR10 but instead remain on UR9. Additionally, upgrading to the release version of VMM 2016 will be supported for the latest VMM 2012 R2 update rollup that's available at the time of release.

Features that are added in this update rollup

Support for using VMM Hardware Profile Properties in Windows Azure Pack

In this update rollup, some VMM Hardware Profile Properties are exposed to VMRoleSizeProfile in Windows Azure Pack (WAP). The Service Provider Admin service can expose these Hardware Profile Properties to tenants so that they can take advantage of these properties. For example, exposing secure boot properties to tenants lets them deploy Gen2 Linux VMRoles.

  • A new HWProfileId parameter is added to the Set-CloudVMRoleSizeProfile cmdlet to link the VMM Hardware Profile to the VMRoleSizeProfile cmdlet.

    Example cmdlet:
    Set-CloudVMRoleSizeProfile -VMRoleSizeProfile CloudVmRoleSizeProfile -HWProfileID HWProfileID


    Note The HWProfileId parameter cannot be specified during an Add operation. It can only be linked to an existing CloudVMRoleSizeProfile cmdlet.

  • You can use the Get-CloudVMRoleSizeProfile cmdlet to obtain the HWProfileId parameter.

Because of this functionality, if any VMRole is deployed or updated by using the linked VMRoleSizeProfile cmdlet, the Hardware Profile Properties are honored and updated for virtual machines (VM).

Important The VMRoleSizeProfile name must give the tenant enough information about the setting to let it select the correct VMRoleSizeProfile value when you deploy a VMRole.

For example, the SecureBootEnabled property is exposed in this update to WAP. This enables tenants to deploy Gen 2 based Linux VM Roles from WAP. To take advantage of this ability, create a hardware profile that has the secure boot option disabled in VMM, and then link the VMRoleSizeProfile cmdlet to the HWProfileId parameter by using the Set-CloudVMRoleSizeProfile cmdlet. You now can deploy a Gen2 based Linux VMRole by using this linked VMRoleSizeProfile cmdlet.

The following are the VMM Hardware Profile Properties that can be used in WAP:

  • SecureBootEnabled
  • LimitCPUForMigration
  • MemoryWeight
  • CPUReserve
  • HAVMPriority
  • RelativeWeight (Priority)
  • LimitCPUFunctionality
  • ExpectedCPUUtilization
  • NetworkUtilization
  • DiskIO
  • CPUType
  • CPUMax
  • NumaIsolationRequired
  • CPUPerVirtualNumaNodeMaximum
  • MemoryPerVirtualNumaNodeMaximumMB
  • VirtualNumaNodesPerSocketMaximum
  • CPUCount (Cores)
  • Memory (related settings)
  • DynamicMemoryEnabled
  • DynamicMemoryMaximumMB
  • DynamicMemoryBufferPercentage
  • DynamicMemoryMinimumMB

Issues that are fixed in this update rollup

  • When you try to change a service template that has a load balancer and a configurable VM network, the changes are not saved. Additionally, the Save dialog box may reappear.

    Note This issue occurs when you change the VM Network from an existing configurable setting to a different configurable setting.

  • When you try to edit or view a service template that has a load balancer and a VM network in Designer view, one or more VM Networks that you had added previously disappear.

  • When you try to perform Remediation on Hyper-V cluster nodes or put the nodes into maintenance mode, VMM occasionally cannot update the Hyper-V Network Virtualization (HNV) Policy on the Hyper-V cluster nodes. When this failure occurs, the affected Hyper-V hosts stay in the failed state permanently or until the System Center Virtual Machine Manager service is restarted. Typically, this issue affects only the nodes that exit Maintenance mode. The other nodes in the cluster continue to work as expected.

    The issue is fixed in this update rollup. However, to temporarily work around this issue, restart the System Center Virtual Machine Manager service, and then update all the VMs on the affected nodes after the nodes are in a failed state. This is the only known method to update the HNV policy and to make sure that the hosts obtain a Provider Address (PA).

  • When a service is serviced, the Guest Agent fails and returns the following error message:
    Error (22758)
    The guest agent encountered an exception while running a script command. Win32ErrorCode: 2147942402 DetailedErrorMessage: The system cannot find the file specified.

  • When you, as a tenant, try to deploy a VM or a VM Role by using a differencing disk through WAP, the VM or VM Role fails and generates disk quota errors. This issue may occur even though there is enough quota remaining. This issue occurs because of inconsistent usage calculations done by VMM for base and differencing disk scenarios. When this issue occurs, you receive one of the following error messages:

    • Error (23419)
      The operation results in a violation of the disk space quota for cloud * for the user role *.

      Recommended Action
      Ensure sufficient disk space quota for the user role specified and try the operation again. Please contact your system administrator with this error ID.
    • Error (22042)
      The service <name> was not successfully deployed. Review the event log to determine the cause and corrective actions.

      Recommended Action
      The deployment can be restarted by retrying the job.
    • Error (31304)
      VM Role resource <name> was not successfully deployed in the Cloud Service.

      Recommended Action
      VM Role can be repaired if the entity was created.
    For example, assume that you have three VM roles deployed by assigning every role to a 60-gigabyte (GB) operating system disk. The VM Role use Differencing Disks for the operating system disk, and the parent or base disk is a 60-GB hard disk.
    VM Role 01: Parent: 60 GB, Child: 43 GB
    VM Role 02: Parent: 60 GB, Child: 42 GB
    VM Role 03: Parent: 60 GB, Child: 42 GB


    When VMM tries to calculate the disk usage, it incorrectly adds the size of the base disk three times (instead of just one time) to obtain the current usage:

    3x60GB (180GB) + 43+42+42 (127GB) = 307 GB

    Ideally, the base disk should have been considered only one time (60+43+42+42 = 187GB). Therefore, if the tenant has a quota that is set to 300 GB, for example, deployments of new VMs and VM Roles fail and generate a quota violation.

  • When you have two replication groups that have the same name on a storage array, and you try to refresh or rescan the array by using VMM, you receive the following exception:
    Error (20413)
    VMM encountered a critical exception and created an exception report at C:\ProgramData\VMMLogs\SCMM.guid\report.txt.

    Recommended Action
    See the report for more details and search user forums for well-known root causes for self-help.

    The handling of the exception is improved in this update. The refresh or rescan job now fails, and you receive the following error message to help you resolve the issue:
    Error (24403)
    Unable to import replication group "%Name;". VMM does not support more than one replication group with the same name.

    Recommended Action
    Remove the duplicate replication group and try the operation again.


  • When you create a Gen 2 VM by using VMM, the VM creation fails, and you receive the following error message:
    Error (13206)
    Virtual Machine Manager cannot locate the boot or system volume on virtual machine <name>. The resulting virtual machine might not start or operate properly.


  • When you add a VM template that is configured to use the AutoLogonCredential parameter to a WAP plan, the plan goes into an Active (Out of Sync) state. This state continues until the VM template is removed or manual permissions are granted in the VMM Console to enable the tenants user role to access the specified Run As Account. WAP cannot sync a plan if the plan includes a VM template that has the AutoLogonCredential parameter added. Also, running the Get-SCVMtemplate -ID <ID cmdlet does not return the VM template if the VM template has AutoLogon enabled and AutoLogonCredential added.

Known issues from previous update rollups

  • Reinstallation of Update Rollup 8 for System Center 2012 R2 Virtual Machine Manager or a later update

    The reinstallation of Update Rollup 8 or a later update rollup fails, and you receive the following error message:
    time:InnerException.Type: System.Data.SqlClient.SqlException, InnerException.Message: Violation of PRIMARY KEY constraint 'PK_tbl_WLC_ServiceTemplate'. Cannot insert duplicate key in object 'dbo.tbl_WLC_ServiceTemplate'. The duplicate key value is (5fddb85c-4ae5-4c8b-be83-9b2961a316dd).

    Note This issue is not fixed in Update Rollup 10. To successfully reinstall Update Rollup 8 or a later update rollup, follow these steps:

    1. Uninstall the product and retain the update rollup database.
    2. Run the PreR2ReInstall script on the retained database.
    3. Install the release version of System Center 2012 R2 Virtual Machine Manager by having the program point to the retained database.

      Note The installation finishes but the VMM service might not start.
    4. Install the update rollup, and then run the PostInstall script.
    5. Start the VMM service if it does not start automatically.

    For more information, see the following article in the Microsoft Knowledge Base:
    3132774 How to retain the database when you reinstall Virtual Machine Manager
  • Adding a new node to a Highly Available VMM (HAVMM) Cluster

    When you add a new node to an HAVMM cluster and install Update Rollup 8 or a later update rollup on the new node, you may receive the following exception:
    time:InnerException.Type: System.Data.SqlClient.SqlException, InnerException.Message: Violation of PRIMARY KEY constraint 'PK_tbl_WLC_ServiceTemplate'. Cannot insert duplicate key in object 'dbo.tbl_WLC_ServiceTemplate'. The duplicate key value is (5fddb85c-4ae5-4c8b-be83-9b2961a316dd).

    This issue is not fixed in Update Rollup 10. To fix this exception, follow these steps:

    1. Add the second node to the cluster.
    2. Stop the System Center Virtual Machine Manager service on the node where VMM is installed.
    3. Run the PreR2ReInstall script on the database.
    4. Install the release version of System Center 2012 R2 Virtual Machine Manager on the second node, pointing to the existing database.
    5. Install the update rollup on the second node, and then run the PostInstall script.
    6. Start the VMM service on the active node.


    For more information, see the following article in the Microsoft Knowledge Base:
    3132774 How to retain the database when you reinstall Virtual Machine Manage
For information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

How to obtain and install Update Rollup 10 for System Center 2012 R2 Virtual Machine Manager

Download information

Update packages for Virtual Machine Manager are available from Microsoft Update or by manual download.

Microsoft Update
To obtain and install an update package from Microsoft Update, follow these steps on a computer that has a Virtual Machine Manager 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 package, and then click OK.
  6. Click Install updates to install the update package.
Manual download
Go to the following websites to manually download the update packages from the Microsoft Update Catalog:

Installation instructions

To manually install the update packages, run the following command at an elevated command prompt:

msiexec.exe /update <packagename>

For example, to install the Update Rollup 10 package for a System Center 2012 Virtual Machine Manager SP1 server (KB3147167), run the following command:

msiexec.exe /update kb3147167_vmmserver_amd64.msp

Note Updating to Update Rollup 10 on the VMM server requires you to install both the VMM Console and Server updates. For more information, see the How to install, remove, or verify update rollups for System Center 2012 VMM topic on the Microsoft TechNet website.

Files updated in this update rollup

Administrator Console KB3147191
Files that are changedFile sizeVersionLanguage IDPlatform
Engine.Deployment.dll6874643.2.8169.00
Errors.dll47583763.2.8169.00x86
Errors.dll47583763.2.8169.00x64
ImgLibEngine.dll43620883.2.8169.00
Microsoft.VirtualManager.UI.Dialogs.dll32167443.2.8169.00
Remoting.dll10724883.2.8169.00x86
Remoting.dll10724883.2.8169.00x64
VMM.dll|Microsoft.SystemCenter.VirtualMachineManager.dll20637123.2.8169.00
VMWareImplementation.dll20657683.2.8169.00
WsManWrappers.dll38321683.2.8169.00
Errors.resources.dll16413123.2.8169.04x86
Errors.resources.dll16413123.2.8169.04x64
Microsoft.SystemCenter.VirtualMachineManager.resources.dll269843.2.8169.04x86
Microsoft.SystemCenter.VirtualMachineManager.resources.dll269843.2.8169.04x64
Remoting.resources.dll1145363.2.8169.04x86
Remoting.resources.dll1145363.2.8169.04x64
Errors.resources.dll19285523.2.8169.05x86
Errors.resources.dll19285523.2.8169.05x64
Microsoft.SystemCenter.VirtualMachineManager.resources.dll280003.2.8169.05x86
Microsoft.SystemCenter.VirtualMachineManager.resources.dll280003.2.8169.05x64
Remoting.resources.dll1222163.2.8169.05x86
Remoting.resources.dll1222163.2.8169.05x64
Errors.resources.dll20688403.2.8169.07x86
Errors.resources.dll20688403.2.8169.07x64
Microsoft.SystemCenter.VirtualMachineManager.resources.dll280083.2.8169.07x86
Microsoft.SystemCenter.VirtualMachineManager.resources.dll280083.2.8169.07x64
Remoting.resources.dll1181123.2.8169.07x86
Remoting.resources.dll1181123.2.8169.07x64
Errors.resources.dll19792403.2.8169.010x86
Errors.resources.dll19792403.2.8169.010x64
Microsoft.SystemCenter.VirtualMachineManager.resources.dll280083.2.8169.010x86
Microsoft.SystemCenter.VirtualMachineManager.resources.dll280083.2.8169.010x64
Remoting.resources.dll1211923.2.8169.010x86
Remoting.resources.dll1211923.2.8169.010x64
Errors.resources.dll20355603.2.8169.012x86
Errors.resources.dll20355603.2.8169.012x64
Microsoft.SystemCenter.VirtualMachineManager.resources.dll280083.2.8169.012x86
Microsoft.SystemCenter.VirtualMachineManager.resources.dll280083.2.8169.012x64
Remoting.resources.dll1211923.2.8169.012x86
Remoting.resources.dll1211923.2.8169.012x64
Errors.resources.dll20806163.2.8169.014x86
Errors.resources.dll20806163.2.8169.014x64
Microsoft.SystemCenter.VirtualMachineManager.resources.dll280083.2.8169.014x86
Microsoft.SystemCenter.VirtualMachineManager.resources.dll280083.2.8169.014x64
Remoting.resources.dll1217043.2.8169.014x86
Remoting.resources.dll1217043.2.8169.014x64
Errors.resources.dll19208723.2.8169.016x86
Errors.resources.dll19208723.2.8169.016x64
Microsoft.SystemCenter.VirtualMachineManager.resources.dll280083.2.8169.016x86
Microsoft.SystemCenter.VirtualMachineManager.resources.dll280083.2.8169.016x64
Remoting.resources.dll1196483.2.8169.016x86
Remoting.resources.dll1196483.2.8169.016x64
Errors.resources.dll22721043.2.8169.017x86
Errors.resources.dll22721043.2.8169.017x64
Microsoft.SystemCenter.VirtualMachineManager.resources.dll285123.2.8169.017x86
Microsoft.SystemCenter.VirtualMachineManager.resources.dll285123.2.8169.017x64
Remoting.resources.dll1222163.2.8169.017x86
Remoting.resources.dll1222163.2.8169.017x64
Errors.resources.dll20186643.2.8169.018x86
Errors.resources.dll20186643.2.8169.018x64
Microsoft.SystemCenter.VirtualMachineManager.resources.dll280083.2.8169.018x86
Microsoft.SystemCenter.VirtualMachineManager.resources.dll280083.2.8169.018x64
Remoting.resources.dll1181123.2.8169.018x86
Remoting.resources.dll1181123.2.8169.018x64
Errors.resources.dll18937283.2.8169.019x86
Errors.resources.dll18937283.2.8169.019x64
Microsoft.SystemCenter.VirtualMachineManager.resources.dll280083.2.8169.019x86
Microsoft.SystemCenter.VirtualMachineManager.resources.dll280083.2.8169.019x64
Remoting.resources.dll1191443.2.8169.019x86
Remoting.resources.dll1191443.2.8169.019x64
Errors.resources.dll19879443.2.8169.021x86
Errors.resources.dll19879443.2.8169.021x64
Microsoft.SystemCenter.VirtualMachineManager.resources.dll280003.2.8169.021x86
Microsoft.SystemCenter.VirtualMachineManager.resources.dll280003.2.8169.021x64
Remoting.resources.dll1211923.2.8169.021x86
Remoting.resources.dll1211923.2.8169.021x64
Errors.resources.dll27190723.2.8169.025x86
Errors.resources.dll27190723.2.8169.025x64
Microsoft.SystemCenter.VirtualMachineManager.resources.dll295443.2.8169.025x86
Microsoft.SystemCenter.VirtualMachineManager.resources.dll295443.2.8169.025x64
Remoting.resources.dll1350083.2.8169.025x86
Remoting.resources.dll1350083.2.8169.025x64
Errors.resources.dll18512403.2.8169.029x86
Errors.resources.dll18512403.2.8169.029x64
Microsoft.SystemCenter.VirtualMachineManager.resources.dll274963.2.8169.029x86
Microsoft.SystemCenter.VirtualMachineManager.resources.dll274963.2.8169.029x64
Remoting.resources.dll1181203.2.8169.029x86
Remoting.resources.dll1181203.2.8169.029x64
Errors.resources.dll18691603.2.8169.031x86
Errors.resources.dll18691603.2.8169.031x64
Microsoft.SystemCenter.VirtualMachineManager.resources.dll274963.2.8169.031x86
Microsoft.SystemCenter.VirtualMachineManager.resources.dll274963.2.8169.031x64
Remoting.resources.dll1186323.2.8169.031x86
Remoting.resources.dll1186323.2.8169.031x64
WSManAutomation.dll351763.2.8169.0127
Errors.resources.dll16664083.2.8169.01028x86
Errors.resources.dll16664083.2.8169.01028x64
Microsoft.SystemCenter.VirtualMachineManager.resources.dll269843.2.8169.01028x86
Microsoft.SystemCenter.VirtualMachineManager.resources.dll269843.2.8169.01028x64
Remoting.resources.dll1150483.2.8169.01028x86
Remoting.resources.dll1150483.2.8169.01028x64
Errors.resources.dll19311123.2.8169.01046x86
Errors.resources.dll19311123.2.8169.01046x64
Microsoft.SystemCenter.VirtualMachineManager.resources.dll280083.2.8169.01046x86
Microsoft.SystemCenter.VirtualMachineManager.resources.dll280083.2.8169.01046x64
Remoting.resources.dll1206803.2.8169.01046x86
Remoting.resources.dll1206803.2.8169.01046x64
Errors.resources.dll19526163.2.8169.02070x86
Errors.resources.dll19526163.2.8169.02070x64
Microsoft.SystemCenter.VirtualMachineManager.resources.dll280083.2.8169.02070x86
Microsoft.SystemCenter.VirtualMachineManager.resources.dll280083.2.8169.02070x64
Remoting.resources.dll1211843.2.8169.02070x86
Remoting.resources.dll1211843.2.8169.02070x64
Errors.resources.dll16664083.2.8169.03076x86
Errors.resources.dll16664083.2.8169.03076x64
Microsoft.SystemCenter.VirtualMachineManager.resources.dll269843.2.8169.03076x86
Microsoft.SystemCenter.VirtualMachineManager.resources.dll269843.2.8169.03076x64
Remoting.resources.dll1150403.2.8169.03076x86
Remoting.resources.dll1150403.2.8169.03076x64


Virtual Machine Manager Server KB3147167
Files that are changedFile sizeVersion IDLanguagePlatform
DBUpdate.dll7140883.2.8169.00
Engine.CloudService.dll2066883.2.8169.00
Engine.Deployment.dll6874643.2.8169.00x86
Engine.Deployment.dll6874643.2.8169.00x64
Engine.ImgLibOperation.dll5497363.2.8169.00
Engine.VmOperations.dll12844563.2.8169.00
Errors.dll47583763.2.8169.00x86
Errors.dll47583763.2.8169.00x64
Errors.dll47583763.2.8169.00x86
Errors.dll47583763.2.8169.00x64
ImgLibEngine.dll43620883.2.8169.00x86
ImgLibEngine.dll43620883.2.8169.00x64
Microsoft.SystemCenter.VirtualMachineManager.2012.Discovery.mp4459203.2.8169.00
Microsoft.SystemCenter.VirtualMachineManager.2012.Monitoring.mp7162563.2.8169.00
Microsoft.SystemCenter.VirtualMachineManager.2012.Reports.mp10316483.2.8169.00
Microsoft.SystemCenter.VirtualMachineManager.Library.mp1632963.2.8169.00
Microsoft.SystemCenter.VirtualMachineManager.Pro.2008.Library.mp1100483.2.8169.00
Microsoft.SystemCenter.VirtualMachineManager.Pro.2012.Diagnostics.mp235203.2.8169.00
Microsoft.SystemCenter.VirtualMachineManager.PRO.Library.mp204483.2.8169.00
Microsoft.SystemCenter.VirtualMachineManager.PRO.V2.HyperV.HostPerformance.mp568003.2.8169.00
Microsoft.SystemCenter.VirtualMachineManager.PRO.V2.Library.mp690883.2.8169.00
Remoting.dll10724883.2.8169.00x86
Remoting.dll10724883.2.8169.00x64
SCXStorageWrapper.dll1462723.2.8169.00
VMWareImplementation.dll20657683.2.8169.00x86
VMWareImplementation.dll20657683.2.8169.00x64
WsManWrappers.dll38321683.2.8169.00x86
WsManWrappers.dll38321683.2.8169.00x64
Errors.resources.dll16413123.2.8169.04x86
Errors.resources.dll16413123.2.8169.04x64
Remoting.resources.dll1145363.2.8169.04x86
Remoting.resources.dll1145363.2.8169.04x64
Errors.resources.dll19285523.2.8169.05x86
Errors.resources.dll19285523.2.8169.05x64
Remoting.resources.dll1222163.2.8169.05x86
Remoting.resources.dll1222163.2.8169.05x64
Errors.resources.dll20688403.2.8169.07x86
Errors.resources.dll20688403.2.8169.07x64
Remoting.resources.dll1181123.2.8169.07x86
Remoting.resources.dll1181123.2.8169.07x64
Errors.resources.dll19792403.2.8169.010x86
Errors.resources.dll19792403.2.8169.010x64
Remoting.resources.dll1211923.2.8169.010x86
Remoting.resources.dll1211923.2.8169.010x64
Errors.resources.dll20355603.2.8169.012x86
Errors.resources.dll20355603.2.8169.012x64
Remoting.resources.dll1211923.2.8169.012x86
Remoting.resources.dll1211923.2.8169.012x64
Errors.resources.dll20806163.2.8169.014x86
Errors.resources.dll20806163.2.8169.014x64
Remoting.resources.dll1217043.2.8169.014x86
Remoting.resources.dll1217043.2.8169.014x64
Errors.resources.dll19208723.2.8169.016x86
Errors.resources.dll19208723.2.8169.016x64
Remoting.resources.dll1196483.2.8169.016x86
Remoting.resources.dll1196483.2.8169.016x64
Errors.resources.dll22721043.2.8169.017x86
Errors.resources.dll22721043.2.8169.017x64
Remoting.resources.dll1222163.2.8169.017x86
Remoting.resources.dll1222163.2.8169.017x64
Errors.resources.dll20186643.2.8169.018x86
Errors.resources.dll20186643.2.8169.018x64
Remoting.resources.dll1181123.2.8169.018x86
Remoting.resources.dll1181123.2.8169.018x64
Errors.resources.dll18937283.2.8169.019x86
Errors.resources.dll18937283.2.8169.019x64
Remoting.resources.dll1191443.2.8169.019x86
Remoting.resources.dll1191443.2.8169.019x64
Errors.resources.dll19879443.2.8169.021x86
Errors.resources.dll19879443.2.8169.021x64
Remoting.resources.dll1211923.2.8169.021x86
Remoting.resources.dll1211923.2.8169.021x64
Errors.resources.dll27190723.2.8169.025x86
Errors.resources.dll27190723.2.8169.025x64
Remoting.resources.dll1350083.2.8169.025x86
Remoting.resources.dll1350083.2.8169.025x64
Errors.resources.dll18512403.2.8169.029x86
Errors.resources.dll18512403.2.8169.029x64
Remoting.resources.dll1181203.2.8169.029x86
Remoting.resources.dll1181203.2.8169.029x64
Errors.resources.dll18691603.2.8169.031x86
Errors.resources.dll18691603.2.8169.031x64
Remoting.resources.dll1186323.2.8169.031x86
Remoting.resources.dll1186323.2.8169.031x64
WSManAutomation.dll351763.2.8169.0127x86
WSManAutomation.dll351763.2.8169.0127x64
Errors.resources.dll16664083.2.8169.01028x86
Errors.resources.dll16664083.2.8169.01028x64
Remoting.resources.dll1150483.2.8169.01028x86
Remoting.resources.dll1150483.2.8169.01028x64
vmmAgent.exe63640083.2.8169.01033
vmmguestagent.exe3505603.2.8169.01033
vmmguestservice.exe2543123.2.8169.01033
vmmguestservice.exe2916883.2.8169.01033
Errors.resources.dll19311123.2.8169.01046x86
Errors.resources.dll19311123.2.8169.01046x64
Remoting.resources.dll1206803.2.8169.01046x86
Remoting.resources.dll1206803.2.8169.01046x64
Errors.resources.dll19526163.2.8169.02070x86
Errors.resources.dll19526163.2.8169.02070x64
Remoting.resources.dll1211843.2.8169.02070x86
Remoting.resources.dll1211843.2.8169.02070x64
Errors.resources.dll16664083.2.8169.03076x86
Errors.resources.dll16664083.2.8169.03076x64
Remoting.resources.dll1150403.2.8169.03076x86
Remoting.resources.dll1150403.2.8169.03076x64


Virtual Machine Manager Guest Agent KB3158139
Files that are changedFile sizeVersionLanguage IDPlatform
ScvmmGuestServiceV5.exe310803.2.8169.00
GuestAgent.AppDownloader.dll469523.2.8169.00
Errors.dll47583763.2.8169.00


Properties

Article ID: 3147167 - Last Review: 06/30/2016 20:18:00 - Revision: 3.0

Microsoft System Center 2012 R2, Microsoft System Center 2012 R2 Virtual Machine Manager

  • kbqfe kbsurveynew kbfix kbexpertiseinter atdownload KB3147167
Feedback