Disk based

Create copies of the source machines, for all types of basic and dynamic disks. Use to quickly check compatibility of non-VMware images

Linked clone

Volume-Based Cloning
During volume-based cloning, volumes from the source machine are copied to the destination machine. Converter Standalone supports volume-based cloning for hot and cold cloning, and during the import of existing virtual machines. During volume-based cloning, all volumes in the destination virtual machine are converted to basic volumes, regardless of their type in the corresponding source volume. Volume-based cloning is performed at the file level or block level, depending on the destination volume size that you select. Volume-based cloning at the file level Performed when you select a size smaller than the original volume for NTFS volumes or you choose to resize a FAT volume.
Volume-based cloning at the file level is supported only for FAT, FAT32, NTFS, ext2, ext3, and ReiserFS file systems. Dynamic source disks are read but not preserved during volume-based conversions. Dynamic disks are converted into basic volumes on the target virtual machine. Volume-based cloning at the block level Performed when you choose to preserve the size of the source volume or when you specify a larger volume size for NTFS source volumes.
For certain cloning modes, Converter Standalone might not support some types of source volumes. Table 1-3 shows the supported and nonsupported source volume types. Table 1-3. Supported and Nonsupported Source Volumes
Cloning Mode Virtual machine conversion Supported Source Volumes
Nonsupported Source Volumes
Basic volumes All types of dynamic volumes Master boot record (MBR) disks
RAID GUID partition table (GPT) disks
Powered-on machine conversion
All types of source volumes that Windows recognizes

Disk-Based Cloning

Converter Standalone supports disk-based cloning to import existing virtual machines. Disk-based cloning transfers all sectors from all disks and preserves all volume metadata. The destination virtual machine receives partitions of the same type, size, and structure, as the partitions of the source virtual machine. All volumes on the source machine's partitions are copied as they are. Disk-based cloning supports all types of basic and dynamic disks.

Full and Linked Clones

Clones can be full or linked depending on the amount of data copied from the source to the destination machine. A full clone is an independent copy of a virtual machine that shares nothing with the parent virtual machine after the cloning operation. Ongoing operation of a full clone is separate from the parent virtual machine. Because a full clone does not share virtual disks with the parent virtual machine, full clones generally perform better than linked clones. Full clones take longer to create than linked clones. Creating a full clone can take several minutes if the files involved are large. You can create a full clone by using any disk clone type other than the linked clone type. A linked clone is a copy of a virtual machine that shares virtual disks with the parent virtual machine in an ongoing manner. A linked clone is a fast way to convert and run a new virtual machine. You can create a linked clone from the current state, or snapshot, of a powered-off virtual machine. This practice conserves disk space and allows multiple virtual machines to use the same software installation. All files available on the source machine at the moment of the snapshot continue to remain available to the linked clone. Ongoing changes to the virtual disk of the parent do not affect the linked clone, and changes to the disk of the linked clone do not affect the source machine. If you make changes to a source Virtual PC and Virtual Server machines, or to LiveState images, the linked clone is corrupted and you cannot use it anymore. A linked clone must have access to the source. Without access to the source, you cannot use a linked clone at all. For more information on how to create a linked clone, see Create a Linked Clone, on page 59.

Destination Disk Types

Depending on the destination you select, several destination disk types are available. For detailed information on destination virtual disks types, see Table 1-4. Table 1-4. Destination Disk Types
Destination VMware Infrastructure virtual machine Available Disk Types Flat Copies the entire source disk size to the destination, regardless of its used and free space. For managed destinations that support thin provisioning through GUI, creates an expanding disk on the destination. For example, if the source disk size is 10GB, but only 3GB is used, the created destination disk is 3GB but can expand to 10GB. Copies the entire source disk size to the destination, regardless of its used and free space. Creates an expanding disk on the destination. For example, if the source disk size is 20GB, but only 5GB is used, the created destination disk is 5GB but can expand to 20GB. Take this expansion into account when you calculate the free disk space on the destination datastore. Splits the source disk into 2GB sections on the destination. Creates 2GB sections on the destination that include only the real used space on the source disk. As the destination disk grows, new 2GB sections are created to accommodate the new data until the size reaches that of the original source disk.
VMware Workstation or other VMware virtual machine
Preallocated Not preallocated
2GB Split preallocated 2GB Split not preallocated
To support destination virtual disks on FAT file systems, divide the source data into 2GB files.
Using Converter Standalone with Virtual Machine Sources and System Images
With Converter Standalone, you can convert virtual machines and system images, and configure VMware virtual machines. Converting virtual machines You can convert VMware virtual machines from and to Workstation, VMware Player, VMware ACE, VMware Fusion, ESX, ESXi Embedded, ESXi Installable, and VMware Server. You can also import virtual machines from Microsoft Virtual Server and Virtual PC.
To be able to run an imported VMware virtual machine and its source virtual machine on the same network, you must modify the network name and IP address on one of the virtual machines. Modifying the network name and IP address allows the original and new virtual machines to coexist on the same network. Configuring virtual machines If the VMware virtual machines have disks that are populated by using a backup of a physical host or by cold cloning, Converter Standalone prepares the image to run on VMware virtual hardware. If you have used a third-party virtualization software to create a virtual machine on an ESX host, you can use Converter Standalone to reconfigure it. You can also reconfigure any operating system installed on a multiboot machine if you have imported the virtual machine to an ESX host. Before you reconfigure a multiboot machine, you must change the boot.ini file.

Third-party virtual machines or system images

n n n n n n

Microsoft Virtual Server 2005 and 2005 R2 (.vmc)
Sources that run Windows 7 and Windows Server 2008 R2 can be converted to ESX 3.5 Update 5, ESX 4.0, or later destinations. ESX 3.5 Update 4 or earlier versions do not support Windows 7.
Conversion Limitations for Powered-On Machines
When you convert a powered-on machine, some conversion features might not be available for certain source operating systems. For a list of limitations dependent on the source operating system, see Table 2-4. Table 2-4. Limitations for Powered-On Machine Conversion
Source Operating System Windows XP and later Linux Limitations Synchronization is supported only for volume-based cloning at the block level.
Only volume-based cloning at the file level is supported. Only managed destinations are supported. You can convert multiboot virtual machines only if GRUB is installed as the boot loader. LILO is not supported. LVM logical volumes are converted to basic volumes on the destination virtual machine.
Conversion Limitations for VMware Virtual Machines
Certain limitations exist when you convert a VMware virtual machine. You must power off source virtual machines before you convert them. You can convert running virtual machines if you follow the procedure for converting powered-on machines.
Certain limitations are applicable when you convert Linux virtual machine sources.
Only disk-based cloning is supported for Linux guest operating systems. Configuration or customization is not supported for Linux guest operating systems. You cannot install VMware Tools on Linux guest operating systems.
Conversion Limitations for Third-Party Virtual Machines or System Images
Converter Standalone can convert third-party virtual machines, system images, ShadowProtect images, and BackupExec System Recovery images. These conversions have limitations.
Third-Party Virtual Machines and System Images
Third-party virtual machines and system images have the following limitations.

Virtual machines created with Macintosh versions of Virtual PC are not supported. The operating system on the source Virtual PC or Virtual Server virtual machine must be a Windows guest operating system supported by the destination VMware platform (for example, Workstation 5 or 6.0.x). For a list of supported operating systems, see the Guest Operating System Installation Guide. Converter Standalone supports Virtual PC and Virtual Server virtual machines with most Windows operating systems earlier than Windows NT 4.0 and with non-Windows operating systems (for example, Linux and DOS) only for cloning. Converter Standalone does not support configuring for these systems.
Parallels Virtuozzo containers are not supported.
ShadowProtect and Backup Exec System Recovery
ShadowProtect and Backup Exec System Recovery have the following limitations.
Dynamic disks are not supported. All images for the backup of a machine must be in a single folder. The source folder must not contain images that are not part of the backup. For volume-based cloning, all volumes in the disk up to the active and system volumes must be backed up. For example, if a disk has four partitions, 1 through 4, with partition 2 as the active volume and partition 3 as the system volume, the backup must include partitions 1 through 3. For incremental images, up to 16 incremental backups are supported. ShadowProtect images of systems with logical drives are not supported if the logical drive is also a system or active volume.
Supported Destination Types
With Converter Standalone, you can create virtual machines compatible with VMware hosted and managed products. Table 2-5 shows the destinations that Converter Standalone supports.
Table 2-5. Supported Destinations
Destination Type VMware Infrastructure virtual machines Supported Versions Managed destinations
ESX Server 3.5, 4.0, and 4.1 ESXi 3.5, 4.0, and 4.1 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.
Datastore.Allocate Space Virtual machine.Inventory.Create new Virtual machine.Configuration.Add new disk Virtual Machine.Interaction.Power On (needed only if you choose to power on the destination virtual machine after conversion) Virtual Machine.Provisioning.Allow Disk Access Resource.Assign Virtual Machine To Resource Pool Network.Assign network (needed only if you plan to connect the destination virtual machine to a network)

If you have Converter 3.0.x installed and your machine runs Windows Vista, uninstall Converter 3.0.x manually before you install Converter Standalone 4.3. If you have an earlier version of Converter Standalone agent on the system, uninstall Converter Standalone agent. Procedure 3 Download the latest version of Converter Standalone from the VMware Web site. In the local directory to which you downloaded the installer, check the number of the build, which is a part of the installer filename. At the command line, install Converter Standalone silently with the log file written to the temp directory.
VMware-converter-<build>.exe /s /v"/qn ADDLOCAL=ALL /l*v %TEMP%\vmconvservermsi.log"
For more command-line options, see Command-Line Options for Windows Installation, on page 36. What to do next You can use Converter Standalone to convert physical or virtual machine sources to virtual machine destinations.
Command-Line Options for Windows Installation
You can use the command-line installation options when you install Converter Standalone from the MS-DOS command prompt in Windows or by writing a Windows batch file (.bat). For a list of options to perform command-line installation, see Table 3-1. Table 3-1. Command-Line Options
Option /s /v"<params>" /qn /qb /qf /l*v <Logfile> /x ADDLOCAL="ALL" PROPERTY=<property value> VMCE_HTTP_PORT Action Does not display the Windows Installer version check. Passes parameters to the msiexec.exe file. Runs the msi command in silent mode. Runs the msi command in basic mode. Runs the msi command in full mode. Records login information in the file provided in <Logfile>. Uninstalls VMware vCenter Converter Standalone. Installs full package. The parameter is case-sensitive. Sets the value of a property to <property value>. Sets the HTTP port. The default is 80. Remote machines connect to the server through this port to download the Converter Standalone client. Set the HTTPS port. The default is 443. Remote Converter Standalone clients connect to this port on the server and submit conversion tasks. Sets an Agent port. The default is 9089. Remote Converter Standalone servers connect to this port to convert this machine.

VMCE_HTTPS_PORT

VMCE_AGENT_PORT
Modify Converter Standalone in Windows
To change the installed Converter Standalone agent or the communication ports for the Converter Standalone components, you must modify the Converter Standalone installaton. Prerequisites Make sure that you have Administrator privileges. Close the Converter Standalone application before you start the installer wizard. Procedure 1 To start the Converter Standalone installer, do one of the following:

Uninstall Converter Standalone in Windows
You can uninstall Converter Standalone by using the Microsoft Windows Add or Remove Programs utility from the Control Panel or by using the VMware vCenter Converter Standalone installer wizard. Prerequisites Make sure that you have Administrator privileges. Close the Converter Standalone application before you start the installer wizard.
Procedure 1 To start the Converter Standalone installer, do one of the following:
On the Welcome page of the installer wizard, click Next. On the Program Maintenance page, select Remove and click Next. On the Ready to Remove page, click Remove. On the Installation Completed page, click Finish. A prompt might ask you to restart your system.
Connect to a Remote Converter Standalone Server
You can use the Converter Standalone client to connect to a Converter Standalone server installed on a remote machine. Prerequisites Ensure that the Converter Standalone server and agent are installed on the remote machine. Procedure Start Converter Standalone. Follow the procedure that is applicable for your installation type.
Option Local installation Action a b c Client-server installation with remote access a b Select Administration > Connect to another server. On the Converter Standalone login page, select Enter the IP address or host name of the Converter Standalone server. Provide the IP address and Administrator credentials, and click Login. On the Converter Standalone login page, select Enter the IP address or host name of the Converter Standalone server. Provide the IP address and Administrator credentials, and click Login.
What to do next You can now use the remote Converter Standalone server to set up and manage conversion tasks.
Convert a Physical or Virtual Machine
You can create a conversion task to convert a physical or virtual machine to a variety of destinations. You can convert physical machines, VMware virtual machines, third-party backup images and virtual machines, and Hyper-V Server virtual machines into VMware standalone virtual machines or virtual machines that vCenter Server manages. The approach you take for creating the conversion task is determined by the type of source and the type of destination that you select. Source type A powered-on physical or virtual machine, a VMware Infrastructure virtual machine running on an ESX host, or a standalone virtual machine. Standalone virtual machines include VMware virtual machines, backup images, and third-party virtual machines such as VMware Workstation, VMware Server, Acronis True Image, Microsoft Virtual PC and Virtual Server, Symantec Backup Exec Server Recovery (formerly known as LiveState Recovery), LiveState Recovery, StorageCraft, Parallels Desktop for Microsoft Windows and Mac OS, Parallels Workstation, and Norton Ghost (only.sv2i) images. Supported Source Types, on page 23 contains a full list of supported source types and product versions. Destination type ESX host, ESX host that vCenter Server manages, or a VMware standalone virtual machine. Supported Destination Types, on page 25 contains a full list of supported destination types and product versions. Procedure 5 Start the Wizard for a Conversion on page 42 The Conversion wizard guides you through the steps of creating a conversion task. Select a Source Machine to Convert on page 42 You can select from several source options for the type of machine to convert. Select a Destination for the New Virtual Machine on page 48 When you set up a conversion task, you must select a destination for the new virtual machine. Configure the Hardware of the Destination Virtual Machine on page 51 You can configure the virtual hardware resources that the destination virtual machine uses. Configure the Software on the Destination Virtual Machine on page 62 You can configure the guest operating system so that it is ready to operate in a virtual environment.

(Optional) To refresh the Inventory, click Refresh. (Optional) To view more details about a machine, select it and click View source details. Click Next to proceed to the Destination System page.
What to do next On the Destination System page you can select the destination type for the new virtual machine.
Select a VMware Hosted Virtual Machine to Convert
You can convert a virtual machine created or used in a VMware hosted product, such as VMware Workstation, VMware Player, VMware Fusion, and VMware Server. Prerequisites Verify that your source machine is a supported VMware Desktop products virtual machine Supported Source Types, on page 23. If you plan to use a network path to locate the source, verify that the machine where Converter Standalone server runs has access to that network path. Power off the source machine before the conversion. Procedure On the Source System page of the Conversion wizard, select VMware Workstation or other VMware virtual machine from the Select source type drop-down menu. Locate the virtual machine source.
If you are connected to a remote Converter Standalone server, provide a network path to the source virtual machine file (.vmx) in the Virtual machine file text box. For example, \\server\virtual_machines\virtual_machine.vmx. If you are connected to a local Converter Standalone server, provide a network path or a local path to the.vmx file.
The file type choices are limited to VMware Workstation *.vmx files. 3 If you are connected to a remote Converter Standalone server, enter user credentials for accessing the source virtual machine. You do not have to provide user credentials if you are connected to a local Converter Standalone server. In such cases, Converter Standalone uses the Windows credentials to connect to the source machine. (Optional) To view more information about the selected source, click View source details Click Next to proceed to the Destination System page.
Select a Backup Image or a Third-Party Virtual Machine to Convert
You can select a backup image or a third-party virtual machine as the conversion source. Prerequisites Verify that your machine is a supported backup image or third-party virtual machine here Supported Source Types, on page 23. If you plan to use a network path to locate the source, verify that the machine where Converter Standalone server runs has access to that network path. Power off the source machine before the conversion.
Procedure On the Source System page, select Backup image or third-party virtual machine from the Select source type drop-down menu. Locate the source backup image or virtual machine file.
If you are connected to a remote Converter Standalone server, provide a valid network path to the source backup image or virtual machine file in the Virtual machine file text box. For example, \\server\backup_images\backup_image.pvs. If you are connected to a local Converter Standalone server, provide a network path or a local path to the source backup image or virtual machine file.

Select volumes to copy

Depending on the destination you select, several destination disk types are available. To support destination virtual disks on FAT file systems, divide the source data into 2GB files. For detailed information on destination virtual disks types, see Destination Disk Types, on page 18.

Resize a Volume

To manage disk space on the destination datastore, you can resize the disk volumes before you begin the conversion. Prerequisites On the Options page of the Conversion wizard, click Data to copy in the options list. Procedure From the Data copy type drop-down menu, select Select volumes to copy. In the Destination size column, select an option to specify the size of a destination volume.
Option Maintain size Min size Type size in GB Description Maintains the original source volume size. Copies only the used space of the source volume. Allows you to type a custom size in GB for the destination volume. The value cannot be smaller than the used space on the source volume, but can be larger than the total size of the source volume. The maximum allowed disk size for the destination is 999GB. Allows you to type a custom size in MB for the destination volume. The value cannot be smaller than the used space on the source volume, but can be larger than the total size of the source volume. The maximum allowed disk size for the destination is 999GB.

Type size in MB

Save your settings.
Option Select another option from the options list Click Next Description Saves your settings and displays the pane for the selected option. Saves your settings and displays the next page of the Conversion wizard. n The Customizations page is displayed if you select Customize guest preferences for the virtual machine in the Advanced options pane. n The Summary page is displayed if you do not select Customize guest preferences for the virtual machine in the Advanced options pane.
Exclude a Source Volume from the Conversion Process
You can choose not to copy a volume from the source machine to the destination virtual machine. During the conversion process, Converter Standalone ignores the deselected volumes and copies only the volumes that are selected. The source virtual machine must have more than one volume to be able to deselect existing volumes. You cannot delete the system volume from the destination virtual machine. For example, if C: is the volume that contains the Windows operating system installation, you cannot remove it from the destination virtual machine. Prerequisites On the Options page of the Conversion wizard, click Data to copy in the options list. Procedure 3 From the Data copy type drop-down menu, select Select volumes to copy. Deselect the volumes that you do not want to copy to the destination virtual machine. Save your settings.

Procedure 1 From the Disk controller drop-down menu, select a disk controller for the destination virtual disk.
Option SCSI Bus Logic IDE LSI Logic LSI Logic SAS Preserve source Description Use SCSI virtual disks in the destination virtual machine. Use IDE virtual disks in the destination virtual machine. Use LSI Logic SCSI virtual disks in the destination virtual machine. Use LSI Logic SCSI (SAS) virtual disks in the destination virtual machine. Use the same types of disk controllers as those installed on the source machine.
Configure the Network Settings of the Destination Virtual Machine
You can change the number of network adapters and select the network that the destination virtual machine uses. You can also set network adapters to connect to the network when the destination virtual machine powers on. NOTE You cannot use IPv6 to customize the guest operating systems of virtual machines. Prerequisites On the Options page of the Conversion wizard, select Networks from the options list. Procedure From the Network adapters to connect drop-down menu, select the number of network adapters to be used by the destination virtual machine. Use the Network drop-down menu to select the network that the adapter connects to. To connect an adapter when you power on the destination virtual machine, select the Connect at poweron check box. Save your settings.
Configure the Network for the Helper Virtual Machine
When you convert a powered-on Linux machine, Converter Standalone creates a Helper virtual machine on the destination. The Helper virtual machine needs network access to the source machine to clone the source files. Default conversion settings enforce automatic acquisition of an IPv4 address and a DNS server for the Helper virtual machine, but you can set up this network connection manually. Procedure On the Options page of the Conversion wizard, click Helper VM network. (Optional) To assign a static IPv4 address to the Helper virtual machine, select Use the following IP address and specify the IPv4 address, subnet mask, and default gateway. Be sure that the IP address you specify for the Helper virtual machine is not already in use on the network. 3 (Optional) Select Use the following DNS server address and type the preferred DNS server address to configure the DNS server address manually. Optionally, you can type an alternative DNS server address as well. 4 Save your settings.

Save Sysprep Files

To customize the guest operating system of a virtual machine that runs Windows Server 2003 or Windows XP, you must save the Sysprep files to the specified locations on the machine where Converter Standalone server runs. Prerequisites You must download the Sysprep files that correspond to the operating system of the source machine.
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. What to do next You can now use the Configuration wizard to customize Windows guest operating systems.
Start the Configuration Wizard
You can configure VMware desktop virtual machines or virtual machines managed by ESX hosts or vCenter Server. A physical machine cannot be a configuration source. You can configure only powered-off virtual machines. Procedure Start the VMware vCenter Converter Standalone application. Click Configure Machine in the application menu.
The Configuration wizard opens. What to do next Select the source machine to configure.
Select a Source Machine to Configure
You can select a powered-off VMware virtual machine as the source for a configuration task. Prerequisites On the Source System page of the Configuration wizard, select a source type from the drop-down menu. What to do next On the Options page of the Configuration wizard, you can select the required configuration options.
Chapter 5 Configure Virtual Machines
Select a VMware Infrastructure Virtual Machine to Configure
If the system you want to configure is a virtual machine that runs on an ESX host or on an ESX host managed by vCenter Server, you must select a VMware Infrastructure virtual machine as the source type. Prerequisites Power off the source machine before the configuration. In the main application window of Converter Standalone, click Configure Machine to open the Configuration wizard. Procedure On the Source System page of the Configuration wizard, select VMware Infrastructure virtual machine from the Select source type drop-down menu. Provide the IP address or host name and credentials for authentication with the ESX host or the vCenter Server, and click Next.
The Source Machine page appears, displaying the host name or IP address and the inventory of the ESX host or the vCenter Server. What to do next On the Source Machine page of the Configuration wizard you can browse the virtual infrastructure inventory and select the virtual machine to configure.
Specify the vCenter Server Virtual Machine to Configure

The Windows license information is saved to the configuration source machine when the configuration task is completed. What to do next You can select another option to set or click Next to view a summary of the configuration task. If the Next button is inactive, check the Current settings list for other settings that need your attention on this page.

Set the Time Zone

You can configure the time zone for a virtual machine. Prerequisites On the Options page of the Configuration wizard, select Customize guest preferences for the virtual machine and click Next to view and adjust the available customization options. Procedure On the Customizations page, select Time zone from the options list. Select the target time zone from the Time zone drop-down menu.
The time zone is set on the source machine when the configuration task completes. What to do next You can select another option to set or click Next to view a summary of the configuration task. If the Next button is inactive, check the Current settings list for other settings that need your attention on this page.
You can change the network settings of a virtual machine to work with the network configuration of the virtual environment. The options for configuring network adapters are available for all supported customization sources.
Prerequisites On the Options page of the Configuration wizard, select Customize guest preferences for the virtual machine and click Next to view and adjust the available customization options. Procedure On the Customizations page, select Network interface settings from the options list. Select a network adapter and click Customize to configure its properties. a b c On the General tab, type the IPv4 address and DNS server address. On the DNS tab, specify the DNS connections by entering DNS suffixes. Enter a DNS suffix and click Add. You can add more than one DNS suffix. d e If you are specifying multiple DNS suffixes, use Move up and Move down to specify the order in which the guest operating system uses the connections. On the WINS tab, type the primary and secondary WINS IP address in the text box.
When powered on, the configured virtual machine uses the network settings that you specified. What to do next You can select another option to set or click Next to view a summary of the configuration task. If the Next button is inactive, check the Current settings list for other settings that need your attention on this page.

You can configure the workgroup and the domain for a virtual machine. Prerequisites On the Options page of the Configuration wizard, select Customize guest preferences for the virtual machine and click Next to view and adjust the available customization options. Procedure On the Customizations page, select Workgroup/Domain from the options list. Select how the virtual machine participates in the destination network.
The configured virtual machine connects to the specified workgroup and domain server. What to do next You can select another option to set or click Next to view a summary of the configuration task. If the Next button is inactive, check the Current settings list for other settings that need your attention on this page.
Remove the System Restore checkpoints of newly imported source machines to prevent them from reverting to a preconversion state. For other configuration source machines, removing System Restore checkpoints helps you save disk space by deleting unnecesary data. Procedure
On the Options page of the Configuration wizard, select Remove System Restore checkpoints on the destination and click Next.
The System Restore checkpoints are deleted from the configuration source machine. What to do next Depending on the configuration options you selected, you can either customize the guest operating system or view the Summary page of the Configuration wizard.
Update the Device Drivers of a Virtual Machine
If a newly converted virtual machine does not start properly in the destination virtual environment, try configuring it to update its device drivers. Procedure
On the Options page of the Configuration wizard, select Reconfigure destination virtual machine and click Next.
Converter Standalone updates the device drivers on the source machine so it can work in the virtual environment. What to do next Depending on the configuration options you selected, you can either customize the guest operating system or view the Summary page of the Configuration wizard.
Review and Submit the Configuration Task
After you review your settings on the Summary page of the Configuration wizard, you can go back and change a setting or submit the task. Procedure Review the summary of the settings for the source virtual machine. Click Finish to submit the configuration task.

vCenter Converter migration with 10 tasks 10 vCenter permissions 26 vCenter Server, destination 25 vCenter Server support 23 vCenter Server virtual machines 45 vCenter Server VM, source 44 version support 23 viewing a task's progress 88 viewing conversion task summary 73 viewing the log files 88, 89 virtual disk 53, 54 virtual disk, adding 54 virtual hardware CPU issues 19 disk device issues 19 Ethernet adapter issues 19 graphics card issues 19 Virtual Iron, source 23 virtual machines conversion limitations 24 converting existing 18 destination on same network as source 18 VirtualCenter destination 25 source 23 support 23 VMware Fusion destination 25 source 23 support 23 VMware hosted products support 23 VMware managed products support 23 VMware Player destination 25 source 23 support 23 VMware Server destination 25 source 23 support 23 VMware Tools 66 VMware vCenter Converter Boot CD 10 VMware vCenter Converter Standalone command-line installation in Windows 35 installing remote access in Windows 34 uninstalling in Windows 38 volume-based cloning 16, 5254, 56, 57 volume-based cloning, defined 16 volume, supported types 16 volumes, excluding 53
volumes, moving 54 volumes, resizing 52 VSS snapshots limitations 30
Windows, Simple File Sharing 29 Windows virtual machines, configuring 75 Windows XP, turning off Simple File Sharing 29 Windows XP, checking Windows Firewall blocks 29 worker 10 Workstation destination 25 source 23 support 23

Xen, source 23

The following workflow demonstrates the principles of hot cloning physical machine sources that run Linux to managed destinations. 1 The Converter Standalone agent uses SSH to connect to the source machine and retrieves source information. The Converter Standalone agent creates an empty helper virtual machine based on your conversion task settings. The helper virtual machine serves as a container for the new virtual machine during conversion. The Converter Standalone agent deploys the helper virtual machine on the managed destination, an ESX/ESXi host. The helper virtual machine boots from a *.iso file that is located on the converter Standalone server machine.
vCenter Converter Standalone agent and server Converter Standalone agent deploys helper virtual machine network ESX/ESXi

powered-on Linux machine

Helper VM
The helper virtual machine powers on, boots from the Linux image, and connects to the source machine through SSH. Then it starts retrieving the selected data from the source. While you set up the conversion task, you can select which source volumes to be copied to the destination machine.
vCenter Converter Standalone agent and server

network

data copied to the helper virtual machine
Optionally, when data copying is complete, the target virtual machine is reconfigured to allow the operating system to boot in a virtual machine. The Converter Standalone agent shuts down the helper virtual machine. The conversion process is complete.
Optionally, you can configure Converter Standalone to power on the newly created virtual machine after the conversion is complete.

Cloning Modes

Converter Standalone implements volume-based cloning, disk-based cloning, and linked cloning. Table 1-3. Cloning Modes
Cloning Mode Volume based Application Selects the volumes to copy from the source machine to the destination machine. Description Volume-based cloning is relatively slow. File-level cloning is slower than block-level cloning. Dynamic disks are converted into basic volumes on the target virtual machine. You cannot select which data to copy. Disk-based cloning is faster than volume-based cloning. For certain third-party sources, the linked clone is corrupted if you power on the source machine. Linked cloning is the fastest (but incomplete) cloning mode that Converter Standalone supports.

Disk based

Creates exact copies of the source machines, for all types of basic and dynamic disks. Use to quickly check compatibility of non-VMware images

Linked clone

Volume-Based Cloning Converter Standalone supports volume-based cloning for hot and cold cloning and to import existing virtual machines. In volume-based cloning, all volumes in the destination virtual machine are converted to basic volumes, regardless of their type in the corresponding source volume. Volume-based cloning at the file or block level is performed, depending on the volume size you select. Dynamic source disks are read but not preserved during volume-based conversions. Dynamic disks are converted into basic volumes on the target virtual machine. Volume-based cloning at the file level Volume-based cloning at the block level Performed when any size smaller than the original is selected. Performed when the volume size is maintained or extended.
Depending on the cloning mode, Converter Standalone might not support some types of source volumes. Table 1-4 shows the supported and unsupported source volume types. Table 1-4. Supported and Unsupported Source Volumes
Cloning Mode Virtual machine importing Source Volumes Supported
Source Volumes Not Supported
Basic volumes All types of dynamic volumes Windows NT 4 with mirrored volumes Only master boot record (MBR) disks
RAID Windows NT4 fault-tolerant volumes GUID partition table (GPT) disks

Hot cloning

All types of source volumes that Windows recognizes
Any volumes that reside on Windows NT operating systems
Volume-based cloning at the file level is supported only for FAT, FAT32, NTFS, ext2, ext3, and ReiserFS file systems.
Disk-Based Cloning Converter Standalone supports disk-based cloning to import existing virtual machines. Disk-based cloning transfers all sectors from all disks and preserves all volume metadata. The destination virtual machine receives the same volumes, of the same type as the volumes of the source virtual machine. Disk-based cloning supports all types of basic and dynamic disks. Full and Linked Clones Clones can be full or linked according to the amount of data copied from the source to the destination machine. A full clone is an independent copy of a virtual machine that shares nothing with the parent virtual machine after the cloning operation. Ongoing operation of a full clone is separate from the parent virtual machine. Because a full clone does not share virtual disks with the parent virtual machine, full clones generally perform better than linked clones. Full clones take longer to create than linked clones. Creating a full clone can take several minutes if the files involved are large. You can create a full clone by using any disk clone mode other than the linked clone mode. A linked clone is a copy of a virtual machine that shares virtual disks with the parent virtual machine in an ongoing manner. A linked clone is a fast way to convert and run a new virtual machine. You can create a linked clone from the current state, or snapshot, of a powered-off virtual machine. This practice conserves disk space and allows multiple virtual machines to use the same software installation. All files available on the source machine at the moment of the snapshot continue to remain available to the linked clone. Ongoing changes to the virtual disk of the parent do not affect the linked clone, and changes to the disk of the linked clone do not affect the source machine. If you make changes to a source Virtual PC and Virtual Server machines, or to LiveState images, the linked clone is corrupted and you cannot use it anymore. A linked clone must have access to the source. Without access to the source, you cannot use a linked clone at all. To quickly convert a virtual machine, create a linked clone. See Create a Linked Clone, on page 53.

Conversion Limitations for Third-Party Virtual Machines or System Images
Converter Standalone can convert third-party virtual machines, system images, and ShadowProtect and BackupExec System Recovery images. These conversions have some limitations. Third-party virtual machines and system images have the following limitations:
Virtual machines from Macintosh versions of Virtual PC are not supported. The operating system on the source Virtual PC or Virtual Server virtual machine must be a Windows guest operating system supported by the intended VMware platform (for example, Workstation 5 or 6.0.x). For a list of supported operating systems, see the Guest Operating System Installation Guide. Converter Standalone supports Virtual PC and Virtual Server virtual machines with most Windows operating systems earlier than Windows NT 4.0 and with non-Windows operating systems (for example, Linux and DOS) only for cloning. Converter Standalone does not support configuring for these systems.
ShadowProtect and Backup Exec System Recovery have the following limitations:
Dynamic disks are not supported. All images for the backup of a machine must be in a single folder with no other images placed there. For volume-based cloning, all volumes in the disk up to the active and system volumes must be backed up. For example, if a disk has four partitions, 1 through 4, with partition 2 as the active volume and partition 3 as the system volume, the backup must include partitions 1 through 3. For incremental images, up to 16 incremental backups are supported. Images of systems with logical drives are not supported if the logical drive is also a system or active volume (ShadowProtect only).
Conversion Limitations for Virtual Appliances
Some limitations exist when you convert virtual appliances. The following scenarios are not supported:
Converting local and remote physical machines to virtual appliances Selecting a subset of the volumes or resizing the volumes. You must select all volumes for an import and maintain the size of all of the volumes on the target machine. Converting from OVF to OVF. That is, when both source and destination are virtual appliances. Converting third-party backup images or virtual machine images to a virtual appliance. Converting Windows 2000 virtual machines with scsiport.sys driver version 5.0.2195.7017 to a virtual appliance. Converting Windows NT 4 SMP virtual machines to a virtual appliance.

Install Converter Standalone in Windows
You can install Converter Standalone onto a physical or a virtual machine. The Local setup installs the Converter Standalone server, Converter Standalone agent, and Converter Standalone client for local use. For remote access, you can create a Client-server installation. With remote access you can create and manage conversion tasks remotely. When you install the Converter Standalone agent and the Converter Standalone server, the local machine becomes a server for conversions, which you can manage remotely. When you use the local machine with the Converter Standalone client, you can convert the full range of machine types. If you install only Converter Standalone client, you can connect to remote Converter Standalone server. You can then use the remote machine to convert hosted virtual machines, managed virtual machines, or remote physical machines. If you install Remote Access, local and multiple remote Converter Standalone clients can connect to the local Converter Standalone server. Prerequisites Make sure your system meets the Converter Standalone system requirements. If you have Converter 3.0.x installed and your machine runs Windows Vista, you must uninstall Converter 3.0.x manually before you install Converter Standalone 4.0.1.
Procedure Download the latest version of Converter Standalone from the VMware Web site. Check the number of the build, which should be in the local directory to which you downloaded the installer. Navigate to the folder that contains the installer file you downloaded and double-click the VMwareconverter-4.x.x-<xxxxx>.exe file, where <xxxxx> is the number of the build. Click Next. Select I accept the terms in the License agreement and click Next. Select the location folder for Converter Standalone on the Destination Folder page and click Next. The default location is C:\Program Files\VMware\VMware vCenter Converter Standalone. 9 (Optional) To install to another location, click Change and browse for the new location. On the Setup Type page, select Local installation or Client-Server installation (advanced) and click Next. (Optional) On the Custom Setup page, make a selection and click Next. Converter Standalone server, Converter Standalone agent, Converter Standalone client, and Remote access are selected by default. 10 (Optional) If you select Client-Server Installation (advanced) from the Setup Type page, do the following: a b c Enter the HTTPS port service number. Enter the HTTP port service number. Enter the Agent port service number.

(Optional) If you are connected to a remote Converter Standalone server, click Connect As and enter the address and user credentials.
If the source is a remote physical machine, enter the address and user credentials for a location that is accessible from that source machine. If the source is another virtual machine, enter the address and user credentials for a location that is accessible to the machine that runs the remote Converter Standalone server.

Click Next.

You selected to create a standalone virtual machine to run on one of the supported VMware products. What to do next On the View/Edit Options page, you can make more precise settings to the conversion task.
View Setup Options for a New Virtual Machine
Depending on the selected source machine and destination type, the View/Edit Options page provides setup options for the destination virtual machine or virtual appliance.
Select the Destination Folder on page 46 The Destination Attributes option is available for VMware Infrastructure destinations. This option allows you to determine the logical relationship of the new virtual machine to the virtual environment. You select the folder to which the target virtual machine belongs.
Organizing the Data to Copy to the Destination Machine on page 46 Depending on the selected source and destination, you can select what data to copy to the destination virtual machine. You can also select the data's location on specific datastores in your virtual environment.
Change Device Settings on the New Virtual Machine on page 53 You can change the number of processors, the amount of memory, and the disk controller type to run on the destination virtual machine.
Change Network Connections on the Destination on page 54 You can change the number of network adapters to appear on the destination virtual machine. Control the Status of Windows Services During Conversion on page 54 You can change the starting mode of the source Windows services on the target virtual machine and stop the Windows services on the source machine during the conversion. Stopping some services on the source machine allows easier synchronization between the source and the target machine.
Advanced Customization Options on page 55 Before you start the conversion, you can use the View/Edit Options page in the Conversion wizard to adjust advanced settings. These settings include postconversion synchronization between source and destination, postconversion power state of the source and destination virtual machine, VMware tools installation, reconfiguration of destination virtual machine, destination computer information, and system restore checkpoints.

Depending on the selected source and destination, you can select what data to copy to the destination virtual machine. You can also select the data's location on specific datastores in your virtual environment. For detailed information on data copy types, see Table 4-1.
Table 4-1. Data Copy Types
Data Copy Type Select volumes to copy Supported Sources and Destinations Source operating systems that support disk volumes Description Volume-based cloning allows resizing the source volumes on the destination machine, volume reordering, and selection. Disk-based cloning does not allow resizing the source disks on the destination machine. For hosted destinations, you can change the disk type. For VMware Infrastructure destinations, you can change the datastore. You can locate source disks to different datastores on managed destinations (VMware ESX, ESXi, or vCenter Server). A linked clone allows you to create a VMware virtual machine that shares the virtual disk of the source virtual machine or system image.

Select disks to copy

Virtual machine sources and hosted or managed destinations
Hosted sources and hosted destinations
Depending on the destination you select, several target disk types are available. To support target virtual disks on FAT file systems, divide the source into 2GB files. For detailed information on target virtual disks types, see Table 4-2.
Table 4-2. Destination Disk Types
Destination VMware Infrastructure virtual machine Available Disk Types Flat Copies the entire source disk size to the destination, regardless of its used and free space. For managed destinations that support thin provisioning, creates an expanding disk on the destination. For example, if the source disk size is 10GB, but only 3GB are used space, the created destination disk is 3GB but potentially expands to 10GB. Copies the entire source disk size to the destination, regardless of its used and free space. Creates an expanding disk on the destination. For example, if the source disk size is 20GB, but only 5GB are used space, the created destination disk is 5GB but potentially expands to 20GB. Take this measurement into account when you calculate the free disk space on the destination datastore. Splits the source disk into 2GB sections on the destination. Creates 2GB sections on the destination that include only the real used space on the source disk. As the destination disk grows, new 2GB sections are created to accommodate the new data until the original source disk size is reached.

Customize the following text boxes: a In the Computer Name text boxes, specify a computer name to identify the virtual machine on the network. Valid characters include A-Z, a-z, 0-9, and the hyphen (-). The underscore (_) is nonstandard, but Converter Standalone permits its use. The computer name cannot have more than 15 characters or consist only of numerals. b In the Owner name field, specify a unique name to identify the virtual machine on the network. Valid characters include A-Z, a-z, 0-9, and the hyphen (-). The underscore (_) is nonstandard, but Converter Standalone permits its use. The owner name cannot have more than 63 characters or consist only of numerals. c In the Organization field, enter an organization name. Valid characters include all printable characters. The limit is 63 characters.
(Optional) To create a new security identifier, select Generate New Security ID (SID). By default, the security ID is selected for Windows Vista systems and Longhorn sources and you cannot deselect it.
Enter the Windows License Information VMware recommends entering licensing information for all destination virtual machines that are subject to licensing. Some new virtual machines do not require a license. Procedure 3 On the View/Edit Options page, click Advanced conversion options and select Configure guest preferences for the virtual machine. Click Next to access the guest operating system settings. In the options list to the left, select Windows License. The customization fields appear to the right. 6 Enter Product ID information for the destination virtual machine. (Optional) Select Include Server License Information if the destination operating system is Microsoft Windows 2000 Server or Microsoft Windows 2003 Server. Select a Server License Mode option.
Option Per seat Per server Description For individual user licenses. For a concurrent user license. Specify the Maximum Connections number when you select this option.
The Windows license information is saved to the destination virtual machine during the conversion.
Set the Time Zone You can set the time zone if you are converting a virtual machine to use in a remote location. Procedure 5 On the View/Edit Options page, click Advanced options and select Configure guest preferences for the virtual machine. Click Next to access the guest operating system settings. In the options list, select Time Zone. Select the target time zone from the Time Zone drop-down menu. Select another option to set or click Next to view a summary of the conversion task.

The time zone is set on the destination virtual machine. Set Up the Network Adapters You can customize network adapter settings on the destination virtual machine. The network adapters option is available for all supported destinations except virtual appliances. Procedure 3 On the View/Edit Options page, click Advanced conversion options and select Configure guest preferences for the virtual machine. Click Next to access the guest operating system settings. In the options list to the left, select Network Interface Settings. The list of network adapters appears to the right. 4 Select the relevant adapter and click Customize to open its properties. a b c d e 5 On the General tab, manually enter the IP address and DNS server address. On the DNS tab, specify the DNS connections by entering DNS suffixes. For each DNS suffix you enter, click Add. If you are entering multiple DNS suffixes, use Move Up and Move Down to specify the order in which a virtual machine is to use the connections. On the WINS tab, type the primary and secondary WINS IP address in the text box.
Assign a Workgroup or Domain Details You can set up how a target virtual machine participates in the destination network. This option is available for all supported destinations except virtual appliances. Procedure 3 On the View/Edit Options page, click Advanced options and select Configure guest preferences for the virtual machine. Click Next to access the guest operating system settings. In the options list to the left, select Workgroup/Domain. The workgroup and domain settings appear to the right.
Select how the virtual machine participates in a network.
Option Workgroup Windows Server Domain Description Valid characters include A-Z, a-z, 0-9, space, and the hyphen (-). Maximum length is 15 characters. The text box must have a value. Valid characters include A-Z, a-z, 0-9, space, period , and hyphen (-). Each label delineated by a period can be 63 characters. The entire text string can be up to 254 characters. User credentials are required.
Remove System Restore Checkpoints For source machines running in Windows XP or later, VMware recommends that you remove all System Restore checkpoints, regardless of the cloning mode, unless you want the target virtual machine to be a replica of the source system. System Restore is enabled on Windows Vista and Windows XP systems by default. For Windows Vista, if you are performing volume-based file-level cloning, System Restore checkpoints are automatically removed from the target virtual machine, regardless of whether the check box is selected or deselected. If you are performing disk-based cloning or volume-based block-level cloning, deselecting the check box instructs Converter to keep the System Restore check points in the target virtual machine. Removing all System Restore checkpoints prevents the target machine from reverting to a preconversion state. Restoring a checkpoint in the target virtual machine that was created before you cloned the source machine can damage the system and cause the target virtual machine to become unbootable. Procedure 3 On the View/Edit Options page, click Advanced options. Select Remove System Restore checkpoints on destination. Select another option to set or click Next to view a summary of the conversion task.

(Optional) To edit or delete a product property, select it in the list and click Edit or Delete.
You listed the custom product properties to add in the target virtual appliance. What to do next You can edit another option on the View/Edit Options page or click Next to view a summary of the conversion task.
View the Summary of a Conversion Task
On the Ready to Complete page, you can view a summary of the new conversion task before you add it to the task list. The summary includes information about the source machine, the destination virtual machine, and destination customization settings, if any. Converter Standalone performs task validation at this stage. Prerequisites You must complete all task configuration steps to access the Ready to Complete page. Procedure 3 Click Next on the View/Edit Options page to go to the Ready to Complete page. (Optional) To change a task setting, click Back until you reach the relevant setup page. Click Finish to add the conversion task to the task list. Finish is active only when task validation is complete. This might take several minutes. Your conversion task is added to the task list.
Configuring VMware Virtual Machines
You can use Converter Standalone to configure VMware virtual machines that have disks populated by restoration from a backup of a physical host or by some other direct means of copying a virtual machines disks. Configuring such machines with Converter Standalone enables them to boot in VMware products. NOTE You cannot configure OVF images.
Configure a Virtual Machine
You can configure files from a VMware standalone virtual machine, from an ESX server or vCenter Server virtual machine, or from a VMware Server virtual machine. NOTE A physical machine cannot be a configuration source. You configure a virtual machine in the VMware vCenter Converter Standalone application. Procedure 1 Save Sysprep Files on page 66 To customize the guest operating system of a virtual machine, you must save the Sysprep files to the specified locations on the machine where Converter Standalone server runs. Select a Source to Configure on page 67 You can select a VMware virtual machine as the source for a configuration task. Select the Options to Configure on page 67 Configuring the source machine helps to improve its performance, customize its operating system, and install the necessary device drivers. 4 Customize a Virtual Machines Guest Operating System on page 68 On the Configure Wizard Customization page, you can customize the identity of the configured virtual machine and generate a new security identifier. 5 View the Summary of a Configuration Task on page 72 On the Ready to Complete page, you can view a summary of the new configuration task before you add it to the task list. Converter Standalone performs task validation at this stage.

In the options list to the left, select Windows License. The customization text boxes appear to the right.
Enter Product ID information for the destination virtual machine. (Optional) Select Include Server License Information if the destination operating system is Microsoft Windows 2000 Server or Microsoft Windows 2003 Server. Select a Server License Mode option.
Select another option to set or click Next to view a summary of the configuration task.
Set the Time Zone of a Configured Virtual Machine
You must set the time zone if you are configuring a virtual machine to use in a remote location. Prerequisites To perform a configuration task, you must save the Sysprep files to the corresponding location on the machine where Converter Standalone server runs. Procedure 5 On the View/Edit Options page, select Configure guest preferences for the virtual machine. Click Next to access the guest operating system settings. In the options list, select Time Zone. Select the target time zone from the Time Zone drop-down menu. Select another option to set or click Next to view a summary of the configuration task.
Set Up the Network Adapters of a Configured Virtual Machine
You can customize the network adapter settings of the source virtual machine to avoid duplicating IP addresses or other network conflicts. The network adapters option is available for all sources that support system reconfiguration. Prerequisites To perform a configuration task, you must save the Sysprep files to the corresponding location on the machine where Converter Standalone server runs. Procedure On the View/Edit Options page, click Advanced conversion options and select Configure guest preferences for the virtual machine. Click Next to access the guest operating system settings.
In the options list to the left, select Network Interface Settings. The list of network adapters appears to the right.
Select the adapter to customize and click Customize to open its properties. a b c d e f On the General tab, enter the IP address and DNS server address. On the DNS tab, specify the DNS connections by entering DNS suffixes. (Optional) For each DNS suffix you enter, click Add. (Optional) If you are entering multiple DNS suffixes, use Move Up and Move Down to specify the order in which a virtual machine is to use the connections. On the WINS tab, type the primary and secondary WINS IP address in the text field. Click OK to return to the Network Interface Setting page. Reset All is enabled if you modify one or more network adapters. Click this button to revert all settings for all adapters to the default.

Filter Tasks by Status

You can change which tasks appear in the task list based on their running status. Procedure On the main menu, select View > Filter by. Select a level of display from the drop-down menu. If you are connected to a remote Converter Standalone server, you can select My own to view only tasks that you create.
Filter Tasks by Multiple Criteria
You can combine filtering criteria to filter tasks in the task list. Currently running tasks are displayed regardless of the filtering criteria you apply. Procedure
Use the drop-down menus in the toolbar to select the status and history criteria. The two filtering conditions combine to show only tasks that comply with both conditions. If you select Failed and Past week filters, the resulting task list contains their combined output:
All tasks with failed status that were active within the last 24 hours All tasks with failed status that were completed in the past 7 days

Glossary

BIOS (basic input/output system) Firmware that controls machine startup and manages communication between the CPU and other devices, such as the keyboard, monitor, printers, and disk drives. bridged networking In hosted products, a type of network connection between a virtual machine and the hosts physical network. With bridged networking, a virtual machine appears to be an additional computer on the same physical Ethernet network as the host. See also custom networking, host-only networking, NAT (network address translation). child A managed entity grouped by a folder object or another managed entity. See also folder. clone (n.) A duplicate of a virtual machine. (v.) To make a copy of a virtual machine. Hosted products distinguish between full clones and linked clones. See also full clone, linked clone. cluster A server group in the virtual environment. Clusters enable a high-availability solution. cluster compute resource An extended compute resource that represents a cluster of hosts available for backing virtual machines. See also compute resource. cold cloning In VMware vCenter Converter Standalone, cloning a local physical machine while it is running in WinPE from the vCenter Converter Boot CD, not from its own operating system. See also hot cloning. compute resource A managed object that represents either a single host or a cluster of hosts available for backing virtual machines. See also cluster compute resource. concurrent migrations In VMware vCenter Converter Standalone, the Task Managers ability to direct the conversion and migration of multiple virtual machines at the same time. configuration See virtual machine configuration. current virtual machine (1) A virtual machine of the latest version supported by the product in use. See also legacy virtual machine. (2) In hosted products, the virtual machine that has focus in the service console.

suspend A state in which settings are preserved and actions are no longer performed. To turn off a virtual machine while preserving the current state of a running virtual machine. See also resume. swap file See page file. task A managed object representing the state of a long-running operation.
TCP (Transmission Control Protocol) A reliable transfer protocol used between two endpoints on a network. TCP is built on top of the Internet Protocol (IP). See also TCP/IP (Transmission Control Protocol/Internet Protocol). TCP/IP (Transmission Control Protocol/Internet Protocol) The set of protocols that is the language of the Internet, designed to enable communication between networks regardless of the computing technologies that they use. TCP connects hosts and provides a reliable exchange of data streams with guaranteed delivery. IP specifies the format of packets and handles addressing. See also UDP (User Datagram Protocol). team A group of virtual machines configured to operate as one object. You can power on, power off, and suspend a team with one command. You can configure a team to communicate independently of any other virtual or real network by setting up a LAN segment. See also LAN segment, virtual network. template A master image of a virtual machine. The template typically includes a specified operating system and a configuration that provides virtual counterparts to hardware components. Optionally, a template can include an installed guest operating system and a set of applications. Templates are used by vcenter to create new virtual machines. See also linked clone, parent, snapshot. UDP (User Datagram Protocol) One of the core protocols in the Internet protocol suite. UDP enables a program to send packets (datagrams) to other programs on remote machines. UDP does not require a connection and does not guarantee reliable communication. It is a quick and efficient method for broadcasting messages over a network. See also TCP/IP (Transmission Control Protocol/Internet Protocol). vCenter Converter Boot CD (VMware vCenter Converter Boot CD) The means by which a user can perform a local cold clone of a physical machine. When the physical machine is booted from the vCenter Converter Boot CD, the Converter application runs on WinPE. It uses a RAM disk for its operations and leaves no footprint on the physical machine. virtual disk A file or set of files that appears as a physical disk drive to a guest operating system. These files can be on the host machine or on a remote file system. See also growable disk, physical disk, preallocated disk. virtual hardware The devices that make up a virtual machine. The virtual hardware includes the virtual disk, removable devices such as the DVD-ROM/CD-ROM and floppy drives, and the virtual Ethernet adapter. See also virtual machine settings editor. virtual machine A virtual machine is a software computer that, like a physical computer, runs an operating system and applications. Multiple virtual machines can operate on the same host system concurrently. See the guidelines for using the acronym VM in place of virtual machine. virtual machine administrator A role in which the user can perform all the virtual machine management functions.

virtual machine configuration The specification of which virtual devices, such as disks and memory, are present in a virtual machine and how they are mapped to host files and devices. In vConverter, VMware virtual machines whose disks have been populated by restoring from a backup or by some other direct means of copying undergo configuration to enable them to boot in VMware products. See also virtual machine. virtual machine settings editor A point-and-click control panel used to view and modify the settings of a virtual machine setting. virtual memory An extension of a systems physical memory, enabled by the declaration of a page file. See also page file. virtual network A network connecting virtual machines that does not depend on physical hardware connections. For example, you can create a virtual network between a virtual machine and a host that has no external network connections. You can also create a LAN segment for communication between virtual machines on a team. See also LAN segment, team. virtual switch A virtualized network switch used by ESX server to manage traffic between virtual machines, the service console, and the physical network adapters on the ESX server machine. VM (acronym for virtual machine) Restricted use. A virtual machine is a software computer that, like a physical computer, runs an operating system and applications. A virtual machine is also referred to as a VM. Use the acronym VM when the screen or controls do not have sufficient space to use the complete term virtual machine.
Acronis True Image, source 21, 40 adding tasks 74 advanced customization guest operating system 56 installing VMware Tools 56 overview 55 powering machines on and off 56 removing system restore checkpoints 60 synchronizing source and destination 55
changing the number of tasks displayed 77, 78 cloning cloning modes 46 defined 10 disk cloning modes 16 disk-based cloning 17, 48 full clones 17 hot cloning 13 linked clones 17, 53 local cloning, defined 13 remote cloning, defined 13 volume-based cloning 16, 49 cold cloning, boot CD 12 command-line commands 31 configuring guest operating system 68 moving volumes to target virtual disk 50 new target disks 50 options 67 overview 65 selecting a source 67 selecting the options 67 selecting VMware Fusion source 67 selecting VMware Player source 67 selecting VMware Server source 67 selecting Workstation source 67 starting the Wizard 65 Sysprep files locations 66 target datastore 51 view summary 64, 72 viewing task summary 64, 72 connect to a remote Converter Standalone server 35