~ Mike Briggs | Supportability Program Manager
Per the Release Notes for Virtual Machine Manager in System Center 2012 R2, the previous P2V functionality has been removed. The diagram below outlines the mitigation process to perform P2V conversions in a System Center 2012 R2 Virtual Machine Manager environment.
1. Use a down-level version of VMM such as VMM 2012 SP1 to perform any remaining Physical-to-Virtual conversions. This will require that you install VMM 2012 SP1 or earlier if not already available in your environment.
2. Identify the server to be converted to a virtual machine.
3. Use the Convert Physical Server to P2V the intended target.
4. Using Hyper-V Manager, Export the new VM to a Host being managed by System Center 2012 R2 VMM (VMM 2012 R2)
5. Import the VM to that Host
NOTE: VM’s from Windows Server 2012 can be imported on Hosts running Windows Server 2012 and R2 only.
The Product group is aware of the P2V requirement and is working on alternate methods to provide this functionality.
Mike Briggs | Supportability Program Manager | Microsoft GBS Management and Security Division
Get the latest System Center news on Facebook and Twitter:
System Center All Up: http://blogs.technet.com/b/systemcenter/ System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/ System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/ System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/ System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm
Windows Intune: http://blogs.technet.com/b/windowsintune/ WSUS Support Team blog: http://blogs.technet.com/sus/ The AD RMS blog: http://blogs.technet.com/b/rmssupp/
The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
Will this mean that tools like MAT will no longer work as well or do they use different tools that will still work for doing V2V at least?
Reading through the Release Notes I get the sense that VMM 2012 R2 has been rushed out to meet the Server 2012 R2 GA date.
VMM 2012 R2 doesn't support Gen2 VM's? - I imagine a cumulative update will bring this support some time in the future but this should have been in the product at GA. You take the time to remove P2V but don't take the time to ship Gen2 VM support?
Non-functional SCOM dashboard in the media? - Where is the Quality testing here?
I also struggle to understand what is the thinking behind retiring the P2V feature within VMM 2012 R2? - yes there's alternative stand alone tools and 3rd party products etc but why remove a feature that serves its purpose fine and replace it with a terrible 'down level 2012 SP1 server' solution that is quite frankly messy and in no way slick. I cant take the advice "keep an old version around" seriously!
I have to agree with Gary: why remove a fundamental feature of Hypervisor Managment? No SCOM integration worth using, no G2 support, has the baremetal configuration for hyper-v been improved or is that basically useless still a well (actually why wasn't it simply scripted into SCCM instead of SCVMM? Let the guys who understand OSD do it)
What about nic configuration for non-virtual switches?
R2 isn't worth advertising at this point: nothing seems to have improved and things are being taken away.
For years you hear the term 'Single Pane of Glass' mentioned in MMS and TechED keynotes and we are still being asked to pick an interface depending on what we are trying to achieve?
Brad Anderson should do a new blog post entitled "You wanted a pane of Glass?, I thought you said pain in the...."
SCVMM 2012 R2 / Windows Server 2012 R2
.... oh dear, what a shame.
Thanks for the feedback folks.
In discussion with customers, conversion capabilities are best served as standalone tools that can be released at a cadence faster than the product itself. Take for example the case when a new version of vSphere is released, this allows us to add support for that version in the tool as opposed to wait for the product ship. It is with this goal that we moved out P2V.
On the support for Gen2, it is there in SC 2012 R2, VMM. It was not there in the preview release but has been added since. So, get those bits on Oct 18 and give it a whirl.
As always keep the feedback coming.
(Group Program Manager, VMM, Microsoft Corp)
@Vijayte: If I was being picky I would point out that "released at a cadence faster than the product itself" would mean that the "alternate methods to provide this functionality" would be available prior to GA of R2 on October 18th.
If your then saying that the alternative method will be released at some point between 2012 R2 GA and the v.next in x months/years time then I'm still none the wiser when I should expect an alternative.
Lucky I'm not picky.....
Just sent this to our MS TAM:
"The message this is sending to us is that MS appears to be making it more complex for organisations like Kmart to convert physical servers to run on Hyper-V. While there are many customers running hypervisors in their DCs to consolidate, many orgs are still working through virtualisation of branch office workloads. To have P2V functionality removed doesn’t make sense to organisations that still have to go through the ROBO virtualisation process."
Vijayte. You have made mention of standalone conversion tools. Is MSFT developing standalone conversion tools?
I have to agree that removing P2V functionality is very silly. It is always going to be a relevant feature so long as you are able to install a application on a physical server.
When will Microsoft get it? If you intend to replace the feature with a stand-alone tool, release the tool before you remove the functionality... Whoever made that engineering decision should be demoted.
So now, why in the world would I use Hyper-V over VMWare if I need to virtualize my datacenter? Here's how this plays out:
VMWare: Download and install VMWare Converter, point it to ESXI host, and the wizard takes care of the rest FOR FREE.
Microsoft: Buy System Center, bring up instance of old VMM, install agent on physical, convert, export using Hyper-V Manager, then import into current version of VMM.
Yup, I'm sticking with VMWare on this one. I'm a MCITP that is forced to use VMWare where I work because my team is not going through that stupid process every time we need to convert a physical server...
Yes I get it, VMM is NOT the Hypervisor, in fact we all get it. The Lack of documentation for a released product aside, taking away the administrative bits piece by piece (or bit by bit) leads me to wonder just how lazy development is. I always hear "our customers say" yet none of my peers are confirming these requests just more bemoaning YAM (yet another Microsoft) removal of a desired feature. I suppose I could run a mixed bag of SC products or add even more vm servers to precious resources to support what should be.
This is a viable alternative that is not mentioned in the blog post:
Any news about the 'alternative methods' for the P2V requirement the product group is working on?
oh my gourd! why wasn't this in bold somewhere in the release notes? we just went through the trouble of rolling out a new VMM 12 R2 server only to realize P2V wasn't there when we needed it. yes, we should know better, but live P2V is about 33% of the reason to own VMM in small datacenters. why remove such a huge selling point?
Disk2vhd tool is not even close. do you want your customers to go back to VMware because you just removed a pretty important checkbox from your comparison list?