User guide

vConverter Functional Overview 21
Conversion Process
Note A P2V conversion using the VA as a target may fail if the resulting VM will have the same
name as another VM within the vCenter infrastructure. The error message "Can't find
proper disk-name amount attached disks to VA” will be displayed. Additionally, several
indexed VM copies may be created on the target ESX host.
Windows V2P
vConverter offers the ability to convert Windows VMs back to a physical target.
vConverter uses a VistaPE boot image to boot the physical system, so the target server
does not need to have an OS.
Once you configure a task and specify the source VM, vConverter obtains the essential
information about it using the Conversion Service. This is done either via a special API
provided by the source virtualization platform (for ESX, and Hyper-V servers). This
information is saved in vConverter together with the task settings, and is used during the
conversion process.
To specify the target system in the Task Properties pane, you need to first boot it using
the VistaPE boot image. The Server Information Tool is then launched, which enables
vConverter to get required disk information from the target.
When V2P conversion is started, the Conversion Service enables the V2P Migration
Tool on the target. The tool reads the source VM disk image sector by sector and
restores an exact partition layout. After that, it launches the Adaptation Process inside
V2P Migration Tool, which prepares the restored system for the first run on the new
hardware.