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
Procedure
u
Save the Sysprep files that correspond to the source operating system to the specified location on the
machine where Converter Standalone server runs.
Option Description
Windows Server 2003 (32bit)
The Sysprep files Location for Windows: %ALLUSERSPROFILE
%\Application Data\VMware\VMware vCenter Converter
Standalone\sysprep\svr2003
Windows Server 2003 (64bit)
The Sysprep files Location for Windows: %ALLUSERSPROFILE
%\Application Data\VMware\VMware vCenter Converter
Standalone\sysprep\svr2003-64
Windows XP (32bit)
The Sysprep files Location for Windows: %ALLUSERSPROFILE
%\Application Data\VMware\VMware vCenter Converter
Standalone\sysprep\xp
Windows XP (64bit)
The Sysprep files Location for Windows: %ALLUSERSPROFILE
%\Application Data\VMware\VMware vCenter Converter
Standalone\sysprep\xp-64
What to do next
You can now customize Windows Server 2003 (32bit and 64bit) and Windows XP (32bit and 64bit) guest
operating systems by using the Conversion or the Configuration wizard.
Limitations Related to Creating Snapshots of Windows Sources
Converter Standalone uses VSS snapshots to save the state of source volumes during hot cloning of physical
and virtual machines that run Windows. VSS snapshots are also used to synchronize the destination virtual
machine with the source machine after the initial conversion. Some of the VSS-related issues are inherited in
Converter Standalone and can prevent the proper completion of your conversion tasks.
Read the limitations listed in Table 2-11 before you initiate a conversion task.
If your conversion task fails with an VSS-related error message, you can check the table for possible reasons
and workarounds.
Table 2-11. VSS Snapshotting Limitations
VSS Limitations Error Messages Workarounds
For all operating systems that
support volume-based cloning,
you need at least one NTFS
volume for VSS to work.
There is no workaround for this
limitation.
VSS under Windows Server 2008
does not support FAT and FAT32.
Deselect all FAT and FAT32
volumes on the View/Edit
Options page of the
vCenter Converter wizards.
VSS under Windows Server 2008
does not support unformatted or
unrecognized volumes.
Failed to create VSS snapshot of source
volume. Error code :2147754764
(0x8004230C)
n
Format all unformatted or
unrecognized volumes and
try the conversion again.
n
Deselect all unformatted or
unrecognized volumes while
setting up the conversion task
in the Data to copy pane of the
View/Edit Options page.
Chapter 2 System Requirements
VMware, Inc. 29