First Win 2016 DC in Win 2008 R2 Domain complains that Migration to DFSR has not reached a consistent state
We have a Domain with 10 Win 2008 R2 Domain Controllers in different sites. More than a year ago we migrated from FRS to DFRS successfully. Now I brought the first Win 2016 Domain Controller into the Domain (let's name it WIN2016DCNAME here). Generally the promotion worked well (incl. Forest and Domain Prep), although the server crashed once after the reboot following the promotion to a DC. Since then all looks good and the system is stable incl. SYSVOL Replication. "repadmin /replsummary" also shows all now 11 DCs in sync.
By chance I came across an indication that there is an issue with DFSR and found that "dfsrmig /getMigrationState" shows the following status:
Because of the error in DCDIAG that NtFrs is disabled I enabled and started the Service but it immediately stops and writes into C:\Windows\debug\NtFrs_xxx
May this situation be a result of the crash during the first boot after promotion?
Can it be safely ignored?
Would you recommend to demote the DC and then promote it again? I would like to avoid to reinstall the OS and to give it a new name!
Any other suggestions?
By chance I came across an indication that there is an issue with DFSR and found that "dfsrmig /getMigrationState" shows the following status:
The following domain controllers have not reached Global state ('Eliminated'):
Domain Controller (Local Migration State) - DC Type
===================================================
WIN2016DCNAME ('Start') - Writable DC
Migration has not yet reached a consistent state on all domain controllers.
State information might be stale due to Active Directory Domain Services latency. Starting test: Services
Invalid service startup type: NtFrs on WIN2016DCNAME, current value DISABLED, expected value AUTO_START
NtFrs Service is stopped on [WIN2016DCNAME ]
......................... WIN2016DCNAME failed test Services
Starting test: SystemLog
......................... WIN2016DCNAME passed test SystemLog
Starting test: VerifyReferences
Some objects relating to the DC WIN2016DCNAME have problems:
[1] Problem: Missing Expected Value
Base Object: CN=WIN2016DCNAME,OU=Domain Controllers,DC=XXX,DC=com
Base Object Description: "DC Account Object"
Value Object Attribute Name: frsComputerReferenceBL
Value Object Description: "SYSVOL FRS Member Object"
Recommended Action: See Knowledge Base Article: Q312862
......................... WIN2016DCNAME failed test VerifyReferences20181009 10:04:13.971 5148 MIGM 738 [ERROR] main Error:
+ [Error:9512(0x2528) Process main.cpp:602 5148 C Migration have not yet reached to a consistent state on all Domain Controllers]
+ [Error:9512(0x2528) ProcessGetMigrationState main.cpp:485 5148 C [b]Migration have not yet reached to a consistent state on all Domain Controllers[/b]]Because of the error in DCDIAG that NtFrs is disabled I enabled and started the Service but it immediately stops and writes into C:\Windows\debug\NtFrs_xxx
<DbgInitLogTraceFile: 6860: 1884: S0: 08:28:28> :S: Full pathname for c:\windows\system32\ntfrs.exe
<Migrate: 6860: 1376: S0: 08:28:28> Returning DFSR Migration Local state: 3.
<FrsPrintEvent: 6860: 619: S0: 08:28:28> :E: Eventlog written for EVENT_FRS_STOPPED_ELIMINATED_STATE (13575) severity: Error at: Wed, Oct 10 2018 08:28:28May this situation be a result of the crash during the first boot after promotion?
Can it be safely ignored?
Would you recommend to demote the DC and then promote it again? I would like to avoid to reinstall the OS and to give it a new name!
Any other suggestions?
ASKER
I bet there was no issue with the FRS to DFSR Migration before I promoted the first Win 2016 DC. Obviously I did not check explicitly because the migration took place long time in the past and was successfully completed, but there is no indication that there was any issue. Depart from that Dfsrdiag /GetMigrationState currently points to the shown issue with the new DC on all DCs. In my eyes this also states that if any, there is issue with the new DC. If I would demote it, it will be gone I bet. But just to try that, it's too much effort and risk in a productive environment. I will now promote another Win 2016 DC to see if it will have the same issue or not.
after migrating frs to dfsr you did not promoted any 2012 / 2008 r2 DC, hence you did not notice the problem
I believe the problem must exists from beginning and its popping out after you promoted new DC, promoting new DC won't solve the issue IMHO
I believe the problem must exists from beginning and its popping out after you promoted new DC, promoting new DC won't solve the issue IMHO
ASKER
Not true! I promoted 2 Win 2008 R2 DCs after the Migration to DFSR and they don't have that issue.
I agree that promoting new DC won't solve the issue IMHO for the DC which has the issue now but until we get a better idea it will show if another Win 2016 DC will run into the same issue or not. If yes, it seems to be symptomatic, if no, demoting the current one looks more promising then it is now.
I agree that promoting new DC won't solve the issue IMHO for the DC which has the issue now but until we get a better idea it will show if another Win 2016 DC will run into the same issue or not. If yes, it seems to be symptomatic, if no, demoting the current one looks more promising then it is now.
can you run dcdiag /v on pdc with elevated prompt and post results here?
ASKER
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
* Verifying that the local machine XXXDARS2, is a Directory Server.
Home Server = XXXDARS2
* Connecting to directory service on server XXXDARS2.
* Identified AD Forest.
Collecting AD specific global data
* Collecting site info.
Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=XXX,DC=com,LDAP_SCOPE_SUBTREE,(objectCategory=ntDSSiteSettings),.......
The previous call succeeded
Iterating through the sites
Looking at base site object: CN=NTDS Site Settings,CN=Site1,CN=Sites,CN=Configuration,DC=XXX,DC=com
Getting ISTG and options for the site
Looking at base site object: CN=NTDS Site Settings,CN=Site2,CN=Sites,CN=Configuration,DC=XXX,DC=com
Getting ISTG and options for the site
Looking at base site object: CN=NTDS Site Settings,CN=Site3,CN=Sites,CN=Configuration,DC=XXX,DC=com
Getting ISTG and options for the site
Looking at base site object: CN=NTDS Site Settings,CN=Site4,CN=Sites,CN=Configuration,DC=XXX,DC=com
Getting ISTG and options for the site
Looking at base site object: CN=NTDS Site Settings,CN=Site5,CN=Sites,CN=Configuration,DC=XXX,DC=com
Getting ISTG and options for the site
Looking at base site object: CN=NTDS Site Settings,CN=Site6,CN=Sites,CN=Configuration,DC=XXX,DC=com
Getting ISTG and options for the site
Looking at base site object: CN=NTDS Site Settings,CN=Site7,CN=Sites,CN=Configuration,DC=XXX,DC=com
Getting ISTG and options for the site
* Identifying all servers.
Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=XXX,DC=com,LDAP_SCOPE_SUBTREE,(objectClass=ntDSDsa),.......
The previous call succeeded....
The previous call succeeded
Iterating through the list of servers
Getting information for the server CN=NTDS Settings,CN=XXXDARS4,CN=Servers,CN=Site5,CN=Sites,CN=Configuration,DC=XXX,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=XXXDARS5,CN=Servers,CN=Site4,CN=Sites,CN=Configuration,DC=XXX,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=XXXDARS6,CN=Servers,CN=Site4,CN=Sites,CN=Configuration,DC=XXX,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=XXXDARS2,CN=Servers,CN=Site5,CN=Sites,CN=Configuration,DC=XXX,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=XXXMBORS2,CN=Servers,CN=Site1,CN=Sites,CN=Configuration,DC=XXX,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=XXXDONRS2,CN=Servers,CN=Site3,CN=Sites,CN=Configuration,DC=XXX,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=XXXURBRS2,CN=Servers,CN=Site2,CN=Sites,CN=Configuration,DC=XXX,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=XXXOPORS1,CN=Servers,CN=Site6,CN=Sites,CN=Configuration,DC=XXX,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=XXX1EUW1ADC001,CN=Servers,CN=Site7,CN=Sites,CN=Configuration,DC=XXX,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=XXX1EUW1ADC002,CN=Servers,CN=Site7,CN=Sites,CN=Configuration,DC=XXX,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=XXXOPORS2,CN=Servers,CN=Site6,CN=Sites,CN=Configuration,DC=XXX,DC=com
objectGuid obtained
InvocationID obtained
dnsHostname obtained
site info obtained
All the info for the server collected
* Identifying all NC cross-refs.
* Found 11 DC(s). Testing 1 of them.
Done gathering initial info.
Doing initial required tests
Testing server: Site5\XXXDARS2
Starting test: Connectivity
* Active Directory LDAP Services Check
Determining IP4 connectivity
* Active Directory RPC Services Check
......................... XXXDARS2 passed test Connectivity
Doing primary tests
Testing server: Site5\XXXDARS2
Starting test: Advertising
The DC XXXDARS2 is advertising itself as a DC and having a DS.
The DC XXXDARS2 is advertising as an LDAP server
The DC XXXDARS2 is advertising as having a writeable directory
The DC XXXDARS2 is advertising as a Key Distribution Center
The DC XXXDARS2 is advertising as a time server
The DS XXXDARS2 is advertising as a GC.
......................... XXXDARS2 passed test Advertising
Test omitted by user request: CheckSecurityError
Test omitted by user request: CutoffServers
Starting test: FrsEvent
* The File Replication Service Event log test
Skip the test because the server is running DFSR.
......................... XXXDARS2 passed test FrsEvent
Starting test: DFSREvent
The DFS Replication Event Log.
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may cause
Group Policy problems.
A warning event occurred. EventID: 0x80001396
Time Generated: 10/09/2018 19:46:30
Event String:
The DFS Replication service is stopping communication with partner XXXDONRS2 for replication group Domain System Volume due to an error. The service will retry the connection periodically.
Additional Information:
Error: 9036 (Paused for backup or restore)
Connection ID: 751B61C9-28DF-4A3C-9D24-C800DEF7D3E9
Replication Group ID: 3225C610-2AA7-4280-8F4C-0DD765F0CA2E
A warning event occurred. EventID: 0x80001396
Time Generated: 10/09/2018 19:53:09
Event String:
The DFS Replication service is stopping communication with partner XXXDONRS2 for replication group Domain System Volume due to an error. The service will retry the connection periodically.
Additional Information:
Error: 9036 (Paused for backup or restore)
Connection ID: 751B61C9-28DF-4A3C-9D24-C800DEF7D3E9
Replication Group ID: 3225C610-2AA7-4280-8F4C-0DD765F0CA2E
A warning event occurred. EventID: 0x80001396
Time Generated: 10/09/2018 19:53:48
Event String:
The DFS Replication service is stopping communication with partner XXXDONRS2 for replication group Domain System Volume due to an error. The service will retry the connection periodically.
Additional Information:
Error: 9036 (Paused for backup or restore)
Connection ID: 751B61C9-28DF-4A3C-9D24-C800DEF7D3E9
Replication Group ID: 3225C610-2AA7-4280-8F4C-0DD765F0CA2E
A warning event occurred. EventID: 0x80001396
Time Generated: 10/09/2018 21:00:32
Event String:
The DFS Replication service is stopping communication with partner XXXDARS4 for replication group Domain System Volume due to an error. The service will retry the connection periodically.
Additional Information:
Error: 9036 (Paused for backup or restore)
Connection ID: 5B774AE7-F14A-43C3-9323-38A9CA66CEB6
Replication Group ID: 3225C610-2AA7-4280-8F4C-0DD765F0CA2E
A warning event occurred. EventID: 0x80001396
Time Generated: 10/09/2018 21:30:11
Event String:
The DFS Replication service is stopping communication with partner XXXDONRS2 for replication group Domain System Volume due to an error. The service will retry the connection periodically.
Additional Information:
Error: 9036 (Paused for backup or restore)
Connection ID: 751B61C9-28DF-4A3C-9D24-C800DEF7D3E9
Replication Group ID: 3225C610-2AA7-4280-8F4C-0DD765F0CA2E
A warning event occurred. EventID: 0x80001396
Time Generated: 10/09/2018 22:01:21
Event String:
The DFS Replication service is stopping communication with partner XXXDARS4 for replication group Domain System Volume due to an error. The service will retry the connection periodically.
Additional Information:
Error: 9036 (Paused for backup or restore)
Connection ID: 5B774AE7-F14A-43C3-9323-38A9CA66CEB6
Replication Group ID: 3225C610-2AA7-4280-8F4C-0DD765F0CA2E
A warning event occurred. EventID: 0x80001396
Time Generated: 10/09/2018 22:05:51
Event String:
The DFS Replication service is stopping communication with partner XXXDARS4 for replication group Domain System Volume due to an error. The service will retry the connection periodically.
Additional Information:
Error: 9036 (Paused for backup or restore)
Connection ID: 5B774AE7-F14A-43C3-9323-38A9CA66CEB6
Replication Group ID: 3225C610-2AA7-4280-8F4C-0DD765F0CA2E
A warning event occurred. EventID: 0x80001396
Time Generated: 10/09/2018 22:31:29
Event String:
The DFS Replication service is stopping communication with partner XXXDARS6 for replication group Domain System Volume due to an error. The service will retry the connection periodically.
Additional Information:
Error: 9036 (Paused for backup or restore)
Connection ID: 1EE2A6E6-0C45-4305-97CE-974D36C9E6E9
Replication Group ID: 3225C610-2AA7-4280-8F4C-0DD765F0CA2E
A warning event occurred. EventID: 0x80001396
Time Generated: 10/09/2018 22:33:35
Event String:
The DFS Replication service is stopping communication with partner XXXDARS6 for replication group Domain System Volume due to an error. The service will retry the connection periodically.
Additional Information:
Error: 9036 (Paused for backup or restore)
Connection ID: 1EE2A6E6-0C45-4305-97CE-974D36C9E6E9
Replication Group ID: 3225C610-2AA7-4280-8F4C-0DD765F0CA2E
A warning event occurred. EventID: 0x80001396
Time Generated: 10/10/2018 05:31:34
Event String:
The DFS Replication service is stopping communication with partner XXXMBORS2 for replication group Domain System Volume due to an error. The service will retry the connection periodically.
Additional Information:
Error: 9036 (Paused for backup or restore)
Connection ID: 18E5040E-B13D-4970-9C50-DCFF41F36F27
Replication Group ID: 3225C610-2AA7-4280-8F4C-0DD765F0CA2E
A warning event occurred. EventID: 0x80001396
Time Generated: 10/10/2018 05:38:03
Event String:
The DFS Replication service is stopping communication with partner XXXMBORS2 for replication group Domain System Volume due to an error. The service will retry the connection periodically.
Additional Information:
Error: 9036 (Paused for backup or restore)
Connection ID: 18E5040E-B13D-4970-9C50-DCFF41F36F27
Replication Group ID: 3225C610-2AA7-4280-8F4C-0DD765F0CA2E
A warning event occurred. EventID: 0x80001396
Time Generated: 10/10/2018 05:41:24
Event String:
The DFS Replication service is stopping communication with partner XXXMBORS2 for replication group Domain System Volume due to an error. The service will retry the connection periodically.
Additional Information:
Error: 9036 (Paused for backup or restore)
Connection ID: 18E5040E-B13D-4970-9C50-DCFF41F36F27
Replication Group ID: 3225C610-2AA7-4280-8F4C-0DD765F0CA2E
A warning event occurred. EventID: 0x80001396
Time Generated: 10/10/2018 08:00:18
Event String:
The DFS Replication service is stopping communication with partner XXXDARS6 for replication group Domain System Volume due to an error. The service will retry the connection periodically.
Additional Information:
Error: 9036 (Paused for backup or restore)
Connection ID: 1EE2A6E6-0C45-4305-97CE-974D36C9E6E9
Replication Group ID: 3225C610-2AA7-4280-8F4C-0DD765F0CA2E
A warning event occurred. EventID: 0x80001396
Time Generated: 10/10/2018 10:00:20
Event String:
The DFS Replication service is stopping communication with partner XXX1EUW1ADC001 for replication group Domain System Volume due to an error. The service will retry the connection periodically.
Additional Information:
Error: 9036 (Paused for backup or restore)
Connection ID: F815657D-A808-40BF-8B4C-537796BA7CAC
Replication Group ID: 3225C610-2AA7-4280-8F4C-0DD765F0CA2E
......................... XXXDARS2 passed test DFSREvent
Starting test: SysVolCheck
* The File Replication Service SYSVOL ready test
File Replication Service's SYSVOL is ready
......................... XXXDARS2 passed test SysVolCheck
Starting test: KccEvent
* The KCC Event log test
Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
......................... XXXDARS2 passed test KccEvent
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS Settings,CN=XXXDARS2,CN=Servers,CN=Site5,CN=Sites,CN=Configuration,DC=XXX,DC=com
Role Domain Owner = CN=NTDS Settings,CN=XXXDARS2,CN=Servers,CN=Site5,CN=Sites,CN=Configuration,DC=XXX,DC=com
Role PDC Owner = CN=NTDS Settings,CN=XXXDARS2,CN=Servers,CN=Site5,CN=Sites,CN=Configuration,DC=XXX,DC=com
Role Rid Owner = CN=NTDS Settings,CN=XXXDARS2,CN=Servers,CN=Site5,CN=Sites,CN=Configuration,DC=XXX,DC=com
Role Infrastructure Update Owner = CN=NTDS Settings,CN=XXXDARS2,CN=Servers,CN=Site5,CN=Sites,CN=Configuration,DC=XXX,DC=com
......................... XXXDARS2 passed test KnowsOfRoleHolders
Starting test: MachineAccount
Checking machine account for DC XXXDARS2 on DC XXXDARS2.
* SPN found :LDAP/XXXDARS2.XXX.com/XXX.com
* SPN found :LDAP/XXXDARS2.XXX.com
* SPN found :LDAP/XXXDARS2
* SPN found :LDAP/XXXDARS2.XXX.com/XXX
* SPN found :LDAP/65f810d5-426c-4557-86ae-f2bbf2b8a8f0._msdcs.XXX.com
* SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/65f810d5-426c-4557-86ae-f2bbf2b8a8f0/XXX.com
* SPN found :HOST/XXXDARS2.XXX.com/XXX.com
* SPN found :HOST/XXXDARS2.XXX.com
* SPN found :HOST/XXXDARS2
* SPN found :HOST/XXXDARS2.XXX.com/XXX
* SPN found :GC/XXXDARS2.XXX.com/XXX.com
......................... XXXDARS2 passed test MachineAccount
Starting test: NCSecDesc
* Security Permissions check for all NC's on DC XXXDARS2.
* Security Permissions Check for
DC=DomainDnsZones,DC=XXX,DC=com
(NDNC,Version 3)
* Security Permissions Check for
DC=ForestDnsZones,DC=XXX,DC=com
(NDNC,Version 3)
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=XXX,DC=com
(Schema,Version 3)
* Security Permissions Check for
CN=Configuration,DC=XXX,DC=com
(Configuration,Version 3)
* Security Permissions Check for
DC=XXX,DC=com
(Domain,Version 3)
......................... XXXDARS2 passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
Verified share \\XXXDARS2\netlogon
Verified share \\XXXDARS2\sysvol
......................... XXXDARS2 passed test NetLogons
Starting test: ObjectsReplicated
XXXDARS2 is in domain DC=XXX,DC=com
Checking for CN=XXXDARS2,OU=Domain Controllers,DC=XXX,DC=com in domain DC=XXX,DC=com on 1 servers
Object is up-to-date on all servers.
Checking for CN=NTDS Settings,CN=XXXDARS2,CN=Servers,CN=Site5,CN=Sites,CN=Configuration,DC=XXX,DC=com in domain CN=Configuration,DC=XXX,DC=com on 1 servers
Object is up-to-date on all servers.
......................... XXXDARS2 passed test ObjectsReplicated
Test omitted by user request: OutboundSecureChannels
Starting test: Replications
* Replications Check
* Replication Latency Check
DC=DomainDnsZones,DC=XXX,DC=com
Latency information for 11 entries in the vector were ignored.
11 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
DC=ForestDnsZones,DC=XXX,DC=com
Latency information for 11 entries in the vector were ignored.
11 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
CN=Schema,CN=Configuration,DC=XXX,DC=com
Latency information for 11 entries in the vector were ignored.
11 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
CN=Configuration,DC=XXX,DC=com
Latency information for 11 entries in the vector were ignored.
11 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
DC=XXX,DC=com
Latency information for 11 entries in the vector were ignored.
11 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
......................... XXXDARS2 passed test Replications
Starting test: RidManager
* Available RID Pool for the Domain is 33418 to 1073741823
* XXXDARS2.XXX.com is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 32418 to 32917
* rIDPreviousAllocationPool is 32418 to 32917
* rIDNextRID: 32543
......................... XXXDARS2 passed test RidManager
Starting test: Services
* Checking Service: EventSystem
* Checking Service: RpcSs
* Checking Service: NTDS
* Checking Service: DnsCache
* Checking Service: DFSR
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: w32time
* Checking Service: NETLOGON
......................... XXXDARS2 passed test Services
Starting test: SystemLog
* The System Event log test
A warning event occurred. EventID: 0x00000427
Time Generated: 10/10/2018 13:04:13
Event String:
Scope, 192.168.102.0, is 88 percent full with only 8 IP addresses remaining.
A warning event occurred. EventID: 0x000003FC
Time Generated: 10/10/2018 13:13:06
Event String:
Scope, 192.168.175.0, is 100 percent full with only 0 IP addresses remaining.
A warning event occurred. EventID: 0x000003FC
Time Generated: 10/10/2018 13:13:06
Event String:
Scope, 192.168.102.0, is 88 percent full with only 8 IP addresses remaining.
A warning event occurred. EventID: 0x000003FC
Time Generated: 10/10/2018 13:13:06
Event String:
Scope, 192.168.175.0, is 100 percent full with only 0 IP addresses remaining.
A warning event occurred. EventID: 0x000003FC
Time Generated: 10/10/2018 13:13:18
Event String:
Scope, 192.168.102.0, is 88 percent full with only 8 IP addresses remaining.
A warning event occurred. EventID: 0x000003FC
Time Generated: 10/10/2018 13:13:18
Event String:
Scope, 192.168.175.0, is 100 percent full with only 0 IP addresses remaining.
An error event occurred. EventID: 0x00009018
Time Generated: 10/10/2018 13:37:43
Event String:
The following fatal alert was generated: 20. The internal error state is 960.
......................... XXXDARS2 failed test SystemLog
Test omitted by user request: Topology
Test omitted by user request: VerifyEnterpriseReferences
Starting test: VerifyReferences
The system object reference (serverReference)
CN=XXXDARS2,OU=Domain Controllers,DC=XXX,DC=com and backlink on
CN=XXXDARS2,CN=Servers,CN=Site5,CN=Sites,CN=Configuration,DC=XXX,DC=com
are correct.
The system object reference (serverReferenceBL)
CN=XXXDARS2,CN=Topology,CN=Domain System Volume,CN=DFSR-GlobalSettings,CN=System,DC=XXX,DC=com
and backlink on
CN=NTDS Settings,CN=XXXDARS2,CN=Servers,CN=Site5,CN=Sites,CN=Configuration,DC=XXX,DC=com
are correct.
The system object reference (msDFSR-ComputerReferenceBL)
CN=XXXDARS2,CN=Topology,CN=Domain System Volume,CN=DFSR-GlobalSettings,CN=System,DC=XXX,DC=com
and backlink on CN=XXXDARS2,OU=Domain Controllers,DC=XXX,DC=com are
correct.
......................... XXXDARS2 passed test VerifyReferences
Test omitted by user request: VerifyReplicas
Test omitted by user request: DNS
Test omitted by user request: DNS
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones 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 : XXX
Starting test: CheckSDRefDom
......................... XXX passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... XXX passed test CrossRefValidation
Running enterprise tests on : XXX.com
Test omitted by user request: DNS
Test omitted by user request: DNS
Starting test: LocatorCheck
GC Name: \\XXXDARS2.XXX.com
Locator Flags: 0xe00033fd
PDC Name: \\XXXDARS2.XXX.com
Locator Flags: 0xe00033fd
Time Server Name: \\XXXDARS2.XXX.com
Locator Flags: 0xe00033fd
Preferred Time Server Name: \\XXXDARS2.XXX.com
Locator Flags: 0xe00033fd
KDC Name: \\XXXDARS2.XXX.com
Locator Flags: 0xe00033fd
......................... XXX.com passed test LocatorCheck
Starting test: Intersite
Skipping site Site1, this site is outside the scope provided by
the command line arguments provided.
Skipping site Site2, this site is outside the scope provided
by the command line arguments provided.
Skipping site Site3, this site is outside the scope provided by
the command line arguments provided.
Skipping site Site4, this site is outside the scope
provided by the command line arguments provided.
Skipping site Site5, this site is outside the scope
provided by the command line arguments provided.
Skipping site Site6, this site is outside the scope provided by the
command line arguments provided.
Skipping site Site7, this site is outside the scope
provided by the command line arguments provided.
......................... XXX.com passed test Intersite
in the results posted,
File Replication Service SYSVOL ready test
File Replication Service's SYSVOL is ready
......................... XXXDARS2 passed test SysVolCheck
can you chek if still ntfrs (file replication service) is running on PDC?
File Replication Service SYSVOL ready test
File Replication Service's SYSVOL is ready
......................... XXXDARS2 passed test SysVolCheck
can you chek if still ntfrs (file replication service) is running on PDC?
ASKER
No, it isn't, neither on PDC. nor on the new Server:
C:\Windows\system32>sc query ntfrs
SERVICE_NAME: ntfrs
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
I meanwhile promoted the new DC and...guess what...it is now part of the list provided by dfsrmig /getMigrationState! So, at least for my Domain it seems to be a systematic issue.
C:\Windows\system32>sc query ntfrs
SERVICE_NAME: ntfrs
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
I meanwhile promoted the new DC and...guess what...it is now part of the list provided by dfsrmig /getMigrationState! So, at least for my Domain it seems to be a systematic issue.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
If not check on each DC what is global state in registry
once problem is resolved, promote new 2016 DC