One of the issues some of you will have to address when moving from Windows Server 2008 or Windows Server 2008 R2 will be the migration of your virtualized machines onto the newer Hyper-V in Windows Server 2012.
http://mschnlnine.vo.llnwd.net/d1/inetpub/kevinremde/KROmniture.htmThe good news is that you won’t have to re-build or recreate machine configurations. In fact, it’s a fairly straightforward import at worst.
In Part 10 of our “Migration and Deployment” series, my friend (and newest member of our team) Tommy Patterson provides an article describing just how it’s done.
READ HIS EXCELLENT ARTICLE HERE
Have you done this migration yet? Have you even bothered to try out Windows Server 2012? What about the free Microsoft Hyper-V Server? What do you think?
3 thoughts on “Migrating Hyper-V Virtual Machines – Migration and Deployment (Part 10 of 19)”
I disagree with the author regarding admins not wanting to do an in place upgrade. If it's supported, many will prefer that if the only role the machine is server is as an Hyper-V server.
Thanks for the comment Tom, I think what I meant was "many" admins especially those that inherited environments from past admins, or see Server 2012 as new technology that opens many doors would feel that a fresh install would be preferable. Thanks for calling this out, I will look to reword it a bit to be more clear.
The newly revised post reads this way:
Since in-place upgrades of server operating systems is not something some administrators like to do for various good reasons(ex. inherited the environment, past hardware issues, lack of documentation for prior deployments), a simpler way to upgrade the Hyper-V infrastructure is to simply blow away the current operating system, then install Server 2012 fresh on the hardware.
Hope this clears up my thoughts on it. Keep it coming Tom!