
Vlado Vajdic
5.3K posts






ACTIVE DIRECTORY: FULL RECOVERY COMPLETED We just walked through a 4 hour process to recover an Active Directory domain where the PDCe VM had its storage pulled out from under it. A recovery was done but the recovered PDCe image was 1 week back from the secondary DC! Oh-Oh! Nothing showed up to the on-site IT until today when things went into a form of lockdown mode. The loose process: 1: DFS-R BURFLAGS ** Had to D4 on PDCe and D2 on Secondary *** That failed ** Had to D4 on Secondary and D2 on Primary *** That worked *** Replication still failed 2: ADDS Complained about 31 days for no replication ** Had to adjust the tombstone on both ** Replication still failed 3: FSMO Roles Conflict ** Seized FSMO Roles on secondary ** Both Secondary & old PDCe showed the correct FSMO Role Holder after this step ** But everything still wanted OldPDCe! :-( 4: Re-Run BURFLAGS ** D4 on new PDCe and D2 on OldPDCe 5: DCDiag points out to disabled Inbound/Outbound Replication ** Enable it using RepAdmin *** NOTE: A "-" means removing the DISABLE *** NOTE: A "+" means setting the DISABLE Users started tagging the IT Admin that things were starting to connect again! Why 4 hours? Sifting through those logs was painful. :-( Oh, and when it comes to "lingering objects" in the logs for replication blogs, do _NOT_ run the steps the "search assistant" comes up with!!! 8-O Dig into the actual Help on the server and Microsoft Learn and a couple of blogs that show how its done. Another one pulled out of the hat!




AdminSDHolder: the AD security feature everyone thinks they understand but probably don't. 😬 @JimSycurity went to the source code to debunk decades of misconceptions — including ones in Microsoft's own docs. Read more ⤵️ ghst.ly/3Lpmjzv


















