Error determining whether the target server is already a domain controller: The domain controller promotion completed, but the server is not advertising as a domain controller.

Question

The domain forest root server was lost. So, I seized the schema and domain naming master to child domain DC controller server. And I wanted to create a new server and promote it to be a DC controller server as a standby server. But it failed and there was tips:

And I checked event viewer in DFS replication:

The DFS Replication service failed to update configuration in Active Directory Domain Services. The service will retry this operation periodically.

ID 6016

Additional Information:

Object Category: msDFSR-LocalSettings

Error: 2（系统找不到指定的文件。）

Domain Controller: ourdomain.com

Polling Cycle: 60.

I queried some links on the website. But I can't fix it.

Thanks,

Answer

Hello

The error message you're seeing indicates that the domain controller promotion process completed, but the new server is not advertising itself as a domain controller. The DFS Replication service is also failing to update configuration in Active Directory, and there’s an error indicating that it couldn’t find a specific file. This points to a few potential underlying issues that we need to investigate and resolve. Here’s a structured troubleshooting guide:

Verify the Domain Controller Role and DNS Configuration

The error could happen if the new server isn't correctly recognized as a domain controller or if DNS is not properly configured.

Check DNS Configuration: Ensure that the new server’s DNS settings are correct. It should point to the domain controller (PDC or any other DC in the domain) for DNS resolution. This is crucial for AD functionality.

Open DNS Manager and ensure the new server is able to resolve DNS queries for the domain and Active Directory services.

Check Active Directory Services:

Open Server Manager and make sure that Active Directory Domain Services and DNS are running on the new server.

You can verify this with the dcdiag tool:
dcdiag /v
This will give you detailed information about the health of the domain controller, DNS configuration, and other AD-related checks.

Check Event Logs for More Information

It seems you're already checking the event logs, but let's take a closer look:

Event ID 6016 (DFS Replication Error): The DFS Replication service is trying to update configuration in AD DS but is failing.

This is often related to issues with replication and the availability of Active Directory services. The error code Error: 2 (系统找不到指定的文件) suggests that the DFS Replication service is looking for certain files or configurations in AD and is not able to find them.

Look for errors in the DFS Replication logs (Applications and Services Logs > DFS Replication), which could give you more context.

Seize FSMO Roles (If Applicable)

Since you mentioned that you seized the Schema Master and Domain Naming Master roles, ensure that the new DC server has successfully received and taken over these roles, and that the roles are being replicated properly.

Verify FSMO Roles:

You can use the following command to check which server holds each FSMO role:
netdom query fsmo

Ensure that the correct server holds the Schema Master and Domain Naming Master roles.

You can check the replication status of the FSMO roles with the following:
repadmin /showrepl

Manually Force Active Directory Replication

If the new server is not correctly advertising itself as a domain controller or if replication has issues, you can manually force replication:

On the new domain controller, run the following command to trigger AD replication:
repadmin /syncall /AdeP
This will force replication from all domain controllers.

You can also restart the Active Directory Domain Services and DFS Replication services on the new server:
net stop ntds
net start ntds
net stop dfs
net start dfs

Check SYSVOL and DFS Replication Health

The issue with DFS Replication in the event logs suggests there could be a problem with SYSVOL replication. This is critical for the domain controllers, as it stores group policies and other domain-wide settings.

Verify the SYSVOL share is properly configured and accessible:

Run the following command to check SYSVOL replication status:
dfsrdiag ReplicationState

Look for any replication issues or warnings.

Re-run Domain Controller Promotion

If the new server is still not functioning properly after the above steps, consider re-running the domain controller promotion process using DCPromo (or via Server Manager if on Server 2012 or later). This might fix any misconfigurations.

Remove the server from the domain (if possible), then promote it again as a domain controller.

Make sure to demote the server (if it was incorrectly promoted) first by running:
dcpromo /forceremoval

Check Active Directory Health

Run the following command to check the health of your Active Directory environment and identify any potential replication or configuration issues:

dcdiag /a /v

This provides a more detailed output of the domain controller's health and replication status.

I hope the above information is helpful to you.

Windows Client for IT Pros and Windows Server forums are moving to Microsoft Q&A

We’re transitioning to Microsoft Q&A for a more streamlined experience. Starting 21 February, new questions can only be posted on Microsoft Q&A. Existing discussions will remain accessible here.

From the 26 February customers looking for support on Answers will be automatically redirected to Microsoft Q&A.

Best regards

Runjie Zhai

Answer

Today I follow your advices check both servers again. I recorded a event file.

dc1server: 172.31.15.250

PS C:\Users\Administrator> netdom query fsmo

Schema master DC1SERVER.Qingdao.DALLAS.usagroup.com

Domain naming master DC1SERVER.Qingdao.DALLAS.usagroup.com

PDC DC1SERVER.Qingdao.DALLAS.usagroup.com

RID pool manager DC1SERVER.Qingdao.DALLAS.usagroup.com

Infrastructure master DC1SERVER.Qingdao.DALLAS.usagroup.com

The command completed successfully.

PS C:\Users\Administrator> dcdiag /test:dns

Directory Server Diagnosis

Performing initial setup:

Trying to find home server...

Home Server = DC1SERVER

* Identified AD Forest.

Done gathering initial info.

Doing initial required tests

Testing server: STAGING\DC1SERVER

Starting test: Connectivity

The host 588b7734-c9e2-46ef-8cf0-92b9d9c148c2._msdcs.DALLAS.usagroup.com could not be resolved to an IP

address. Check the DNS server, DHCP, server name, etc.

Got error while checking LDAP and RPC connectivity. Please check your firewall settings.

......................... DC1SERVER failed test Connectivity

Doing primary tests

Testing server: STAGING\DC1SERVER

Starting test: DNS

DNS Tests are running and not hung. Please wait a few minutes...

......................... DC1SERVER passed test DNS

Running partition tests on : Qingdao

Running partition tests on : ForestDnsZones

Running partition tests on : Schema

Running partition tests on : Configuration

Running partition tests on : DomainDnsZones

Running enterprise tests on : DALLAS.usagroup.com

Starting test: DNS

Test results for domain controllers:

DC: DC1SERVER.Qingdao.DALLAS.usagroup.com

Domain: Qingdao.DALLAS.usagroup.com

TEST: Basic (Basc)

Error: No LDAP connectivity

Warning: adapter [00000010] Broadcom NetXtreme Gigabit Ethernet has invalid DNS server: 172.31.15.250

(DC1SERVER)

Error: all DNS servers are invalid

No host records (A or AAAA) were found for this DC

TEST: Forwarders/Root hints (Forw)

Error: All forwarders in the forwarder list are invalid.

TEST: Records registration (RReg)

Error: Record registrations cannot be found for all the network adapters

Summary of test results for DNS servers used by the above domain controllers:

DNS server: 10.0.0.10 (

1 test failure on this DNS server

PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 10.0.0.10 Name re

solution is not functional. _ldap._tcp.DALLAS.usagroup.com. failed on the DNS server 10.0.0.10

DNS server: 114.114.114.114 (

1 test failure on this DNS server

Name resolution is not functional. _ldap._tcp.DALLAS.usagroup.com. failed on the DNS server 114.114.114.

114

DNS server: 172.31.15.250 (DC1SERVER)

1 test failure on this DNS server

Name resolution is not functional. _ldap._tcp.DALLAS.usagroup.com. failed on the DNS server 172.31.15.25

0

DNS server: 202.102.128.68 (

1 test failure on this DNS server

PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 202.102.128.68 Na

me resolution is not functional. _ldap._tcp.DALLAS.usagroup.com. failed on the DNS server 202.102.128.68

DNS server: 223.6.6.6 (

1 test failure on this DNS server

Name resolution is not functional. _ldap._tcp.DALLAS.usagroup.com. failed on the DNS server 223.6.6.6

Summary of DNS test results:

Auth Basc Forw Del Dyn RReg Ext

_________________________________________________________________

Domain: Qingdao.DALLAS.usagroup.com

DC1SERVER PASS FAIL FAIL PASS PASS FAIL n/a

......................... DALLAS.usagroup.com failed test DNS

PS C:\Users\Administrator>

PS C:\Users\Administrator> repadmin /showrepl

Repadmin: running command /showrepl against full DC localhost

STAGING\DC1SERVER

DSA Options: IS_GC

Site Options: (none)

DSA object GUID: 588b7734-c9e2-46ef-8cf0-92b9d9c148c2

DSA invocationID: 444e0925-efa3-485b-b253-075e209e82e9

Source: MADISON\TDGAD

******* 31 CONSECUTIVE FAILURES since 2025-02-27 01:13:02

Last error: 8524 (0x214c):

The DSA operation is unable to proceed because of a DNS lookup failure.

Source: WHITEHOUSE\NJ-DC-02

******* 47 CONSECUTIVE FAILURES since 2025-02-26 21:01:35

Last error: 1722 (0x6ba):

The RPC server is unavailable.

Naming Context: CN=Configuration,DC=DALLAS,DC=usagroup,DC=com

Source: WHITEHOUSE\NJ-DC-02

******* WARNING: KCC could not add this REPLICA LINK due to error.

Naming Context: DC=ForestDnsZones,DC=DALLAS,DC=usagroup,DC=com

Source: WHITEHOUSE\NJ-DC-02

******* WARNING: KCC could not add this REPLICA LINK due to error.

Naming Context: DC=DALLAS,DC=usagroup,DC=com

Source: WHITEHOUSE\NJ-DC-02

******* WARNING: KCC could not add this REPLICA LINK due to error.

Naming Context: DC=texascity,DC=DALLAS,DC=usagroup,DC=com

Source: WHITEHOUSE\NJ-DC-02

******* WARNING: KCC could not add this REPLICA LINK due to error.

Source: WHITEHOUSE\NJ-DC-01

******* 3 CONSECUTIVE FAILURES since 2025-02-27 09:03:54

Last error: 1722 (0x6ba):

The RPC server is unavailable.

Naming Context: CN=Configuration,DC=DALLAS,DC=usagroup,DC=com

Source: WHITEHOUSE\NJ-DC-01

******* WARNING: KCC could not add this REPLICA LINK due to error.

Naming Context: DC=ForestDnsZones,DC=DALLAS,DC=usagroup,DC=com

Source: WHITEHOUSE\NJ-DC-01

******* WARNING: KCC could not add this REPLICA LINK due to error.

Naming Context: DC=DALLAS,DC=usagroup,DC=com

Source: WHITEHOUSE\NJ-DC-01

******* WARNING: KCC could not add this REPLICA LINK due to error.

Source: STAGING\DALLAS-EXTRADC

******* 81 CONSECUTIVE FAILURES since 2025-02-26 12:09:53

Last error: 1722 (0x6ba):

The RPC server is unavailable.

Naming Context: CN=Configuration,DC=DALLAS,DC=usagroup,DC=com

Source: STAGING\DALLAS-EXTRADC

******* WARNING: KCC could not add this REPLICA LINK due to error.

Naming Context: CN=Schema,CN=Configuration,DC=DALLAS,DC=usagroup,DC=com

Source: STAGING\DALLAS-EXTRADC

******* WARNING: KCC could not add this REPLICA LINK due to error.

Naming Context: DC=Qingdao,DC=DALLAS,DC=usagroup,DC=com

Source: STAGING\DALLAS-EXTRADC

******* WARNING: KCC could not add this REPLICA LINK due to error.

PS C:\Users\Administrator> dfsrdiag replicationstate

Summary

Active inbound connections: 0

Updates received: 0

Active outbound connections: 0

Updates sent out: 0

Operation Succeeded

PS C:\Users\Administrator> dcdiag /a /v

Directory Server Diagnosis

Performing initial setup:

Trying to find home server...

* Verifying that the local machine DC1SERVER, is a Directory Server.

Home Server = DC1SERVER

* Connecting to directory service on server DC1SERVER.

* Identified AD Forest.

Collecting AD specific global data

* Collecting site info.

Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=DALLAS,DC=usagroup,DC=com,LDAP_SCOPE_SUBTREE,(objectC

ategory=ntDSSiteSettings),.......

The previous call succeeded

Iterating through the sites

Looking at base site object: CN=NTDS Site Settings,CN=STAGING,CN=Sites,CN=Configuration,DC=DALLAS,DC=usagroup,DC=com

Getting ISTG and options for the site

Looking at base site object: CN=NTDS Site Settings,CN=JEFFERSONVILLE,CN=Sites,CN=Configuration,DC=DALLAS,DC=usagroup

,DC=com

Getting ISTG and options for the site

Looking at base site object: CN=NTDS Site Settings,CN=TEXASCITY,CN=Sites,CN=Configuration,DC=DALLAS,DC=usagroup,DC=c

om

Getting ISTG and options for the site

Looking at base site object: CN=NTDS Site Settings,CN=MADISON,CN=Sites,CN=Configuration,DC=DALLAS,DC=usagroup,DC=com

Getting ISTG and options for the site

Looking at base site object: CN=NTDS Site Settings,CN=WHITEHOUSE,CN=Sites,CN=Configuration,DC=DALLAS,DC=usagroup,DC=

com

Getting ISTG and options for the site

* Identifying all servers.

Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=DALLAS,DC=usagroup,DC=com,LDAP_SCOPE_SUBTREE,(objectC

lass=ntDSDsa),.......

The previous call succeeded....

The previous call succeeded

Iterating through the list of servers

Getting information for the server CN=NTDS Settings,CN=NJ-DC-02,CN=Servers,CN=WHITEHOUSE,CN=Sites,CN=Configuration,DC

=DALLAS,DC=usagroup,DC=com

objectGuid obtained

InvocationID obtained

dnsHostname obtained

site info obtained

All the info for the server collected

Getting information for the server CN=NTDS Settings,CN=NJ-DC-01,CN=Servers,CN=WHITEHOUSE,CN=Sites,CN=Configuration,DC

=DALLAS,DC=usagroup,DC=com

objectGuid obtained

InvocationID obtained

dnsHostname obtained

site info obtained

All the info for the server collected

Getting information for the server CN=NTDS Settings,CN=TX-DC-01,CN=Servers,CN=TEXASCITY,CN=Sites,CN=Configuration,DC=

DALLAS,DC=usagroup,DC=com

objectGuid obtained

InvocationID obtained

dnsHostname obtained

site info obtained

All the info for the server collected

Getting information for the server CN=NTDS Settings,CN=DLLASGRP-DC3,CN=Servers,CN=JEFFERSONVILLE,CN=Sites,CN=Configur

ation,DC=DALLAS,DC=usagroup,DC=com

objectGuid obtained

InvocationID obtained

dnsHostname obtained

site info obtained

All the info for the server collected

Getting information for the server CN=NTDS Settings,CN=TDGAD,CN=Servers,CN=MADISON,CN=Sites,CN=Configuration,DC=DALLA

S,DC=usagroup,DC=com

objectGuid obtained

InvocationID obtained

dnsHostname obtained

site info obtained

All the info for the server collected

Getting information for the server CN=NTDS Settings,CN=DC1SERVER,CN=Servers,CN=STAGING,CN=Sites,CN=Configuration,DC=DA

LLAS,DC=usagroup,DC=com

objectGuid obtained

InvocationID obtained

dnsHostname obtained

site info obtained

All the info for the server collected

Getting information for the server CN=NTDS Settings,CN=DALLAS-EXTRADC,CN=Servers,CN=STAGING,CN=Sites,CN=Configuration

,DC=DALLAS,DC=usagroup,DC=com

objectGuid obtained

InvocationID obtained

site info obtained

All the info for the server collected

* Identifying all NC cross-refs.

Ldap search capability attribute search failed on server DALLAS-EXTRADC, return value = 81

Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and

DfsrEvent tests might fail because of this error.

* Found 7 DC(s). Testing 2 of them.

Done gathering initial info.

Doing initial required tests

Testing server: STAGING\DC1SERVER

Starting test: Connectivity

* Active Directory LDAP Services Check

The host 588b7734-c9e2-46ef-8cf0-92b9d9c148c2._msdcs.DALLAS.usagroup.com could not be resolved to an IP

address. Check the DNS server, DHCP, server name, etc.

Got error while checking LDAP and RPC connectivity. Please check your firewall settings.

......................... DC1SERVER failed test Connectivity

Testing server: STAGING\DALLAS-EXTRADC

Starting test: Connectivity

* Active Directory LDAP Services Check

The host 6fbc7b6c-e934-44c3-9db1-5f209f481fa2._msdcs.DALLAS.usagroup.com could not be resolved to an IP

address. Check the DNS server, DHCP, server name, etc.

Neither the the server name (DALLAS-EXTRADC.@missing_dnsHostName@) nor the Guid DNS name

(6fbc7b6c-e934-44c3-9db1-5f209f481fa2._msdcs.DALLAS.usagroup.com) could be resolved by DNS. Check that the

server is up and is registered correctly with the DNS server.

Got error while checking LDAP and RPC connectivity. Please check your firewall settings.

......................... DALLAS-EXTRADC failed test Connectivity

Doing primary tests

Testing server: STAGING\DC1SERVER

Skipping all tests, because server DC1SERVER is not responding to directory service requests.

Test omitted by user request: Advertising

Test omitted by user request: CheckSecurityError

Test omitted by user request: CutoffServers

Test omitted by user request: FrsEvent

Test omitted by user request: DFSREvent

Test omitted by user request: SysVolCheck

Test omitted by user request: KccEvent

Test omitted by user request: KnowsOfRoleHolders

Test omitted by user request: MachineAccount

Test omitted by user request: NCSecDesc

Test omitted by user request: NetLogons

Test omitted by user request: ObjectsReplicated

Test omitted by user request: OutboundSecureChannels

Test omitted by user request: Replications

Test omitted by user request: RidManager

Test omitted by user request: Services

Test omitted by user request: SystemLog

Test omitted by user request: Topology

Test omitted by user request: VerifyEnterpriseReferences

Test omitted by user request: VerifyReferences

Test omitted by user request: VerifyReplicas

Testing server: STAGING\DALLAS-EXTRADC

Skipping all tests, because server DALLAS-EXTRADC is not responding to directory service requests.

Test omitted by user request: Advertising

Test omitted by user request: CheckSecurityError

Test omitted by user request: CutoffServers

Test omitted by user request: FrsEvent

Test omitted by user request: DFSREvent

Test omitted by user request: SysVolCheck

Test omitted by user request: KccEvent

Test omitted by user request: KnowsOfRoleHolders

Test omitted by user request: MachineAccount

Test omitted by user request: NCSecDesc

Test omitted by user request: NetLogons

Test omitted by user request: ObjectsReplicated

Test omitted by user request: OutboundSecureChannels

Test omitted by user request: Replications

Test omitted by user request: RidManager

Test omitted by user request: Services

Test omitted by user request: SystemLog

Test omitted by user request: Topology

Test omitted by user request: VerifyEnterpriseReferences

Test omitted by user request: VerifyReferences

Test omitted by user request: VerifyReplicas

Test omitted by user request: DNS

Running partition tests on : Qingdao

Starting test: CheckSDRefDom

......................... Qingdao passed test CheckSDRefDom

Starting test: CrossRefValidation

For the partition (DC=Qingdao,DC=DALLAS,DC=usagroup,DC=com) we encountered the following error retrieving

the cross-ref's (CN=QINGDAO,CN=Partitions,CN=Configuration,DC=DALLAS,DC=usagroup,DC=com) information:

LDAP Error 0x3a (58).

......................... Qingdao failed test CrossRefValidation

Running partition tests on : ForestDnsZones

Starting test: CheckSDRefDom

For the partition (DC=ForestDnsZones,DC=DALLAS,DC=usagroup,DC=com) we encountered the following error

retrieving the cross-ref's

(CN=7398587e-b7e5-44b2-989b-7f3884511790,CN=Partitions,CN=Configuration,DC=DALLAS,DC=usagroup,DC=com)

information:

LDAP Error 0x3a (58).

......................... ForestDnsZones failed test CheckSDRefDom

Starting test: CrossRefValidation

For the partition (DC=ForestDnsZones,DC=DALLAS,DC=usagroup,DC=com) we encountered the following error

retrieving the cross-ref's

(CN=7398587e-b7e5-44b2-989b-7f3884511790,CN=Partitions,CN=Configuration,DC=DALLAS,DC=usagroup,DC=com)

information:

LDAP Error 0x3a (58).

......................... ForestDnsZones failed test CrossRefValidation

Running partition tests on : Schema

Starting test: CheckSDRefDom

......................... Schema passed test CheckSDRefDom

Starting test: CrossRefValidation

For the partition (CN=Schema,CN=Configuration,DC=DALLAS,DC=usagroup,DC=com) we encountered the following

error retrieving the cross-ref's

(CN=Enterprise Schema,CN=Partitions,CN=Configuration,DC=DALLAS,DC=usagroup,DC=com) information:

LDAP Error 0x3a (58).

......................... Schema failed test CrossRefValidation

Running partition tests on : Configuration

Starting test: CheckSDRefDom

......................... Configuration passed test CheckSDRefDom

Starting test: CrossRefValidation

For the partition (CN=Configuration,DC=DALLAS,DC=usagroup,DC=com) we encountered the following error

retrieving the cross-ref's

(CN=Enterprise Configuration,CN=Partitions,CN=Configuration,DC=DALLAS,DC=usagroup,DC=com) information:

LDAP Error 0x3a (58).

......................... Configuration failed test CrossRefValidation

Running partition tests on : DomainDnsZones

Starting test: CheckSDRefDom

......................... DomainDnsZones passed test CheckSDRefDom

Starting test: CrossRefValidation

For the partition (DC=DomainDnsZones,DC=Qingdao,DC=DALLAS,DC=usagroup,DC=com) we encountered the following

error retrieving the cross-ref's

(CN=8ebf1ff0-36d8-4f81-9380-ce4b462180f4,CN=Partitions,CN=Configuration,DC=DALLAS,DC=usagroup,DC=com)

information:

LDAP Error 0x3a (58).

......................... DomainDnsZones failed test CrossRefValidation

Running partition tests on : DomainDnsZones

Starting test: CheckSDRefDom

......................... DomainDnsZones passed test CheckSDRefDom

Starting test: CrossRefValidation

For the partition (DC=DomainDnsZones,DC=Qingdao,DC=DALLAS,DC=usagroup,DC=com) we encountered the following

error retrieving the cross-ref's

(CN=8ebf1ff0-36d8-4f81-9380-ce4b462180f4,CN=Partitions,CN=Configuration,DC=DALLAS,DC=usagroup,DC=com)

information:

LDAP Error 0x3a (58).

......................... DomainDnsZones failed test CrossRefValidation

Running enterprise tests on : DALLAS.usagroup.com

Test omitted by user request: DNS

Starting test: LocatorCheck

GC Name: \DC1SERVER.Qingdao.DALLAS.usagroup.com

Locator Flags: 0xe00073fd

PDC Name: \DC1SERVER.Qingdao.DALLAS.usagroup.com

Locator Flags: 0xe00073fd

Time Server Name: \DC1SERVER.Qingdao.DALLAS.usagroup.com

Locator Flags: 0xe00073fd

Preferred Time Server Name: \DC1SERVER.Qingdao.DALLAS.usagroup.com

Locator Flags: 0xe00073fd

KDC Name: \DC1SERVER.Qingdao.DALLAS.usagroup.com

Locator Flags: 0xe00073fd

......................... DALLAS.usagroup.com passed test LocatorCheck

Starting test: Intersite

Doing intersite inbound replication test on site STAGING:

Locating & Contacting Intersite Topology Generator (ISTG) ...

The ISTG for site STAGING is: DC1SERVER.

Checking for down bridgeheads ...

*Warning: Remote bridgehead MADISON\TDGAD is not eligible as a bridgehead due to too many failures.

Replication may be disrupted into the local site STAGING.

Bridghead STAGING\DC1SERVER is up and replicating fine.

Remote bridgehead STAGING\DC1SERVER also couldn't be contacted by dcdiag. Check this server.

*Warning: Remote bridgehead WHITEHOUSE\NJ-DC-02 is not eligible as a bridgehead due to too many

failures. Replication may be disrupted into the local site STAGING.

*Warning: Remote bridgehead WHITEHOUSE\NJ-DC-01 has some replication syncs failing. It will be 1 hours

3 minutes before the bridgehead is considered ineligible to be a bridgehead.

*Warning: Remote bridgehead STAGING\DALLAS-EXTRADC is not eligible as a bridgehead due to too many

failures. Replication may be disrupted into the local site STAGING.

Remote bridgehead STAGING\DALLAS-EXTRADC also couldn't be contacted by dcdiag. Check this server.

Doing in depth site analysis ...

Remote site MADISON is replicating to the local site STAGING the writeable NC ForestDnsZones correctly.

Remote site MADISON is replicating to the local site STAGING the writeable NC Schema correctly.

Remote site MADISON is replicating to the local site STAGING the writeable NC Configuration correctly.

Remote site MADISON is replicating to the local site STAGING the writeable NC Qingdao correctly.

Remote site WHITEHOUSE is replicating to the local site STAGING the writeable NC ForestDnsZones

correctly.

Remote site WHITEHOUSE is replicating to the local site STAGING the writeable NC Schema correctly.

Remote site WHITEHOUSE is replicating to the local site STAGING the writeable NC Configuration

correctly.

Remote site WHITEHOUSE is replicating to the local site STAGING the writeable NC Qingdao correctly.

Skipping site JEFFERSONVILLE, this site is outside the scope provided by the command line arguments provided.

Skipping site TEXASCITY, this site is outside the scope provided by the command line arguments provided.

Skipping site MADISON, this site is outside the scope provided by the command line arguments provided.

Skipping site WHITEHOUSE, this site is outside the scope provided by the command line arguments provided.

......................... DALLAS.usagroup.com passed test Intersite

PS C:\Users\Administrator>

dallas-extradc: 172.31.15.104

repadmin /showrepl

PS C:\Users\administrator.QINGDAO> repadmin /showrepl

Repadmin: running command /showrepl against full DC localhost

STAGING\DALLAS-EXTRADC

DSA Options: IS_GC

WARNING: Not advertising as a global catalog.

Site Options: (none)

DSA object GUID: 6fbc7b6c-e934-44c3-9db1-5f209f481fa2

DSA invocationID: 8126e391-9613-4320-9a4c-57b45c88f379

Source: STAGING\DC1SERVER

******* 82 CONSECUTIVE FAILURES since 2025-02-26 13:18:00

Last error: 8464 (0x2110):

Synchronization attempt failed because the destination DC is currently waiting to synchronize new partial at

tributes from source. This condition is normal if a recent schema change modified the partial attribute set. The destina

tion partial attribute set is not a subset of source partial attribute set.

Share via

Error determining whether the target server is already a domain controller: The domain controller promotion completed, but the server is not advertising as a domain controller.

2 answers