5.1
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
- 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 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
- 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 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
Converter Standalone supports all IPv6 notations for all components of the system.
n
Converter Standalone installer
n
Converter Standalone client
n
Converter Standalone agent
n
All destinations supported in Converter Standalone
Along with the higher security level and much larger address space, IPv6 brings about some compatibility
tasks that have not been resolved yet. For example, IPv4-only nodes cannot communicate directly with IPv6
nodes and need additional routing. This makes the end-to-end support of mixed IPv4 and IPv6 environments
precarious.
To reduce this complexity, Converter Standalone supports only pure IPv6 or IPv4 environments, where the
protection source, the protection destination, and the Converter Standalone server and agent must run the
same version of IP.
NOTE You cannot use IPv6 to customize the guest operating systems of virtual machines.
Installation Space Requirements
During installation, you can select the Converter Standalone components that you want to install. All
components require different amounts of free disk space to install.
Table 2-7 shows the disk space required to install Converter Standalone and its components.
Table 2-7. 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.
Configuring Permissions for vCenter Users
To convert virtual machines to vCenter Server machines with Converter Standalone, you must have certain
vCenter Server permissions set at the datacenter level.
To start using Converter Standalone, you need to set a number of minimum privileges at the datacenter level.
n
Datastore.Allocate space
n
Datastore.Browse datastore
n
Host.Local operations.Create virtual machine
n
Host.Local operations.Delete virtual machine
n
Host.Local operations.Reconfigure virtual machine
n
Network.Assign network (required only if you plan to connect the destination virtual machine to a
network)
Chapter 2 System Requirements
VMware, Inc. 23