• Vmware Converter Windows 2003
• Vmware Converter For Windows 2000
• Vmware Converter 4

Vmware Converter Windows 2003

Vmware Converter For Windows 2000

We are trying to convert a Windows Server 2000 Physical server to a Virtual Server on ESXi 5.5. In the converter when it goes to the de. 10 replies VMware. We need to convert Windows Server 2000 sp4 DC into vSphere. Unfortunately vSphere 4.1 with Converter 4.2 (4.3) is not supporting Windows 2000 anymore.

We need to convert Windows Server 2000 sp4 DC into vSphere. Unfortunately vSphere 4.1 with Converter 4.2 (4.3) is not supporting Windows 2000 anymore (received error code 1603). So we decided first to downloaded vCenter Converter Standalone 4.0.1 and installed it on XP machine. Agent is installed but when we try to connect the agent just stops responding. This is the output of the logs saved by the agent on the 2000 machine. Section for VMware vCenter Converter Standalone, pid=4396, version=4.0.1, build=build-161434, option=Release 2010-12-09 21:50:28.750 01980 warning 'App' Failed to create console writer 2010-12-09 21:50:28.750 04136 info 'App' Current working directory: C: Program Files VMware VMware vCenter Converter Standalone 2010-12-09 21:50:28.750 04136 info 'Libs' HOSTINFO: Seeing Intel CPU, numCoresPerCPU 1 numThreadsPerCore 2. 2010-12-09 21:50:28.750 04136 info 'Libs' HOSTINFO: This machine has 2 physical CPUS, 2 total cores, and 4 logical CPUs.

Vmware Converter 4

2010-12-09 21:50:28.750 04136 info 'Libs' Using system libcrypto, version 9070AF 2010-12-09 21:50:29.921 04136 info 'App' Vmacore::InitSSL: doVersionCheck = true, handshakeTimeoutUs = 120000000 2010-12-09 21:50:29.937 04136 info 'App' ,0 MntapiInit Asked - 1.0 Served - 1.0 was successful,TempDirectory: C: WINNT TEMP vmware-temp vmware-SYSTEM. 2010-12-09 21:50:29.937 04136 info 'App' serviceWin32,413 vmware-converter-agent service started 2010-12-09 21:51:50.937 04140 info 'App' serviceWin32,277 vmware-converter-agent service stopped Any idea what can be wrong? I did a quick test with clean install of 2000 sp4 and it is working great. Here is current progress - not able to connect to any 2000 machine in our network - able to convert 2003 machines with Converter 3.0.3 and vmkfstools into vSphere - able to convert 2008 and 7 machines with Converter 4.2 plugin into vSphere and. if I try to connect with Converter 3.0.3 to any other machine I get 'ERROR: Failed to take snapshot of a source volume.

Possible causes include not having any NTFS volumes on Windows XP or Windows 2003 source systems, and not having enough free disk space.' - if I try to connect with Converter 4.2 to any other machine I get 'error code 1603'.