Hello,

I have a single server Exchange 2013 installation on Windows Server 2012.  I need to virtualize this server onto new hardware using Hyper-V and VMM.  Could someone please give me guidance as too the best way to accomplish this.  Somewhere I am doing something wrong.  I tried Disk2VHD but when I created a new VM and added this vhd the virtual machine would not start.  When trying both online and offline P2V within VMM the process fails along the way.

Someone please point me in the right direction as I am under the gun to get this migration done.

Your help is greatly appreciated.

Thanks,

Kevin

Hi,

We can refer to the following article:

http://technet.microsoft.com/en-us/library/jj619301%28v=exchg.150%29.aspx

Thanks,

If you have feedback for TechNet Subscriber Support, contact tnsfl@microsoft.com

Thank you for your reply, however this does not help me convert my existing physical exchange server over to virtual.

Kevin

I just tried an offline P2V today and the process fails during the VM Integration Services phases after the the hard drives have been copied and the physical machine has been rebooted.  I get two errors:

Error (13210)
Timeout occured while waiting for VM Intergration services to be installed on virtual machine "NEWP2V" residing on host "VMMHOST".

Error (13222)
An internal error occured while Virtual Guest Services were being installed on virtual machine "NEWP2V" residing on host "VMMHOST"

At this point the virtual machine is unable to boot and requesting Windows Repair

Any ideas?  

Kevin

Can anyone help me with this task?  Has anyone had success with a migration like this.  It has been a week and I hoped someone would have commented by now.

Any help is appreciated

Hi Kevin - wondered if you managed to make any progress with this ?
I have an identical project coming up

Any guidance most welcome

Martin

I don't like P2V on a host that runs an app as important as exchange, a lot can go wrong.

I think it would be easier to just stand up a new VM and install exchange (of course test the storage to make sure it can handle the load) and setup the name spaces and certs the same.

From there you can either setup new databases and migrate the user's mailboxes to the new server.  Or you can configure a DAG use that to replicate the databases over to the new server and then decom the physical server.

IMO this is the safe way to migrate from a physical machine to a VM and it involves zero downtime.

• Proposed as answer by Hinte Thursday, January 15, 2015 6:07 PM

Hi,

I have a single xchng 2013 that we are planning to move to hyper-v platform. Regarding your second option, if I give the new vm guest the same name as the physical one, how am I going to replicate the database? Would you please elaborate that section if possible?

thank you

Kuby