AD broken

%3CLINGO-SUB%20id%3D%22lingo-sub-2738781%22%20slang%3D%22en-US%22%3EAD%20broken%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2738781%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDC%20is%20Virtualized%20in%20vmware%2C%20I%20got%20it%20restored%20from%20Veeam%20backup%2C%20meaning%20it%20is%20not%20in%20the%20current%20state%2C%20that%20caused%20AD%20broken%2C%20how%20could%20I%20get%20it%20fixed%3F%26nbsp%3B%3C%2FP%3E%3CP%3EI%20forced%20replication%20between%202%20DCs%20it%20failed.%20Here%20and%20there%20we%20got%20a%20number%20of%20PCs%20that%20have%20the%20error%3A%3C%2FP%3E%3CDIV%3E%3CSTRONG%3EThe%20trust%20relationship%20between%20this%20Workstation%20and%20the%20primary%20Domain%20failed%3C%2FSTRONG%3E%3C%2FDIV%3E%3CDIV%3EAny%20help%2F%20advice%20would%20be%20appreciated.%3C%2FDIV%3E%3CDIV%3ECheers%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2738781%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EActive%20Directory%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2739966%22%20slang%3D%22en-US%22%3ERe%3A%20AD%20broken%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2739966%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20should%20never%20restore%20a%20domain%20controller%20in%20a%20multi-domain%20controller%20environment.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EPlease%20run%3B%3C%2FP%3E%0A%3CP%3EDcdiag%20%2Fv%20%2Fc%20%2Fd%20%2Fe%20%2Fs%3A%25computername%25%20%26gt%3BC%3A%5Cdcdiag.log%3CBR%20%2F%3Erepadmin%20%2Fshowrepl%20%26gt%3BC%3A%5Crepl.txt%3CBR%20%2F%3Eipconfig%20%2Fall%20%26gt%3B%20C%3A%5Cdc1.txt%3CBR%20%2F%3Eipconfig%20%2Fall%20%26gt%3B%20C%3A%5Cdc2.txt%3CBR%20%2F%3Eipconfig%20%2Fall%20%26gt%3B%20C%3A%5Cproblemworkstation.txt%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3Ethen%20put%20%3CEM%3E%3CSTRONG%3Eunzipped%3C%2FSTRONG%3E%3C%2FEM%3E%20text%20files%20up%20on%20%3CA%20href%3D%22https%3A%2F%2Fonedrive.live.com%2Fabout%2Fen-us%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EOneDrive%3C%2FA%3E%20and%20share%20a%20link.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2741147%22%20slang%3D%22en-US%22%3ERe%3A%20AD%20broken%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2741147%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20checking%20if%20there's%20any%20progress%20or%20updates%3F%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3E--please%20don't%20forget%20to%20%60upvote%60%20and%20%60Accept%20as%20answer%60%20if%20the%20reply%20is%20helpful--%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi All,

 

DC is Virtualized in vmware, I got it restored from Veeam backup, meaning it is not in the current state, that caused AD broken, how could I get it fixed? 

I forced replication between 2 DCs it failed. Here and there we got a number of PCs that have the error:

The trust relationship between this Workstation and the primary Domain failed
Any help/ advice would be appreciated.
Cheers
 
3 Replies

You should never restore a domain controller in a multi-domain controller environment.

 

Please run;

Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log
repadmin /showrepl >C:\repl.txt
ipconfig /all > C:\dc1.txt
ipconfig /all > C:\dc2.txt
ipconfig /all > C:\problemworkstation.txt


then put unzipped text files up on OneDrive and share a link.

 

 

 

Just checking if there's any progress or updates? 

  

--please don't forget to `upvote` and `Accept as answer` if the reply is helpful--

 

 

 

@Dave Patrick 

thanks for the help.

I found the error 8606 and 1988, because the restored DC was outdated I believe.

At the moment I managed to replicate between 2 DCs by disabling the Strict Replication Consistency and removed the lingering object with LOL tool.

I am monitoring the replication for a week or so then going to enable the Strict Replication Consistency.

 

Cheers