Dcpromo /forceremval wiped new DC. Help!
-
Replacing a 2008 standard r2 with 2012 standard r2. Joined the 2012 to domain, set as domain controller to existing domain, allowed replication, transferred fsmo roles from 2008 box to 2012. Verified ALL fsmo roles are now with the 2012 box (verified from 2008 and 2012 box). From the 2008 box, my coworker tried dcpromo, but got an error "cannot contact the pdc". He then did a "dcpromo /forceremoval" and it successfully demoted the 2008 box, but when he looked at the 2012 box, AD, DNS was wiped out. So now the 2012 box no longer thinks it's a DC. Could someone tell me what happened and what we can do to fix this? Also, the 2008 server is now in a workgroup.
-
can you restore the 2008 box back to pre dcpromo?
-
@dashrender said in Dcpromo /forceremval wiped new DC. Help!:
can you restore the 2008 box back to pre dcpromo?
Customer has back ups from Windows Server Backup. Which is bare metal. It should be able to restore?
-
Didn't you install DNS on the new DC?
-
That the old server said that the new one could not be contacted, I'm going to guess that whatever issue you have here happened prior to demoting the old one.
-
@tim_g said in Dcpromo /forceremval wiped new DC. Help!:
Didn't you install DNS on the new DC?
Yes. DNS was installed and had replicated everything on the old.
-
@fredtx said in Dcpromo /forceremval wiped new DC. Help!:
@tim_g said in Dcpromo /forceremval wiped new DC. Help!:
Didn't you install DNS on the new DC?
Yes. DNS was installed and had replicated everything on the old.
It's pretty weird that it all vanished. Possibly the person running the commands accidentally connected to the wrong host and ran the DCPROMO again in the wrong place?
-
@scottalanmiller said in Dcpromo /forceremval wiped new DC. Help!:
That the old server said that the new one could not be contacted, I'm going to guess that whatever issue you have here happened prior to demoting the old one.
I was just told that adprep should have been ran when migrating a 2008 to 2012. That may be why it was unsuccessful. We had just did a 2012 to 2012 migration a day prior and was successful without adprep.
-
Oh.. maybe you didn't have AD on the server, only DNS. DNS will sync without the new DNS being an AD server.
-
@dashrender said in Dcpromo /forceremval wiped new DC. Help!:
Oh.. maybe you didn't have AD on the server, only DNS. DNS will sync without the new DNS being an AD server.
It was clearly stated the FSMO was moved.
-
Just i case, see more context on the SW post
https://community.spiceworks.com/topic/2090334-dcpromo-forceremoval-wiped-new-dc-help?source=superfeed -
@scottalanmiller said in Dcpromo /forceremval wiped new DC. Help!:
@fredtx said in Dcpromo /forceremval wiped new DC. Help!:
@tim_g said in Dcpromo /forceremval wiped new DC. Help!:
Didn't you install DNS on the new DC?
Yes. DNS was installed and had replicated everything on the old.
It's pretty weird that it all vanished. Possibly the person running the commands accidentally connected to the wrong host and ran the DCPROMO again in the wrong place?
I’m not sure what happened. He said he ran it from the 2008 and when it completed the 2008 was now in a workgroup. He then checked the 2012 and it’s still in the domain, but is no longer a DC. If we have to rebuild the domain, should we reinstall the OS on the 2012?
-
@fredtx said in Dcpromo /forceremval wiped new DC. Help!:
r a DC. If we have to rebuild the domain, should we reinstall the OS on the 2012?
It would be best to reinstall to do a clean setup.
-
@dbeato said in Dcpromo /forceremval wiped new DC. Help!:
Just i case, see more context on the SW post
https://community.spiceworks.com/topic/2090334-dcpromo-forceremoval-wiped-new-dc-help?source=superfeedThat was me...lol! Just trying to get all the help I can from different communities.
-
@fredtx said in Dcpromo /forceremval wiped new DC. Help!:
lol! Just trying to get all the help I can from different communities.
Yes, I know
-
@fredtx said in Dcpromo /forceremval wiped new DC. Help!:
@dbeato said in Dcpromo /forceremval wiped new DC. Help!:
Just i case, see more context on the SW post
https://community.spiceworks.com/topic/2090334-dcpromo-forceremoval-wiped-new-dc-help?source=superfeedThat was me...lol! Just trying to get all the help I can from different communities.
I didn't post there as there was many responses.
-
@dbeato said in Dcpromo /forceremval wiped new DC. Help!:
@fredtx said in Dcpromo /forceremval wiped new DC. Help!:
@dbeato said in Dcpromo /forceremval wiped new DC. Help!:
Just i case, see more context on the SW post
https://community.spiceworks.com/topic/2090334-dcpromo-forceremoval-wiped-new-dc-help?source=superfeedThat was me...lol! Just trying to get all the help I can from different communities.
I didn't post there as there was many responses.
And I usually just don't post there ^_^
-
Interesting concept there. if you use /forceremove that it can kill an entire domain.
-
@dashrender said in Dcpromo /forceremval wiped new DC. Help!:
Interesting concept there. if you use /forceremove that it can kill an entire domain.
If you are down to the last DC< yes.
-
My guess is that the second DC failed and never actually became a DC. If there wasn't solid confirmation of that, this would be the expected result.
