Single server migration - Do you set new servers IP & name same as old server?

[TwistedHelixis]

Primary school, single server setup.

 

At some point I need to migrate the domain controller from 2012r2 to 2019. After I have migrated AD, DNS, GP etc do others normally then change the IP and name of the new server so it is the same as the old server?

Edited March 16, 2021 by TwistedHelixis

[Davit2005]

Primary school, single server setup.

 

At some point I need to migrate the domain controller from 2012r2 to 2019. After I have migrated AD, DNS, GP etc do others normally then change the IP and name of the new server so it is the same as the old server?

 

I only replicate the IP address (just create new DC with temp IP address) and I've never bothered changing the name. I only run basic functions on DCs i.e. FSMO roles, DNS/DHCP, so no real need to bother with the name.

 

Once you have migrated the FSMO roles over to the new DC and have again checked dcdiag etc. then you can look at de-promoting it and cleanup.

 

I normally do a ipconfig /registerdns once changed the IP address but that is just force of habit I think.

Edited March 16, 2021 by Davit2005

[PlantHead]

Primary school, single server setup.

 

At some point I need to migrate the domain controller from 2012r2 to 2019. After I have migrated AD, DNS, GP etc do others normally then change the IP and name of the new server so it is the same as the old server?

 

It depends on if you have used DNS addresses to refer to the server previously but I would keep the same IP address

 

1. build new server

2. give it a temp IP Address

3. Join to domain and promote to DC

4. Add FSMO roles etc

5. Change old DC IP address

6. Reboot the old DC at least twice - you need to clear all reference to it from AD

7. Wait for replication to complete - about an hour

8. Give new DC old DC IP address

9. Reboot the new DC

10. Wait for replication

11. Demote the old DC

12. Relax

 

 

Forgot, Switch off the old DC if you don't need it anymore

Edited March 16, 2021 by PlantHead

[TwistedHelixis]

I only replicate the IP address and I've never bothered changing the name. I only run basic functions on DCs i.e. FSMO roles, DNS/DHCP, so no real need to bother with the name.

I assume you make the switch shortly after you have de commissioned and shutdown the old server.

 

EDIT - you posted when I did so ignore

Edited March 16, 2021 by TwistedHelixis

[TwistedHelixis]

1. build new server

2. give it a temp IP Address

3. Join to domain and promote to DC

4. Add FSMO roles etc

5. Change old DC IP address

6. Reboot the old DC at least twice - you need to clear all reference to it from AD

7. Wait for replication to complete - about an hour

8. Give new DC old DC IP address

9. Reboot the new DC

10. Wait for replication

11. Demote the old DC

12. Relax

 

I would have thought you needed to wait until the old server was decomissioned and removed from the network before giving the new server its IP?

[Davit2005]

I assume you make the switch shortly after you have de commissioned and shutdown the old server.

 

EDIT - you posted when I did so ignore

 

Yep give new DC a temp IP address then migrate old DC to a different temp IP address then change new DC to original IP address.

 

But yes give it a chance to replicate and run a dcdiag before you start, midway and when you finish so you are playing with a happy domain to start with :-)

 

And yes migrate all the FSMO roles as well.

 

@PlantHead has broken it down a bit more. The only thing I would add is to do a ipconfig /registerdns after changing IP addresses each time.

Edited March 16, 2021 by Davit2005

[snagrat]

It depends on if you have used DNS addresses to refer to the server previously but I would keep the same IP address

 

1. build new server

2. give it a temp IP Address

3. Join to domain and promote to DC

4. Add FSMO roles etc

5. Change old DC IP address

6. Reboot the old DC at least twice - you need to clear all reference to it from AD

7. Wait for replication to complete - about an hour

8. Give new DC old DC IP address

9. Reboot the new DC

10. Wait for replication

11. Demote the old DC

12. Relax

 

 

Forgot, Switch off the old DC if you don't need it anymore

 

Extra step I generally do then is to rename the DC to the old name. Everything just continues to work then and the clients haven’t got a clue the server has changed....

[TwistedHelixis]

something just crashed when i posted - hold on

[TwistedHelixis]

I just assumned the order would be.....

 

a. build new server.

b. give it a temp IP Address.

c. Join to domain and promote to DC

d. Add FSMO roles etc

e. Wait for replication to complete - about an hour

f. Demote old server

g. turn off old server

h. Give new DC old DC IP address

i. Reboot the new DC

j. do ipconfig /registerdns

 

Just double checking - So is my way not correct?

and is everyone in agreement that step 5 should be 'change old DC IP'?

[TwistedHelixis]

6. Reboot the old DC at least twice - you need to clear all reference to it from AD

But surely DNS & AD will still have references as its not been demoted yet?????

[TwistedHelixis]

Out of interest, what do you do about DHCP?

 

Do you migrate it to the new server somehow or rebuild from scratch?

[TwistedHelixis]

Extra step I generally do then is to rename the DC to the old name. Everything just continues to work then and the clients haven’t got a clue the server has changed....

 

Which step do you change the name?

1. build new server

2. give it a temp IP Address

3. Join to domain and promote to DC

4. Add FSMO roles etc

5. Change old DC IP address

6. Reboot the old DC at least twice - you need to clear all reference to it from AD

7. Wait for replication to complete - about an hour

8. Give new DC old DC IP address

9. Reboot the new DC

10. Wait for replication

11. Demote the old DC

12. Relax

[snagrat]

Out of interest, what do you do about DHCP?

 

Do you migrate it to the new server somehow or rebuild from scratch?

 

Netsh dhcp server export c:\dhcp all

 

Then On new server

 

Netsh dhcp server import c:\dhcp all

 

Easy!

[snagrat]

Which step do you change the name?

1. build new server

2. give it a temp IP Address

3. Join to domain and promote to DC

4. Add FSMO roles etc

5. Change old DC IP address

6. Reboot the old DC at least twice - you need to clear all reference to it from AD

7. Wait for replication to complete - about an hour

8. Give new DC old DC IP address

9. Reboot the new DC

10. Wait for replication

11. Demote the old DC

12. Relax

 

Depends really. Normally l rename the old right at the start so the new new goes on with the correct name. But that’s downtime.

 

Renaming at step 12 (instead of relaxing!) would also work.

[Guest Guest]

As its a single server setup I assume it'll be hosting shares? If so I'd change both the name and IP to match the old