Need a good P2V plan for a DC.

Need a good P2V plan for a DC.

Here are the requirements:

Physical DC = server 2008 R2

Converted VM = needs to be server 2012R2

Needs to have the same name and IP as the physical dc.

What would be the best way to accomplish this task?

Here is my plan so far:

1.)      Transfer all FSMO rolls to another already running DC
2.)      Demote, and Decommission Physical DC, and shut down
3.)      Reset computer object in AD
4.)      In Vcenter, Stand up new vm
5.)      Make it a member server with same name as the physical
6.)      Give it same IP as old physical dc
8.)      Promote to DC

Will this work?  is there a better way?

your thoughts
JB BlancoSr Systems EngineerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Carl WebsterCitrix Technology Professional - FellowCommented:
3. Delete computer object
3a. Remove server from Sites & Services
3b. Remove server from DNS forward and reverse lookup zones
3c. Remove server from every zone as a name server
3d. Remove server from the _msdcs and AD forward zone sub zones (there are always 3 or 4 DNS entries lurking around)

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization ConsultantCommented:
is this a single domain controller ?

how does

Physical DC = server 2008 R2 become 2012R2 ??
Carl WebsterCitrix Technology Professional - FellowCommented:
Looks like that is what the OP will do in step 4, make the new VM Server 2012 R2.

Why not go with Server 2016, or better Server 2019.
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization ConsultantCommented:
So this is not a P2V ????
Carl WebsterCitrix Technology Professional - FellowCommented:
When I saw the original title, my response was going to be NEVER P2V a DC. Build new. To me, it looks like the OP is doing demotion of a physical DC, cleaning stuff up and building a new VM to become a new DC, reusing the original DC's name and IP address.
JB BlancoSr Systems EngineerAuthor Commented:
When I saw the original title, my response was going to be NEVER P2V a DC. Build new. To me, it looks like the OP is doing demotion of a physical DC, cleaning stuff up and building a new VM to become a new DC, reusing the original DC's name and IP address.

Exactly!

I know you never p2v a dc but thats what we call it.  Actually we are replacing a DC with a 2012,2016,or 2019 DC

Highest Domain Functional level is 2008 R2
But this will not hold the Domain naming or Schema master role.

is this a single domain controller ?

how does

Physical DC = server 2008 R2 become 2012R2 ??

No this is not a single domain controller
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
No P2V needed.

Install base OS in VM.
Install necessary roles: ADDS, DNS, DHCP, any others
DCPromo
Transfer FSMO Roles
Verify replication and DNS
DCPromo OldDC out
Clean-up AD and DNS
Done.

EDIT: This post is flawless for migrating existing DHCP.
JB BlancoSr Systems EngineerAuthor Commented:
No P2V needed.

Install base OS in VM.
Install necessary roles: ADDS, DNS, DHCP, any others
DCPromo
Transfer FSMO Roles
Verify replication and DNS
DCPromo OldDC out
Clean-up AD and DNS
Done.

EDIT: This post is flawless for migrating existing DHCP.

Need to keep the same name and IP though.  Its still simple just thought it would be a little tricky because of this
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
How is that?

Set up the DC on whatever IP DHCP hands to it.

Once the entire process is finished flip OldDC onto DHCP and NewDC onto OldDC's IP address.

IPConfig /RegisterDNS on both DCs to get things aligned.

Once everything is happy run through the DCPromo steps to remove OldDC and clean-up as mentioned.

It's a few extra steps but you end up with a fresh DC.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Virtualization

From novice to tech pro — start learning today.