Brief summary of our topology:
- Several AD sites for regional offices.
- Current domain/forest functional level is Windows Server 2003.
- Currently a mix of 2003, 2008 R2 and 2012 R2 domain controllers (in the process of retiring the 2003 ones).
- Each site has at least one DC, with our HQ having three.
So I wanted to retire the Windows 2003 DC in our Seattle site. I've done this at two other sites without incident:
- I prepped a server and shipped it.
- Once onsite I joined the domain and promoted the server to a DC.
- Migrate DHCP database from old server to new one.
- Shortly thereafter (usually the next day) I'd demote the old server.
- After a few days I'd shut the server down and have it shipped back.
This week I shipped a new server with Windows 2012 R2 installed, joined the domain while onsite and promoted it to a DC. Replication within the site appears to be working fine. The NTDS settings on the existing server (SEA-SERVERA) have automatically
generated connections for DET-DC1 (our primary HQ domain controller) and SEA-SERVERB (the new server I brought online Friday morning). SEA-SERVERB however only has an automatically generated item for SEA-SERVERA, the original 2003 DC in that site.
==================================\
Attempting to manually create a connection in SEA-SERVERB for DET-DC1 and trying to replicate results in the following dreaded error:
The following error occurred during the attempt to synchronize naming context domain.local from Domain Controller DET-DC1 to Domain Controller SEA-SERVERB:
The naming context is in the process of being removed or is not replicated from the specified server.
This operation will not continue.
==================================/
I've looked a number of posts both here and elsewhere and am not seeing anything in my environment that matches what others have experienced. My SYSVOL share is created and operational on SEA-SERVERB and commands like DCDIAG and REPADMIN /SHOWREPL aren't
indicating (to me, anyway) any issues.
I do see the following error in my event log on DET-DC1 from Friday morning, but this is about the time I was completing the DC promotion on SEA-SERVERB:
==================================\
Log Name: Directory ServiceSource: Microsoft-Windows-ActiveDirectory_DomainServiceDate: 8/26/2016 10:25:28 AMEvent ID: 2002Task Category: Knowledge Consistency CheckerLevel: ErrorKeywords: ClassicUser: ANONYMOUS LOGONComputer: DET-DC1.domain.localDescription:The Knowledge Consistency Checker (KCC) could not run successfully because the attribute on the following object did not have enough values. Object:CN=NTDS Settings,CN=SEA-SERVERB,CN=Servers,CN=Seattle,CN=Sites,CN=Configuration,DC=domain,DC=local Attribute name:hasMasterNCs An attempt to replicate this attribute will be tried again at the next scheduled replication. User Action If this condition continues, verify that replication is working correctly.==================================/
Here is the DCDIAG output from SEA-SERVERB:
==================================\
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = SEA-SERVERB
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Seattle\SEA-SERVERB
Starting test: Connectivity
......................... SEA-SERVERB passed test Connectivity
Doing primary tests
Testing server: Seattle\SEA-SERVERB
Starting test: Advertising
......................... SEA-SERVERB passed test Advertising
Starting test: FrsEvent
......................... SEA-SERVERB passed test FrsEvent
Starting test: DFSREvent
......................... SEA-SERVERB passed test DFSREvent
Starting test: SysVolCheck
......................... SEA-SERVERB passed test SysVolCheck
Starting test: KccEvent
......................... SEA-SERVERB passed test KccEvent
Starting test: KnowsOfRoleHolders
......................... SEA-SERVERB passed test KnowsOfRoleHolders
Starting test: MachineAccount
......................... SEA-SERVERB passed test MachineAccount
Starting test: NCSecDesc
......................... SEA-SERVERB passed test NCSecDesc
Starting test: NetLogons
......................... SEA-SERVERB passed test NetLogons
Starting test: ObjectsReplicated
......................... SEA-SERVERB passed test ObjectsReplicated
Starting test: Replications
......................... SEA-SERVERB passed test Replications
Starting test: RidManager
......................... SEA-SERVERB passed test RidManager
Starting test: Services
......................... SEA-SERVERB passed test Services
Starting test: SystemLog
......................... SEA-SERVERB passed test SystemLog
Starting test: VerifyReferences
......................... SEA-SERVERB passed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running partition tests on : domain
Starting test: CheckSDRefDom
......................... domain passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... domain passed test CrossRefValidation
Running enterprise tests on : domain.local
Starting test: LocatorCheck
......................... domain.local passed test LocatorCheck
Starting test: Intersite
......................... domain.local passed test Intersite
==================================/
Here is the REPADMIN /SHOWREPL output from the same server:
==================================\
Repadmin: running command /showrepl against full DC localhost
Seattle\SEA-SERVERB
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: add917cb-4aee-491f-8ca0-89d5de621002
DSA invocationID: 32849b6e-384c-4266-a146-482b88eff7d5
==== INBOUND NEIGHBORS ======================================
DC=domain,DC=local
Seattle\SEA-SERVERA via RPC
DSA object GUID: 082b7765-e422-41e3-8ef1-d59498cf0bb3
Last attempt @ 2016-08-27 19:14:16 was successful.
CN=Configuration,DC=domain,DC=local
Seattle\SEA-SERVERA via RPC
DSA object GUID: 082b7765-e422-41e3-8ef1-d59498cf0bb3
Last attempt @ 2016-08-27 19:14:19 was successful.
CN=Schema,CN=Configuration,DC=domain,DC=local
Seattle\SEA-SERVERA via RPC
DSA object GUID: 082b7765-e422-41e3-8ef1-d59498cf0bb3
Last attempt @ 2016-08-27 18:51:05 was successful.
DC=DomainDnsZones,DC=domain,DC=local
Seattle\SEA-SERVERA via RPC
DSA object GUID: 082b7765-e422-41e3-8ef1-d59498cf0bb3
Last attempt @ 2016-08-27 19:14:22 was successful.
DC=ForestDnsZones,DC=domain,DC=local
Seattle\SEA-SERVERA via RPC
DSA object GUID: 082b7765-e422-41e3-8ef1-d59498cf0bb3
Last attempt @ 2016-08-27 18:51:05 was successful.
==== OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS ============
DC=domain,DC=local
Seattle\SEA-SERVERA via RPC
DSA object GUID: 082b7765-e422-41e3-8ef1-d59498cf0bb3
Last attempt @ 2016-08-27 19:14:31 was successful.
CN=Configuration,DC=domain,DC=local
Seattle\SEA-SERVERA via RPC
DSA object GUID: 082b7765-e422-41e3-8ef1-d59498cf0bb3
Last attempt @ 2016-08-27 18:41:21 was successful.
CN=Schema,CN=Configuration,DC=domain,DC=local
Seattle\SEA-SERVERA via RPC
DSA object GUID: 082b7765-e422-41e3-8ef1-d59498cf0bb3
Last attempt @ 2016-08-26 10:25:04 was successful.
DC=DomainDnsZones,DC=domain,DC=local
Seattle\SEA-SERVERA via RPC
DSA object GUID: 082b7765-e422-41e3-8ef1-d59498cf0bb3
Last attempt @ 2016-08-27 19:14:37 was successful.
DC=ForestDnsZones,DC=domain,DC=local
Seattle\SEA-SERVERA via RPC
DSA object GUID: 082b7765-e422-41e3-8ef1-d59498cf0bb3
Last attempt @ 2016-08-26 10:25:09 was successful.
==================================/
I'm not sure what else to look at. I had this happen once before and just left it overnight and it resolved itself, but this still isn't showing up. One thing to note is that I've set the primary DNS on SEA-SERVERB to be the IP of DET-DC1.
If there's anything else I can provide just let me know. Thank you.