Convert to generation 2 on a VM in Hyper-V 2012 R2 with Powershell

I have done blog posts about why you should create your new VM´s with Windows Server 2012 instead of 2008 R2 or older even if you were not able to create them with the generation 2 at that time as the Windows 2012 R2 was not released back then.

I also did a blog post how to use a third party product to do the migration from generation 1 to 2 with Double Take Move software.

Now I found John Howards script that he has made public that does the migration from generation 1 to 2 🙂 He also has a blog series about generation 2 VM´s that is definitely worth the time to check out.

I got an error when running it though and it seems that it does not work so good with the partition on the gen 1 virtual disk..  It appears that when I have created my virtual machine with the Convert-WindowsImage.ps1 script that only creates one partition the row in the script that checks for $partitions.length fails and I could not get it to continue but when I commented that away I got my first conversion on the way 🙂

Screen Shot 2013-10-30 at 20.40.59

And here you can se in the PowerShell ISE my alteration  🙂

Screen Shot 2013-10-30 at 22.15.58

Now I am sure that John and his team will work and distribute new versions with correct error checking and I am truly glad that they have released this so I could test it right now anyway 🙂 !!

Here is my VM in generation 1

Screen Shot 2013-10-30 at 21.50.07

And here is the converted VM,

Screen Shot 2013-10-30 at 22.21.34

And here you can see that during the conversion that I have two disks attached to my server and that the one at the bottom has got some new partitions for the gen 2 UEFI boot process

Screen Shot 2013-10-30 at 22.15.03

Happy converting and making generation 2 VM´s your standard in Hyper-V

SC VMM 2012 SP1 UR4 – fixes the Cluster resource bug

I have on my blog done a post about how the VMM 2012 Sp1 not updated the cluster resource when doing Live Storage migration from one CSV volume to another in a Hyper-V cluster and now in the Update Release 4 of VMM 2012 SP1 they have finally fixed it!

Here you can see the Issue 13 that has been fixed

Screen Shot 2013-10-29 at 23.08.44

Also as in Issue 15 there was stuff left after a canceled or failed migration

Screen Shot 2013-10-29 at 23.09.00

One thing that could have been a wish was that they in this UR would have added the Windows 2012 R2 as an operating system, you can run Windows 2012 R2 as virtual machines in your 2012 Hyper-V but not assign the right OS on the properties on the VMM 2012 Sp1 🙁

vmmos

In Hyper-V this does not have an impact for the successful boot as in VMware VM´s where you set the best matching OS for the boot process to work flawlessly. In Hyper-V it uses the same BIOS for all your VM´s and this list is something for VMM and the database.

Strange Creation Date on Hyper-V 2012 R2 VM

I have some VM´s on my new Windows 2012 R2 host that have a strange creation date on the properties.

The VM´s have been created on different times and it was a customer that noticed it.

quite fun as there was not computers or even Hyper-V invented in the 17 century or was it? 😉

Here is my lab/demo VMM 2012 R2 virtual machine and as you can see it is created the 1 of january 1601

WOWAn

 

and here is the other virtual machine, a windows 8 template

Screen Shot 2013-10-29 at 21.59.33

 

I have not been able to reproduce it now with either PowerShell or via the GUI, If you have seen the same issue please comment the post 🙂