VMware P2V Assistant 1.0.1 Release Notes

  Documentation | Troubleshooting

Check back frequently for additions and updates to these release notes.

 Version 1.0.1 | 8/27/03 | Build 5606

What's in This Release Note

Version Compatibility for This Release

This P2V Assistant 1.0.1 version requires and/or functions with the listed versions of the following:
  • VMware ESX Server - all versions

  • VMware GSX Server - all versions

  • VMware Workstation 3.2

  • VMware Workstation 4.0
    Note: Do not have the P2V Assistant create a clone disk from within VMware Workstation 4.0. The P2V Assistant does not support Workstation 4.0 virtual disk formats. You can however,create a disk outside of Workstation 4.0 and attach it to the helper virtual machine running in Workstation 4.0.

Known Installation Issues with This Release

List of Known Installation Issues

Updating from P2V Assistant version 1.0

Updating your P2V Assistant from version 1.0 to 1.0.1 requires that you first uninstall version 1.0, then install 1.0.1.

NOTE: The licensing information in the registry is preserved between the 1.0 and 1.0.1 versions. This includes your system reconfiguration licenses.

To uninstall the P2V Assistant, version 1.0:

  1. Using your Windows tools, select:
    Start > Settings > Control Panel > Add/Remove Programs
  2. Scroll through the displayed list until you find: VMware P2V Assistant
  3. Click Change/Remove.
    An install shield starts.
  4. Confirm the uninstall.
    Click OK at the prompt, Are you sure you want to completely remove 'VMware P2V Assistant' and all of its components?. The install shield continues.
  5. Complete the uninstall. Reboot your system.
    Select Yes, I want to restart my computer now. Click Finish.
To install the P2V Assistant, version 1.0.1:
  1. Obtain the latest version of the VMware P2V Assistant. Check with your VMware Sales representative.
  2. Log on to the P2V Assistant machine.

    Two user types are acceptable: as the Administrator user or as a user who is a member of the Administrators group.

    The P2V Assistant machine is a physical or virtual machine where you install the VMware P2V Assistant application.

  3. Start the VMware P2V Assistant installer.

    With the P2V Assistant installer software on the Application CD or downloaded to a local location, do one of the following:

    • From the Start menu, choose Run. Browse to the directory where you saved the installer file. Double-click on the setup.exe file.
    • Navigate through your file manager interface, such as Windows Explorer, to the folder that contains the installer file. Double-click the setup.exe file.

  4. Proceed through the installer, answering the prompts as indicated.

    1. Begin the installation. Click Next.
    2. Acknowledge the license agreement. Click Yes.
    3. Enter user identification and user access information. Click Next.
      Type your name, your companyís name, and your productís serial number in the respective fields. The serial number can be found on your software registration email or contact your Professional Services Organization representative.
    4. Select the P2V Assistant installation location. Click Next.
      Accept the default folder or select a folder by clicking Browse button. If the selected directory does not exist, the installer creates it for you.

      NOTE:You must install the P2V Assistant on a local drive, not a network drive.

    5. Select the P2V Assistant icon location. Click Next.
      Various messages indicating the progress of the P2V Assistant installation are displayed. The P2V Assistant checks the machine it is installed on for a compatible Windows Script version.
    6. Close the P2V Assistant installer. Click Finish.
      You have completed P2V Assistant installation.

Known Issues with This Release

List of Known Limitations

List of Windows NT 4 Related Limitations

Installation Issues

Initializing Storage Subsystem Message

During P2V Assistant installation sometimes an error message is displayed: Initializing Storage Subsystem.


  1. Click Cancel on the error message.
  2. Reboot the P2V Assistant machine.

Repair Option Generates Error Message

When the P2V Assistant is being reinstalled or updated and the Repair option is selected from the Installation Wizard screen, an error is displayed: Cannot Find File.

This occurs if the P2V Assistant was not uninstalled, including rebooting the system, prior to attempting the reinstallation or updating.

Perform either of the following:

  • Uninstall the P2V Assistant. Then run the installer.
  • Rerun the installer. Then select the Modify option.

Installing on Windows 2000 with Terminal Services

The P2V Assistant cannot be installed on Windows 2000 systems with Terminal Services.


  1. Run a virtual machine on the Windows 2000 system with Terminal Services.
  2. Install the P2V Assistant in the virtual machine.

Known Limitations

Cloning Multiboot Systems

P2V Assistant does not support dual-boot or multiboot systems. Although P2V Imaging will clone the image of your source disk into a virtual machine, System Reconfiguration reconfigures only the active Windows system.

Multiboot systems are those systems with multiple versions of Windows installed, either under Windows itself or through third party tools such as Linux LILO or V Communications System Commander.

No action required. Information only.

Running Sysprep on a Source Machine Prior to Cloning

If Sysprep has been run on the source machine boot disk prior to cloning the machine, you will need to perform a second system reconfiguration after you complete the Sysprep on the new virtual machine.


  1. Perform Sysprep preparation on source machine.
  2. Perform System Reconfiguration on new virtual disk.
  3. Boot new virtual disk.
  4. Complete Sysprep process.
  5. Shutdown new virtual disk.
  6. Re-run System Reconfiguration.

P2V Assistant Multi-Tasking

While the P2V Assistant is processing and showing a progress message do not try another P2V Assistant action.

Allow the P2V Assistant to complete its task before attempting another task.

Non-Standard Hardware Drivers

When a source machine uses non-standard hardware components, conversion to a virtual machine might cause a blue screen in the virtual machine.

This includes non-standard keyboards and mice.


  1. Uninstall the non-standard hardware.
  2. Install standard hardware.
  3. Re-run the cloning process.

Physical Additional Extensions in NT 4 Systems

P2V Assistant cannot perform a system reconfiguration on NT systems with greater than 4 GB of RAM.

Reduce the RAM prior to performing the cloning process.

Cannot Find the SWAP File

The swap file may have been on a partition that is not recognized or was not cloned.


  • Verify the drive letter mapping.
  • Verify all partitions in the disk were imported.

Check through Control Panel > Administrative Tools > Disk Management.

Maximum Registry Size is Too Small

During system reconfiguration, Windows displays a message Your maximum registry size is too small.


  1. Increase the maximum registry size of the helper virtual machine.
  2. Re-run the P2V Assistant process.

Partition Size Extended During Cloning

P2V Assistant extends the size of cloned partitions. For example, a source partition might have been 1000 MB, after cloning the partition on the target disk can be 1300 MB.

Informational message. No action required.

De-referenced Files to Prevent Blue Screen

Selected Compaq product files, that are not used in a virtual machine, are disabled to prevent a blue screen. These include:

  • cpqalert.exe - for Compaq's Insight Manager Agent
  • cpqdmi.exe - for Compaq's version of the Desktop Management Interface
  • cpqagent.dll - for Compaq application agent

No action required. Information only.

Source Volume Access Error

When P2V Assistant is directed to a partition, the user logged onto the P2V Assistant must also have permission to access the designated partition.

The error message is displayed:
The boot.ini file in the active partition refers to an unformatted or inaccessible system volume. This may happen is the currently logged on user does not have the permissions to access the system volume.

Re-logon to the P2V Assistant as a user that has access to the designated volumes (partitions).

Too Many Small Partitions Error

When adjusting the sizes of partitions to clone, if the last partition listed is less than 8 MB, an error is displayed:
Could not use new partition layout: Too many small partitions at end of disk

Set the last partition to at least 8 MB.

Migration Appears Successful During Network Failure

If a network failure occurs during the migration phase of the cloning process, the P2V Assistant does not stop the processes.

In the event of a clone and system reconfiguration together, error messages are displayed during the system reconfiguration phase:

System Reconfiguration Failed: Unable to locate system hive.
Exception in ShutdownVstorDisk from VieLib.Vielocator: error reading drive layout: Data error (Cyclic redundancy check).

Rerun the P2V Assistant process if a network error occurs during the cloning phase.

High Encryption Service Pack on NT 4

File version mismatch errors are displayed during a system reconfiguration of an NT 4 system with High Encryption Service Pack 4.

This is error is specific to the filename of the service pack only.

The error does not occur with Service Pack 5 or Service Pack 6.

Change the name of the high encryption service pack filename, Nt4sp4i.128.exe, to the name expected by the P2V Assistant, that is, sp4i386.exe.

Note: This does not change the encryption level of the Service Pack, only the name the P2V Assistant uses to apply it.

NT 4 Systems with Connectix Virtual PC Additions Errors

Connectix Virtual PC Additions might blue screen in a cloned virtual machine.

Uninstall the Additions and rerun the cloning and system reconfiguration processes.

Boot Error When Target Disk Accessed Through a Network Share

When the target disk for a clone or system reconfiguration process is a .vmdk formatted file and is stored on a network mounted (shared) drive, the virtual machine generates boot errors upon startup.

Cancel the error message(s) and reboot the virtual machine.

NTDETECT Error with NT 4 Systems

There are two possible reasons for this error.

  • The first partition on the system is smaller than 32MB and was cloned using a tool such as PowerQuest DiskImagePro.
  • An NT 4 system has a machine specific system partition in the first partition, for example, Compaq Smart Start partitions or HP/Dell utilities partitions. This error is displayed during startup.

If the error is due to a small first partition combined with cloning using a third party tool such as PowerQuest, then resize the first partition to greater than 32MB using a tool like PowerQuest Partition Magic.

If the error is due to a machine specific system partition, perform the following:

  • Delete the machine specific system partition and edit the boot.ini file on the cloned machine
  • Reduce all the 'partition' numbers for all entries by 1.

One way to delete the partition is to use the P2V Assistant Boot CD itself to delete the partition from the cloned image.

To delete a partition using the P2V Assistant Boot CD:

  1. Attach the cloned disk in a virtual machine.
  2. Boot the virtual machine with the P2V Assistant Boot CD.
  3. When the Welcome screen is displayed, press ALT+F2 to switch terminals on the boot CD.
  4. Login as root. No password is required.
  5. Type fdisk /dev/sda.
    This example assumes the cloned disk is the first SCSI disk on the virtual machine being used. If it is the second disk then change the entry accordingly, for example to /dev/sdb and so on.
  6. Type p.
    This displays all the partitions of the selected disk to confirm you are working on the right disk.
  7. Type d to delete a partition.
  8. Select 1 to delete the first partition.
  9. Type w to save the changes and quit fdisk.
  10. Shut down the virtual machine.

Then make the changes to the boot.ini file on the cloned disk:

  1. Attach the cloned disk as a second disk in a helper virtual machine, running another working operating system (Windows NT 4 or 2000) on the first disk.
  2. Boot using the operating system on the first disk.
  3. Open the boot.ini file on the second cloned disk.
  4. Find all entries of the form partition(). Reduce the number by 1 for all the entries in the boot.ini file.
  5. Close and save the file.
  6. Shut down the virtual machine.

The cloned NT 4 disk should no longer give the NTDETECT failure error and can be booted in its own virtual machine.

Additional Troubleshooting Resources

The following files can give you additional information about a problem that you are seeing. However, they are mainly intended to be used by VMware personnel for debugging.

  • For Boot CD only support refer to the bootcdlog.txt file.

    Whenever a Source machine is booted with the P2V Assistant Boot CD, a support file is generated and stored in /etc/bootcdlog.txt.

  • For application or cloned virtual machine support refer to the P2V Assistant .sup file for the session that corresponds with the bootcdlog.txt.

    The P2V Assistant Boot CD Troubleshooting Tips screen lists the path to this support file and instructions on how to locate it. This file is available if you used the P2V Assistant to create a clone.

    The support file is in the form:
    for example:

    The file is located in the system's temporary directory, which on most systems will be something similar to C:\Documents and Settings\username\Local Settings\Temp. It can be found by typing %temp% in the explorer address bar.