4.0.1
Table Of Contents
- User's Guide
- Contents
- Updated Information
- About This Book
- Introduction
- Migration with Converter Standalone
- Converter Standalone Components
- Converter Standalone Features
- System Requirements
- Supported Operating Systems
- Installation Space Requirements
- Supported Source Types
- Supported Destination Types
- Restoring VCB Images in Converter Standalone
- How Conversion Affects the Source Settings When They Are Applied to the Destination
- Changes That Conversion Causes to Virtual Hardware
- TCP/IP Port Requirements for Conversion
- Common Requirements for Remote Hot Cloning of Windows Operating Systems
- Installing and Uninstalling VMware vCenter Converter Standalone
- Install Converter Standalone in Windows
- Uninstall, Modify, or Repair Converter Standalone in Windows
- Perform a Command-Line Installation in Windows
- Command-Line Options for Windows Installation
- Perform a Local Installation in Linux
- Perform a Client-Server Installation in Linux
- Uninstall Converter Standalone in Linux
- Modify or Repair Converter Standalone in Linux
- Connect to a Remote Converter Standalone Server
- Converting Machines
- Convert a Machine
- Start the Wizard for a Conversion
- Select a Source to Convert
- Select a Destination for the New Virtual Machine
- View Setup Options for a New Virtual Machine
- Select the Destination Folder
- Organizing the Data to Copy to the Destination Machine
- Distribute Disks over Several Datastores
- Distribute Volumes over Several Datastores
- Create or Delete a Target Disk
- Move a Source Volume to a Target Virtual Disk
- Modify the Settings in the Source Volumes List
- Change the Target Datastore for a Destination Virtual Disk
- Create a Thin Provisioned Disk
- Create a Linked Clone
- Change Device Settings on the New Virtual Machine
- Change Network Connections on the Destination
- Control the Status of Windows Services During Conversion
- Advanced Customization Options
- Synchronize the Source with the Destination Machine
- Adjust the Post-Conversion Power State
- Install VMware Tools
- Customize the Guest Operating System
- Edit the Destination Computer Information
- Enter the Windows License Information
- Set the Time Zone
- Set Up the Network Adapters
- Assign a Workgroup or Domain Details
- Remove System Restore Checkpoints
- Set Up the Network for the Helper Virtual Machine
- Customize a VMware Infrastructure Virtual Machine
- Customize a Standalone or Workstation Virtual Machine
- Customize a Virtual Appliance
- Configure the Product Properties of an Exported Virtual Appliance
- View the Summary of a Conversion Task
- Convert a Machine
- Configuring VMware Virtual Machines
- Configure a Virtual Machine
- Save Sysprep Files
- Select a Source to Configure
- Select the Options to Configure
- Customize a Virtual Machine’s Guest Operating System
- Edit the Computer Information of a Configured Virtual Machine
- Enter the Windows License Information of a Configured Virtual Machine
- Set the Time Zone of a Configured Virtual Machine
- Set Up the Network Adapters of a Configured Virtual Machine
- Assign a Workgroup or Domain Details of a Configured Virtual Machine
- View the Summary of a Configuration Task
- Configure a Virtual Machine
- Managing Conversion and Configuration Tasks
- Glossary
- Index
Changes That Conversion Causes to Virtual Hardware
Most migrated applications function correctly in the VMware virtual machine because their configuration and
data files have the same location as the source virtual machine. Applications might not work if they depend
on specific characteristics of the underlying hardware such as the serial number or the device manufacturer.
The following hardware changes might occur after virtual machine migration:
n
CPU model and serial numbers (if activated) can be different after the migration. These numbers
correspond to the physical computer hosting the VMware virtual machine.
n
Ethernet adapter can be different (AMD PCNet or VMXnet) with a different MAC address. Each interface
IP address must be individually reconfigured.
n
Graphics card can be different (VMware SVGA card).
n
The number of disks and partitions remains the same, but each disk device can have a different model
and different manufacturer strings.
n
Primary disk controllers can be different from the source machine’s controllers.
n
Applications might not work if they depend on devices that are not available from within a virtual
machine.
TCP/IP Port Requirements for Conversion
Converter Standalone uses specific ports in the conversion process.
For a list of required TCP/IP ports during conversion, see Table 2-9.
Table 2-9. Converter Standalone Port Requirements
Communication Path Port
Converter Standalone server to remote Windows powered-on machine 445, 139, 9089
Converter Standalone server to remote Linux powered-on machine 22
Helper virtual machine to remote Linux powered-on machine 22
Converter Standalone to a VMware vCenter Server 443
Converter Standalone to ESX 3.x 443
Converter Standalone server to a helper virtual machine 443
Powered-on machine to a VMware vCenter Server 443
Powered-on machine to ESX 3.x 443, 902
Common Requirements for Remote Hot Cloning of Windows Operating
Systems
The following information can help you avoid issues related to permissions and network access when you
perform hot cloning of Windows operating systems.
To ensure successful remote hot cloning of Windows platforms, verify the following items on the source
machine before you start the application:
n
Ensure that Simple File Sharing is turned off.
n
Ensure that file and printer sharing is not blocked by Windows Firewall.
User's Guide
26 VMware, Inc.