1

Scenario= Have a physical server that is running AD,DNS,DHCP main DC. win 2008r2

It also has a hyper v- EMR software running.

I want to go to a vmware host better box. Create the 2 vms one for the DC the other for the EMR software.

Can I P to V this?

If so is there a better tool to used then Vmwares P to V tool?

How would you all do this?

Big question is once I (P to V )the win 2008 r2 servers can I do a inplace upgrade to win 2012 r2?

Or do I have to do the ole migration?

PLEASE ANY ALL DETAIL FOR INSTRUCTION IS GREATLY APPRECIATED :slight_smile:

@VMware

2 Spice ups
2

As has been said before DO NOT P2V a DC.

Just build yourself a new Windows 2012 DC in VMWare, DCPromo it, move DHCP and the FSMO roles across, install DNS, sync it, update the clients to point to the new server then dcrpomo down the physical server.

http://community.spiceworks.com/topic/305206-domain-controller-p2v-yes-or-no

http://community.spiceworks.com/topic/413878-p2v-domain-controller

http://community.spiceworks.com/topic/380971-p2v-server-that-is-it-own-domain

6 Spice ups
3

Okay Gary,

What about the EMR that is in win2008r2 hyper v can I P to V it?

Then upgrade to win 2012r2?

4

That wouldn’t be P2V as its already a VM. Can VMware import a HyperV VM?

5

VMWare can’t import a Hyper-V VM but you can V2V it using the VMWare convertor.

6

What’s an EMR?

7

VMWare can import a HyperV VM using the vCenter Converter. The only issue is, the VM needs to be shut down. Gary D Williams is correct regarding best path to virtualize the DC.

8

Gary… EMR - electronic medial records software like NextGen, etc.

Spartacus1… you should be able to do as Gary suggested. An in-place upgrade from 2008R2 to 2012R2 should work just fine. That said, I am a firm believer in not upgrading servers from version to version but, instead, building new and migrating.

It can be a bit more work up front, but you never have to go back and fix stuff that didn’t go right during the upgrade. Additionally, it is less intrusive and inconvenient for the users. Build the server, install all your apps, printers, etc without bringing the old server down. Then migrate data after hours.

But that’s just my preference.

3 Spice ups
9

Just curious - you evidently already know a bit about Hyper-V. Why switch to VMWare?

Hyper-V Server 2012 has a lot of nice new features compared to the 2008 R2 version, and you wouldn’t have to convert the existing VM.

10

Moving any DC to a virtual machine can be cause for extreme headaches and late nights.

11

why? I’ve done this many times via a DCPromo with no issues.

12

I’ve had my DC’s virtualized for years with no issues. I would typically avoid P2V or V2V unless strictly required though. The performance is usually pretty poor compared to a newly built VM on the target hypervisor. I would migrate, if possible.

I would also avoid in-place OS upgrades. Migrating offers better performance, easier cut-over, and easier roll-back in the event of an issue.

Also, be careful trying to upgrade production EMR systems to the latest versions of Windows. More times than not, the vendor will not support the latest stuff and it may invalidate your support with them. If you want to hold them accountable for supporting their product, it has to be 100% within their guidelines.

1 Spice up