How do I replace a 2008 Domain Controller with a new Domain Controller running 2019?
I have a domain controller now running Windows Server 2008 R2. I need to take it off line and replace it with a new server running Windows 2019 that was just purchased. I have never done this before and want to keep all settings the same. Can any one assist me in how to do this correctly?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Since I am replacing the 5 computers/workstations that make up the domain, would it just be easier to start from scratch. Although a ll the computers/workstations will be Windows 10, they are being replaced one day at a time. It is a fairly simple domain setup. All 5 computers access one Access database and the domain controller runs a time clock for the shop. Also the server is used for a file server. What do you think?
ASKER
Yes it mostly just runs DNS, DHCP and an application for a shop that all 5 computer/ workstations access (one being a shop time clock). Other than that, files are copied to it.
ASKER
Actual services are Active Directory, DNS, DHCP, File Services, and Print and Document Services
From what your saying, it would not matter if you named the new DC a different name.
You would need to rehome their shares to point to the new server.
And definitely write down a timeline, with a plan.
You would need to rehome their shares to point to the new server.
And definitely write down a timeline, with a plan.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
And don't forget that Windows Server licensing nowadays allows 3 Operating System Environments (OSE) per license.
So, 1 for the Hypervisor host to run the hardware.
1 for the AD server
1 for the backup AD server, or application server.
So, 1 for the Hypervisor host to run the hardware.
1 for the AD server
1 for the backup AD server, or application server.
Above migration path needs to be followed only if you wanted to retain old server and upgrade same to 2019
Else follow below plan which is normally stand out.
1st check AD health by running command from elevated prompt : dcdiag /v
Check output and resolve any critical issues
Add 2019 server as member server in existing AD domain
Then install ADDS role on 2019 server and promote it to domain controller
Again check AD health and ensure AD is replicating and netlogon and sysvol shares are available on new DC
If everything is OK, transfer FSMO roles to new DC
demote old server to member server, now its up to you if you want to keep it as member server or you may transfer data on that server to new server. If you have any other roles on that server, you need to migrate those as well
https://techcommunity.microsoft.com/t5/ITOps-Talk-Blog/How-to-Migrate-Windows-Server-2008-R2-FSMO-roles-to-Windows/ba-p/538377
Else follow below plan which is normally stand out.
1st check AD health by running command from elevated prompt : dcdiag /v
Check output and resolve any critical issues
Add 2019 server as member server in existing AD domain
Then install ADDS role on 2019 server and promote it to domain controller
Again check AD health and ensure AD is replicating and netlogon and sysvol shares are available on new DC
If everything is OK, transfer FSMO roles to new DC
demote old server to member server, now its up to you if you want to keep it as member server or you may transfer data on that server to new server. If you have any other roles on that server, you need to migrate those as well
https://techcommunity.microsoft.com/t5/ITOps-Talk-Blog/How-to-Migrate-Windows-Server-2008-R2-FSMO-roles-to-Windows/ba-p/538377
ASKER
Thanks for your suggestions
ASKER
I did transfer all roles to new server and did not just create a new domain.
let's start with making a plan before jumping into action