SCVMM is unable to handle this conversion - just tells me flat out that my Proliant 3000 (yes, go ahead and laugh) isn't a P2V option unless I upgrade it to 2003 server for an online conversion.
Just wondered if anyone had already skinned this cat before I get started.
 I should mention that the eventual destination is a HyperV server, so I'll be putting the poor VM through a SCVMM conversion to VHD, in case that has any impact on the answer.
Update The .vmdk from the Converter works phenomenally ... in vmware player. Converting with either vmdk2vhd or SCVMM results in a machine that freezes during windows load, or a blue screen.
Reading up teaches me that VMWare machines boot to SCSI, and hyper V CANNOT boot from SCSI, which is what the converter is supposed to remedy. So far I've tried removing scsi devices before the conversion (didn't help) and replacing the %windir%\system32\hal.dll with one from a functioning VM of the same OS/patch (no joy).