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
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
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
Why not go with Server 2016, or better Server 2019.
So this is not a P2V ????
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.
ASKER
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
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.
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.
ASKER
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
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.
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.
how does
Physical DC = server 2008 R2 become 2012R2 ??