VMM: Tips About P2V Conversions in Virtual Machine Manager 2007
Just another of my personal experiences with VMM. I just completed a P2V of a Windows Server 2003 Domain Controller. Actually, it was a V2V as I was using my virtual environment. Anyhow, one of the things to be aware of is that after doing the conversion and bringing the other system online it prompted to reactivate Windows due to the "significant hardware changes".It also required a system restart due to the same newly detected hardware. Not a big deal, so to speak, but certainly a concern for production environments.
Lastly, I have to admit that the conversion process was not seamless. Because you’re transferring a live server to a virtualised version of the same, there are additional concerns that you have to tend to. Probably the most important of these is the need to properly reconfigure your network settings on the VM. While I updated my virtual machine settings to include the proper IP configuration settings, it actually took yet another restart for those settings to take effect. While I thought this odd, I was too tired and frustrated to try to figure it out. (continue at source)








