Moving Servers from VMware to Hyper-V (DCs)

[newpersn]

As above.

 

We now got a fault on one of our VM Hosts. (older server which runs vmware ESXi 4.1.0) which hosts a few of our DC's

 

Is there a simple way of transferring these hosts off and moving these to the Hyper-V?

 

Or any other ways of doing it? (hoping it will last til after the xmas break......)

 

EDIT: our PDC is on this host....

[Steve21]

https://www.microsoft.com/en-gb/download/details.aspx?id=42497

 

Should still be the easiest way assuming you can access the files etc?

 

Or Disk2VHD can be used if you'd prefer something standalone

 

Steve

[newpersn]

I know the only setup i need to do is the VLANS on the Hyper-V (Wonders if he can use all 4 ports on the server for Hyper-V)

[Steve21]

Can use all the ports you want We're running 8 on each host here. (Unless you meant that in another way).

 

Steve

[FN-GM]

3 Methods I have used. Options 1 & 2 require you to have a Vcenter server

 

1. Use SCVMM to convert

2. Use this https://www.microsoft.com/en-gb/download/details.aspx?id=42497

3. Use the software from step 2 along with the attached powershell script. You download the VM files from VMware, specify and input and output folder and it makes VHDX files.

 

I have used number 3 this week to move machines from a standalone ESXi host.

convert.ps1

[DavetheITguy]

I simply created a new VM on Hyper-v, installed Server 2012r2 and promoted it to a domain controller. setup replication between DCs and then retired the old one. I then had a fresh server with the replicated data on. Might be worth doing it that way. At least you know that the new VM has a fresh OS and won't have any VMware software on that could screw with hyper-v.

[3s-gtech]

I've used Disk2VHD with great success here, you will only be able to use Gen 1 settings for the resultant VM but no great hardship. Edited December 16, 2016 by 3s-gtech
Speeling

[Davit2005]

DC's can be funny/picky animals. I'd +1 for a new install, migrate FSMO roles etc.

 

Use a different DC hostname but you could use same IP address once everything is happy, done that a few times before with no issues.

 

Do a DCDIAG before you start anything just to make sure their are no existing issues that need sorting.

Edited December 16, 2016 by Davit2005

[RLR]

We recently migrated from Hyper-V to VMware and got told not to migrate DC's and instead re-create new DC's.

[newpersn]

Is there a easy guide of mirgrating the roles to new servers?

 

Also do i need to have a dc on each vlan doing dhcp/dns/wins?

[3s-gtech]

Depends what you have VLAN'd off and how they route across to each other, whether those devices have static IPs etc. You shouldn't need DCs but you may need DHCP servers.

[RLR]

Is there a easy guide of mirgrating the roles to new servers?

 

Also do i need to have a dc on each vlan doing dhcp/dns/wins?

 

I've not done it myself but from what I understand, when you build a new Domain controller you can replicate the DHCP/DNS and other settings from another DC that is still live.

 

As for for vlans, you should be able to setup ip helpers on your core switch/router to point to your DC. This can also depend on how your network is setup etc.

[DavetheITguy]

Build the new domain controller, promote it to a dc and then add it to the domain forest as a 2nd dc. then all the services should replicate between each other. You will need to manually replicate DHCP which is easy enough to do.

[Davit2005]

I've not done it myself but from what I understand, when you build a new Domain controller you can replicate the DHCP/DNS and other settings from another DC that is still live.

 

As for for vlans, you should be able to setup ip helpers on your core switch/router to point to your DC. This can also depend on how your network is setup etc.

 

Also Transfer the 5 FSMO roles across to the new server, I normally wait 24 hours after introducing the new DC to do this. It is fairly simple to do, done it my self about 10 times now.

 

You may also need to point the DC that holds the PDC Emulator FSMO role to an external NTP time source.

[john]

I simply created a new VM on Hyper-v, installed Server 2012r2 and promoted it to a domain controller. setup replication between DCs and then retired the old one. I then had a fresh server with the replicated data on. Might be worth doing it that way. At least you know that the new VM has a fresh OS and won't have any VMware software on that could screw with hyper-v.

 

This I'd never P2V or migrate a DC always build new from scratch