5.0
Table Of Contents
- VMware vCenter Converter Standalone User's Guide
- Contents
- About This Book
- Introduction to VMware vCenter Converter Standalone
- System Requirements
- Supported Operating Systems
- Installation Space Requirements
- Screen Resolution Requirements
- Supported Source Types
- Supported Destination Types
- Restoring VCB Images in Converter Standalone
- Configuring Permissions for vCenter Users
- Support for IPv6 in Converter Standalone
- TCP/IP and UDP Port Requirements for Conversion
- Requirements for Remote Hot Cloning of Windows Operating Systems
- 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 Copy 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
- Specify 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 Copy 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
Table 2-5. Supported Destinations
Destination Type Supported Versions
VMware vCenter virtual machines Managed destinations
n
ESX Server 3.5, 4.0, and 4.1
n
ESXi 3.5, 4.0, 4.1, and 5.0
n
vCenter Server 2.5, 4.0, 4.1, and 5.0
VMware hosted virtual machines Hosted destinations
n
VMware Workstation 5.x, 6.x, 7.x, and 8.x
n
VMware Fusion 2.x, 3.x, and 4.x
n
VMware Player 2.x, and 3.0
n
VMware Server 2.x
NOTE For hosted destinations that reside on SMB or NFS shares, you must use volume-based cloning and
create 2GB disks that are not pre-allocated.
Restoring VCB Images in Converter Standalone
You can use VMware Consolidated Backup to back up all of the virtual machines of an entire ESX installation.
The backup is stored by using Workstation disks, a .vmx file, and a catalog file. Converter Standalone can restore
VCB images to ESX hosts and convert them to VMware standalone virtual machines.
Converter Standalone supports restore operations for VCB images of the source operating systems described
in “Supported Operating Systems,” on page 19.
Converter Standalone does not maintain the .nvram file or the VMware log files.
Converter Standalone does not read the original location settings from the catalog file. To restore to the same
location, find information such as datastore, host name, folder name, and resource pool in the catalog file and
specify it in the Conversion wizard. In addition, Converter Standalone does not read the original display name
from the catalog file. If you want to use the same name but do not remember it, you can look it up in the catalog
file. You can read the catalog file as a plain text file.
Information Not Preserved When Using Converter Standalone for Managed
Product Destinations
When you restore VCB images for managed product destinations (ESX hosts, for example), Converter
Standalone does not preserve certain hardware backing information from the original image, but rather
substitutes default settings.
Table 2-6 shows the areas that are affected.
Table 2-6. Changes to Hardware Information Because of Conversion
Affected Area Behavior
CD-ROM Defaults to the client device type.
Floppy Defaults to the client device type.
Network adapters Defaults to the list of network adapters in the GUI. The MAC address is not preserved. The destination
host regenerates the MAC address.
Serial port Defaults to the physical serial port on destination host machine.
Parallel port Defaults to the physical parallel port on destination host machine.
When you restore images, the Converter Standalone GUI does not preserve certain other virtual machine
properties from the original image, but substitutes default settings. Table 2-7 shows the affected areas.
VMware vCenter Converter Standalone User's Guide
24 VMware, Inc.