During TechEd 2011 in Atlanta last week I immersed myself in almost all of the VMM 2012 sessions. There is a lot of great stuff coming down the line and a whole new learning curve for new capabilities that can automate LUN creation., Networking, Load Balancers, and Host provisioning just to name a few. There is even Host, Library, and VMM server patching capabilities that can tie directly into your WSUS 3.0 SP2 server. All great improvements, but as VMM and Microsoft server virtualization products have matured, we have finally come to a point where support has been dropped for a past product. Virtual Server 2005 R2 SP1 will no longer be supported in VMM 2012. Which means you will not be able to manage any of these legacy hosts. Not that there are many installs still out there, but it is a passing of a product that I spent many hours with over the years.
Below is the official word and some guidance from the VMM team as a response to my query for support in VMM 2012.
Posted by Microsoft on 5/20/2011 at 6:12 AM
“will pass on the feedback. Due to products reaching their end of life it difficult to continue adding support for these products.”
Posted by Microsoft on 5/20/2011 at 10:59 AM
“Thank you for your feedback Rob, unfortunately at this time we cannot accommodate this suggestion, the VMM 2012 product is going through stabilization phase right now and therefore our whole focus is right now is to make VMM 2012 robust, reliable and fast.
My suggestion would be to move all of your VMs that are on Virtual Server with VMM 2008 R2 SP1 before upgrading to VMM 2012.
Our V2V feature in VMM 2008 R2 SP1 will help you greatly with this task. Otherwise VMM 2012 upgrade code will ask your permission to remove all of your Virtual Server hosts from your environment during upgrade (you can always say NO and cancel upgrade at that stage).
If you don’t transition your VMs with VMM 2008 R2 SP1 and upgrade, all of your VS hosts will be removed from VMM’s management, (VS hosts and VMs will still continue running with of course) but at this time you would have to move your VMs manually to Hyper-V, as you may already know the VHD format is compatible between Virtual Server (VS) and Hyper-V once you remove the additions from VS VM. So the procedure will be to uninstall additions from each VM on VS host and then copy that VM manually to Hyper-V host and register it, then install Hyper-V integration components to each VM.
Therefore I suggest you do this work prior to upgrade with VMM 2008 R2 SP1.
Hope this helps.
With your permission I am resolving this bug as Won’t Fix.”