I've had mixed results when using Converter with (physical) Windows machines. Sometimes, the conversion process will go smoothly, and all that's needed to get the newly-virtualized machine up and running is a couple of reboots and a reactivation. Other times, the guest will BSOD on the first boot, and nothing I do thereafter will make the VM boot.
Is there anything in particular I should watch out for when performing the conversion?
> Is there anything in particular I should watch out for when performing the conversion?
Yes - most important is to understand that Converter is just one of the tools to get the job done.
Using Converter is no art in itself.
You want to acchieve the end-result : which is a vmdk-file plus a vmx file that boots in ESX.
To do that you have to do 3 steps:
Converter makes this 3 steps look as if it was one single step.
So if a VM bluescreens folks think the whole process failed and they start over again - wasting lots of time.
Step 1 is a success if the VM boots and then throws the error: "No OS found"
Step 2 is a success if the VM boots with a bluescreen - it is a failure if you get "ntldr missing" or "No OS found"
Step 3 is a success if the VM boots and finds new drivers - it is a failure when you get bluescreens.
Next time you get a bluescreen as the result understand that this is no complete failure - instead realize that the first 2 steps are done and you only have to do step 3 again.
The patching drivers part has a wizard in Converter called "configure machine"
Patching drivers can also be acchieved with more reliable procedures using a LiveCD against the bluescreening VM.
All Converter versions use an over-simplified GUI to patch drivers. It is important to understand the start conditions that are required to make the "configure machine" wizard work.
Not sure if it is worth the effort to explain more - some folks simply insist on using latest Converter 4.3 and tell me that editing registry yourself is not mentioned in the Converter doumentation. If you are one of those blockheads I would only waste my time ![]()
Anyway - Converter may be the most convenient double-clickable tool to get the job done - but you can also do any of the 3 steps involved with various other tools that are more reliable, predictable and sometimes also faster.
For the end result it does not matter if you create the new VM with Converter, Vi-client, Workstation or a texteditor
For the end result it does not matter if you do the imaging step with Ghost,Acronis, Knoppix, disk2vhd, vmware-vdiskmanager, Converter ...
For the end result it does not matter if you do the patching step with Converter or manually with a LiveCDhe
as soon as you understand that there is always plan B you can look forward to the next p2v in a relaxed way
which version of converter you are using? standalone or enterprise?
Standalone
Disable unnecesary services, like AV / Firewall whille converting
Check for dongles and other dependencies
Install VMTools if possible
What error are you getting on the BSOD? Can you safe boot?
I have converted (literally) hundreds of Windows hosts and only ever once had a BSOD - caused by 3rd party software that did not like the change.
Have you noticed any common trends amnong the machines? mnoving to same VLAN? moving to same ESX host? Could the actual physical ESX host have dodgy hardware perhaps?
> Is there anything in particular I should watch out for when performing the conversion?
Yes - most important is to understand that Converter is just one of the tools to get the job done.
Using Converter is no art in itself.
You want to acchieve the end-result : which is a vmdk-file plus a vmx file that boots in ESX.
To do that you have to do 3 steps:
Converter makes this 3 steps look as if it was one single step.
So if a VM bluescreens folks think the whole process failed and they start over again - wasting lots of time.
Step 1 is a success if the VM boots and then throws the error: "No OS found"
Step 2 is a success if the VM boots with a bluescreen - it is a failure if you get "ntldr missing" or "No OS found"
Step 3 is a success if the VM boots and finds new drivers - it is a failure when you get bluescreens.
Next time you get a bluescreen as the result understand that this is no complete failure - instead realize that the first 2 steps are done and you only have to do step 3 again.
The patching drivers part has a wizard in Converter called "configure machine"
Patching drivers can also be acchieved with more reliable procedures using a LiveCD against the bluescreening VM.
All Converter versions use an over-simplified GUI to patch drivers. It is important to understand the start conditions that are required to make the "configure machine" wizard work.
Not sure if it is worth the effort to explain more - some folks simply insist on using latest Converter 4.3 and tell me that editing registry yourself is not mentioned in the Converter doumentation. If you are one of those blockheads I would only waste my time ![]()
Anyway - Converter may be the most convenient double-clickable tool to get the job done - but you can also do any of the 3 steps involved with various other tools that are more reliable, predictable and sometimes also faster.
For the end result it does not matter if you create the new VM with Converter, Vi-client, Workstation or a texteditor
For the end result it does not matter if you do the imaging step with Ghost,Acronis, Knoppix, disk2vhd, vmware-vdiskmanager, Converter ...
For the end result it does not matter if you do the patching step with Converter or manually with a LiveCDhe
as soon as you understand that there is always plan B you can look forward to the next p2v in a relaxed way
