RecepYUKSEL

3 Sep 2014 6:45 AM

Thank you.

Ed (DareDevil57)

3 Sep 2014 6:58 AM

thanks for sharing.

Ed (DareDevil57)

3 Sep 2014 6:59 AM

thanks for sharing.

Mustafa YUKSEL

3 Sep 2014 8:44 AM

Thanks for sharing Rhoderick. Have a nice day.

Sam Boutros

9 Sep 2014 12:22 AM

perhaps not direct import export, but we can:
1. Remove the integration services from the VM,
2. Build a new VM on 2012 host using the same VHD(x) disks
but I cannot imagine why would anyone want to downgrade from 2012 R2 to 2012..

Rhoderick Milne [MSFT]

9 Sep 2014 6:20 AM

Exactly Sam, and that's what's in here http://blogs.technet.com/b/rmilne/archive/2014/09/03/importing-server-2012-r2-hyper-v-vm-into-server-2012.aspx

In terms of wanting this, its kinda clear cut on the import/export side. However this also applies to live migration too - so if someone moved the VM over to test out a net new 2012 R2 box then it cannot move back to 2012.

I do agree - In general it is normally upwards and onwards when it comes to such things.

Cheers,
Rhoderick

Chris

19 Nov 2014 7:43 PM

One scenario I ran into with this....I had pre-configured a server using hyper-v manager on my windows 8.1 machine to be imported later at the office into my 2012 hyper-v server......however i got the same error messages using the powershell method and using the gui.

Windows 8.1 and Server 2012 r2 have this issue with backward compatibility on importing vm's.