Quest® vConverter

Version 5.2

Release Notes

March 2012


Welcome to vConverter

New in this Release

Resolved Issues and Enhancements

Known Issues

Upgrade and Compatibility

System Requirements

Global Operations

Getting Started

For More Information


Welcome to vConverter


    vConverter is complete workload migration platform.   It provides the functionality, flexibility, and speed needed for high-volume migrations of Windows or Linux servers within the datacenter.

    vConverter provides numerous features for medium to large server consolidation initiatives, as well as options for ongoing disaster recovery. Multiple conversion modes and target options ensure data consistency with minimal downtime. The ability to automate many pre- and post-migration tasks, along with a streamlined data transfer mechanism, allows vConverter to migrate more servers per conversion window than any other conversion method or technology. vConverter is also available in a 'Continuous Protection' mode, which performs incremental syncs at user-defined intervals to ensure the integrity of the source physical server and the viability of virtual standby systems.

    These Release Notes cover the resolved issues, known issues, workarounds, and other important information about the 5.2 release of vConverter. Review all sections before starting the installation.


New in this Release

This release contains the following updates:


Resolved Issues and Enhancements

The following is a list of issues addressed and enhancements implemented in this release.

Defect ID

Resolved Issue

9695 When vConverter is installed in a non-default directory, and then uninstalled, all files in that directory are deleted.
9855 During V2P conversions, if the source VM is located on an ESX 4.1 host, the conversion task will fail with an "unrecognized image" error.
9918 When adding ESX hosts to vConverter, the host IP address is shown rather than the name.
10083 Database corruption may occur after subsequent Continuous Protection conversions.


Note - see the known issue Limitations for CP conversions for limitations regarding continuous protection of SQL databases.

10977 Changed error message referring to non-existent section of documentation.
11670 Upgrade fails with "vConverter Service failed to start error"
11723 After performing a resize operation to ESXi, thin disks are shown as thick.
12277 ESX passwords are not being obfuscated in log files.


Known Issues

The following is a list of issues known to exist at the time of this release.



Known Issue

General Application Tasks fail with 'access denied' error. This can occur when a task is scheduled and is run by vConverter Service.


vConverter Service uses System account when running. System account does not have network access by default. To avoid this problem please start vConverterService using 'Run As' context menu under a user that has Administrator privileges.
VMCI  does not  work correctly on target VM after Windows P2V conversion. This occurs when you do not configure installation of VMware tools in the task.


To fix the problem please install VMware Tools manually or change task (check "Install VMware tools" checkbox).
SC/DDC Task failed with "No network provider accepted the given network path" error.
This may occur when Win 2000 is set as source for task, network has DHCP server and VM is added to task using its IP address. DHCP could change IP address after VM reboot and vConverter is not able to locate VM.


Add VM by name or change IP address in task.
Task failed with "Failed to open Disk Image" error. This may occur for the task when target ESX was reconfigured in Preferences to use VA.


For some tasks (Single, DDC) re-save could help; other tasks you might not be able to run.

General recommendation is not to reconfigure ESX when it is used in one or more tasks.
VM is not bootable after conversion with "Operation System not found" message.

This issue occurs if source machine has physical drives located on disk controllers of different types (SCSI, IDE) and IDE drive presented as Disk0 and SCSI drive presented as Disk1 inside OS and boot partition is on Disk1. Because of this target machine will not boot after conversion if preserve disk structure mode used.

This issue occurs because of the following reasons:

1. BIOS enumerates SCSI drives first to find active partition to boot from.

2. vConverter doesn't provide functionality to select target disk type separately (one to SCSI, second to IDE as example). So all disks convert to the same format(SCSI or IDE).

3. So if preserve disk structure used, target machine will try to boot from first disk (Disk0). But provided configuration doesn't have boot partition on first drive and should be boot from second.


Go to BIOS on the target machine and change boot order of hard drives so that Disk1 is a first boot (see below).

OEM partition cannot be captured by vConverter, as it has no Volume GUID. To preserve the disk structure, unallocated space will be created instead of OEM partitions.

For other volume mapping types,  OEM partitions will be silently skipped.

These partitions are not shown in the vConverter User Interface.

There is no workaround for this issue.

Minimum disk free space after a conversion with resize cannot be less than a certain value.

Minimum disk size after conversion is determined: (Used space)+1GB+0.01*(Total size). This formula is managed by vConverter and cannot be changed

vConverter client may hang when switching from the view of one task to another quickly. vConverter updates information about a task each time you click to view it:  generating this information takes between several seconds to several minutes.


Do not click too fast, and wait until the view is complete before viewing another task.
If the vConverter license file is updated while one or more tasks is running, the tasks may fail with the error "License checking is failed"


Restart failed tasks.  To avoid interruption, do not update the license file while tasks are running.

Virtual Appliance

MS SQL DB is located on different volumes, then there is NO chance for the user to perform a SQL DB consistent conversion via vMA. The reason is that vMA always perform conversions in “separate” mode which means that each volume will be converted into different VMDK file.

Conversion using the VA may create 1-2MB of unallocated space on each disk.

For small disks, unallocated space may be created after conversion jobs using the VA.

There is no workaround for this issue.

In certain cases (mostly incorrect termination of tasks, services, tools and/or hosts during conversion process), the VA may be left with attached VM disks (which were created during the conversion). These disks will require manual removal.

Disks should be detached manually.
Application Consistency vConverter  does not guarantee that created VM will be bootable in case the source VM has two or more OS (boot records) and one of the OS is Vista or later while another is earlier than Vista.
The reason is that there could be problems with boot records because of different volume boot records.


Do not select for conversion disks that contains different volume boot records.


Repair the boot record manually after conversion.
MS SQL database might be corrupted after conversion (Suspected state).

To ensure MS SQL database is not corrupted after conversion, use the following configuration:

Continuous Protection

The following conditions should be met for successful CP conversions of running SQL Servers:

  • All volumes which contain DB files must be selected for capturing;
  • "Create separate file for each volume” option must be unchecked because source database files (data and logs) are located on different volumes and a snapshot should be taken at one moment. So all source volumes must be converted to one disk.
  • VSS server should be configured the way it is described in section "Configuring the MSDE Writer to Ignore SQL Server 2005 Instances"  from “SQL Writer.doc”
Different Destinations Cutover DDC task fails with "Failed to create virtual disk image. VA script error: unable to attach Virtual Disk to Session" error.
This error might appear when you are trying to perform "final sync" after VM was migrated.

The reasons for the error are the following:

  • A task was configured vConverter using the "vConverter name scheme" (VMDK files are named as follows: 'vm_name_C.vmdk')
  • A "Migrate" operation was performed over the VM to place VM to another location
  • VMware renames VMDK files when performing migrate operation (to 'vm_name_1.vmdk').
  • vConverter cannot map VMDK file names that are stored in task to a new machine - error occurs.


There are several workarounds that could be used to avoid such problem:


Workaround #1:
Use VMware naming convention in vConverter prior to creating task.

(This could be configured in Preferences->Windows P2V Conversion tab)

Workaround #2:
Do not perform "Migrate" operation using VMware. Instead, simply change datastore for VM when you want to change VM location.

Linux Conversion

vConverter  Linux P2V conversions support only ext2, ext3, and ext4 file systems for '/' and '/boot' file systems migration.

Conversions of Linux machines will create a VM with a static IP, regardless of source configuration. The source system NICs configurations are not collected for Linux systems. Configurations for NICs given via vConverter UI are not applied on migrated system. vConverter treates all Linux VMs as being configured with static IP addess.
When performing conversions of Linux servers, an error during a conversion may leave a virtual disk attached to the VA, causing subsequent conversion tasks using that VA to fail.



Unnecessary virtual disks must be manually detached from the VA, as described in the procedure below:

  1. Run "ppsd_clean_and_restart --all" as superuser on the VA.
  2. Shutdown VA.
  3. Remove disks attached to VA that were created by vConverter. Do not remove VA disks.
  4. To distinguish them from those which are required for VA work, consider the following:
  • VMDK files created by vConverter are placed in the target folder specified during the creation of the conversion task.
  • VMDK files created by vConverter have filenames like "VM_name.vmdk" and "VM_name_1.vmdk" (or "VM_name_C.vmdk" and "VM_name_E.vmdk" depending on the program preferences).
  • Generally, disks created by vConverter are attached to free (empty) Virtual Deviced nodes after system disks of VA machine (e.g. if system disk is attached to SCSI (0:0), vConverter will attach disks to SCSI (0:1), (0:2) etc.).
During P2V Linux conversions, the target Linux VM could be damaged (or not created) when Grub on the source machine is manually changed.This occurs on machines using EXT4 file system and with manually configured (changed) grub loader when the following option is not selected for the task: "If all volumes from a disk are selected, convert the whole disk, including unallocated space"

This can lead to unpredictable task failure or unresponsive VMs.


Option 1. Reinstall Grub loader on the source machine before conversion to restore default configuration


Option 2: Check option "If all volumes from a disk are selected, convert the whole disk, including unallocated space" for the task.

If task already failed, perform the following actions:
- Restart VA (if it is hang)
- Manually detach disks attached to VA
- Manually remove folder with target machine from datastore.

Conversions of RHEL machines with 2 disks to ESX(i) 3.5 fail due to errors in vMA machine config file.

Workaround #1:
1. Run "ppsd_clean_and_restart --all" as superuser on the VA;
2. Reboot VA;
3. Restart conversion.

Workaround #2:

If the conversion fails after performing Workaround #1, you will need to re-create the VA by performing the following steps:
1. Shutdown VA;
2. Create new machine, attach disks from old VA to a newly created one;
3. Run "ppsd_clean_and_restart --all" as superuser on the newly created VA;
4. Change setting in vConverter so that newly creates VM is now used as VA.
5. Restart conversion.

Hyper-V Conversions The following limitations exist when converting from VMware To Hyper-V:
  • VMware tools will not work on target, so it is highly recommended to do the following:
    • Disable VMware tools on target machine (could be done in task settings);
    • remove/disable  VMware tools on source machine before the conversion;
    • uninstall VMware tools on target after the conversion.

If you do not follow this instructions, this could lead to  STOP: c000021a {Fatal System Error} error on the target VM. Uninstalling VMware tools should help resolve this error.

The following limitations exist when performing V2P conversions from Hyper-V:
  • vConverter requires read/write permissions to Hyper-V folder where source VM is placed;
  • It is recommended that Hyper-V integration Services is installed on source machine


Upgrade and Compatibility

For information on upgrading from a previous version of vConverter, please see the vConverter Installation and Setup Guide.


The following is a list of upgrade issues known to exist at the time of this release.


Known Issue

Application Preferences Reserved ports on the Conversion tab in the vConverter preferences don't preserve while upgrading/importing setting from vConverter 5.1 and vConverter 5.1.1.

This issue is connected to a defect that existed in previous vConverter versions. It was fixed in 5.2, but still exists when converting settings/upgrade from previous versions to v5.2

System Requirements

Before installing vConverter, ensure your system meets the following minimum hardware and software requirements:

Platform 1 GHz x86 processor or higher


1 GHz x64 processor or higher

Memory Minimum 1 GB
Hard Disk Space 4 GB of free hard disk space
Operating System Windows XP Professional SP2 - (x64)

Windows XP Professional SP3 -(x86)

Windows Server 2003 -Enterprise Edition - SP2 (x86,x64)

Windows Server 2003 R2 - Enterprise Edition - SP2 (x86,x64)

Windows Vista - Ultimate - SP2 (x86,x64)

Windows Server 2008 - Enterprise Edition - SP2 (x86,x64)

Windows Server 2008 R2 SP1 - Enterprise Edition (x64)

Windows 7 - Professional SP1 (x86,x64)

The above information is a summary only. Please refer to the vConverter System Requirements Guide for complete information.


Global Operations

This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

This release supports any single-byte character set. Double-byte or multi-byte character sets are not supported. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia.


Getting Started

Contents of the Release Package

The vConverter release package contains the following products:

  1. Quest vConverter version 5.2
  2. Product Documentation, including:

Installation Instructions


For detailed information about installing vConverter, see the vConverter Installation and Setup Guide.


For More Information

Get the latest product information, find helpful resources, test the product betas, and join a discussion with the vConverter Quest team and other community members. Join the vConverter Community at


Contacting Quest Software:

Mail Quest Software, Inc.
World Headquarters
5 Polaris Way
Aliso Viejo, CA 92656

Refer to our Web site for regional and international office information.

Contacting Quest Support:

Quest Support is available to customers who have a trial version of a Quest product or who have purchased a Quest product and have a valid maintenance contract. Quest Support provides unlimited 24x7 access to our support portal. Visit our support portal at

From our support portal, you can do the following:

View the Global Support Guide for a detailed explanation of support programs, online services, contact information, policies, and procedures.
The guide is available at


© 2011 Quest Software, Inc. ALL RIGHTS RESERVED.


This document contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software, Inc.


If you have any questions regarding your potential use of this material, contact:

Quest Software World Headquarters
5 Polaris Way
Aliso Viejo, CA 92656


Refer to our Web site for regional and international office information.



Quest, Quest Software, the Quest Software logo, Foglight, IntelliProfile, PerformaSure, Spotlight, StealthCollect, TOAD, Tag and Follow, Vintela Single Sign-on for Java, vConverter and vFoglight are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. For a complete list of Quest Software's trademarks, please see Other trademarks and registered trademarks are property of their respective owners.


Third Party Contributions

vConverter contains some third party components. For a complete list, see the Third Party Contributions section in the vConverter User Guide.



The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.