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.

Comments

Gabriel Callegari
Reply

Dear Niklas,

a client of mine has VMM Server 2012 SP1 on a Windows 2012 (not R2), and used to manage the VMM console from a notebook with Windows 10. A few months ago he upgraded to Windows 10 Anniversary edition (v1607) and now the VMM console under Windows 10 crashes. I was consulted, and I could read on several websites that Update Release 11 fixes that bug…BUT FOR VMM 2012 R2. I upgraded both Server and Console to the latest UR available for VMM 2012 SP1, but had no luck to make the console work under Windows 10 v1607. Do you have any workaround/patch/solution? Thank you very much in advance… GABRIEL (from Buenos Aires, Argentina)

Leave a comment

name*

email* (not published)

website