K2 Systems Inc. Support > Help Desk K2 Systems > Knowledgebase

Search help:

HOW TO: Convert a physical server or virtual server (P2V/V2V) to Microsoft Hyper-V using Microsoft Virtual Machine Converter 3.1


HOW TO: Convert a physical server or virtual server (P2V/V2V) to Microsoft Hyper-V using Microsoft Virtual Machine Converter 3.1.

MVMC 3.1 Pre-requisites

  • MVMC 3.1 can only be installed on Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server 2012 R2.
  • Microsoft .NET Framework 3.5 and .NET Framework 4 installed.
  • Background Intelligent Transfer Servers (BITS) installed.
  • Feature Bits Compact server installed.


(if the last two features are not installed your conversion will fail, with a root namespace issue!).

The software download links can be found in my previous Experts Exchange article HOW TO:  P2V, V2V for FREE to Hyper-V - Microsoft Virtual Machine Converter 3.1.

Install Microsoft Virtual Machine Converter 3.1 on the server taking note of the Pre-requisites above. In this tutorial, we've installed Microsoft Virtual Machine Converter 3.1 on the Microsoft Hyper-V server that will be hosting the converted physical server.

In this tutorial we will convert a small physical file server called FS01, which has 4GB RAM, 2 Processors, 40GB hard disk, and the operating system is Windows Server 2012 R2 Daatcenter. 

Start Microsoft Virtual Machine Converter 3.1 from the Start Menu.

Select Yes, to the "Do you want to allow the following program to make changes to this computer?"

At the Microsoft Virtual Machine Converter "Before You Begin Welcome Page" select Next to continue.

In this tutorial we will be completing a Physical machine conversion. So select Physical machine conversion and click Next to continue. If you want to complete a virtual machine conversion, select Virtual machine conversion.

 2014-12-09-15-00-14-Greenshot.jpgSelect the Source physical machine for conversion, by entering​

  • IP Address or computer name or fully qualified domain name. (fqdn)
  • Username
  • Password

Click next to continue.

TOP TIP No.1  I would recommend using a fully qualified domain name and Local Administrator username and password for the physical machine. It's always advised to have good working DNS for your network infrastructure. 

TOP TIP No.2  I would recommend disabling the firewall on Source Physical machine!  

Click Scan System at the System Information page, and click Next to continue.

Confirm the System Information is correct, and select Next to continue.

At the Volume Configuration page, select your VHD Type preference, between Dynamic (the default) or Fixed. 

Select Next to continue.

Specify the Virtual machine name as you would like it to appear in the Hyper-V inventory and enter the number of processors and total memory for the virtual machine. Click Next to continue.

Select a Hyper-V host as the destination for the virtual machine. Enter the

  • IP Address or computer name or fully qualified domain name (FQDN)
  • Username
  • Password

Click Next to continue.

Specify a network share on the Hyper-V server. We have created a share on the virtual machine root folder (VMs). Click Next to continue.

Select a location on this machine with enough free space for the converted virtual machine. (This is a temporary location used in the conversion process). Click Next to continue.

Select a virtual switch to connect to the virtual machine. Click Next to continue.

Check the Final Summary, and click Finish to submit the conversion job.

Be patient; grab a coffee whilst the job starts...

2014-12-09-15-40-49-Greenshot.jpgThe conversion job is in progress
The disk conversion has finished, and the disks will be fixed-up.

The conversion was successful. The conversion from physical to virtual has taken approx 30 minutes. Click Close.

If you click Hyper-V Manager from the Start Menu, you can check and start-up the VM.

The physical machine which has been converted will be displayed in the Hyper-V inventory. Right Click the Virtual Machine fs01, and select Connect.

Press the Power On button highlighted to Power On the virtual machine fs01.

Screenshot of converted physical server fs01, running as a virtual machine hosted on Hyper-V.

In the above tutorial we have converted a physical server to Microsoft Hyper-V using Microsoft Virtual Machine Converter 3.1, the same process can be used to convert a virtual machine, by selefting the virtual machine selection at the beginning or the conversion job.

Was this article helpful? yes / no
Related articles How to Create an FQDN to 3CX Phone System that resolves locally
How To: Perform a Hardware Independent Restore ( HIR )
Creating Panoramic Virtual Tours
3CXPhone MyPhone Connection Issues (Self-Help)
Configuring MS Exchange Server 2013 Unified Messaging with 3CX Phone System
Article details
Article ID: 169
Category: HOW 2 for iphone, android, pc
Date added: 2018-01-22 14:13:09
Views: 809
Rating (Votes): Article not rated yet (0)

« Go back

Powered by Help Desk Software HESK, in partnership with SysAid Technologies