1 person found this helpful
Windows 2003 is still supported in vSphere 6.5 - VMware Compatibility Guide - Guest/Host Search .
So you can install VMware vCenter Converter Standalone 6.0 on one of your machines and run the P2V to vSphere 6.5. It should work fine.
I would also recommend VM HW version 11 (vSphere 6.0) to begin with and you need VMware Tools for legacy OSs - VMware Tools 10.0.12 Release Notes .
Hope this information helps.
This thread is old, but it was one of the first ones to pop up when googling how to convert Windows 2003 server.
I know this is not supported, but I could convert with vCenter Converter 6.2 with the steps below.
I couldn't download vCenter Converter 6.0 from the official site as it's not provided anymore, so I just tried with 6.2.
- Install all Windows updates on Windows 2003 server. If Windows Update is complaining that it cannot connect to update server, install Internet Explorer 8.
- Install vCenter Converter 6.2 on a Windows 10 computer.
- Manually copy the Converter Agent Installer, VMware-Converter-Agent.exe located at C:\Program Files (x86)\VMware\VMware vCenter Converter Standalone
- I couldn't deploy the Agent with vCenter Converter, so I copied it manually to the Win 2003 server, source: https://kb.vmware.com/s/article/1021465
- Disable firewall on the source computer.
- Convert the VM to HW 11.
- I installed VMware Tools 10.0.12 as suggested in the previous message.
Before starting the conversion there was a warning of source not having sysrep files or something like that, but I just ignored the warning.
I didn't do extensive testing with the VM, but I could power it on and RDP to it.
My destination was ESXi 6.7 U2.
Source was 32 bit Windows Server 2003 SP2 Enterprise Edition.
The vCenter converter 6.0 cannot convert p2v directly to the VMware 6.5 version
I can advise you to convert it to an environment with vCenter 6.0, then export vm and import to vCenter 6.5