4.3
Table Of Contents
- VMware vCenter Converter Standalone User's Guide
- Contents
- Updated Information
- About This Book
- Introduction to VMware vCenter Converter Standalone
- System Requirements
- Supported Operating Systems
- Installation Space Requirements
- Supported Source Types
- Supported Destination Types
- Configuring Permissions for VirtualCenter 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
- 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
- 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 Task
- Copy All Disks to the Destination
- Create a Linked Clone
- Edit the Number of Processors
- 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 Task
- 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 Task
- Uninstall Converter Standalone Agent from the Source Machine
- Review the Summary and Submit the Conversion Task
- 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 Task
- Managing Conversion and Configuration Tasks
- Index
Table 2-5. Supported Destinations
Destination Type Supported Versions
VMware Infrastructure virtual machines Managed destinations
n
ESX Server 3.5, 4.0, and 4.1
n
ESXi 3.5, 4.0, and 4.1
n
vCenter Server 2.5, 4.0, and 4.1
VMware Hosted virtual machines Hosted destinations
n
VMware Workstation 5.x, 6.x, and 7.x
n
VMware Fusion 1.x, 2.x, and 3.0
n
VMware Player 1.x, 2.x, and 3.0
n
VMware Server 1.x and 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.
Configuring Permissions for VirtualCenter Users
To convert virtual machines to vCenter with Converter Standalone, you must have certain vCenter permissions
set at the datacenter level.
n
Datastore.Allocate Space
n
Virtual machine.Inventory.Create new
n
Virtual machine.Configuration.Add new disk
n
Virtual Machine.Interaction.Power On (needed only if you choose to power on the destination virtual
machine after conversion)
n
Virtual Machine.Provisioning.Allow Disk Access
n
Resource.Assign Virtual Machine To Resource Pool
n
Network.Assign network (needed only if you plan to connect the destination virtual machine to a
network)
For more information about setting permissions, see the vSphere Datacenter Administration Guide.
Support for IPv6 in Converter Standalone
Converter Standalone supports both IPv4 and IPv6 Internet protocols with several limitations.
Internet Protocol version 6 (IPv6 or IPng) is the successor to Internet Protocol version 4 (IPv4), which is the
currently used protocol for assigning IP addresses to computers on the Internet. IPv6 was adopted to overcome
the expected exhaustion of IPv4 addresses that might be caused by the constantly increasing number of
computers on the Internet.
While IPv4 uses 32bit addresses, IPv6 uses 128bit. IPv6 addresses can have different formats or notations.
n
1040:0:0:0:0:0:0:1
n
1040::1
n
21DA:00D3:0010:2F3B:02AA:00FF:FE28:9C5A
n
[2001:0db8:85a3:08d3:1319:8a2e:0370:7344]:443
Converter Standalone supports all IPv6 notations for all components of the system.
n
Converter Standalone installer
n
Converter Standalone client
VMware vCenter Converter Standalone User's Guide
26 VMware, Inc.