SBS 2011 to 2016 Std DC Issue
-
Hey now,
I've got a 2016 server I've stood up in a sbs2011 domain, added it as a DC, moved all FSMO roles to the new server since the goal is to murder the sbs2011 machine, verified replication is healthy, migrated exchange to o365. Here's where the fun starts.....
In order to test the server, I've shut down the SBS2011 box and reboot a domain joined computer, and hope that hey.... it's gonna use the new DC as the logon server... nope. any ideas what I'm lacking here folks?
-
Did you configure DNS to point to the new DC? Is your DHCP set up to point to the new DC instead of the old(if you're using it)? If on DHCP did you release/renew or reboot to obtain new settings?
-
yep. dhcp's DNS points to the new DC. all works fine until I shut down the SBS server. then AD dies.
-
Everyone loves SBS!
-
Sites, subnets, services set up correctly? New PC using the new DNS server? Can you ping the new DC by it's DNS name? (when SBS is down)
Could be so many things...
-
Double check FSMO? I've had to manually override the Global Catalog before.
-
@hubtechagain said in SBS 2011 to 2016 Std DC Issue:
yep. dhcp's DNS points to the new DC. all works fine until I shut down the SBS server. then AD dies.
Test on a client and make sure that DHCP has renewed the lease since you made that setting. Just because DHCP has the setting doesn't mean it's been handed out yet.
-
I had two posts last year on this for SBS alone and basically it was down to DHCP or File Replication.
https://goo.gl/T5DkfL
https://goo.gl/wcFbq1
