I am using standalone converter ver. 4.0.1 build-161434 in windows 2003 Standard R2 with SP2 (Dell 2950) to make vm to vmware esxi 4 server.
Only 95% the conversion got failed. I have attached the error and logs for the references. I done the troubleshotting as mentioned :
a) Copied the sysprep file to all users\documents and settings\vmware\ location.
b) Only selected one drive for test, but no luck.
c) Up to date windows patches installed, rebooted the server and ran the job, but failed at 95%.
d) Ran the vm conversion job from another server instead of using locan one, but it failed at 95%.
Please help me to get rid of this. Early responses are highly appreciated.
Regards
Udayan Sarkar
Did the VM arrive ?
If yes - try to start it - if it comes up with a BSOD 7B please post the vmx-file
do you get 7B bluescreen or a different one ?
Yes, I am getting blue screen. But unable to view as it is quickly restarting.
try to run Converter again - this time select "configure machine" and point to the already created VM.
If that fails - please post the boot.ini
It is showing "Unable to obtain hardware information for the selected domain."
please post the boot.ini
For physical server or vm one.
I guess they are the equal - anyone will do
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2003, Enterprise" /noexecute=optout /fastdetect /3GB /PAE
ok - that smells like trouble
can you remove the entries /3GB /PAE in the boot.ini of the VM ?
I would also like to see a screenshot of the disklayout of the existing vmdk
Could you try the conversion, or at least configure task, with standalone Converter 5.0?
Getting...Warning: Unable to locate the required Sysprep files. Upload them under 'C:\Documents and Settings\All Users\Application Data\VMware\VMware vCenter Converter Standalone\sysprep\svr2003' on the vCenter Converter server machine. See 'Help' for more details.
dont use sysprep in a tricky case like this
How can I edit boot.ini in VM ? It is not even running.
best option is to use a LiveCD
second best: attach the vmdk to another working VM
Still failed in 98%. Uhhh so fraustated.
Please upload log bundle for failed conversion.