I had this error when I installed version 4.x.x of the Converter software on a Windows 2000 server. After some research it seems that ONLY the Converter 3.0.3 version is compatible with Windows 2000 Server SP4. It is a tricky version to get hold of but is available if you search.
After installing the latest Windows updates and restarting the server you get the message ‘Preparing to configure Windows – Do not turn off your computer’ which seems like it has hung.
Initially I was unable to connect to the server at all via vSphere client or RDP. After a mild panic I connected to each vSphere node with the vSphere client until I found the server that was hosting the vCentre server. I was then able to access the console.
Panic over I decided to restart the server which kick started whatever update had crashed the server and I was able to then log in.
I received this error when trying to upgrade an ESXi 4.1 server to 5.1. The error is caused when the No-Execute Memory Protection option is set to disabled. In my scenario I had a HP server so this was quite a simple process to enable the option in the BIOS. I was then able to run the setup successfully thereafter.
You receive the error when using Veeam Backup and FastSCP 3.0.2 and when you are attempting to transfer files between a client and an ESX/ESXi server.
Found this excellent post which recommended upgrading the Veeam software from 3.0.2 to 3.0.3 and voila it does indeed work:
I tried to move a Windows 7 VM from ESXi to vSphere but as it neared completion the Converter stated that it had failed.
After a little search I found this from VMware
It described a long process of going through an OS repair mode on the original source machine and using BCDEDIT to reset the partition settings used during the boot process.
I didn’t go through the repair process but instead booted the source VM to run the three BCDEDIT commands that it lists. I was only getting success with the first one:
bcdedit /set {bootmgr} device partition=C:
and an error regarding syntax with the other two commands:
bcdedit /set {default} device partition=C:
bcdedit /set {default} osdevice partition=C:
In the end and out of curiosity I checked the destination VM because even though it had errorred, it had still completed the conversion and was listed as a powered off VM in the Virtual Infrastructure.
Strangely it powered on and worked as normal! I can only assume that the error was some kind of registration problem as the VM functions correctly and its’ partitions are listed correctly.
I find sometimes that the POST screen can pass too quickly which makes it pretty impossible to to access the BIOS.
If you are using vSphere or ESXi connect to the server using the vSphere or VI client
Right click on the VM that you need to access the BIOS of
Select Edit Settings then Options
Click on Boot Options and in the right hand pane tick the box under the Force BIOS setup field
Restart the VM and the BIOS will automatically load. This will only happen once so if you need to access it multiple times then you will need to manually set it each time
I accidently disabled the VMware Tools Tray icon on a VM and subsequently couldn’t find a way to re-enable it
Had an issue moving a Windows 2008 x64 R2 Server and constantly recived the error unable to determine guest operating system.
Found this excellent solution here http://wiert.me/2010/06/10/vmware-converter-4-01-unable-to-obtain-hardware-information-or-unable-to-determine-guest-operating-system/
Was able to change the guest operating system to just Windows 2008 and was then able to convert. Then I was able to change the guest OS back to R2 x64 after the conversion.
