2003 DC server to 2016 DC

Viewing 1 post (of 1 total)
  • Author
    Posts
  • Avatar
    saviobarnes
    Member
    #167645

    So here’s what I’ve done. I raised the 2003 server from 2k to 2k3 and got the FSMO transferred from 2003 to the new 2016 server, I’ve got the AD replicated over into 2016, I’ve done the RID, PID, and else pointing to the new DC in 2016. I got the DNS and DHCP setup in 2016 and pc’s are pulling IP and DNS lookups. I confirmed the FSMO was successful with netdom /query fsmo and it’s all pointing to the new 2016 DC. Pretty much everything I did in Step 1 and Step 2 on this website went smoothly. My problems arrise in Step 3.
    TutuappWhen I go to run DCPROMO to demote 2003 and promote 2016 as the main domain controller, it says it can’t see the 2016 DC. And if I try to tell it that it’s the last DC on the network, it errors out saying that it isn’t the last DC on the network. So right now I can’t demote the 2003 server and let 2016 take over for AD. So I thought, hey let’s just try https://9apps.ooo/ unplugging the 2003 DC from the network and see what happens. Immeadiately my 2016 DC ShowBox can’t communicate to the domain and will not load. So it’s like my 2016 DC is replicating only when 2003DC is connected to the network. My DHCP is working fine on 2016 server, so now I’m here on Reddit to ask if someone has ran into this problem before and can tell me what I might have missed.

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.