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-2. Installation Space Requirements
Installation Component Disk Space Required
Disk Space Requirement for Decompressed
Files
Installation file 100MB 100MB
vCenter Converter client 25MB 25MB
vCenter Converter server 120MB 300MB
vCenter Converter agent 25MB 100MB
Screen Resolution Requirements
To display wizards properly, Converter Standalone requires a screen resolution of at least 1024x768 pixels.
Supported Source Types
With Converter Standalone, you can convert remote powered-on machines, powered-off VMware virtual
machines, Hyper-V virtual machines, and other third-party virtual machines and system images.
Table 2-3 shows the sources that Converter Standalone supports.
Table 2-3. Supported Sources
Source Type Sources
Powered-on machines
n
Remote Windows physical machines
n
Remote Linux physical machines
n
Local Windows physical machines
n
Windows virtual machines running on Hyper-V Server
n
Powered-on VMware virtual machines
n
VMware VCB backup images
VMware vCenter virtual
machines
Powered-off virtual machines managed by the following servers:
n
VirtualCenter 2.5
n
vCenter Server 4.0, 4.1, and 5.0
n
ESX Server 2.5.x (if VirtualCenter 2.5 or later manages ESX)
n
ESX Server 3.0, 3.5, 4.0, and 4.1
n
ESXi 3.5, 4.0, 4.1, and 5.0
VMware virtual machines Powered-off hosted virtual machines running on the following VMware products:
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.x
n
VMware Server 2.x
Chapter 2 System Requirements
VMware, Inc. 21