Server 2012 DC VMware > HyperV.

[swiftysw1]

ATM we have two 2012 Dc Servers on a VMware platform. But migrating them onto too a HyperV platform. Any advice you can offer would be great.?

 

At this time I am NOT looking to upgrade the OS’s on these DC’s

 

When I initially installed a ‘test’ server system on hyper I was getting connectivity issues. But that was because I was using Gen 1 and not 2.

 

Thanks

[mrbios]

I know you're saying you're not looking to upgrade the OS on those DCs, but given they go EOL in October, is there a specific reason as to why you're not wanting to do that?

 

Personally i would build a two new VMs on 2022 on Hyper-V, promote it as a DC, move FSMO roles and then demote the ones on VMware, rather than even bother migrating anything or upgrading OS's. Two birds, one stone as it were and a much cleaner transition.

[swiftysw1]

That’s what worries me. lol.

After promoting the demoting. Would I them move the IP’s and names back to the original?

[mrbios]

Retaining the same IPs is simple enough but retaining names has an extra step as renaming an active DC isn't a good idea (to the best of my knowledge anyway, unless guidance has changed since i last did it...)

 

In which case:

Create one new 2022 DC, name it something new, give it a new IP, promote it and make sure any roles are setup correctly so that it can stand on its own easily enough to serve the network. Demote one of the old ones. Then make the second DC and reuse the name and IP of that old one you demoted, then do the same again, demote the other old one, promote a new one using same name and IP. You end up with 3 DCs, but you can get rid of the one that doesn't match your old names and IPs if you want to at the end, it's just there as a cut over really.

 

Obviously make sure you give each promotion and demotion a good deal of replication time, double and triple check roles like DNS are setup correctly to match the old DCs. There might be any easier way to do this without needing the third DC but the above is how i've done it before and it's always seemed like the simplest process in my mind.

[3s-gtech]

For my last DC on VMWare I just demoted it then gave the IP address to a new DC on Hyper-V. Didn’t try to move it. New name.

 

I did move our SIMS server on 2012 R2 between these platforms - Disk2VHD then converted to a gen 2 server using Powershell. Fairly easy.

[FN-GM]

That’s what worries me. lol.

 

To be honest, I would be worried about having your domain controllers on a operating system with security issues.

 

 

After promoting the demoting. Would I them move the IP’s and names back to the original?

 

I wouldn’t rename them.

[Davit2005]

If you are running other services on DCs I'd take the opportunity to separate them. So yep build new and transfer FSMO roles, DHCP and DNS and leave none MS third party software where it is to migrate to a supported OS at a later date but you are running a risk with lack of security updates.

[ITGURU]

Did this myself a few years ago, spun up new Hyper-V DCs moved the roles etc don't convert Vmware to Hyper-V DCs, fine for all file servers/member servers but DC's always do clean.

If you must re-use same IPs/Names, demote one of them, bring up a new one on Hyper-V , test test test, then do the second one.

Had no issues myself, but definitely upgrade from 2012 - there is no reason not to?

[pete]

You can build 2 DCs in the time it takes to swear at one VMware > HyperV migration.

 

AD is (surprisingly for Microsoft) one of the easiest and fastest service to migrate.