5.5
Table Of Contents
- VMware vCenter Converter Standalone User's Guide
- Contents
- About This Book
- Introduction to VMware vCenter Converter Standalone
- Migration with Converter Standalone
- Converter Standalone Components
- Cloning and System Configuration of Physical Machines
- Types of Data Cloning Operations
- Using Converter Standalone with Virtual Machine Sources and System Images
- System Settings Affected by Conversion
- Changes to Virtual Hardware After Virtual Machine Migration
- System Requirements
- Supported Operating Systems
- Supported Firmware Interfaces
- Supported Source Types
- Supported Destination Types
- Supported Source Disk Types
- Supported Destination Disk Types
- Support for IPv6 in Converter Standalone
- Installation Space Requirements
- Screen Resolution Requirements
- Configuring Permissions for vCenter Users
- TCP/IP and UDP Port Requirements for Conversion
- Requirements for Remote Hot Cloning of Windows Operating Systems
- Conversion Limitations
- Installing and Uninstalling Converter Standalone
- Perform a Local Installation on Windows
- Perform a Client-Server Installation in Windows
- Perform a Command-Line Installation in Windows
- Command-Line Options for Windows Installation
- Modify Converter Standalone in Windows
- Repair Converter Standalone in Windows
- Uninstall Converter Standalone in Windows
- Connect to a Remote Converter Standalone Server
- Convert a Physical or Virtual Machine
- Start the Wizard for a Conversion
- Select a Source Machine to Convert
- Select a Powered On Windows Machine to Convert
- Select a Powered On Linux Machine to Convert
- Select an ESX/ ESXi or vCenter Server Virtual Machine to Convert
- Select a VMware Hosted Virtual Machine to Convert
- Select a Backup Image or a Third-Party Virtual Machine to Convert
- Select a Hyper-V Server Virtual Machine to Convert
- Select a Destination for the New Virtual Machine
- Configure the Hardware of the Destination Virtual Machine
- Organize the Data to Be Copied on the Destination Machine
- Resize a Volume
- Change a Volume Cluster Size
- Exclude a Source Volume from the Conversion Process
- Move a Volume to a Different Virtual Disk
- Select the Destination Datastore for a Source Volume
- Add a Virtual Disk
- Set Up a Virtual Disk as a Logical-Volume Group Container
- Move a Disk to a Different Datastore
- Create an Expandable Disk on a Managed Destination
- Create an Expandable Disk on a Hosted Destination
- Exclude a Source Disk from the Conversion Process
- Copy All Disks to the Destination
- Create an Optimized Partition Layout
- Create a Linked Clone
- Edit the Number of Processor Sockets and Cores
- Allocate Memory for the Destination Virtual Machine
- Select a Disk Controller for the Destination Virtual Machine
- Configure the Network Settings of the Destination Virtual Machine
- Configure the Network for the Helper Virtual Machine
- Organize the Data to Be Copied on the Destination Machine
- Configure the Software on the Destination Virtual Machine
- Configure the Conversion Job
- Set the Startup Mode for Destination Services
- Stop Services Running on the Source Machine
- Synchronize the Destination Machine with Changes Made to the Source Machine
- Power Off the Source Machine After Conversion
- Power On the Destination Virtual Machine After Conversion
- Limit the Amount of Resources Used by the Conversion Job
- Uninstall Converter Standalone Agent from the Source Machine
- Review the Summary and Submit the Conversion Job
- Configure Virtual Machines
- Save Sysprep Files
- Start the Configuration Wizard
- Select a Source Machine to Configure
- Select the Options to Configure
- Review and Submit the Configuration Job
- Manage Conversion and Configuration Jobs and Tasks
- Index
Convert a Physical or Virtual Machine 5
You can create a conversion job to convert a physical or virtual machine to a variety of destinations. You can
convert physical machines, VMware virtual machines, third-party backup images and virtual machines, and
Hyper-V Server virtual machines into VMware standalone virtual machines or virtual machines that
vCenter Server manages.
The approach you take for creating the conversion job is determined by the type of source and the type of
destination that you select.
Source type
A powered on physical or virtual machine, a vSphere virtual machine
running on an ESX/ESXi host, a standalone virtual machine, or a third-party
backup image.
Standalone virtual machines include VMware virtual machines, and third-
party virtual machines and backup images, such as VMware Workstation,
Acronis True Image, Microsoft Virtual PC, Symantec Backup Exec
Server Recovery (formerly known as LiveState Recovery),
LiveState Recovery, StorageCraft, Parallels Desktop for Microsoft Windows
and Mac OS, Parallels Workstation, and Norton Ghost (only .sv2i) images.
For a complete list of supported source types and product versions, see
“Supported Source Types,” on page 19.
Destination type
ESX/ESXi host, ESX/ESXi host that vCenter Server manages, or a VMware
standalone virtual machine.
For a complete list of supported destination types and product versions, see
“Supported Destination Types,” on page 20.
Procedure
1 Start the Wizard for a Conversion on page 42
The Conversion wizard guides you through the steps of creating a conversion job.
2 Select a Source Machine to Convert on page 42
You can select from several source options for the type of machine to convert.
3 Select a Destination for the New Virtual Machine on page 48
When you set up a conversion job, you must select a destination for the new virtual machine.
4 Configure the Hardware of the Destination Virtual Machine on page 51
You can configure the virtual hardware resources that the destination virtual machine uses.
5 Configure the Software on the Destination Virtual Machine on page 64
You can configure the guest operating system so that it is ready to operate in a virtual environment.
VMware, Inc.
41