VMware CONVERTER STANDALONE 4.3 User manual

VMware vCenter Converter Standalone
User's Guide
vCenter Converter Standalone 4.3
This document supports the version of each product listed and
supports all subsequent versions until the document is replaced
by a new edition. To check for more recent editions of this
document, see http://www.vmware.com/support/pubs.
EN-000369-01

VMware vCenter Converter Standalone User's Guide
2 VMware, Inc.
You can find the most up-to-date technical documentation on the VMware Web site at:
http://www.vmware.com/support/
The VMware Web site also provides the latest product updates.
If you have comments about this documentation, submit your feedback to:
[email protected]
Copyright ©2008–2010 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and
intellectual property laws. VMware products are covered by one or more patents listed at
http://www.vmware.com/go/patents.
VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks
and names mentioned herein may be trademarks of their respective companies.
VMware, Inc.
3401 Hillview Ave.
Palo Alto, CA 94304
www.vmware.com

Contents
Updated Information 5
About This Book 7
1Introduction to VMware vCenter Converter Standalone 9
Migration with Converter Standalone 10
Converter Standalone Components 10
Cloning and System Configuration of Physical Machines 11
Types of Data Cloning Operations 16
Using Converter Standalone with Virtual Machine Sources and System Images 18
System Settings Affected by Conversion 19
Changes to Virtual Hardware 19
2System Requirements 21
Supported Operating Systems 21
Installation Space Requirements 22
Supported Source Types 23
Supported Destination Types 25
Configuring Permissions for VirtualCenter Users 26
Support for IPv6 in Converter Standalone 26
TCP/IP and UDP Port Requirements for Conversion 27
Requirements for Remote Hot Cloning of Windows Operating Systems 28
3Installing and Uninstalling Converter Standalone 33
Perform a Local Installation on Windows 33
Perform a Client-Server Installation in Windows 34
Perform a Command-Line Installation in Windows 35
Command-Line Options for Windows Installation 36
Modify Converter Standalone in Windows 37
Repair Converter Standalone in Windows 38
Uninstall Converter Standalone in Windows 38
Connect to a Remote Converter Standalone Server 39
4Convert a Physical or Virtual Machine 41
Start the Wizard for a Conversion 42
Select a Source Machine to Convert 42
Select a Destination for the New Virtual Machine 48
Configure the Hardware of the Destination Virtual Machine 51
Configure the Software on the Destination Virtual Machine 62
Configure the Conversion Task 67
Review the Summary and Submit the Conversion Task 73
VMware, Inc. 3

5Configure Virtual Machines 75
Save Sysprep Files 75
Start the Configuration Wizard 76
Select a Source Machine to Configure 76
Select the Options to Configure 79
Review and Submit the Configuration Task 83
6Managing Conversion and Configuration Tasks 85
Manage Tasks in the Task List 85
Index 91
VMware vCenter Converter Standalone User's Guide
4 VMware, Inc.

Updated Information
This VMware vCenter Converter Standalone User's Guide is updated with each release of the product or when
necessary.
This table provides the update history of the VMware vCenter Converter Standalone User's Guide.
Revision Description
EN-000369-01 In Table 2-3, the formatting for Microsoft VHD sources is corrected for clarity.
EN-000369-00 Initial release.
VMware, Inc. 5

VMware vCenter Converter Standalone User's Guide
6 VMware, Inc.

About This Book
The VMware vCenter Converter Standalone User's Guide provides information about installing and using
VMware® vCenter Converter Standalone 4.3.
Intended Audience
This book is intended for users who want to do the following:
nInstall, upgrade, or use Converter Standalone
nNonintrusively copy and transform physical machines into VMware virtual machines that VMware
vCenter manages
The material in this book is written for information systems engineers, software developers, QA engineers,
trainers, salespeople who run demonstrations, and anyone who wants so create virtual machines.
VMware Technical Publications Glossary
VMware Technical Publications provides a glossary of terms that might be unfamiliar to you. For definitions
of terms as they are used in VMware technical documentation, go to
http://www.vmware.com/support/pubs.
Document Feedback
VMware welcomes your suggestions for improving our documentation. If you have comments, send your
feedback to [email protected].
VMware, Inc. 7

Technical Support and Education Resources
The following technical support resources are available to you. To access the current version of this book and
other books, go to http://www.vmware.com/support/pubs.
Online and Telephone
Support
To use online support to submit technical support requests, view your product
and contract information, and register your products, go to
http://www.vmware.com/support.
Customers with appropriate support contracts should use telephone support
for the fastest response on priority 1 issues. Go to
http://www.vmware.com/support/phone_support.html.
Support Offerings To find out how VMware support offerings can help meet your business needs,
go to http://www.vmware.com/support/services.
VMware Professional
Services
VMware Education Services courses offer extensive hands-on labs, case study
examples, and course materials designed to be used as on-the-job reference
tools. Courses are available onsite, in the classroom, and live online. For onsite
pilot programs and implementation best practices, VMware Consulting
Services provides offerings to help you assess, plan, build, and manage your
virtual environment. To access information about education classes,
certification programs, and consulting services, go to
http://www.vmware.com/services.
VMware vCenter Converter Standalone User's Guide
8 VMware, Inc.

Introduction to VMware vCenter
Converter Standalone 1
VMware® vCenter Converter Standalone is a scalable solution to convert virtual and physical machines to
VMware virtual machines. You can also configure existing virtual machines in your vCenter Server
environment.
Converter Standalone 4.3 eases the exchange of virtual machines among the following products.
nVMware hosted products can be both conversion sources and conversion destinations.
nVMware Workstation
nVMware Fusion™
nVMware Server
nVMware Player
nVirtual machines running on an ESX instance that vCenter Server manages can be both conversion sources
and conversion destinations.
nVirtual machines running on unmanaged ESX hosts can be both conversion sources and conversion
destinations.
This chapter includes the following topics:
n“Migration with Converter Standalone,” on page 10
n“Converter Standalone Components,” on page 10
n“Cloning and System Configuration of Physical Machines,” on page 11
n“Types of Data Cloning Operations,” on page 16
n“Using Converter Standalone with Virtual Machine Sources and System Images,” on page 18
n“System Settings Affected by Conversion,” on page 19
n“Changes to Virtual Hardware,” on page 19
VMware, Inc. 9

Migration with Converter Standalone
Migration with Converter Standalone involves converting physical machines, virtual machines, and system
images for use in VMware hosted and managed products.
You can convert virtual machines that vCenter Server manages for use in other VMware products. You can
use Converter Standalone to perform a number of conversion tasks.
nImport running remote physical and virtual machines as virtual machines to standalone ESX/ESXi or
ESX/ESXi hosts that vCenter Server manages.
nImport virtual machines hosted by VMware Workstation or Microsoft Hyper-V Server to ESX/ESXi hosts
that vCenter Server manages.
nImport third-party backup or disk images to ESX/ESXi hosts that vCenter Server manages.
nExport virtual machines managed by vCenter Server hosts to other VMware virtual machine formats.
nConfigure virtual machines managed by vCenter Server so that they are bootable, and to install VMware
Tools or customize their guest operating systems.
nCustomize the guest operating systems of virtual machines in the vCenter Server inventory (for example,
change the host name or network settings).
nReduce the time needed to set up new virtual machine environments.
nMigrate legacy servers to new hardware without reinstalling operating systems or application software.
nPerform migrations across heterogeneous hardware.
nReadjust volume sizes and place volumes on separate virtual disks.
Converter Standalone Components
The Converter Standalone application consists of Converter Standalone server, Converter Standalone worker,
Converter Standalone client, and Converter Standalone agent.
Converter Standalone
server
Enables and performs the import and export of virtual machines. The
Converter Standalone server comprises two services, Converter Standalone
server and Converter Standalone worker. The Converter Standalone worker
service is always installed with the Converter Standalone server service.
Converter Standalone
agent
The Converter Standalone server installs the agent on Windows physical
machines to import them as virtual machines. You can choose to remove the
Converter Standalone agent from the physical machine automatically or
manually after the import is complete.
Converter Standalone
client
The Converter Standalone server works with the Converter Standalone client.
The client component consists of the Converter Standalone user interface,
which provides access to the Conversion and the Configuration wizards, and
allows you to manage the conversion and the configuration tasks.
VMware vCenter
Converter Boot CD
The VMware vCenter Converter Boot CD is a separate component that you can
use to perform cold cloning on a physical machine. Converter Standalone 4.3
does not provide a Boot CD, but you can use previous versions of the Boot CD
to perform cold cloning. See “Prepare for Cold Cloning,” on page 15.
VMware vCenter Converter Standalone User's Guide
10 VMware, Inc.

Cloning and System Configuration of Physical Machines
When you convert a physical machine, Converter Standalone uses cloning and system reconfiguration steps
to create and configure the destination virtual machine so that it works successfully in the vCenter Server
environment. Because the migration process is nondestructive to the source, you can continue to use the
original source machine after the conversion completes.
Cloning is the process of copying the source physical disks or volumes for the destination virtual machine.
Cloning involves copying the data on the source machine’s hard disk and transferring that data to a destination
virtual disk. The destination virtual disk might have a different geometry, size, file layout, and other
characteristics, so the destination virtual disk might not be an exact copy of the source disk.
System reconfiguration adjusts the migrated operating system to enable it to function on virtual hardware.
If you plan to run an imported virtual machine on the same network as the source physical machine, you must
modify the network name and IP address on one of the machines, so that the physical and virtual machines
can coexist. Besides, you must make sure that the Windows source machine and the destination virtual machine
have different computer names.
NOTE You cannot move original equipment manufacturer (OEM) licenses between physical machines. The
license is attached to the server when you purchase it from the OEM and cannot be reassigned. You can only
reassign retail and volume licenses to new physical servers. If you migrate an OEM Windows image, you must
have a Windows Server Enterprise or Datacenter Edition license to run multiple virtual machines.
Hot and Cold Cloning of Physical Machines
Although Converter Standalone 4.3 supports only hot cloning, you can still perform cold cloning by using the
VMware Converter 4.1.x Boot CD. Depending on your virtual environment, you can choose to use hot or cold
cloning.
Hot cloning, also called live cloning or online cloning, entails converting the source machine while it is running
its operating system. Hot cloning lets you clone machines without shutting them down.
Because processes continue to run on the source machine during conversion, the resulting virtual machine is
not an exact copy of the source machine.
You can set Converter Standalone to synchronize the destination virtual machine with the source machine
after hot cloning. Synchronization is performed by transferring from the source to the destination the blocks
that were changed during the initial cloning period. To avoid loss of data on the destination virtual machine,
Converter Standalone can shut down certain Windows services before the synchronization. Based on your
settings, Converter Standalone shuts down the selected Windows services so that no critical changes occur on
the source machine while destination is being synchronized.
Converter Standalone can shut down the source machine and power on the destination machine when the
conversion process is complete. When combined with synchronization, this action allows seamless migration
of a physical machine source to a virtual machine destination. The destination machine takes over the source
machine operations with the least possible downtime.
NOTE When you hot clone dual-boot systems, you can clone only the default operating system to which the
boot.ini file points. To clone the nondefault operating system, change the boot.ini file to point to the other
operating system and reboot. After the other operating system is booted, you can hot clone it. If your second
operating system is Linux, you can boot it and clone it using the standard procedure for cloning Linux physical
machine sources.
Chapter 1 Introduction to VMware vCenter Converter Standalone
VMware, Inc. 11

Cold cloning, also called offline cloning, entails cloning the source machine when it is not running its operating
system. When you cold clone a machine, you reboot the source machine using a CD that has its own operating
system and the vCenter Converter application on it. Cold cloning allows you to create the most consistent copy
of the source machine because nothing changes on the source machine during the conversion. Cold cloning
leaves no footprint on the source machine, but requires you to have physical access to the source machine that
is being cloned.
When you cold clone a Linux source, the resulting virtual machine is an exact replica of the source machine
and you cannot configure the destination virtual machine. You must configure the destination virtual machine
after the cloning is complete.
Table 1-1 compares the hot and cold cloning modes.
Table 1-1. Hot and Cold Cloning Comparison
Comparison Criteria
Hot Cloning with Converter
Standalone 4.3
Cold Cloning with Converter
Enterprise 4.1.x
Licensing No license required with
VMware vCenter Converter
Standalone 4.3.
License file required for Enterprise
features of
VMware Converter Enterprise.
Required installation Full Converter Standalone installation
is required. As part of the cloning
process, Converter Standalone agent is
installed on the source machine
remotely.
No installation is required. All
components required for the conversion
are on the CD.
Supported sources Local and remote powered-on
physical or virtual machines.
Local powered-off physical or virtual
machines.
Advantages nDoes not require direct access to
the source machine.
nYou can clone the source machine
while it is running.
nCreates the most consistent copy of
the source machine.
nLeaves no footprint on the source
machine.
Disadvantages nApplications that constantly
modify files need to be VSS aware
to allow Converter Standalone to
create a consistent snapshot for
cloning.
nDynamic source disks are read but
not preserved during volume-
based conversions. Dynamic disks
are converted into basic volumes
on the target virtual machine.
nYou must power off the source
machine to clone it.
nRequires physical access to the
source machine.
nHardware detection and
configuration of Boot CD.
nConverter Standalone 4.x features
are not supported.
Use nTo clone running source machines
without shutting them down.
nTo clone unique hardware that the
Boot CD does not recognize.
nTo clone a system that Converter
Standalone does not support.
nTo preserve the exact disk layout in
the target.
nTo preserve logical volumes in
dynamic disks (Windows) or LVM
(Linux).
When to not use When you do not want anything to be
installed on the source system.
nWhen you want Linux P2V with
automatic reconfiguration.
nWhen you do not have physical
access to the source machine.
nWhen you cannot afford a long
downtime of the source system.
nTo perform synchronization after
cloning.
VMware vCenter Converter Standalone User's Guide
12 VMware, Inc.

Remote Hot Cloning of Physical Machine Sources That Are Running Windows
You can use the Conversion wizard to set up conversion tasks and Converter Standalone components perform
all of the cloning tasks.
The following workflow is an example of remote hot cloning in which the physical machine being cloned
experiences no downtime.
1 Converter Standalone prepares the source machine for the conversion.
Converter Standalone installs the agent on the source machine and the agent takes a snapshot of the source
volumes.
agent
vCenter Converter Standalone running
on Windows machine
powered-on
physical machine ESX/ESXi
source destination
network
snapshot
source
volumes
2 Converter Standalone prepares the virtual machine on the destination machine.
Converter Standalone creates a virtual machine on the destination machine and the agent copies volumes
from the source machine to the destination machine.
agent
vCenter Converter Standalone running
on Windows machine
powered-on
physical machine ESX/ESXi
copied
volumes
source destination
network
snapshot
VM
source
volumes
3 Converter Standalone completes the conversion process.
The agent installs the required drivers to allow the operating system to boot in a virtual machine and
personalizes the virtual machine (changes the IP information, for example).
Chapter 1 Introduction to VMware vCenter Converter Standalone
VMware, Inc. 13

agent
vCenter Converter Standalone running
on Windows machine
powered-on
physical machine ESX/ESXi
source destination
network
VM
source
volumes snapshot
reconfiguration
customization (optional)
4 Optionally, Converter Standalone uninstalls the agent from the source machine.
The virtual machine is ready to run on the destination server.
Remote Hot Cloning of Physical Machine Sources That Are Running Linux
The conversion process of physical machines that are running Linux operating systems differs from that of
Windows machines.
In Windows conversions, the Converter Standalone agent is installed on the source machine and the source
information is pushed to the destination.
In Linux conversions, no agent is deployed on the source machine. Instead, a helper virtual machine is created
and deployed on the destination ESX/ESXi host. The source data is then copied from the source Linux machine
to the helper virtual machine. After the conversion is complete, the helper virtual machine shuts down to
become the destination virtual machine the next time you power it on.
Converter Standalone supports conversion of Linux sources only to managed destinations.
VMware vCenter Converter Standalone User's Guide
14 VMware, Inc.

The following workflow demonstrates the principles of hot cloning physical machine sources that run Linux
to managed destinations.
1 Converter Standalone uses SSH to connect to the source machine and retrieves source information.
Converter Standalone creates an empty helper virtual machine based on your conversion task settings.
The helper virtual machine serves as a container for the new virtual machine during conversion. Converter
Standalone deploys the helper virtual machine on the managed destination, an ESX/ESXi host. The helper
virtual machine boots from a *.iso file that is located on the Converter Standalone server machine.
vCenter Converter Standalone
agent and server
Converter Standalone
agent deploys helper
virtual machine
powered-on Linux
machine ESX/ESXi
source destination
network
Helper
VM
source
volumes
2 The helper virtual machine powers on, boots from the Linux image, connects to the source machine
through SSH, and starts retrieving the selected data from the source. While you set up the conversion task,
you can select which source volumes to be copied to the destination machine.
vCenter Converter Standalone
agent and server
powered-on Linux
machine
data copied to the
helper virtual machine
ESX/ESXi
source destination
network
Helper
VM
source
volumes
3 Optionally, after data is copied, the destination virtual machine is reconfigured to allow the operating
system to boot in a virtual machine.
4 Converter Standalone shuts down the helper virtual machine. The conversion process is complete.
You can configure Converter Standalone to power on the newly created virtual machine after the
conversion is complete.
Prepare for Cold Cloning
Because Converter Standalone 4.3 does not support cold cloning, you must use the Boot CD of an earlier
vCenter Converter edition. The features supported on the Boot CD depend on the product version you choose.
When you cold clone a machine, you reboot the source machine from a CD that has its own operating system
and also includes the vCenter Converter application. You can find a detailed description of the cold cloning
process in the documentation of the Boot CD you select to use.
VMware vCenter Converter 4.1.x is not a free software product.
Chapter 1 Introduction to VMware vCenter Converter Standalone
VMware, Inc. 15

Procedure
1 To obtain a Boot CD, go to the VMware Download Web site and download the vCenter Converter 4.1.x
installation package.
2 Extract the Boot CD .iso file from the installation package.
3 Write the Boot CD .iso file on a CD.
What to do next
Follow the onscreen instructions to proceed with cold cloning.
Types of Data Cloning Operations
Converter Standalone supports disk-based cloning, volume-based cloning, and linked-cloning modes.
IMPORTANT Converter Standalone cannot detect any source volumes and file systems that are located on
physical disks larger than 2TB.
Table 1-2. Cloning Modes
Data Copy Types Application Description
Volume based Copy volumes from the source
machine to the destination machine.
Volume-based cloning is relatively
slow. File-level cloning is slower than
block-level cloning. Dynamic disks are
converted into basic volumes on the
target virtual machine.
Disk based Create copies of the source machines,
for all types of basic and dynamic
disks.
You cannot select which data to copy.
Disk-based cloning is faster than
volume-based cloning.
Linked clone Use to quickly check compatibility of
non-VMware images
For certain third-party sources, the
linked clone is corrupted if you power
on the source machine after the
conversion. Linked cloning is the fastest
(but incomplete) cloning mode that
Converter Standalone supports.
Volume-Based Cloning
During volume-based cloning, volumes from the source machine are copied to the destination machine.
Converter Standalone supports volume-based cloning for hot and cold cloning, and during the import of
existing virtual machines.
During volume-based cloning, all volumes in the destination virtual machine are converted to basic volumes,
regardless of their type in the corresponding source volume.
Volume-based cloning is performed at the file level or block level, depending on the destination volume size
that you select.
Volume-based cloning at
the file level
Performed when you select a size smaller than the original volume for NTFS
volumes or you choose to resize a FAT volume.
VMware vCenter Converter Standalone User's Guide
16 VMware, Inc.

Volume-based cloning at the file level is supported only for FAT, FAT32, NTFS,
ext2, ext3, and ReiserFS file systems.
Dynamic source disks are read but not preserved during volume-based
conversions. Dynamic disks are converted into basic volumes on the target
virtual machine.
Volume-based cloning at
the block level
Performed when you choose to preserve the size of the source volume or when
you specify a larger volume size for NTFS source volumes.
For certain cloning modes, Converter Standalone might not support some types of source volumes.
Table 1-3 shows the supported and nonsupported source volume types.
Table 1-3. Supported and Nonsupported Source Volumes
Cloning Mode Supported Source Volumes Nonsupported Source Volumes
Virtual machine conversion nBasic volumes
nAll types of dynamic volumes
nMaster boot record (MBR) disks
nRAID
nGUID partition table (GPT) disks
Powered-on machine conversion All types of source volumes that
Windows recognizes
Disk-Based Cloning
Converter Standalone supports disk-based cloning to import existing virtual machines.
Disk-based cloning transfers all sectors from all disks and preserves all volume metadata. The destination
virtual machine receives partitions of the same type, size, and structure, as the partitions of the source virtual
machine. All volumes on the source machine's partitions are copied as they are.
Disk-based cloning supports all types of basic and dynamic disks.
Full and Linked Clones
Clones can be full or linked depending on the amount of data copied from the source to the destination machine.
A full clone is an independent copy of a virtual machine that shares nothing with the parent virtual machine
after the cloning operation. Ongoing operation of a full clone is separate from the parent virtual machine.
Because a full clone does not share virtual disks with the parent virtual machine, full clones generally perform
better than linked clones. Full clones take longer to create than linked clones. Creating a full clone can take
several minutes if the files involved are large.
You can create a full clone by using any disk clone type other than the linked clone type.
A linked clone is a copy of a virtual machine that shares virtual disks with the parent virtual machine in an
ongoing manner. A linked clone is a fast way to convert and run a new virtual machine. You can create a linked
clone from the current state, or snapshot, of a powered-off virtual machine. This practice conserves disk space
and allows multiple virtual machines to use the same software installation.
All files available on the source machine at the moment of the snapshot continue to remain available to the
linked clone. Ongoing changes to the virtual disk of the parent do not affect the linked clone, and changes to
the disk of the linked clone do not affect the source machine. If you make changes to a source Virtual PC and
Virtual Server machines, or to LiveState images, the linked clone is corrupted and you cannot use it anymore.
A linked clone must have access to the source. Without access to the source, you cannot use a linked clone at
all.
For more information on how to create a linked clone, see “Create a Linked Clone,” on page 59.
Chapter 1 Introduction to VMware vCenter Converter Standalone
VMware, Inc. 17

Destination Disk Types
Depending on the destination you select, several destination disk types are available.
For detailed information on destination virtual disks types, see Table 1-4.
Table 1-4. Destination Disk Types
Destination Available Disk Types
VMware Infrastructure virtual machine Flat Copies the entire source disk size to the
destination, regardless of its used and
free space.
Thin For managed destinations that support
thin provisioning through GUI, creates
an expanding disk on the destination.
For example, if the source disk size is
10GB, but only 3GB is used, the created
destination disk is 3GB but can expand
to 10GB.
VMware Workstation or other VMware virtual machine Pre-
allocated
Copies the entire source disk size to the
destination, regardless of its used and
free space.
Not pre-
allocated
Creates an expanding disk on the
destination. For example, if the source
disk size is 20GB, but only 5GB is used,
the created destination disk is 5GB but
can expand to 20GB. Take this expansion
into account when you calculate the free
disk space on the destination datastore.
2GB Split
pre-
allocated
Splits the source disk into 2GB sections
on the destination.
2GB Split not
pre-
allocated
Creates 2GB sections on the destination
that include only the real used space on
the source disk. As the destination disk
grows, new 2GB sections are created to
accommodate the new data until the size
reaches that of the original source disk.
To support destination virtual disks on FAT file systems, divide the source data into 2GB files.
Using Converter Standalone with Virtual Machine Sources and System
Images
With Converter Standalone, you can convert virtual machines and system images, and configure VMware
virtual machines.
Converting virtual
machines
You can convert VMware virtual machines from and to Workstation,
VMware Player, VMware ACE, VMware Fusion, ESX, ESXi Embedded,
ESXi Installable, and VMware Server. You can also import virtual machines
from Microsoft Virtual Server and Virtual PC.
VMware vCenter Converter Standalone User's Guide
18 VMware, Inc.

To be able to run an imported VMware virtual machine and its source virtual
machine on the same network, you must modify the network name and IP
address on one of the virtual machines. Modifying the network name and IP
address allows the original and new virtual machines to coexist on the same
network.
Configuring virtual
machines
If the VMware virtual machines have disks that are populated by using a
backup of a physical host or by cold cloning, Converter Standalone prepares
the image to run on VMware virtual hardware. If you have used a third-party
virtualization software to create a virtual machine on an ESX host, you can use
Converter Standalone to reconfigure it. You can also reconfigure any operating
system installed on a multiboot machine if you have imported the virtual
machine to an ESX host. Before you reconfigure a multiboot machine, you must
change the boot.ini file.
System Settings Affected by Conversion
A VMware virtual machine that Converter Standalone creates contains a copy of the disk state of the source
physical machine, virtual machine, or system image. Some hardware-dependent drivers and sometimes the
mapped drive letters might not be preserved.
The following source computer settings remain unchanged:
nOperating system configuration (computer name, security ID, user accounts, profiles, preferences, and so
on)
nApplications and data files
nVolume serial number for each disk partition
Because the target and the source virtual machines or system images have the same identities (name, SID, and
so on), running them on the same network might result in conflicts. To redeploy the source virtual machine or
system image, make sure that you do not run the source and target images or virtual machines on the same
network at the same time.
For example, if you use Converter Standalone to test whether you can run a Virtual PC virtual machine as a
VMware virtual machine without first decommissioning the original Virtual PC machine, you must first resolve
the duplicate ID problem. You can resolve this problem by customizing the virtual machines in the
Conversion or the Configuration wizard.
Changes to Virtual Hardware
After conversion, most applications function correctly on the VMware virtual machine because their
configuration and data files have the same location as on the source virtual machine. However, applications
might not work if they depend on specific characteristics of the underlying hardware, such as the serial number
or the device manufacturer.
Table 1-5 contains hardware changes that might occur after virtual machine migration.
Table 1-5. Hardware Changes After Virtual Machine Migration
Hardware Behavior
CPU model and serial numbers Might change after migration if they are activated. They correspond to the physical
computer hosting the VMware virtual machine.
Ethernet adapters Might change (AMD PCNet or VMXnet) and have a different MAC address. The
IP address of each interface must be individually reconfigured.
Graphics cards Might change after migration (VMware SVGA card).
Chapter 1 Introduction to VMware vCenter Converter Standalone
VMware, Inc. 19

Table 1-5. Hardware Changes After Virtual Machine Migration (Continued)
Hardware Behavior
Disks and partitions The number of disks and partitions might change if you rearrange volumes during
the cloning process. Each disk device might have a different model and different
manufacturer strings.
Primary disk controllers Might differ from the source machine.
Applications might not work if they depend on devices that are not available within a virtual machine.
VMware vCenter Converter Standalone User's Guide
20 VMware, Inc.