Questions regarding to removing orphaned dc, adding dc, getting DHCP working
-
I had three locations with three DCs, all are VM guest, and all are server 2008 R2.Site A, DC1. Primary DC, runs DNS, DHCP, and whatever else DC runs.Site B, DC2. Secondary DC, runs DNS, DHCP, File Server, and Printer Server for site B, three employees.Site C, DC3. I'm not sure what it runs, there is no employee working there, so I have not spend any time to look into this.Due to the incident on Tuesday, https://community.spiceworks.com/topic/1993055-need-advise-restoring-domain-controller-and-email-ser... , I am left with an
orphaned DC1 that I have kept offline, but I still have access to it and can view DHCP configurations. I made DC2 seize all 5 roles of FSMO, and it is running DNS. DHCP is currently not working on DC2, event 1046 about not authorized to start. The DHCP scope is not setup. I can see the scope on DC1. I didn't touch DC3 at all.Questions, do I just want to fix the DCHP on DC2 or just build a new DC and run DHCP from there instead?
I plan to:Build a DC0 using DC1's old IP addressAdd DC0 to domain and make it a DC, setup DNS and DCHP scopes
Once DC0 is running good, then delete DC1 from the AD.
Do I have this right? I'm sure I'm missing a few steps. Thanks for your comment.
-
That seems good. Are users at all sites still able to login correctly? Authorizing a dhcp server is rather trivial(right click> Authorize), you probably want to get a dc up at site 1.
-
All users and exchange inbox are working fine.
-
@Harry-Lui said in Questions regarding to removing orphaned dc, adding dc, getting DHCP working:
roles of FSMO, and it is running DNS. DHCP is currently not working on DC2, event 1046 about not authorized to start. The
How are users at site two getting an IP address? Are they still just living off an old lease?
How about Site 1? What is site 1 users using for DNS now? where they pointed to the DC2 DNS server as part of DHCP in the past, therefore the clients automatically failed over to using it?I agree with @momurda , authorizing your DHCP server at site two should be trivial.
Because you probably need to get a DHCP/DNS server up at site 1, I'd stand up an AD server with DNS/DHCP ASAP. You can worry about cleaning up the now dead/defunct DC1 until the rest of things are back to normal.
Why do you want to reuse the IP of DC1 for DC0?
-
@Dashrender
Only a few pc is still on the old lease. I had to set static IP to most pc that had restarted.All Site1 and Site2 users are using DC2 for DNS. Site 1 and Site 2 are VPN together.
All users were using DC1 for DNS before.
Ignorance would be the answer to your last question.
-
You're plan seems pretty good then. Then you can remove those static entries.
-
So, I backed up the DHCP on DC1, save it on the virtual drive, then add that virtual drive on DC2, authorized DC2 to be the DHCP server and then restored the DCHP. DCHP is working again!
Will work on DC0 and DC1 tomorrow.
-
@Harry-Lui said in Questions regarding to removing orphaned dc, adding dc, getting DHCP working:
So, I backed up the DHCP on DC1, save it on the virtual drive, then add that virtual drive on DC2, authorized DC2 to be the DHCP server and then restored the DCHP. DCHP is working again!
Will work on DC0 and DC1 tomorrow.
Huh - that worked, eh? Do you have a single IP space over these two locations? or you mean DHCP is working at site 2 now?
