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.

Virtual Machine fails to start after importing on Windows Server 2012

View products that this article applies to.

Symptoms

A virtual machine that is exported from Windows Server 2012 using a script, fails to start when it is imported on Windows Server 2012 using PowerShell or the User Interface.

↑ Back to the top

Cause

Virtual machines must be imported with the same APIs which were used to export them. Hyper-V PowerShell and User Interface utilize the Hyper-V v2 WMI APIs.

↑ Back to the top

Resolution

Either update export scripts to utilize the WMI v2 export APIs or use a WMI v1 import script to import the virtual machine.

↑ Back to the top

More Information

Hyper-V WMI v1 Export API Documentation:

http://msdn.microsoft.com/en-us/library/cc136793(v=vs.85).aspx
http://msdn.microsoft.com/en-us/library/dd379580(v=vs.85).aspx

Hyper-V WMI v2 Export API Documentation:

http://msdn.microsoft.com/en-us/library/hh850049(v=vs.85).aspx

↑ Back to the top

Applies to:

↑ Back to the top

Keywords: kb

↑ Back to the top

Article Info

Article ID	:	2809266
Revision	:	1
Created on	:	1/7/2017
Published on	:	2/14/2013
Exists online	:	False
Views	:	438