It is a Rich & wonderful posting, very systematic and descriptive, any dumb can convert a P2V. Keep mailing these kinda stuff.

VERY IMPRESSED.

Thanks
Anand MB
Bengaluru -INDIA

SQL servers can be P2V'ed as a rule, but it helps to understand your SQL implementation as a physical server first and duplicate it (as needed) as a VM. For example, if your phyiscal SQL uses RAID 10 but you end up with a VM on VMFS LUN on a RAID 5 array you might be compromising performance. You also want to be sure not to overload one LUN with several heavy I/O VMs.

Thank you, Tom

That's a tough one to answer generically.

Did you integrate the 2003 64 bit version of sysprep with VMware Converter? Each Windows OS has it's own version of sysprep, and Converter has a folder for each version to placed in separately. After that, the sysprep should occur after the new VM boots for the first time and you should see an automatic reboot.

Are you installing VMware tools during the p2v too? That could also interfere so try it without and manually add them afterwords.

I am using VMWare convertor and doing P2V for win 2003 X64 OS.
I am selecting customize option while doing and generating new SID, but after P2V or V2V, I am getting same host name in target VM as source ( Physical machine)

Any clues?

Thanks in advance for help.

I am using VMWare convertor and doing P2V for win 2003 X64 OS.
I am selecting customize option while doing and generating new SID, but after P2V or V2V, I am getting same host name in target VM as source ( Physical machine)

Any clues?

Thanks in advance for help.