Networker 5 3 0 X 2

Networker 5 3 0 X 2

Networker 5 3 0 X 200
3 0google
Estimated reading time: 15 minutes
The Compose file is a YAML file defining services,networks, and volumes for a Docker application.
Dijkstra's link-state routing algorithm. Network Layer: 5-centralized: network topology, link costs known to. Accomplished via 'link state broadcast'.
The Compose file formats are now described in these references, specific to each version.
5.3.0 Problem with MTA, maybe someone has been editing the registry to disable the MTA / Store driver. 5.3.1 Mail system full. Possibly a Standard edition of Exchange reached the 16 GB limit. 5.3.2 System not accepting network messages. Look outside Exchange for a connectivity problem. 5.3.3 Remote server has insufficient disk space to hold email. ConnectX-5 adapter cards are available for PCIe Gen 3.0 and Gen 4.0 servers and provide support for 1, 10, 25, 40, 50 and 100 GbE speeds in stand-up PCIe cards, OCP 2.0, and OCP 3.0 form factors. ConnectX-5 cards also offer advanced Mellanox Multi-Host ® and Mellanox Socket Direct technologies. Cloud and Web 2.0 Environments. Download.NET Framework 3.5 Offline Installer for free. Install.NET Framework 3.5 Offline on Windows 10 & 8. Offline Installer for.NET Framework 3.5 for Windows 10 and 8.x. With this tool, you can install.NET 3.5, 3 and 2 on Windows 10, 8 and 8.1 from existing Windows installation media or mounted ISO.
Reference fileWhat changed in this version
Compose Specification (most current, and recommended)Versioning
Version 3Version 3 updates
Version 2Version 2 updates
Version 1 (Deprecated)Version 1 updates
The topics below explain the differences among the versions, Docker Enginecompatibility, and how to upgrade.
Compatibility matrixThere are several versions of the Compose file format – 1, 2, 2.x, and 3.x
This table shows which Compose file versions support specific Docker releases.
Compose file formatDocker Engine release
Compose specification19.03.0+
3.819.03.0+
3.718.06.0+
3.618.02.0+
3.517.12.0+
3.417.09.0+
3.317.06.0+
3.217.04.0+
3.11.13.1+
3.01.13.0+
2.417.12.0+
2.317.06.0+
2.21.13.0+
2.11.12.0+
2.01.10.0+
In addition to Compose file format versions shown in the table, the Composeitself is on a release schedule, as shown in Composereleases, but file format versionsdo not necessarily increment with each release. For example, Compose file format3.0 was first introduced in Compose release1.10.0, and versionedgradually in subsequent releases.
The latest Compose file format is defined by the Compose Specification and is implemented by Docker Compose 1.27.0+.
Looking for more detail on Docker and Compose compatibility?
We recommend keeping up-to-date with newer releases as much as possible.However, if you are using an older version of Docker and want to determine whichCompose release is compatible, refer to the Compose releasenotes. Each set of release notesgives details on which versions of Docker Engine are supported, alongwith compatible Compose file format versions. (See also, the discussion inissue #3404.)
For details on versions and how to upgrade, seeVersioning andUpgrading.
VersioningThere are three legacy versions of the Compose file format:
Version 1. This is specified by omitting a version key at the root of the YAML.
Version 2.x. This is specified with a version: '2' or version: '2.1', etc., entry at the root of the YAML.
Version 3.x, designed to be cross-compatible between Compose and the Docker Engine'sswarm mode. This is specified with a version: '3' or version: '3.1', etc., entry at the root of the YAML.
The latest and recommended version of the Compose file format is defined by the Compose Specification. This format merges the 2.x and 3.x versions and is implemented by Compose 1.27.0+.
v2 and v3 DeclarationNote: When specifying the Compose file version to use, make sure tospecify both the major and minor numbers. If no minor version is given,0 is used by default and not the latest minor version.
The Compatibility Matrix shows Compose file versions mapped to Docker Engine releases.
To move your project to a later version, see the Upgradingsection.
Note: If you're usingmultiple Compose files orextending services, each file must be of thesame version - you cannot, for example, mix version 1 and 2 in a singleproject.
Several things differ depending on which version you use:
The structure and permitted configuration keys
The minimum Docker Engine version you must be running
Compose's behaviour with regards to networking
These differences are explained below.
Version 1 (Deprecated)Compose files that do not declare a version are considered 'version 1'. In thosefiles, all the services aredeclared at the root of the document.
Version 1 is supported by Compose up to 1.6.x. It will be deprecated in afuture Compose release.
Version 1 files cannot declare namedvolumes, networks orbuild arguments.
Compose does not take advantage of networking when youuse version 1: every container is placed on the default bridge network and isreachable from every other container at its IP address. You need to uselinks to enable discovery between containers.
Example:

Reference file	What changed in this version
Compose Specification (most current, and recommended)	Versioning
Version 3	Version 3 updates
Version 2	Version 2 updates
Version 1 (Deprecated)	Version 1 updates

Compose file format	Docker Engine release
Compose specification	19.03.0+
3.8	19.03.0+
3.7	18.06.0+
3.6	18.02.0+
3.5	17.12.0+
3.4	17.09.0+
3.3	17.06.0+
3.2	17.04.0+
3.1	1.13.1+
3.0	1.13.0+
2.4	17.12.0+
2.3	17.06.0+
2.2	1.13.0+
2.1	1.12.0+
2.0	1.10.0+

Version 2Compose files using the version 2 syntax must indicate the version number atthe root of the document. All servicesmust be declared under the services key.
Version 2 files are supported by Compose 1.6.0+ and require a Docker Engineof version 1.10.0+.
Named volumes can be declared under thevolumes key, and networks can be declaredunder the networks key.
By default, every container joins an application-wide default network, and isdiscoverable at a hostname that's the same as the service name. This meanslinks are largely unnecessary. For more details, seeNetworking in Compose.
Note
When specifying the Compose file version to use, make sure tospecify both the major and minor numbers. If no minor version is given,0 is used by default and not the latest minor version. As a result, features added in later versions will not be supported. For example:
is equivalent to:
Simple example:
A more extended example, defining volumes and networks:
Several other options were added to support networking, such as:
The depends_on option can be used in place of links to indicate dependenciesbetween services and startup order.
Variable substitution also was added in Version 2.
Version 2.1An upgrade of version 2 that introduces new parameters onlyavailable with Docker Engine version 1.12.0+. Version 2.1 files aresupported by Compose 1.9.0+.
Introduces the following additional parameters:
isolation in build configurations andservice definitions
labels for volumes,networks, andbuild
name for volumes
Version 2.2An upgrade of version 2.1 that introduces new parameters onlyavailable with Docker Engine version 1.13.0+. Version 2.2 files aresupported by Compose 1.13.0+. This version also allows you to specifydefault scale numbers inside the service's configuration.
Introduces the following additional parameters:
network for build configurations
Version 2.3An upgrade of version 2.2 that introduces new parameters onlyavailable with Docker Engine version 17.06.0+. Version 2.3 files aresupported by Compose 1.16.0+. Splayerx 1 2 4.
Introduces the following additional parameters:
target, extra_hosts andshm_size for build configurations
start_period for healthchecks
runtime for service definitions
Version 2.4An upgrade of version 2.3 that introduces new parameters onlyavailable with Docker Engine version 17.12.0+. Version 2.4 files aresupported by Compose 1.21.0+.
Introduces the following additional parameters:
platform for service definitions
Support for extension fields at the root of service, network, and volumedefinitions
Version 3Designed to be cross-compatible between Compose and the Docker Engine'sswarm mode, version 3 removes several options and addsseveral more.
Removed: volume_driver, volumes_from, cpu_shares, cpu_quota,cpuset, mem_limit, memswap_limit, extends, group_add. Seethe upgrading guide for how to migrate away from these.(For more information on extends, see Extending services.)
Added: deploy
Note: When specifying the Compose file version to use, make sure tospecify both the major and minor numbers. If no minor version is given,0 is used by default and not the latest minor version. As a result, features added inlater versions will not be supported. For example:
is equivalent to:
Version 3.1An upgrade of version 3 that introduces new parameters onlyavailable with Docker Engine version 1.13.1+, and higher.
Introduces the following additional parameters:
Version 3.2An upgrade of version 3 that introduces new parameters onlyavailable with Docker Engine version 17.04.0+, and higher.
Introduces the following additional parameters:
cache_from in build configurations
Long syntax for ports and volume mounts
attachable network driver option
Version 3.3An upgrade of version 3 that introduces new parameters onlyavailable with Docker Engine version 17.06.0+, and higher.
Introduces the following additional parameters:
Version 3.4An upgrade of version 3 that introduces new parameters. It isonly available with Docker Engine version 17.09.0 and higher.
Introduces the following additional parameters:
target and network inbuild configurations
start_period for healthchecks
order for update configurations
name for volumes
Version 3.5An upgrade of version 3 that introduces new parameters. It isonly available with Docker Engine version 17.12.0 and higher.
Introduces the following additional parameters:
isolation in service definitions
name for networks, secrets and configs
shm_size in build configurations
Version 3.6An upgrade of version 3 that introduces new parameters. It isonly available with Docker Engine version 18.02.0 and higher.
Introduces the following additional parameters:
tmpfs size for tmpfs-type mounts
Version 3.7An upgrade of version 3 that introduces new parameters. It isonly available with Docker Engine version 18.06.0 and higher.
Introduces the following additional parameters: Lingon x 6 6 4 x 8.
init in service definitions
rollback_config in deploy configurations
Support for extension fields at the root of service, network, volume, secretand config definitions
Version 3.8An upgrade of version 3 that introduces new parameters. It isonly available with Docker Engine version 19.03.0 and higher.
Introduces the following additional parameters:
max_replicas_per_node in placementconfigurations
template_driver option for config and secret configurations. This option is only supported when deploying swarm services using docker stack deploy.
driver and driver_opts option for secret configurations. This option is only supported when deploying swarm services using docker stack deploy.
UpgradingVersion 2.x to 3.xBetween versions 2.x and 3.x, the structure of the Compose file is the same, butseveral options have been removed:
volume_driver: Instead of setting the volume driver on the service, definea volume using thetop-level volumes optionand specify the driver there.
volumes_from: To share a volume between services, define it using thetop-level volumes optionand reference it from each service that shares it using theservice-level volumes option.
cpu_shares, cpu_quota, cpuset, mem_limit, memswap_limit: Thesehave been replaced by the resources key underdeploy. deploy configuration only takes effect when usingdocker stack deploy, and is ignored by docker-compose.
extends: This option has been removed for version: '3.x'Compose files. (For more information, see Extending services.)
group_add: This option has been removed for version: '3.x' Compose files.
pids_limit: This option has not been introduced in version: '3.x' Compose files.
link_local_ips in networks: This option has not been introduced inversion: '3.x' Compose files.
Version 1 to 2.xIn the majority of cases, moving from version 1 to 2 is a very simple process:
Indent the whole file by one level and put a services: key at the top.
Add a version: '2' line at the top of the file.
It's more complicated if you're using particular configuration features:
dockerfile: This now lives under the build key:
log_driver, log_opt: These now live under the logging key:
links with environment variables: environment variables created bylinks, such as CONTAINERNAME_PORT, ` have been deprecated for some time. In the new Docker network system,they have been removed. You should either connect directly to theappropriate hostname or set the relevant environment variable yourself,using the link hostname:
external_links: Compose uses Docker networks when running version 2projects, so links behave slightly differently. In particular, twocontainers must be connected to at least one network in common in order tocommunicate, even if explicitly linked together.
Either connect the external container to your app'sdefault network, or connect both the external container andyour service's containers to anexternal network.
Principle 5 8. net: This is now replaced by network_mode:
If you're using net: 'container:[service name]', you must now usenetwork_mode: 'service:[service name]' instead.
If you're using net: 'container:[container name/id]', the value does notneed to change.
volumes with named volumes: these must now be explicitly declared in atop-level volumes section of your Compose file. If a service mounts anamed volume called data, you must declare a data volume in yourtop-level volumes section. The whole file might look like this:
By default, Compose creates a volume whose name is prefixed with yourproject name. If you want it to just be called data, declare it asexternal:

Version 2Compose files using the version 2 syntax must indicate the version number atthe root of the document. All servicesmust be declared under the services key.
Version 2 files are supported by Compose 1.6.0+ and require a Docker Engineof version 1.10.0+.
Named volumes can be declared under thevolumes key, and networks can be declaredunder the networks key.
By default, every container joins an application-wide default network, and isdiscoverable at a hostname that's the same as the service name. This meanslinks are largely unnecessary. For more details, seeNetworking in Compose.
Note
When specifying the Compose file version to use, make sure tospecify both the major and minor numbers. If no minor version is given,0 is used by default and not the latest minor version. As a result, features added in later versions will not be supported. For example:
is equivalent to:
Simple example:
A more extended example, defining volumes and networks:
Several other options were added to support networking, such as:
The depends_on option can be used in place of links to indicate dependenciesbetween services and startup order.
Variable substitution also was added in Version 2.
Version 2.1An upgrade of version 2 that introduces new parameters onlyavailable with Docker Engine version 1.12.0+. Version 2.1 files aresupported by Compose 1.9.0+.
Introduces the following additional parameters:
isolation in build configurations andservice definitions
labels for volumes,networks, andbuild
name for volumes
Version 2.2An upgrade of version 2.1 that introduces new parameters onlyavailable with Docker Engine version 1.13.0+. Version 2.2 files aresupported by Compose 1.13.0+. This version also allows you to specifydefault scale numbers inside the service's configuration.
Introduces the following additional parameters:
network for build configurations
Version 2.3An upgrade of version 2.2 that introduces new parameters onlyavailable with Docker Engine version 17.06.0+. Version 2.3 files aresupported by Compose 1.16.0+. Splayerx 1 2 4.
Introduces the following additional parameters:
target, extra_hosts andshm_size for build configurations
start_period for healthchecks
runtime for service definitions
Version 2.4An upgrade of version 2.3 that introduces new parameters onlyavailable with Docker Engine version 17.12.0+. Version 2.4 files aresupported by Compose 1.21.0+.
Introduces the following additional parameters:
platform for service definitions
Support for extension fields at the root of service, network, and volumedefinitions
Version 3Designed to be cross-compatible between Compose and the Docker Engine'sswarm mode, version 3 removes several options and addsseveral more.
Removed: volume_driver, volumes_from, cpu_shares, cpu_quota,cpuset, mem_limit, memswap_limit, extends, group_add. Seethe upgrading guide for how to migrate away from these.(For more information on extends, see Extending services.)
Added: deploy
Note: When specifying the Compose file version to use, make sure tospecify both the major and minor numbers. If no minor version is given,0 is used by default and not the latest minor version. As a result, features added inlater versions will not be supported. For example:
is equivalent to:
Version 3.1An upgrade of version 3 that introduces new parameters onlyavailable with Docker Engine version 1.13.1+, and higher.
Introduces the following additional parameters:
Version 3.2An upgrade of version 3 that introduces new parameters onlyavailable with Docker Engine version 17.04.0+, and higher.
Introduces the following additional parameters:
cache_from in build configurations
Long syntax for ports and volume mounts
attachable network driver option
Version 3.3An upgrade of version 3 that introduces new parameters onlyavailable with Docker Engine version 17.06.0+, and higher.
Introduces the following additional parameters:
Version 3.4An upgrade of version 3 that introduces new parameters. It isonly available with Docker Engine version 17.09.0 and higher.
Introduces the following additional parameters:
target and network inbuild configurations
start_period for healthchecks
order for update configurations
name for volumes
Version 3.5An upgrade of version 3 that introduces new parameters. It isonly available with Docker Engine version 17.12.0 and higher.
Introduces the following additional parameters:
isolation in service definitions
name for networks, secrets and configs
shm_size in build configurations
Version 3.6An upgrade of version 3 that introduces new parameters. It isonly available with Docker Engine version 18.02.0 and higher.
Introduces the following additional parameters:
tmpfs size for tmpfs-type mounts
Version 3.7An upgrade of version 3 that introduces new parameters. It isonly available with Docker Engine version 18.06.0 and higher.
Introduces the following additional parameters: Lingon x 6 6 4 x 8.
init in service definitions
rollback_config in deploy configurations
Support for extension fields at the root of service, network, volume, secretand config definitions
Version 3.8An upgrade of version 3 that introduces new parameters. It isonly available with Docker Engine version 19.03.0 and higher.
Introduces the following additional parameters:
max_replicas_per_node in placementconfigurations
template_driver option for config and secret configurations. This option is only supported when deploying swarm services using docker stack deploy.
driver and driver_opts option for secret configurations. This option is only supported when deploying swarm services using docker stack deploy.
UpgradingVersion 2.x to 3.xBetween versions 2.x and 3.x, the structure of the Compose file is the same, butseveral options have been removed:
volume_driver: Instead of setting the volume driver on the service, definea volume using thetop-level volumes optionand specify the driver there.
volumes_from: To share a volume between services, define it using thetop-level volumes optionand reference it from each service that shares it using theservice-level volumes option.
cpu_shares, cpu_quota, cpuset, mem_limit, memswap_limit: Thesehave been replaced by the resources key underdeploy. deploy configuration only takes effect when usingdocker stack deploy, and is ignored by docker-compose.
extends: This option has been removed for version: '3.x'Compose files. (For more information, see Extending services.)
group_add: This option has been removed for version: '3.x' Compose files.
pids_limit: This option has not been introduced in version: '3.x' Compose files.
link_local_ips in networks: This option has not been introduced inversion: '3.x' Compose files.
Version 1 to 2.xIn the majority of cases, moving from version 1 to 2 is a very simple process:
Indent the whole file by one level and put a services: key at the top.
Add a version: '2' line at the top of the file.
It's more complicated if you're using particular configuration features:
dockerfile: This now lives under the build key:
log_driver, log_opt: These now live under the logging key:
links with environment variables: environment variables created bylinks, such as CONTAINERNAME_PORT, ` have been deprecated for some time. In the new Docker network system,they have been removed. You should either connect directly to theappropriate hostname or set the relevant environment variable yourself,using the link hostname:
external_links: Compose uses Docker networks when running version 2projects, so links behave slightly differently. In particular, twocontainers must be connected to at least one network in common in order tocommunicate, even if explicitly linked together.
Either connect the external container to your app'sdefault network, or connect both the external container andyour service's containers to anexternal network.
Principle 5 8. net: This is now replaced by network_mode:
If you're using net: 'container:[service name]', you must now usenetwork_mode: 'service:[service name]' instead.
If you're using net: 'container:[container name/id]', the value does notneed to change.
volumes with named volumes: these must now be explicitly declared in atop-level volumes section of your Compose file. If a service mounts anamed volume called data, you must declare a data volume in yourtop-level volumes section. The whole file might look like this:
By default, Compose creates a volume whose name is prefixed with yourproject name. If you want it to just be called data, declare it asexternal:
Compatibility modedocker-compose 1.20.0 introduces a new --compatibility flag designed tohelp developers transition to version 3 more easily. When enabled,docker-compose reads the deploy section of each service's definition andattempts to translate it into the equivalent version 2 parameter. Currently,the following deploy keys are translated:
resources limits and memory reservations
restart_policycondition and max_attempts
All other keys are ignored and produce a warning if present. You can reviewthe configuration that will be used to deploy by using the --compatibilityflag with the config command.
Do not use this in production!
We recommend against using --compatibility mode in production. Because theresulting configuration is only an approximate using non-Swarm modeproperties, it may produce unexpected results.
Compose file format referencesfig, composition, compose, versions, upgrading, dockerFeatures | Documentation | Knowledge Base | Discussion Forums
Notes on VMware Converter 3.0.2, Build 59994 
Build 59994 is a release build of VMware Converter.
The release notes contain the following:
Introduction to VMware Converter 3VMware Converter provides an easy-to-use, scalable solution for migrations of machines, both physical to virtual and virtual to virtual. Optimized for mass migration, VMware Converter is equally effective for single-machine conversions. With its comprehensive and comprehensible wizards and task manager, VMware Converter imports virtual machines faster, with fewer manual steps required, and fewer source hardware limitations than other methods. With its ability to perform hot cloning, VMware Converter can import a virtual machine with no downtime on the source physical machine.
VMware Converter eases interoperability among VMware hosted products (Workstation, VMware Server, VMware Player, and Fusion), VirtualCenter-managed ESX Server 3.x and 2.5.x, and unmanaged ESX Server 3.x.
New in Converter 3.0.2Version 3.0.2 is a maintenance release of VMware Converter. It contains bug fixes described in Resolved Issues, and also incorporates the following new features:
 Conversion of VMware hardware version 6 products: Workstation 6.x, VMware ACE 2.x, VMware Fusion 1.x, and VMware Player 2.x
Conversion of an additional third-party disk image format: Acronis True Image 9
Experimental support for Microsoft Vista 32-bit and 64-bit operating systems
Ability to set speed and duplex settings on the network adapter while performing cold cloning migrations, by using the VMware Converter Enterprise Boot CD
Support for Symantec Backup Exec System Recovery 7.0
New in Converter 3.0.1Version 3.0.1 is a maintenance release of VMware Converter. It contains bug fixes described in Resolved Issues, and also incorporates the following new features:
VMware Converter imports VMware Consolidated Backup images
 Converter can restore Consolidated Backup images into ESX Server machines, and can import them into VMware standalone virtual machines. Converter supports restoring Consolidated Backup images of any guest operating system type.
VMware Converter imports certain StorageCraft ShadowProtect images
 Converter can import ShadowProtect images, with some limitations. These limitations include:
Dynamic disks are not supported
All images for the backup of a machine should 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 have been backed up (For instance: a disk has four partitions, 1 - 4, with partition 2 as the active volume and partition 3 as the system volume. The backup must include 1 through 3)
If it is an incremental image, up to 16 incremental backups are supported
Images of systems with logical drives are not supported if the default boot (Windows) partition is on a logical drive.
VMware Converter provides an experimental command line interface for migrations
 VMware provides p2vTool as a tool for migrating physical and virtual source machines with a command line interface (CLI). Support for this CLI is Experimental. Therefore, users cannot file Support Requests (SRs) to VMware for p2vTool-related issues.
You need an Enterprise license to use p2vTool to migrate machines. The one exception is restoring a VMware Consolidated Backup image; in this case p2vTool can execute the query, verify, import, and postprocess options without needing a license if it detects that the source is a VCB image.
New in Converter 3.0VMware Converter expands the functionality available to users of P2V Assistant and Virtual Machine Importer. In moving from P2V Assistant to VMware Converter, you see more options and abilities in migrating physical machines, along with the new ability to migrate virtual machines. In moving from Virtual Machine Importer to VMware Converter, you see more options and abilities in migrating virtual machines, along with the new ability to convert physical machines.
Installation NotesImportant: Beginning with Converter 3.0.2, the installer uninstalls previously installed versions of Converter such as 3.0.1 or 3.0 before installing version 3.0.2. Before installing Converter 3.0.1 on a machine, you must first uninstall Converter 3.0 if it exists on that machine.
Platforms VMware Converter 3 can be installed on the following platforms:
Windows XP Professional
Windows 2003 Server
Windows 2000 Professional
Windows 2000 Server
Windows NT SP4+ (IE5 or higher required)
Windows Vista (experimental support) 
All target operating systems should have the latest patches available from Microsoft as of the release of this product.
InteroperabilityVMware Converter 3 supports the following sources and destinations:
 Import from Physical Machines
 (Source) Import from Various Third-Party Formats and VMware Products
 (Source) Export to a Virtual Machine for
 VMware Workstation and Datacenter Products
 (Destination)
VMware Converter can hot clone and reconfigure any local or remote physical machine running an operating system noted in Platforms
VMware Converter Boot CD can be started from, and clone, local machines outfitted with storage controllers and network adapters that Microsoft lists as supported in Windows 2003
Microsoft Virtual PC (version 7 and higher)
Microsoft Virtual Server (any version)
Symantec Backup Exec System Recovery images1, 2
StorageCraft ShadowProtect images (experimental)2, 4
Acronis True Image4
VMware Workstation 6.x virtual machine (compatible with VMware Player 2.x, and VMware Server 1.x)4
VMware Workstation 5.x virtual machine (compatible with VMware Player and VMware Server 1.x)
VMware Workstation 4.x virtual machine (compatible with VMware GSX Server 3.x)
VMware ESX Server 3.x
VMware ESX Server 3.x (when managed by VirtualCenter 2.x)
VMware ESX Server 2.5.x (when managed by VirtualCenter 2.x)
VMware ACE 2.x
VMware Fusion 1.x
VMware Consolidated Backup images2
VMware Workstation 6.x virtual machine (compatible with VMware Player 2.x, and VMware Server 1.x)4
VMware Workstation 5.x virtual machine (compatible with VMware Player and VMware Server 1.x)4
VMware Workstation 4.x virtual machine (compatible with VMware GSX Server 3.x, ESX Server 2.5.x)3
VMware ESX Server 3.x (when managed by VirtualCenter 2.x)
VMware ESX Server 3.x
VMware ESX Server 2.5.x (when managed by VirtualCenter 2.x)
VMware ACE 2.x
VMware Fusion 1.x
Not Supported:VMware ESX Server 2.5.x when managed by VirtualCenter 1.x
VMware ESX Server 2.5.x unmanaged
1. The Symantec family of products includes Backup Exec System Recovery (formerly LiveState Recovery) 6.5 and 7.0, LiveState Recovery 3.0 and 6.0, and the Norton Ghost 9, 10, and 12 products. 
2. For conditions and limitations in importing Backup Exec System Recovery, ShadowProtect, and Consolidated Backup images, refer to chapter 2, 'System Requirements,' of the VMware Converter User's Manual.
3. Select Workstation 4.x as the destination in the Converter GUI. After the import is complete, use vmkfstools on the target ESX machine to import the resulting Workstation 4.5 virtual machine to ESX 2.5.x. 
4. Only Workstation 5.5 and 6.x can power on linked imports of .sv2i images. Workstation 6 is required to power on linked clones of Acronis True Image and StorageCraft ShadowProtect images.

Supported Guest Operating Systems The following 32-bit guest operating systems are fully supported by VMware Converter 3:
Windows NT
Windows 2000 Professional
Windows 2000 Server
Windows XP Professional
Windows 2003 Server
 The following 64-bit guest operating systems are fully supported by VMware Converter 3:
Windows XP Professional
Windows 2003 Server
 Support for the following guest operating systems is Experimental. VMware Converter 3 can clone source images containing these operating systems, but the destination virtual machine may or may not work without additional configuration after import. In particular, if the source image contains unsupported hardware, you might need to modify the configuration of the destination virtual machine before using it:
Linux
Windows Vista 
Windows NT 3.x
Windows ME
Windows 98
Windows 95
MS-DOS

Known Issues This VMware Converter 3 release contains the following known issues:
 GENERAL
Hot clone of Windows operating system fails
 A local or remote hot clone of a Windows operating system to a virtual machine fails with the following error message: Image processing task has failed with Platform Error fault: 23. This message indicates a hardware failure error, which causes VMware Converter to stop cloning.
A linked clone of a VMware virtual machine to a hosted destination fails 
 A linked clone of a virtual machine that resides on a File Allocation Table (FAT) file system is supported only if its VMDK files are in 2GB split format. 
Cannot load a Windows 2000 Virtual PC image on a Windows 2000 Server with SP4 host
 The Microsoft Windows system that Converter is installed on must have Microsoft XML Parser (MSXML) 2.6, 3.0 or 4.0 installed to successfully import Virtual PC images.
The source virtual machine does not have the appropriate drivers
 A log file error message such as 'Unable to find symmpi.sys in the specified CAB files,' indicates that reconfiguration failed because the appropriate drivers are not present on the source operating system. This is usually observed in Windows 2003 Server Service Pack 1. 
Workaround 1: 
Set aside the virtual machine created during the failed import.
 Attach the VMDK file containing the system folder to another Windows 2003 virtual machine.
 Replace the WINDOWSDriver Cachei386driver.cab file in the target virtual machine with a version of the driver.cab file that includes the missing driver from the helper virtual machine. 
Detach the VMDK file from the helper virtual machine and run the Configure Machine wizard on the target virtual Machine.
 Workaround 2: Replace the driver.cab file, as mentioned in step 3, in the source virtual and physical machine before the migration.
Rerun the migration.
The CD-ROM device does not work after importing Windows Vista to virtual machines 
 The CD-ROM device does not work after importing Windows Vista to ESX 3.x or to a Workstation version earlier than VMware Workstation 6. The CD-ROM driver that comes with Windows Vista does not work with the emulated CD-ROM devices in ESX 3.x and Workstation versions earlier than 6. Support for Windows Vista as a guest operating system is experimental for ESX 3.0.x and Workstation 5.x. Vista is fully supported as a guest operating system on Workstation 6. Workstation 4.x and ESX 2.x do not support Vista. For a list of VMware products that have experimental support for Windows Vista, see the Guest Operating System Installation Guide .
Hot clone of Windows Vista fails with permission error 
 Although you log in as a user with administrative privileges, the clone of Windows Vista operating system fails because of insufficient permission to perform the operation. To perform a hot clone of Windows Vista, you must run VMware Converter as Administrator by right clicking the VMware Converter icon on your desktop and choosing 'Run as Administrator.' 
Installer creates a new vmware-client-config.xml file
 The Installer creates a new vmware-client-config.xml file and if you have customized the location of logs in the config file, that information will be lost.
Network adapter instances are not listed under the Advanced tab in the Network configuration window when using Converter Boot CD for cold cloning
 Broadcom's NetXtreme II Ethernet controllers 5706 and 5708 are not listed under the Advanced tab in the Network configuration window. These network adapters are not detected during cold cloning because of limitations in the WinPE operating system. The network device's advanced options are not available, even though network connectivity is provided.
Importing images with foreign characters causes an error 
 If you import an image with foreign characters in the path or filename, the following error message is returned: image not supported or corrupted.
Snapshot fails when cloning an unformatted Windows volume
 Vmware Converter does not support hot cloning of a recognized, but unformatted, Windows volume. When doing a hot clone, you must unselect any unformatted volumes.
The target virtual machine is not bootable if the active system volume is not formatted by Microsoft Operating System 
 When you import a virtual machine by using a volume-based cloning method and the source machine's active system volume is not formatted by Microsoft Operating System, the target virtual machine might not boot up. Workaround: Use disk-based cloning (import all disks and maintain the size option) by running the Converter Boot CD.
Target virtual machine might not boot up because an incorrect disk number is reported from Symantec backups 
 In some circumstances, the disk number reported in the Symantec library is incorrect, which causes the resulting image to be unbootable because the virtual machine searches for the Master Boot Record (MBR) in the incorrect device. Workaround: In the main Workstation menu, choose VM > Settings > Hard Disk > Advanced and switch the virtual device node so the target virtual machine boots from the same disk as the source machine.
Manual cleanup required of some Converter Agent files from remote source physical machine
 In some cases, the automatic cleanup of Converter Agent files from the system on which it ran is incomplete. If there are vmware-ufad-p2v-XXXXX subdirectories remaining under %SystemRoot% on the remote source physical machine after completion of the import (either successful or failed), automatic cleanup was not totally successful, and might cause future import attempts to fail. To clean up manually (recommended), follow these steps: 
Launch regedit and navigate to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServices
Remove the stcp2v30 key
Remove the vstor2-p2v30 key
Remove all vmware-ufad-p2v-XXXXX keys
Remove all courier-XXXXX keys
Reboot
Under %SystemRoot%system32, remove all vmware-ufad-p2v-XXXXX subdirectories
Converter does not import Windows NT 4 with mirrored/striped volumes
 Converter is unable to recognize logical devices in Windows NT 4 that span multiple drives. This includes striped and mirrored volumes.
Source with mixed IDE and SCSI disks might not produce a bootable virtual machine
 A source machine with both SCSI and IDE disks has the IDE disks attached to the end of the disk list. If the source machine boots from an IDE disk, the target virtual machine created by Converter boots from the wrong disk because a VMware virtual machine looks for the first disk in the disk list. Workaround: 
Networker 5 3 0 X 200Boot the imported virtual machine and press F2 to enter the BIOS
Go to the Boot menu
Highlight the Hard Drive row and press Enter
Change the boot order of the disks so that the system disk is first
Continue
Incorrect reboot warning when installing Converter Manager only
 When installing only the Converter Manager, and not the Converter Agent, on machines running Windows 2000 or Windows NT operating systems, you do not need to reboot despite the Custom Setup page in the installer warning that you need to.
Sysprep deletes drive letter mappings if your task includes customization
 If you choose customization options and the destination virtual machine fails at a 'Please Wait' screen after the second, sysprep reboot, you will need to rerun the import without customization. This problem occurs because of a problem with Microsoft's sysprep, which has deleted the drive letter mappings, preventing access to certain files.
After customizing a virtual machine, rebooting it produces an error message that msgina.dll failed to load
 See the VMware Knowledge Base article, Error: 'Logon User Interface DLL msgina.dll failed to load':
 and the Microsoft knowledge base article, 'Error Message: User Interface Failure: The Logon User Interface DLL Msgina.dll Failed to Load': 
Windows NT Terminal Server (SP3) fails on boot after import
 Error message:
**STOP : 0x0000007B
 INACCESSIBLE BOOT DEVICE
 When you import some Windows NT machines with old service packs, the resulting virtual machine might fail on boot up. Converter upgrades the virtual machine's file system during the import process, and Windows NT systems with older service packs cannot read upgraded NTFS. Workaround: Ensure that the SP on the source machine is high enough to read newer NTFS file systems (SP4 and above).
Changing account credentials results in a 'Multiple connections to a server…' error message
 When going through the wizard for a remote hot clone, if you provide valid credentials for a valid account, then go back and change the credentials to that of another user you may see this error:
'Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.'
 If you want to change the credentials with which you log into the remote machine you will have to do the following: 
Open a command window
Type in net use [remote host name or IP]ADMIN$ /delete
Type in net use [remote host name or IP]IPC$ /delete
Retry with the new credentials
Customization not applied if virtual machine manually restarted after running the Configure Machine option
 The process for customization occurs in this order: 
Customize the virtual machine image with Converter and wait for 100% Complete
Power on the virtual machine
Wait for it to reboot automatically
Sysprep processes the customizations
Sysprep reboots the virtual machine
The Windows operating system loads, and the network configurations occur
 If the user manually reboots the virtual machine after step 2, not waiting for the virtual machine to automatically reboot, the customization process will be broken. Workaround: Turn off Autologon in the source machine. Wait for the machine to automatically reboot during the first boot up. After the first boot, the machine will reboot twice before the user can safely login. Unable to remote hot clone a Windows NT virtual machine to a folder inside a network share
 When remote hot cloning Windows NT virtual machines, you might have problems importing a virtual machine to a sub-folder under a share. In other words, if [hostname]share_name is the network share, remote hot cloning to [hostname]share_name will work, but cloning to [hostname]share_namesub_folder may not.
UFAD Service startup is delayed when user logs in to Converter as 'Limited User' 
 UFAD might not start up before Windows ServicesPipeTimeout (30 seconds) expires if you do not log in as Administrator. If the source machine is busy or running slow, the service does not start quickly enough for Windows and UFAD is no longer running. A user with administrator privileges can restart the service manually.
The 'Configure Virtual Machine' option should not be used on legacy virtual machines
 'Configure Virtual Machine' automatically upgrades the virtual hardware and config file version of legacy virtual machines. If you run 'Configure Virtual Machine' on a Workstation 4.x or GSX Server 3.x virtual machine, the hardware version is irreversibly upgraded: you will need Workstation 5.x+, VMware Player 1.x+, or VMware Server 1.x+ to power them on after the configure operation.
Fault Tolerant RAID causes 'Unable to Determine Guest Operating System' error during hot clone
 If you attempt to hot clone a Windows physical machine, and if the source machine uses Windows software mirroring, the import will fail with the error message, 'Unable to Determine Guest Operating System.' Workaround: Break the software mirror before running the conversion.
Converter does not distinguish between physical serial ports and virtual serial ports on the source machine
 Virtual serial ports are treated as physical serial ports during the migration. For instance, if a source machine has two physical serial ports and two virtual serial ports, the import creates four serial ports on the destination machine.
Converter fails with a runtime error
 If your user name contains the characters ! or &, Converter can fail with the message, ERROR Runtime error, this application has requested the runtime to terminate it in an unusual way. Please contact application support team.
Converter does not uninstall the Converter Agent from a Windows 2000 remote physical machine
 While uninstalling the Converter Agent from a Windows 2000 remote physical machine, the task can fail at 99%. Attempting to manually uninstall the Agent can fail as well. Workaround: Reboot the remote source machine and uninstall VMware Converter Agent manually using 'Add or Remove Programs' in the Control Panel.
Converter Agent might not run after installation and reboot on Windows 2000 and Windows NT4
 On certain slow machines, you might get a error stating the Converter Agent is not running when you attempt to launch it. Windows Service Control Manager has timed out after 30 seconds. Workaround: Set the ServicePipeTimeout value under HKEY_LOCAL_ MACHINESYSTEMCurrentControlsetControl to 120000 (120 seconds).
Importing a Windows 2000 virtual machine fails when an OEM-type partition is selected
 When selecting individual volumes for a clone, with or without resizing the volumes, do not select any OEM or diagnostic partitions on the disk. The only volumes needed are the active, system, and any data partitions.

 MANAGED PRODUCTS 
Remote hot clone to a managed destination fails if the source virtual machine is not able to reach the destination without the fully qualified hostname
 When doing a remote hot clone to ESX Server, you might see the following error in the Datastore selection page if you do not provide the Fully Qualified name and if the source machine cannot resolve non-Fully Qualified names:
Unable to find the server.
 Please verify that the server name is correct and then try again.
 Workaround: Use Fully Qualified names.
Cloning a large disk with lots of free space to an ESX Server destination fails
 Selecting 'Import all disks and maintain size' on the Converter wizard Source Data page when converting a large disk with lots of free space to an ESX Server destination can cause the import to fail. Check the logs, and if there are error messages with NFC failures, use the 'Import volumes . . .' method with or without resizing.
Converter does not support, as destinations, clusters in which the VMware DRS is set to partially automated or fully automated.
 For a destination, choosing a cluster with an automated DRS setting produces an error message: 'Sorry, automated clusters not yet supported.' Converter can import to a cluster only if its DRS settings are set to manual instead of automatic.

 THIRD-PARTY FORMATS 
Converter does not prevent incompatible imports of certain third-party images
 In Converter, you can import third-party images with guest operating systems' that are the same version or lower than that of the host operating system. However, Converter does not prevent you from doing an incompatible import, and the resulting task fails. Workaround: Make sure that the guest and host operating systems are compatible before creating a task.
Converter does not support Symantec Backup Exec 11
Separate backups should be stored in different folders
 Storing more than one third-party backup in a single folder results in a failed migration. Before using Converter to import the image, each backup should be placed in its own folder.
Resolved Issues3 0google The following are known issues in Converter 3.0. that have since been resolved.

GENERAL
Incorrect message about hardware compatibility during linked clone. Release 3.0.2 corrects this problem. 
Hot cloning fails with a source machine that is low on disk space. Release 3.0.2 corrects this problem.
Virtual machines imported from .sv2i images of systems with diagnostic partitions might not boot because the imported image is not complete and the diagnostic partition is missing. Release 3.0.2 corrects this problem.
Converter cannot hot clone a remote physical machine that has Workstation 6 installed. Release 3.0.2 corrects this problem.
Import of a Windows 2003 machine to a managed destination fails with an unhelpful help message when a virtual machine with the same name already exists on the destination. Release 3.0.2 corrects this problem.
Remote hot clone of the same source machine can fail the second time. Release 3.0.2 corrects this problem. 
Converter 3.0 could fail in a hot clone of a physical machine configured with dynamic disks. Release 3.0.1 corrects this problem.
Converter 3.0 permitted users to mount a read-only network share as the %TEMP% directory during cold cloning, which would result in an error. Release 3.0.1 corrects this problem.
Cloning of some hosts, especially if they had diagnostic partitions, could fail during post-processing with 'can't create undo folder' error messages at the end of the log. This release fixes the problem by correcting the handling of boot.ini.
Converter decreased RAM by 4MB in the destination virtual machine. This problem is fixed in this release.
Converter could fail if you selected 0 NICs in the destination virtual machine and also selected any Customization options. Release 3.0.1 corrects this problem.

HOSTED PRODUCTS
Installing Converter on a system with Workstation 6 beta installed could lead to unexpected errors. Workstation 6 beta 3 fixed coexistence issues between it and Converter 3.