I then retried this on the external server so Converter points directly to the actual ESXi host that has the datastore, it was a none flyer - presenting an error that the host was managed by a vCenter and to connect there instead. This is a real shame, maybe there is some config option. After observing the behaviour of doing a test 2003 P2V inhouse I could see that the source physical server establishes a direct 443 & 902 connection to the target host and not the vCenter. This seemed to look good, allowing a job to be created and selecting an internal ESXi (172.16.x.x) as the host system but it kept resulting in the File I/O error when I attempt to submit the job.
I have white listed it's external IP so traffic from TCP 443 & 902 are directed to vCenter.
The Windows Server is hosted externally as a singe box.
0 kommentar(er)
