Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Hotfix 1 for System Center 2016 Virtual Machine Manager Update Rollup 1

Hotfix 1 for System Center 2016 Virtual Machine Manager Update Rollup 1

View products that this article applies to.

Introduction

This article describes the fix that's included in Hotfix 1 for Microsoft System Center 2016 Virtual Machine Manager Update Rollup 1. Additionally, this article contains the installation instructions for this hotfix.

There are no updates to the Administrator Console or Guest Agent as part of this hotfix. However, installation of this hotfix requires you to update the Host agent on all the VMM-managed hosts.

Note You must have Update Rollup 1 for System Center 2016 Virtual Machine Manager installed to apply this hotfix.

↑ Back to the top

Issues that are fixed in this hotfix

When you use Virtual Machine Manager to live migrate a virtual machine from one host that's running one version of Windows Server 2016 to another host that's running a different version of Windows Server 2016, the placement page assigns a zero rating to the target host. When this issue occurs, migration is blocked, and you receive the following error message:
Unable to migrate or clone the virtual machine VM_name because the version of virtualization software on the host does not match the version of virtual machine's virtualization software on source version_number. To be migrated or cloned, the virtual machine must be stopped and should not contain any saved state.

This issue occurs only when the source and target hosts are running different versions of Windows Server 2016. If the source and target hosts are running the same version of Windows Server 2016, or if one host is running Windows Server 2012 R2 and the other host is running Windows Server 2016, you do not experience this issue.

To work around this issue, migrate the virtual machine outside Virtual Machine Manager by using Failover Cluster Manager.

↑ Back to the top

How to obtain and install Hotfix 1 for System Center 2016 Virtual Machine Manager Update Rollup 1

Download information

The hotfix package for Virtual Machine Manager is available by manual download.
Manual download
Go to the following website to manually download the hotfix package from the Microsoft Update Catalog:

Download Download the Virtual Machine Manager Server update package now.

For more 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.

↑ Back to the top

Prerequisites

You must have Update Roll up 1 for System Center 2016 Virtual Machine Manager installed to apply this hotfix.
Installation instructions
To manually install the hotfix package, run the following command from an elevated command prompt:
msiexec.exe /update <packagename
For example, to install Hotfix 1 (KB3208888), run the following command:
msiexec.exe /update kb3208888_vmmserver_amd64.msp

↑ Back to the top

Files updated in this Update Rollup

Virtual Machine Manager Server KB3208888
Files that are changedVersion
Engine.Deployment.dll4.0.1968.10
vmmAgent.exe4.0.1968.10

↑ Back to the top

Keywords: kbqfe, kbsurveynew, kbnotautohotfix, kbfix, kbexpertiseinter, atdownload, kb

↑ Back to the top

Article Info
Article ID : 3208888
Revision : 2
Created on : 1/24/2017
Published on : 1/24/2017
Exists online : False
Views : 326