I have completed dozens of P2V migrations for various clients and have to walk down the same path each time. One of these days I will get around to scripting some of this stuff, but wanted to at least highlight the steps I take here. I do all of this work on the new VM, despite that it could be done on the physical server before doing the migration. If you do that though, you lose the ability to roll back to the physical server as a failback. I would rather do the work on the VM knowing I can always simply power up the physical box. Steps below:

1) Remove all of those pesky OEM hardware monitoring tools. This includes IBM Director agents, HP SIM, and Dell Openmanage. Since the hardware is no longer OEM, these tools won't be able to launch their services properly and will complain loudly.
2) Remove drivers that exist for hardware that doesn't. The ATI driver on Dell machines comes to mind. So does the Broadcom or Intel drivers for most OEM systems. Go ahead and remove the management tools for these pieces of hardware too. No need to team your NICs in your VM if you have dual uplinks attached to the vSwitch anyway.
3) I have found that APC PowerChute will kill a VM on restart. You will need to drop to Safe Mode and remove it because the service is not present in the service console. Not sure what version I came across, but it also didn't have an MSI based install, so I was able to remove it from Add/Remove programs in Safe Mode.
4) Even if you uninstall all of the software related to the OEM hardware, the entry in Device Manager typically remains. This is easy enough to remediate in the GUI by issusing the following commands: