MICROSOFT VIRTUAL MACHINE CONVERTER

MICROSOFT VIRTUAL MACHINE CONVERTER VERSION 2.0

Overview Free to download tool Standalone tool supporting Hyper-v 2012 R2 and VSphere 5.5 and above Converts VMWare virtual Machines to hyper-v with additional functionality which includes support for later

guest operating systems and target hosts Migrate VMWare Virtual Machines to Azure space

Benefits Quick to deploy Small installer and UI driven tool Support for PowerShell which helps to write customizations Built in migration automation toolkit Fully supported by Microsoft

Note 1 : VHDX format migration is only possible from VMWare to Hyper-V starting from Windows Server 2012 and above

Note 2 : VHD format is supported when migrating Virtual Machine from VMWare to Azure

MICROSOFT VIRTUAL MACHINE CONVERTER

Supported Source and Destination HostsVMWare

• vCenter 4.1

• vCenter 5.1

• vCenter 5.5

• ESX/ESXi 4.1

• ESXi 5.1

• ESXi 5.5

Hyper-V / Microsoft Azure

• Hyper –V 2008 R2 SP1 ( VHD )

• Hyper—V 2012 ( VHD/ VHDX )

• Hyper—V 2012 R (VHD / VHDX)

• Microsoft Azure

MICROSOFT VIRTUAL MACHINE CONVERTER Supported Guest Operating Systems

Note: Microsoft Azure do not support X86 version guests

Note2: Microsoft Azure do not support Windows clients ( All versions )

VMWare Hardware Versions

• 4• 7• 8• 9• 10

Supported Guest OS

• Windows Server 2008 (X86/X64)• Windows Server 2008 R2 (X64)• Windows Server 2012 (X64)• Windows Server 2012 R2 ( X64)• Windows Vista Enterprise ( X86/X64)• Windows 7 Pro/Ent/Ultimate ( X86/X64)• Windows 8 Pro/Ent ( X86/X64)• RHEL 5/6 (X86/X64)• Ubuntu 10.04/12.04 (X86/x64)• SLES 11 (X86/X64)• CentOS 5/6 ( X86/x64)• Debian GNU/Linux 7 (X86/X64)• Oracle Linux 5/6 ( X86/X64)

MICROSOFT VIRTUAL MACHINE CONVERTER

Supported VMWare Virtual Disk Configurations

Note: Virtual Machine disk should be of VMDK format.

VMWare Virtual Machines

• Supported Guest OS versions

Supported VMWare Virtual Disk Types

• MonolithicFlat• MonolithicSparse• TwoGbMaxExtentflat• TwoGbMaxExtentSparse• StreamOptimized• Vmfs• VmfsSparse• Delta disk conversion

MICROSOFT VIRTUAL MACHINE CONVERTER

Destination / Hyper-V Side Requirements

Note: Migration will have two identically sized files , hence double the size of capacity per VM

VMWare Virtual Machines

• User account should have appropriate privileges to conduct migration

Hyper-V Requirements

• Account Should have appropriate privileges to conduct migration

• Account should have write access to UNC path ( SMB share ) on Hyper-v Host

• Double the size of source VMDK capacity per VM migration

• For Windows Guests• Disable Firewall, enable RDP and

ensure VMWare tools are installed• Remote access through WMI is

enabled on source VMWare VM• Account should be part of AD and

has local administrator privileges

MICROSOFT VIRTUAL MACHINE CONVERTER

Azure Requirements

Note: Migration will have two identically sized files , hence double the size of capacity per VM

VMWare Virtual Machines

• MVMC 2.0 performs virtual machine conversion to VHDs and upload the disks to Microsoft Azure blob storage

Azure Requirements

• MVMC 2.0 requires management certificate used to authenticate user subscription ID on Microsoft Azure

• Requires storage account to upload and store the converted VHDs in Microsoft Azure

• To convert and upload to Microsoft Azure, PowerShell 3.0 Runtime component is required on the machine on which MVMC 2.0 is running ( especially when running on legacy OS )

CONVERTING A VM : HIGH LEVEL PROCESS

MVMC will connect to vCenter/ESXi & select the guest to be converted

MVMC will checkpoint the VM / snapshot the VM and uninstall VMWare tools

VMDK to VHD / VHDX copy and conversion will take place

Turn on the VM at the end of the process

CONVERTING A VM : HIGH LEVEL PROCESS

Important Points to be considered

Bulk conversions are not possible, only one VM can be converted at a time

VMWare tools are not required on Hyper-v end, hence uninstall them before converting, but snapshot will still have VMWare tools in it

During copy and conversion, migration time should include copy, conversion and network time should be factored into overall migration effort

Supports Stateless VM migration considering the fact the downtime is very minimal ( just for reboot )

MIGRATION AUTOMATION TOOLKIT FOR MVMC 2.0

PowerShell scripts that wrapper MVMC 2.0 with automation to perform multiple conversions simultaneously

Free download, edit and customize Uses free SQL Express to store information about the conversion process Supports multiple simultaneous conversions per MVMC 2.0 machine Scales out across multiple machines running MVMC 2.0 and scripts all coordinated from central

node. More helper nodes = more simultaneous conversions. This means MVMC 2.0 can be installed on multiple systems and each of the MVMC nodes ( systems ) can run 1-3 migrations at a time