Directory Server Diagnosis Performing initial setup: * Connecting to directory service on server dri-ad.dri.local. * Identified AD Forest. Collecting AD specific global data * Collecting site info. Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=dri,DC=local,LDAP_SCOPE_SUBTREE,(objectCategory=ntDSSiteSettings),....... The previous call succeeded Iterating through the sites Looking at base site object: CN=NTDS Site Settings,CN=LOLA,CN=Sites,CN=Configuration,DC=dri,DC=local Getting ISTG and options for the site * Identifying all servers. Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=dri,DC=local,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=DRI-AD,CN=Servers,CN=LOLA,CN=Sites,CN=Configuration,DC=dri,DC=local 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=DRI-AD-SEC,CN=Servers,CN=LOLA,CN=Sites,CN=Configuration,DC=dri,DC=local 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=DRI-DCRO,CN=Servers,CN=LOLA,CN=Sites,CN=Configuration,DC=dri,DC=local objectGuid obtained InvocationID obtained dnsHostname obtained site info obtained All the info for the server collected * Identifying all NC cross-refs. * Found 3 DC(s). Testing 3 of them. Done gathering initial info. Doing initial required tests Testing server: LOLA\DRI-AD Starting test: Connectivity * Active Directory LDAP Services Check Determining IP4 connectivity * Active Directory RPC Services Check ......................... DRI-AD passed test Connectivity Testing server: LOLA\DRI-AD-SEC Starting test: Connectivity * Active Directory LDAP Services Check Determining IP4 connectivity * Active Directory RPC Services Check ......................... DRI-AD-SEC passed test Connectivity Testing server: LOLA\DRI-DCRO Starting test: Connectivity * Active Directory LDAP Services Check Determining IP4 connectivity * Active Directory RPC Services Check ......................... DRI-DCRO passed test Connectivity Doing primary tests Testing server: LOLA\DRI-AD Starting test: Advertising The DC DRI-AD is advertising itself as a DC and having a DS. The DC DRI-AD is advertising as an LDAP server The DC DRI-AD is advertising as having a writeable directory The DC DRI-AD is advertising as a Key Distribution Center The DC DRI-AD is advertising as a time server The DS DRI-AD is advertising as a GC. ......................... DRI-AD passed test Advertising Starting test: CheckSecurityError * Dr Auth: Beginning security errors check! Found KDC DRI-AD-SEC for domain dri.local in site LOLA Checking machine account for DC DRI-AD on DC DRI-AD-SEC. * SPN found :LDAP/dri-AD.dri.local/dri.local * SPN found :LDAP/dri-AD.dri.local * SPN found :LDAP/DRI-AD * SPN found :LDAP/dri-AD.dri.local/DRI * SPN found :LDAP/c833e342-ab4b-47c7-9a42-ed5fe6a924dd._msdcs.dri.local * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/c833e342-ab4b-47c7-9a42-ed5fe6a924dd/dri.local * SPN found :HOST/dri-AD.dri.local/dri.local * SPN found :HOST/dri-AD.dri.local * SPN found :HOST/DRI-AD * SPN found :HOST/dri-AD.dri.local/DRI * SPN found :GC/dri-AD.dri.local/dri.local Checking for CN=DRI-AD,OU=Domain Controllers,DC=dri,DC=local in domain DC=dri,DC=local on 2 servers Object is up-to-date on all servers. [DRI-AD] No security related replication errors were found on this DC! To target the connection to a specific source DC use /ReplSource:. ......................... DRI-AD passed test CheckSecurityError Starting test: CutoffServers * Configuration Topology Aliveness Check * Analyzing the alive system replication topology for DC=ForestDnsZones,DC=dri,DC=local. * Performing upstream (of target) analysis. * Performing downstream (of target) analysis. * Analyzing the alive system replication topology for DC=DomainDnsZones,DC=dri,DC=local. * Performing upstream (of target) analysis. * Performing downstream (of target) analysis. * Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=dri,DC=local. * Performing upstream (of target) analysis. * Performing downstream (of target) analysis. * Analyzing the alive system replication topology for CN=Configuration,DC=dri,DC=local. * Performing upstream (of target) analysis. * Performing downstream (of target) analysis. * Analyzing the alive system replication topology for DC=dri,DC=local. * Performing upstream (of target) analysis. * Performing downstream (of target) analysis. ......................... DRI-AD passed test CutoffServers Starting test: FrsEvent * The File Replication Service Event log test Skip the test because the server is running DFSR. ......................... DRI-AD 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: 04/03/2022 16:24:50 Event String: The DFS Replication service is stopping communication with partner DRI-AD-SEC for replication group Domain System Volume due to an error. The service will retry the connection periodically. Additional Information: Error: 9033 (The request was cancelled by a shutdown) Connection ID: A1A5907A-0BBF-42AE-994A-34E90B94ABFD Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A An error event occurred. EventID: 0xC000138A Time Generated: 04/03/2022 16:25:04 Event String: The DFS Replication service encountered an error communicating with partner DRI-AD-SEC for replication group Domain System Volume. Partner DNS address: DRI-AD-SEC.dri.local Optional data if available: Partner WINS Address: DRI-AD-SEC Partner IP Address: 192.168.99.55 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: A1A5907A-0BBF-42AE-994A-34E90B94ABFD Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A A warning event occurred. EventID: 0x80001396 Time Generated: 04/03/2022 16:42:10 Event String: The DFS Replication service is stopping communication with partner DRI-DCRO for replication group Domain System Volume due to an error. The service will retry the connection periodically. Additional Information: Error: 9033 (The request was cancelled by a shutdown) Connection ID: E6B3B98F-10E0-4B0E-9F41-2D382B874848 Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A A warning event occurred. EventID: 0x80001396 Time Generated: 04/03/2022 16:42:21 Event String: The DFS Replication service is stopping communication with partner DRI-AD-SEC for replication group Domain System Volume due to an error. The service will retry the connection periodically. Additional Information: Error: 9033 (The request was cancelled by a shutdown) Connection ID: A1A5907A-0BBF-42AE-994A-34E90B94ABFD Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A A warning event occurred. EventID: 0x80001396 Time Generated: 04/03/2022 17:11:49 Event String: The DFS Replication service is stopping communication with partner DRI-AD-SEC for replication group Domain System Volume due to an error. The service will retry the connection periodically. Additional Information: Error: 9033 (The request was cancelled by a shutdown) Connection ID: A1A5907A-0BBF-42AE-994A-34E90B94ABFD Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A A warning event occurred. EventID: 0x80001396 Time Generated: 04/03/2022 17:19:57 Event String: The DFS Replication service is stopping communication with partner DRI-AD-SEC for replication group Domain System Volume due to an error. The service will retry the connection periodically. Additional Information: Error: 1723 (The RPC server is too busy to complete this operation.) Connection ID: A1A5907A-0BBF-42AE-994A-34E90B94ABFD Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A An error event occurred. EventID: 0xC0001390 Time Generated: 04/03/2022 17:20:41 Event String: The DFS Replication service failed to communicate with partner DRI-AD-SEC for replication group Domain System Volume. This error can occur if the host is unreachable, or if the DFS Replication service is not running on the server. Partner DNS Address: DRI-AD-SEC.dri.local Optional data if available: Partner WINS Address: DRI-AD-SEC Partner IP Address: 192.168.99.55 The service will retry the connection periodically. Additional Information: Error: 1722 (The RPC server is unavailable.) Connection ID: A1A5907A-0BBF-42AE-994A-34E90B94ABFD Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A A warning event occurred. EventID: 0x80001396 Time Generated: 04/03/2022 18:20:06 Event String: The DFS Replication service is stopping communication with partner DRI-AD-SEC for replication group Domain System Volume due to an error. The service will retry the connection periodically. Additional Information: Error: 1723 (The RPC server is too busy to complete this operation.) Connection ID: A1A5907A-0BBF-42AE-994A-34E90B94ABFD Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A A warning event occurred. EventID: 0x80001396 Time Generated: 04/03/2022 18:25:35 Event String: The DFS Replication service is stopping communication with partner DRI-DCRO for replication group Domain System Volume due to an error. The service will retry the connection periodically. Additional Information: Error: 9033 (The request was cancelled by a shutdown) Connection ID: E6B3B98F-10E0-4B0E-9F41-2D382B874848 Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A A warning event occurred. EventID: 0x80001396 Time Generated: 04/03/2022 20:13:57 Event String: The DFS Replication service is stopping communication with partner DRI-AD-SEC for replication group Domain System Volume due to an error. The service will retry the connection periodically. Additional Information: Error: 1723 (The RPC server is too busy to complete this operation.) Connection ID: A1A5907A-0BBF-42AE-994A-34E90B94ABFD Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A ......................... DRI-AD failed test DFSREvent Starting test: SysVolCheck * The File Replication Service SYSVOL ready test File Replication Service's SYSVOL is ready ......................... DRI-AD passed test SysVolCheck Starting test: FrsSysVol * The File Replication Service SYSVOL ready test File Replication Service's SYSVOL is ready ......................... DRI-AD passed test FrsSysVol Starting test: KccEvent * The KCC Event log test Found no KCC errors in "Directory Service" Event log in the last 15 minutes. ......................... DRI-AD passed test KccEvent Starting test: KnowsOfRoleHolders Role Schema Owner = CN=NTDS Settings,CN=DRI-AD,CN=Servers,CN=LOLA,CN=Sites,CN=Configuration,DC=dri,DC=local Role Domain Owner = CN=NTDS Settings,CN=DRI-AD,CN=Servers,CN=LOLA,CN=Sites,CN=Configuration,DC=dri,DC=local Role PDC Owner = CN=NTDS Settings,CN=DRI-AD,CN=Servers,CN=LOLA,CN=Sites,CN=Configuration,DC=dri,DC=local Role Rid Owner = CN=NTDS Settings,CN=DRI-AD,CN=Servers,CN=LOLA,CN=Sites,CN=Configuration,DC=dri,DC=local Role Infrastructure Update Owner = CN=NTDS Settings,CN=DRI-AD,CN=Servers,CN=LOLA,CN=Sites,CN=Configuration,DC=dri,DC=local ......................... DRI-AD passed test KnowsOfRoleHolders Starting test: MachineAccount Checking machine account for DC DRI-AD on DC DRI-AD. * SPN found :LDAP/dri-AD.dri.local/dri.local * SPN found :LDAP/dri-AD.dri.local * SPN found :LDAP/DRI-AD * SPN found :LDAP/dri-AD.dri.local/DRI * SPN found :LDAP/c833e342-ab4b-47c7-9a42-ed5fe6a924dd._msdcs.dri.local * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/c833e342-ab4b-47c7-9a42-ed5fe6a924dd/dri.local * SPN found :HOST/dri-AD.dri.local/dri.local * SPN found :HOST/dri-AD.dri.local * SPN found :HOST/DRI-AD * SPN found :HOST/dri-AD.dri.local/DRI * SPN found :GC/dri-AD.dri.local/dri.local ......................... DRI-AD passed test MachineAccount Starting test: NCSecDesc * Security Permissions check for all NC's on DC DRI-AD. * Security Permissions Check for DC=ForestDnsZones,DC=dri,DC=local (NDNC,Version 3) * Security Permissions Check for DC=DomainDnsZones,DC=dri,DC=local (NDNC,Version 3) * Security Permissions Check for CN=Schema,CN=Configuration,DC=dri,DC=local (Schema,Version 3) * Security Permissions Check for CN=Configuration,DC=dri,DC=local (Configuration,Version 3) * Security Permissions Check for DC=dri,DC=local (Domain,Version 3) ......................... DRI-AD passed test NCSecDesc Starting test: NetLogons * Network Logons Privileges Check Verified share \\DRI-AD\netlogon Verified share \\DRI-AD\sysvol ......................... DRI-AD passed test NetLogons Starting test: ObjectsReplicated DRI-AD is in domain DC=dri,DC=local Checking for CN=DRI-AD,OU=Domain Controllers,DC=dri,DC=local in domain DC=dri,DC=local on 3 servers Object is up-to-date on all servers. Checking for CN=NTDS Settings,CN=DRI-AD,CN=Servers,CN=LOLA,CN=Sites,CN=Configuration,DC=dri,DC=local in domain CN=Configuration,DC=dri,DC=local on 3 servers Object is up-to-date on all servers. ......................... DRI-AD passed test ObjectsReplicated Starting test: OutboundSecureChannels * The Outbound Secure Channels test ** Did not run Outbound Secure Channels test because /testdomain: was not entered ......................... DRI-AD passed test OutboundSecureChannels Starting test: Replications * Replications Check * Replication Latency Check DC=ForestDnsZones,DC=dri,DC=local Latency information for 4 entries in the vector were ignored. 4 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=DomainDnsZones,DC=dri,DC=local Latency information for 2 entries in the vector were ignored. 2 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=dri,DC=local Latency information for 4 entries in the vector were ignored. 4 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=dri,DC=local Latency information for 4 entries in the vector were ignored. 4 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=dri,DC=local Latency information for 2 entries in the vector were ignored. 2 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). ......................... DRI-AD passed test Replications Starting test: RidManager * Available RID Pool for the Domain is 5112 to 1073741823 * dri-AD.dri.local is the RID Master * DsBind with RID Master was successful * rIDAllocationPool is 4612 to 5111 * rIDPreviousAllocationPool is 4612 to 5111 * rIDNextRID: 4695 ......................... DRI-AD 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 ......................... DRI-AD passed test Services Starting test: SystemLog * The System Event log test Found no errors in "System" Event log in the last 60 minutes. ......................... DRI-AD passed test SystemLog Starting test: Topology * Configuration Topology Integrity Check * Analyzing the connection topology for DC=ForestDnsZones,DC=dri,DC=local. * Performing upstream (of target) analysis. * Performing downstream (of target) analysis. * Analyzing the connection topology for DC=DomainDnsZones,DC=dri,DC=local. * Performing upstream (of target) analysis. * Performing downstream (of target) analysis. * Analyzing the connection topology for CN=Schema,CN=Configuration,DC=dri,DC=local. * Performing upstream (of target) analysis. * Performing downstream (of target) analysis. * Analyzing the connection topology for CN=Configuration,DC=dri,DC=local. * Performing upstream (of target) analysis. * Performing downstream (of target) analysis. * Analyzing the connection topology for DC=dri,DC=local. * Performing upstream (of target) analysis. * Performing downstream (of target) analysis. ......................... DRI-AD passed test Topology Starting test: VerifyEnterpriseReferences ......................... DRI-AD passed test VerifyEnterpriseReferences Starting test: VerifyReferences The system object reference (serverReference) CN=DRI-AD,OU=Domain Controllers,DC=dri,DC=local and backlink on CN=DRI-AD,CN=Servers,CN=LOLA,CN=Sites,CN=Configuration,DC=dri,DC=local are correct. The system object reference (serverReferenceBL) CN=DRI-AD,CN=Topology,CN=Domain System Volume,CN=DFSR-GlobalSettings,CN=System,DC=dri,DC=local and backlink on CN=NTDS Settings,CN=DRI-AD,CN=Servers,CN=LOLA,CN=Sites,CN=Configuration,DC=dri,DC=local are correct. The system object reference (msDFSR-ComputerReferenceBL) CN=DRI-AD,CN=Topology,CN=Domain System Volume,CN=DFSR-GlobalSettings,CN=System,DC=dri,DC=local and backlink on CN=DRI-AD,OU=Domain Controllers,DC=dri,DC=local are correct. ......................... DRI-AD passed test VerifyReferences Starting test: VerifyReplicas ......................... DRI-AD passed test VerifyReplicas Testing server: LOLA\DRI-AD-SEC Starting test: Advertising The DC DRI-AD-SEC is advertising itself as a DC and having a DS. The DC DRI-AD-SEC is advertising as an LDAP server The DC DRI-AD-SEC is advertising as having a writeable directory The DC DRI-AD-SEC is advertising as a Key Distribution Center The DC DRI-AD-SEC is advertising as a time server The DS DRI-AD-SEC is advertising as a GC. ......................... DRI-AD-SEC passed test Advertising Starting test: CheckSecurityError * Dr Auth: Beginning security errors check! Found KDC DRI-AD-SEC for domain dri.local in site LOLA Checking machine account for DC DRI-AD-SEC on DC DRI-AD-SEC. * SPN found :LDAP/DRI-AD-SEC.dri.local/dri.local * SPN found :LDAP/DRI-AD-SEC.dri.local * SPN found :LDAP/DRI-AD-SEC * SPN found :LDAP/DRI-AD-SEC.dri.local/DRI * SPN found :LDAP/d183b5ab-921e-4861-86f5-1ede5a632382._msdcs.dri.local * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/d183b5ab-921e-4861-86f5-1ede5a632382/dri.local * SPN found :HOST/DRI-AD-SEC.dri.local/dri.local * SPN found :HOST/DRI-AD-SEC.dri.local * SPN found :HOST/DRI-AD-SEC * SPN found :HOST/DRI-AD-SEC.dri.local/DRI * SPN found :GC/DRI-AD-SEC.dri.local/dri.local [DRI-AD-SEC] No security related replication errors were found on this DC! To target the connection to a specific source DC use /ReplSource:. ......................... DRI-AD-SEC passed test CheckSecurityError Starting test: CutoffServers * Configuration Topology Aliveness Check * Analyzing the alive system replication topology for DC=ForestDnsZones,DC=dri,DC=local. * Performing upstream (of target) analysis. * Performing downstream (of target) analysis. * Analyzing the alive system replication topology for DC=DomainDnsZones,DC=dri,DC=local. * Performing upstream (of target) analysis. * Performing downstream (of target) analysis. * Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=dri,DC=local. * Performing upstream (of target) analysis. * Performing downstream (of target) analysis. * Analyzing the alive system replication topology for CN=Configuration,DC=dri,DC=local. * Performing upstream (of target) analysis. * Performing downstream (of target) analysis. * Analyzing the alive system replication topology for DC=dri,DC=local. * Performing upstream (of target) analysis. * Performing downstream (of target) analysis. ......................... DRI-AD-SEC passed test CutoffServers Starting test: FrsEvent * The File Replication Service Event log test Skip the test because the server is running DFSR. ......................... DRI-AD-SEC 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: 0x800008A5 Time Generated: 04/03/2022 16:39:35 Event String: The DFS Replication service stopped replication on volume C:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled. To resolve this issue, back up the files in the affected replicated folders, and then use the ResumeReplication WMI method to resume replication. Additional Information: Volume: C: GUID: 282E804F-2FEB-11EA-93E7-806E6F6E6963 Recovery Steps 1. Back up the files in all replicated folders on the volume. Failure to do so may result in data loss due to unexpected conflict resolution during the recovery of the replicated folders. 2. To resume the replication for this volume, use the WMI method ResumeReplication of the DfsrVolumeConfig class. For example, from an elevated command prompt, type the following command: wmic /namespace:\\root\microsoftdfs path dfsrVolumeConfig where volumeGuid="282E804F-2FEB-11EA-93E7-806E6F6E6963" call ResumeReplication For more information, see http://support.microsoft.com/kb/2663685. A warning event occurred. EventID: 0x800008A5 Time Generated: 04/03/2022 16:42:26 Event String: The DFS Replication service stopped replication on volume C:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled. To resolve this issue, back up the files in the affected replicated folders, and then use the ResumeReplication WMI method to resume replication. Additional Information: Volume: C: GUID: 282E804F-2FEB-11EA-93E7-806E6F6E6963 Recovery Steps 1. Back up the files in all replicated folders on the volume. Failure to do so may result in data loss due to unexpected conflict resolution during the recovery of the replicated folders. 2. To resume the replication for this volume, use the WMI method ResumeReplication of the DfsrVolumeConfig class. For example, from an elevated command prompt, type the following command: wmic /namespace:\\root\microsoftdfs path dfsrVolumeConfig where volumeGuid="282E804F-2FEB-11EA-93E7-806E6F6E6963" call ResumeReplication For more information, see http://support.microsoft.com/kb/2663685. A warning event occurred. EventID: 0x800008A4 Time Generated: 04/03/2022 16:51:42 Event String: The DFS Replication service has detected an unexpected shutdown on volume C:. This can occur if the service terminated abnormally (due to a power loss, for example) or an error occurred on the volume. The service has automatically initiated a recovery process. The service will rebuild the database if it determines it cannot reliably recover. No user action is required. Additional Information: Volume: C: GUID: 282E804F-2FEB-11EA-93E7-806E6F6E6963 An error event occurred. EventID: 0xC0000FAC Time Generated: 04/03/2022 16:52:03 Event String: The DFS Replication service stopped replication on the folder with the following local path: C:\Windows\SYSVOL\domain. This server has been disconnected from other partners for 451 days, which is longer than the time allowed by the MaxOfflineTimeInDays parameter (60). DFS Replication considers the data in this folder to be stale, and this server will not replicate the folder until this error is corrected. To resume replication of this folder, use the DFS Management snap-in to remove this server from the replication group, and then add it back to the group. This causes the server to perform an initial synchronization task, which replaces the stale data with fresh data from other members of the replication group. Additional Information: Error: 9061 (The replicated folder has been offline for too long.) Replicated Folder Name: SYSVOL Share Replicated Folder ID: D2A35C60-7F0C-477E-9F20-33235B01ADFE Replication Group Name: Domain System Volume Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A Member ID: 301A6CCD-F748-49DB-BFAA-E2BC09ACB15F An error event occurred. EventID: 0xC0000FAC Time Generated: 04/03/2022 16:59:03 Event String: The DFS Replication service stopped replication on the folder with the following local path: C:\Windows\SYSVOL\domain. This server has been disconnected from other partners for 451 days, which is longer than the time allowed by the MaxOfflineTimeInDays parameter (60). DFS Replication considers the data in this folder to be stale, and this server will not replicate the folder until this error is corrected. To resume replication of this folder, use the DFS Management snap-in to remove this server from the replication group, and then add it back to the group. This causes the server to perform an initial synchronization task, which replaces the stale data with fresh data from other members of the replication group. Additional Information: Error: 9061 (The replicated folder has been offline for too long.) Replicated Folder Name: SYSVOL Share Replicated Folder ID: D2A35C60-7F0C-477E-9F20-33235B01ADFE Replication Group Name: Domain System Volume Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A Member ID: 301A6CCD-F748-49DB-BFAA-E2BC09ACB15F An error event occurred. EventID: 0xC000138A Time Generated: 04/03/2022 17:12:10 Event String: The DFS Replication service encountered an error communicating with partner DRI-AD for replication group Domain System Volume. Partner DNS address: dri-AD.dri.local Optional data if available: Partner WINS Address: dri-AD Partner IP Address: 192.168.99.20 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: 3CBF9844-9629-4B9F-8237-4AC03D83C7BA Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A An error event occurred. EventID: 0xC000138A Time Generated: 04/03/2022 17:21:42 Event String: The DFS Replication service encountered an error communicating with partner DRI-AD for replication group Domain System Volume. Partner DNS address: dri-AD.dri.local Optional data if available: Partner WINS Address: dri-AD Partner IP Address: 192.168.99.20 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: 3CBF9844-9629-4B9F-8237-4AC03D83C7BA Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A An error event occurred. EventID: 0xC000138A Time Generated: 04/03/2022 17:30:01 Event String: The DFS Replication service encountered an error communicating with partner DRI-AD for replication group Domain System Volume. Partner DNS address: dri-AD.dri.local Optional data if available: Partner WINS Address: dri-AD Partner IP Address: 192.168.99.20 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: 3CBF9844-9629-4B9F-8237-4AC03D83C7BA Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A An error event occurred. EventID: 0xC000138A Time Generated: 04/03/2022 17:45:01 Event String: The DFS Replication service encountered an error communicating with partner DRI-AD for replication group Domain System Volume. Partner DNS address: dri-AD.dri.local Optional data if available: Partner WINS Address: dri-AD Partner IP Address: 192.168.99.20 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: 3CBF9844-9629-4B9F-8237-4AC03D83C7BA Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A An error event occurred. EventID: 0xC000138A Time Generated: 04/03/2022 18:20:18 Event String: The DFS Replication service encountered an error communicating with partner DRI-AD for replication group Domain System Volume. Partner DNS address: dri-AD.dri.local Optional data if available: Partner WINS Address: dri-AD Partner IP Address: 192.168.99.20 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: 3CBF9844-9629-4B9F-8237-4AC03D83C7BA Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A A warning event occurred. EventID: 0x80001396 Time Generated: 04/03/2022 18:25:35 Event String: The DFS Replication service is stopping communication with partner DRI-DCRO for replication group Domain System Volume due to an error. The service will retry the connection periodically. Additional Information: Error: 9033 (The request was cancelled by a shutdown) Connection ID: 4BEC02D3-2FD0-46D2-AD78-C51CD08B1129 Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A An error event occurred. EventID: 0xC000138A Time Generated: 04/03/2022 18:28:42 Event String: The DFS Replication service encountered an error communicating with partner DRI-AD for replication group Domain System Volume. Partner DNS address: dri-AD.dri.local Optional data if available: Partner WINS Address: dri-AD Partner IP Address: 192.168.99.20 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: 3CBF9844-9629-4B9F-8237-4AC03D83C7BA Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A An error event occurred. EventID: 0xC000138A Time Generated: 04/03/2022 18:43:42 Event String: The DFS Replication service encountered an error communicating with partner DRI-AD for replication group Domain System Volume. Partner DNS address: dri-AD.dri.local Optional data if available: Partner WINS Address: dri-AD Partner IP Address: 192.168.99.20 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: 3CBF9844-9629-4B9F-8237-4AC03D83C7BA Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A An error event occurred. EventID: 0xC000138A Time Generated: 04/03/2022 19:43:42 Event String: The DFS Replication service encountered an error communicating with partner DRI-AD for replication group Domain System Volume. Partner DNS address: dri-AD.dri.local Optional data if available: Partner WINS Address: dri-AD Partner IP Address: 192.168.99.20 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: 3CBF9844-9629-4B9F-8237-4AC03D83C7BA Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A An error event occurred. EventID: 0xC000138A Time Generated: 04/03/2022 20:14:11 Event String: The DFS Replication service encountered an error communicating with partner DRI-AD for replication group Domain System Volume. Partner DNS address: dri-AD.dri.local Optional data if available: Partner WINS Address: dri-AD Partner IP Address: 192.168.99.20 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: 3CBF9844-9629-4B9F-8237-4AC03D83C7BA Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A An error event occurred. EventID: 0xC000138A Time Generated: 04/03/2022 20:22:34 Event String: The DFS Replication service encountered an error communicating with partner DRI-AD for replication group Domain System Volume. Partner DNS address: dri-AD.dri.local Optional data if available: Partner WINS Address: dri-AD Partner IP Address: 192.168.99.20 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: 3CBF9844-9629-4B9F-8237-4AC03D83C7BA Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A An error event occurred. EventID: 0xC000138A Time Generated: 04/03/2022 20:37:34 Event String: The DFS Replication service encountered an error communicating with partner DRI-AD for replication group Domain System Volume. Partner DNS address: dri-AD.dri.local Optional data if available: Partner WINS Address: dri-AD Partner IP Address: 192.168.99.20 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: 3CBF9844-9629-4B9F-8237-4AC03D83C7BA Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A An error event occurred. EventID: 0xC000138A Time Generated: 04/03/2022 21:37:34 Event String: The DFS Replication service encountered an error communicating with partner DRI-AD for replication group Domain System Volume. Partner DNS address: dri-AD.dri.local Optional data if available: Partner WINS Address: dri-AD Partner IP Address: 192.168.99.20 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: 3CBF9844-9629-4B9F-8237-4AC03D83C7BA Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A An error event occurred. EventID: 0xC000138A Time Generated: 04/04/2022 01:37:35 Event String: The DFS Replication service encountered an error communicating with partner DRI-AD for replication group Domain System Volume. Partner DNS address: dri-AD.dri.local Optional data if available: Partner WINS Address: dri-AD Partner IP Address: 192.168.99.20 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: 3CBF9844-9629-4B9F-8237-4AC03D83C7BA Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A An error event occurred. EventID: 0xC000138A Time Generated: 04/04/2022 09:01:10 Event String: The DFS Replication service encountered an error communicating with partner DRI-AD for replication group Domain System Volume. Partner DNS address: dri-AD.dri.local Optional data if available: Partner WINS Address: dri-AD Partner IP Address: 192.168.99.20 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: 3CBF9844-9629-4B9F-8237-4AC03D83C7BA Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A An error event occurred. EventID: 0xC000138A Time Generated: 04/04/2022 09:01:10 Event String: The DFS Replication service encountered an error communicating with partner DRI-DCRO for replication group Domain System Volume. Partner DNS address: DRI-DCRO.dri.local Optional data if available: Partner WINS Address: DRI-DCRO Partner IP Address: 192.168.99.24 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: 4BEC02D3-2FD0-46D2-AD78-C51CD08B1129 Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A An error event occurred. EventID: 0xC000138A Time Generated: 04/04/2022 09:08:12 Event String: The DFS Replication service encountered an error communicating with partner DRI-AD for replication group Domain System Volume. Partner DNS address: dri-AD.dri.local Optional data if available: Partner WINS Address: dri-AD Partner IP Address: 192.168.99.20 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: 3CBF9844-9629-4B9F-8237-4AC03D83C7BA Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A An error event occurred. EventID: 0xC000138A Time Generated: 04/04/2022 09:23:12 Event String: The DFS Replication service encountered an error communicating with partner DRI-AD for replication group Domain System Volume. Partner DNS address: dri-AD.dri.local Optional data if available: Partner WINS Address: dri-AD Partner IP Address: 192.168.99.20 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: 3CBF9844-9629-4B9F-8237-4AC03D83C7BA Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A An error event occurred. EventID: 0xC000138A Time Generated: 04/04/2022 10:26:06 Event String: The DFS Replication service encountered an error communicating with partner DRI-AD for replication group Domain System Volume. Partner DNS address: dri-AD.dri.local Optional data if available: Partner WINS Address: dri-AD Partner IP Address: 192.168.99.20 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: 3CBF9844-9629-4B9F-8237-4AC03D83C7BA Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A An error event occurred. EventID: 0xC000138A Time Generated: 04/04/2022 14:26:07 Event String: The DFS Replication service encountered an error communicating with partner DRI-AD for replication group Domain System Volume. Partner DNS address: dri-AD.dri.local Optional data if available: Partner WINS Address: dri-AD Partner IP Address: 192.168.99.20 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: 3CBF9844-9629-4B9F-8237-4AC03D83C7BA Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A ......................... DRI-AD-SEC failed test DFSREvent Starting test: SysVolCheck * The File Replication Service SYSVOL ready test File Replication Service's SYSVOL is ready ......................... DRI-AD-SEC passed test SysVolCheck Starting test: FrsSysVol * The File Replication Service SYSVOL ready test File Replication Service's SYSVOL is ready ......................... DRI-AD-SEC passed test FrsSysVol Starting test: KccEvent * The KCC Event log test Found no KCC errors in "Directory Service" Event log in the last 15 minutes. ......................... DRI-AD-SEC passed test KccEvent Starting test: KnowsOfRoleHolders Role Schema Owner = CN=NTDS Settings,CN=DRI-AD,CN=Servers,CN=LOLA,CN=Sites,CN=Configuration,DC=dri,DC=local Role Domain Owner = CN=NTDS Settings,CN=DRI-AD,CN=Servers,CN=LOLA,CN=Sites,CN=Configuration,DC=dri,DC=local Role PDC Owner = CN=NTDS Settings,CN=DRI-AD,CN=Servers,CN=LOLA,CN=Sites,CN=Configuration,DC=dri,DC=local Role Rid Owner = CN=NTDS Settings,CN=DRI-AD,CN=Servers,CN=LOLA,CN=Sites,CN=Configuration,DC=dri,DC=local Role Infrastructure Update Owner = CN=NTDS Settings,CN=DRI-AD,CN=Servers,CN=LOLA,CN=Sites,CN=Configuration,DC=dri,DC=local ......................... DRI-AD-SEC passed test KnowsOfRoleHolders Starting test: MachineAccount Checking machine account for DC DRI-AD-SEC on DC DRI-AD-SEC. * SPN found :LDAP/DRI-AD-SEC.dri.local/dri.local * SPN found :LDAP/DRI-AD-SEC.dri.local * SPN found :LDAP/DRI-AD-SEC * SPN found :LDAP/DRI-AD-SEC.dri.local/DRI * SPN found :LDAP/d183b5ab-921e-4861-86f5-1ede5a632382._msdcs.dri.local * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/d183b5ab-921e-4861-86f5-1ede5a632382/dri.local * SPN found :HOST/DRI-AD-SEC.dri.local/dri.local * SPN found :HOST/DRI-AD-SEC.dri.local * SPN found :HOST/DRI-AD-SEC * SPN found :HOST/DRI-AD-SEC.dri.local/DRI * SPN found :GC/DRI-AD-SEC.dri.local/dri.local ......................... DRI-AD-SEC passed test MachineAccount Starting test: NCSecDesc * Security Permissions check for all NC's on DC DRI-AD-SEC. * Security Permissions Check for DC=ForestDnsZones,DC=dri,DC=local (NDNC,Version 3) * Security Permissions Check for DC=DomainDnsZones,DC=dri,DC=local (NDNC,Version 3) * Security Permissions Check for CN=Schema,CN=Configuration,DC=dri,DC=local (Schema,Version 3) * Security Permissions Check for CN=Configuration,DC=dri,DC=local (Configuration,Version 3) * Security Permissions Check for DC=dri,DC=local (Domain,Version 3) ......................... DRI-AD-SEC passed test NCSecDesc Starting test: NetLogons * Network Logons Privileges Check Verified share \\DRI-AD-SEC\netlogon Verified share \\DRI-AD-SEC\sysvol ......................... DRI-AD-SEC passed test NetLogons Starting test: ObjectsReplicated DRI-AD-SEC is in domain DC=dri,DC=local Checking for CN=DRI-AD-SEC,OU=Secondary,OU=Domain Controllers,DC=dri,DC=local in domain DC=dri,DC=local on 3 servers Object is up-to-date on all servers. Checking for CN=NTDS Settings,CN=DRI-AD-SEC,CN=Servers,CN=LOLA,CN=Sites,CN=Configuration,DC=dri,DC=local in domain CN=Configuration,DC=dri,DC=local on 3 servers Object is up-to-date on all servers. ......................... DRI-AD-SEC passed test ObjectsReplicated Starting test: OutboundSecureChannels * The Outbound Secure Channels test ** Did not run Outbound Secure Channels test because /testdomain: was not entered ......................... DRI-AD-SEC passed test OutboundSecureChannels Starting test: Replications * Replications Check * Replication Latency Check DC=ForestDnsZones,DC=dri,DC=local Latency information for 4 entries in the vector were ignored. 4 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=DomainDnsZones,DC=dri,DC=local Latency information for 2 entries in the vector were ignored. 2 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=dri,DC=local Latency information for 4 entries in the vector were ignored. 4 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=dri,DC=local Latency information for 4 entries in the vector were ignored. 4 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=dri,DC=local Latency information for 2 entries in the vector were ignored. 2 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). ......................... DRI-AD-SEC passed test Replications Starting test: RidManager * Available RID Pool for the Domain is 5112 to 1073741823 * dri-AD.dri.local is the RID Master * DsBind with RID Master was successful * rIDAllocationPool is 3612 to 4111 * rIDPreviousAllocationPool is 3612 to 4111 * rIDNextRID: 3734 ......................... DRI-AD-SEC 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 ......................... DRI-AD-SEC passed test Services Starting test: SystemLog * The System Event log test Found no errors in "System" Event log in the last 60 minutes. ......................... DRI-AD-SEC passed test SystemLog Starting test: Topology * Configuration Topology Integrity Check * Analyzing the connection topology for DC=ForestDnsZones,DC=dri,DC=local. * Performing upstream (of target) analysis. * Performing downstream (of target) analysis. * Analyzing the connection topology for DC=DomainDnsZones,DC=dri,DC=local. * Performing upstream (of target) analysis. * Performing downstream (of target) analysis. * Analyzing the connection topology for CN=Schema,CN=Configuration,DC=dri,DC=local. * Performing upstream (of target) analysis. * Performing downstream (of target) analysis. * Analyzing the connection topology for CN=Configuration,DC=dri,DC=local. * Performing upstream (of target) analysis. * Performing downstream (of target) analysis. * Analyzing the connection topology for DC=dri,DC=local. * Performing upstream (of target) analysis. * Performing downstream (of target) analysis. ......................... DRI-AD-SEC passed test Topology Starting test: VerifyEnterpriseReferences ......................... DRI-AD-SEC passed test VerifyEnterpriseReferences Starting test: VerifyReferences The system object reference (serverReference) CN=DRI-AD-SEC,OU=Secondary,OU=Domain Controllers,DC=dri,DC=local and backlink on CN=DRI-AD-SEC,CN=Servers,CN=LOLA,CN=Sites,CN=Configuration,DC=dri,DC=local are correct. The system object reference (serverReferenceBL) CN=DRI-AD-SEC,CN=Topology,CN=Domain System Volume,CN=DFSR-GlobalSettings,CN=System,DC=dri,DC=local and backlink on CN=NTDS Settings,CN=DRI-AD-SEC,CN=Servers,CN=LOLA,CN=Sites,CN=Configuration,DC=dri,DC=local are correct. The system object reference (msDFSR-ComputerReferenceBL) CN=DRI-AD-SEC,CN=Topology,CN=Domain System Volume,CN=DFSR-GlobalSettings,CN=System,DC=dri,DC=local and backlink on CN=DRI-AD-SEC,OU=Secondary,OU=Domain Controllers,DC=dri,DC=local are correct. ......................... DRI-AD-SEC passed test VerifyReferences Starting test: VerifyReplicas ......................... DRI-AD-SEC passed test VerifyReplicas Testing server: LOLA\DRI-DCRO Starting test: Advertising The DC DRI-DCRO is advertising itself as a DC and having a DS. The DC DRI-DCRO is advertising as an LDAP server The DC DRI-DCRO is advertising as having a writeable directory The DC DRI-DCRO is advertising as a Key Distribution Center The DC DRI-DCRO is advertising as a time server The DS DRI-DCRO is advertising as a GC. ......................... DRI-DCRO passed test Advertising Starting test: CheckSecurityError * Dr Auth: Beginning security errors check! Found KDC DRI-AD-SEC for domain dri.local in site LOLA Checking machine account for DC DRI-DCRO on DC DRI-AD-SEC. * SPN found :LDAP/DRI-DCRO.dri.local/dri.local * SPN found :LDAP/DRI-DCRO.dri.local * SPN found :LDAP/DRI-DCRO * SPN found :LDAP/DRI-DCRO.dri.local/DRI * SPN found :LDAP/cda06af1-1b57-4810-bbbc-378a98069d60._msdcs.dri.local * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/cda06af1-1b57-4810-bbbc-378a98069d60/dri.local * SPN found :HOST/DRI-DCRO.dri.local/dri.local * SPN found :HOST/DRI-DCRO.dri.local * SPN found :HOST/DRI-DCRO * SPN found :HOST/DRI-DCRO.dri.local/DRI * SPN found :GC/DRI-DCRO.dri.local/dri.local Checking for CN=DRI-DCRO,OU=Secondary,OU=Domain Controllers,DC=dri,DC=local in domain DC=dri,DC=local on 2 servers Object is up-to-date on all servers. [DRI-DCRO] No security related replication errors were found on this DC! To target the connection to a specific source DC use /ReplSource:. ......................... DRI-DCRO passed test CheckSecurityError Starting test: CutoffServers * Configuration Topology Aliveness Check * Analyzing the alive system replication topology for DC=ForestDnsZones,DC=dri,DC=local. * Performing upstream (of target) analysis. * Performing downstream (of target) analysis. * Analyzing the alive system replication topology for DC=DomainDnsZones,DC=dri,DC=local. * Performing upstream (of target) analysis. * Performing downstream (of target) analysis. * Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=dri,DC=local. * Performing upstream (of target) analysis. * Performing downstream (of target) analysis. * Analyzing the alive system replication topology for CN=Configuration,DC=dri,DC=local. * Performing upstream (of target) analysis. * Performing downstream (of target) analysis. * Analyzing the alive system replication topology for DC=dri,DC=local. * Performing upstream (of target) analysis. * Performing downstream (of target) analysis. ......................... DRI-DCRO passed test CutoffServers Starting test: FrsEvent * The File Replication Service Event log test Skip the test because the server is running DFSR. ......................... DRI-DCRO 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: 0x800008A5 Time Generated: 04/03/2022 16:39:53 Event String: The DFS Replication service stopped replication on volume C:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled. To resolve this issue, back up the files in the affected replicated folders, and then use the ResumeReplication WMI method to resume replication. Additional Information: Volume: C: GUID: A198F344-33C0-11EA-93E7-806E6F6E6963 Recovery Steps 1. Back up the files in all replicated folders on the volume. Failure to do so may result in data loss due to unexpected conflict resolution during the recovery of the replicated folders. 2. To resume the replication for this volume, use the WMI method ResumeReplication of the DfsrVolumeConfig class. For example, from an elevated command prompt, type the following command: wmic /namespace:\\root\microsoftdfs path dfsrVolumeConfig where volumeGuid="A198F344-33C0-11EA-93E7-806E6F6E6963" call ResumeReplication For more information, see http://support.microsoft.com/kb/2663685. A warning event occurred. EventID: 0x800008A5 Time Generated: 04/03/2022 16:42:15 Event String: The DFS Replication service stopped replication on volume C:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled. To resolve this issue, back up the files in the affected replicated folders, and then use the ResumeReplication WMI method to resume replication. Additional Information: Volume: C: GUID: A198F344-33C0-11EA-93E7-806E6F6E6963 Recovery Steps 1. Back up the files in all replicated folders on the volume. Failure to do so may result in data loss due to unexpected conflict resolution during the recovery of the replicated folders. 2. To resume the replication for this volume, use the WMI method ResumeReplication of the DfsrVolumeConfig class. For example, from an elevated command prompt, type the following command: wmic /namespace:\\root\microsoftdfs path dfsrVolumeConfig where volumeGuid="A198F344-33C0-11EA-93E7-806E6F6E6963" call ResumeReplication For more information, see http://support.microsoft.com/kb/2663685. A warning event occurred. EventID: 0x800008A4 Time Generated: 04/03/2022 16:54:00 Event String: The DFS Replication service has detected an unexpected shutdown on volume C:. This can occur if the service terminated abnormally (due to a power loss, for example) or an error occurred on the volume. The service has automatically initiated a recovery process. The service will rebuild the database if it determines it cannot reliably recover. No user action is required. Additional Information: Volume: C: GUID: A198F344-33C0-11EA-93E7-806E6F6E6963 An error event occurred. EventID: 0xC0000FAC Time Generated: 04/03/2022 16:54:20 Event String: The DFS Replication service stopped replication on the folder with the following local path: C:\Windows\SYSVOL\domain. This server has been disconnected from other partners for 451 days, which is longer than the time allowed by the MaxOfflineTimeInDays parameter (60). DFS Replication considers the data in this folder to be stale, and this server will not replicate the folder until this error is corrected. To resume replication of this folder, use the DFS Management snap-in to remove this server from the replication group, and then add it back to the group. This causes the server to perform an initial synchronization task, which replaces the stale data with fresh data from other members of the replication group. Additional Information: Error: 9061 (The replicated folder has been offline for too long.) Replicated Folder Name: SYSVOL Share Replicated Folder ID: D2A35C60-7F0C-477E-9F20-33235B01ADFE Replication Group Name: Domain System Volume Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A Member ID: 5738C567-99AB-40B3-8BAD-EE5F0CF9C1F6 An error event occurred. EventID: 0xC0000FAC Time Generated: 04/03/2022 16:56:38 Event String: The DFS Replication service stopped replication on the folder with the following local path: C:\Windows\SYSVOL\domain. This server has been disconnected from other partners for 451 days, which is longer than the time allowed by the MaxOfflineTimeInDays parameter (60). DFS Replication considers the data in this folder to be stale, and this server will not replicate the folder until this error is corrected. To resume replication of this folder, use the DFS Management snap-in to remove this server from the replication group, and then add it back to the group. This causes the server to perform an initial synchronization task, which replaces the stale data with fresh data from other members of the replication group. Additional Information: Error: 9061 (The replicated folder has been offline for too long.) Replicated Folder Name: SYSVOL Share Replicated Folder ID: D2A35C60-7F0C-477E-9F20-33235B01ADFE Replication Group Name: Domain System Volume Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A Member ID: 5738C567-99AB-40B3-8BAD-EE5F0CF9C1F6 An error event occurred. EventID: 0xC0000FAC Time Generated: 04/03/2022 17:03:38 Event String: The DFS Replication service stopped replication on the folder with the following local path: C:\Windows\SYSVOL\domain. This server has been disconnected from other partners for 451 days, which is longer than the time allowed by the MaxOfflineTimeInDays parameter (60). DFS Replication considers the data in this folder to be stale, and this server will not replicate the folder until this error is corrected. To resume replication of this folder, use the DFS Management snap-in to remove this server from the replication group, and then add it back to the group. This causes the server to perform an initial synchronization task, which replaces the stale data with fresh data from other members of the replication group. Additional Information: Error: 9061 (The replicated folder has been offline for too long.) Replicated Folder Name: SYSVOL Share Replicated Folder ID: D2A35C60-7F0C-477E-9F20-33235B01ADFE Replication Group Name: Domain System Volume Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A Member ID: 5738C567-99AB-40B3-8BAD-EE5F0CF9C1F6 An error event occurred. EventID: 0xC0000FAC Time Generated: 04/03/2022 17:27:38 Event String: The DFS Replication service stopped replication on the folder with the following local path: C:\Windows\SYSVOL\domain. This server has been disconnected from other partners for 451 days, which is longer than the time allowed by the MaxOfflineTimeInDays parameter (60). DFS Replication considers the data in this folder to be stale, and this server will not replicate the folder until this error is corrected. To resume replication of this folder, use the DFS Management snap-in to remove this server from the replication group, and then add it back to the group. This causes the server to perform an initial synchronization task, which replaces the stale data with fresh data from other members of the replication group. Additional Information: Error: 9061 (The replicated folder has been offline for too long.) Replicated Folder Name: SYSVOL Share Replicated Folder ID: D2A35C60-7F0C-477E-9F20-33235B01ADFE Replication Group Name: Domain System Volume Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A Member ID: 5738C567-99AB-40B3-8BAD-EE5F0CF9C1F6 An error event occurred. EventID: 0xC000138A Time Generated: 04/03/2022 18:25:49 Event String: The DFS Replication service encountered an error communicating with partner DRI-AD for replication group Domain System Volume. Partner DNS address: dri-AD.dri.local Optional data if available: Partner WINS Address: dri-AD Partner IP Address: 192.168.99.20 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: CF113B2A-7CCA-431A-B4A1-F028CBB27099 Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A An error event occurred. EventID: 0xC000138A Time Generated: 04/03/2022 18:34:05 Event String: The DFS Replication service encountered an error communicating with partner DRI-AD for replication group Domain System Volume. Partner DNS address: dri-AD.dri.local Optional data if available: Partner WINS Address: dri-AD Partner IP Address: 192.168.99.20 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: CF113B2A-7CCA-431A-B4A1-F028CBB27099 Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A An error event occurred. EventID: 0xC000138A Time Generated: 04/03/2022 18:49:05 Event String: The DFS Replication service encountered an error communicating with partner DRI-AD for replication group Domain System Volume. Partner DNS address: dri-AD.dri.local Optional data if available: Partner WINS Address: dri-AD Partner IP Address: 192.168.99.20 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: CF113B2A-7CCA-431A-B4A1-F028CBB27099 Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A An error event occurred. EventID: 0xC000138A Time Generated: 04/03/2022 19:49:05 Event String: The DFS Replication service encountered an error communicating with partner DRI-AD for replication group Domain System Volume. Partner DNS address: dri-AD.dri.local Optional data if available: Partner WINS Address: dri-AD Partner IP Address: 192.168.99.20 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: CF113B2A-7CCA-431A-B4A1-F028CBB27099 Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A A warning event occurred. EventID: 0x80001396 Time Generated: 04/03/2022 20:13:57 Event String: The DFS Replication service is stopping communication with partner DRI-AD-SEC for replication group Domain System Volume due to an error. The service will retry the connection periodically. Additional Information: Error: 1723 (The RPC server is too busy to complete this operation.) Connection ID: 2001B7F0-B12C-49BE-BCF5-72359332C17E Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A An error event occurred. EventID: 0xC000138A Time Generated: 04/03/2022 23:49:06 Event String: The DFS Replication service encountered an error communicating with partner DRI-AD for replication group Domain System Volume. Partner DNS address: dri-AD.dri.local Optional data if available: Partner WINS Address: dri-AD Partner IP Address: 192.168.99.20 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: CF113B2A-7CCA-431A-B4A1-F028CBB27099 Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A An error event occurred. EventID: 0xC000138A Time Generated: 04/04/2022 07:49:06 Event String: The DFS Replication service encountered an error communicating with partner DRI-AD for replication group Domain System Volume. Partner DNS address: dri-AD.dri.local Optional data if available: Partner WINS Address: dri-AD Partner IP Address: 192.168.99.20 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: CF113B2A-7CCA-431A-B4A1-F028CBB27099 Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A A warning event occurred. EventID: 0x80001396 Time Generated: 04/04/2022 08:47:07 Event String: The DFS Replication service is stopping communication with partner DRI-AD-SEC for replication group Domain System Volume due to an error. The service will retry the connection periodically. Additional Information: Error: 1723 (The RPC server is too busy to complete this operation.) Connection ID: 2001B7F0-B12C-49BE-BCF5-72359332C17E Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A An error event occurred. EventID: 0xC000138A Time Generated: 04/04/2022 08:47:21 Event String: The DFS Replication service encountered an error communicating with partner DRI-AD-SEC for replication group Domain System Volume. Partner DNS address: DRI-AD-SEC.dri.local Optional data if available: Partner WINS Address: DRI-AD-SEC Partner IP Address: 192.168.99.55 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: 2001B7F0-B12C-49BE-BCF5-72359332C17E Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A An error event occurred. EventID: 0xC000138A Time Generated: 04/04/2022 09:01:28 Event String: The DFS Replication service encountered an error communicating with partner DRI-AD for replication group Domain System Volume. Partner DNS address: dri-AD.dri.local Optional data if available: Partner WINS Address: dri-AD Partner IP Address: 192.168.99.20 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: CF113B2A-7CCA-431A-B4A1-F028CBB27099 Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A An error event occurred. EventID: 0xC000138A Time Generated: 04/04/2022 09:09:16 Event String: The DFS Replication service encountered an error communicating with partner DRI-AD for replication group Domain System Volume. Partner DNS address: dri-AD.dri.local Optional data if available: Partner WINS Address: dri-AD Partner IP Address: 192.168.99.20 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: CF113B2A-7CCA-431A-B4A1-F028CBB27099 Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A An error event occurred. EventID: 0xC000138A Time Generated: 04/04/2022 09:24:16 Event String: The DFS Replication service encountered an error communicating with partner DRI-AD for replication group Domain System Volume. Partner DNS address: dri-AD.dri.local Optional data if available: Partner WINS Address: dri-AD Partner IP Address: 192.168.99.20 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: CF113B2A-7CCA-431A-B4A1-F028CBB27099 Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A An error event occurred. EventID: 0xC000138A Time Generated: 04/04/2022 10:28:21 Event String: The DFS Replication service encountered an error communicating with partner DRI-AD for replication group Domain System Volume. Partner DNS address: dri-AD.dri.local Optional data if available: Partner WINS Address: dri-AD Partner IP Address: 192.168.99.20 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: CF113B2A-7CCA-431A-B4A1-F028CBB27099 Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A An error event occurred. EventID: 0xC000138A Time Generated: 04/04/2022 14:28:21 Event String: The DFS Replication service encountered an error communicating with partner DRI-AD for replication group Domain System Volume. Partner DNS address: dri-AD.dri.local Optional data if available: Partner WINS Address: dri-AD Partner IP Address: 192.168.99.20 The service will retry the connection periodically. Additional Information: Error: 1753 (There are no more endpoints available from the endpoint mapper.) Connection ID: CF113B2A-7CCA-431A-B4A1-F028CBB27099 Replication Group ID: 00AF8B53-0730-472D-8033-9A24DA701B3A ......................... DRI-DCRO failed test DFSREvent Starting test: SysVolCheck * The File Replication Service SYSVOL ready test File Replication Service's SYSVOL is ready ......................... DRI-DCRO passed test SysVolCheck Starting test: FrsSysVol * The File Replication Service SYSVOL ready test File Replication Service's SYSVOL is ready ......................... DRI-DCRO passed test FrsSysVol Starting test: KccEvent * The KCC Event log test Found no KCC errors in "Directory Service" Event log in the last 15 minutes. ......................... DRI-DCRO passed test KccEvent Starting test: KnowsOfRoleHolders Role Schema Owner = CN=NTDS Settings,CN=DRI-AD,CN=Servers,CN=LOLA,CN=Sites,CN=Configuration,DC=dri,DC=local Role Domain Owner = CN=NTDS Settings,CN=DRI-AD,CN=Servers,CN=LOLA,CN=Sites,CN=Configuration,DC=dri,DC=local Role PDC Owner = CN=NTDS Settings,CN=DRI-AD,CN=Servers,CN=LOLA,CN=Sites,CN=Configuration,DC=dri,DC=local Role Rid Owner = CN=NTDS Settings,CN=DRI-AD,CN=Servers,CN=LOLA,CN=Sites,CN=Configuration,DC=dri,DC=local Role Infrastructure Update Owner = CN=NTDS Settings,CN=DRI-AD,CN=Servers,CN=LOLA,CN=Sites,CN=Configuration,DC=dri,DC=local ......................... DRI-DCRO passed test KnowsOfRoleHolders Starting test: MachineAccount Checking machine account for DC DRI-DCRO on DC DRI-DCRO. * SPN found :LDAP/DRI-DCRO.dri.local/dri.local * SPN found :LDAP/DRI-DCRO.dri.local * SPN found :LDAP/DRI-DCRO * SPN found :LDAP/DRI-DCRO.dri.local/DRI * SPN found :LDAP/cda06af1-1b57-4810-bbbc-378a98069d60._msdcs.dri.local * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/cda06af1-1b57-4810-bbbc-378a98069d60/dri.local * SPN found :HOST/DRI-DCRO.dri.local/dri.local * SPN found :HOST/DRI-DCRO.dri.local * SPN found :HOST/DRI-DCRO * SPN found :HOST/DRI-DCRO.dri.local/DRI * SPN found :GC/DRI-DCRO.dri.local/dri.local ......................... DRI-DCRO passed test MachineAccount Starting test: NCSecDesc * Security Permissions check for all NC's on DC DRI-DCRO. * Security Permissions Check for DC=ForestDnsZones,DC=dri,DC=local (NDNC,Version 3) * Security Permissions Check for DC=DomainDnsZones,DC=dri,DC=local (NDNC,Version 3) * Security Permissions Check for CN=Schema,CN=Configuration,DC=dri,DC=local (Schema,Version 3) * Security Permissions Check for CN=Configuration,DC=dri,DC=local (Configuration,Version 3) * Security Permissions Check for DC=dri,DC=local (Domain,Version 3) ......................... DRI-DCRO passed test NCSecDesc Starting test: NetLogons * Network Logons Privileges Check Verified share \\DRI-DCRO\netlogon Verified share \\DRI-DCRO\sysvol ......................... DRI-DCRO passed test NetLogons Starting test: ObjectsReplicated DRI-DCRO is in domain DC=dri,DC=local Checking for CN=DRI-DCRO,OU=Secondary,OU=Domain Controllers,DC=dri,DC=local in domain DC=dri,DC=local on 3 servers Object is up-to-date on all servers. Checking for CN=NTDS Settings,CN=DRI-DCRO,CN=Servers,CN=LOLA,CN=Sites,CN=Configuration,DC=dri,DC=local in domain CN=Configuration,DC=dri,DC=local on 3 servers Object is up-to-date on all servers. ......................... DRI-DCRO passed test ObjectsReplicated Starting test: OutboundSecureChannels * The Outbound Secure Channels test ** Did not run Outbound Secure Channels test because /testdomain: was not entered ......................... DRI-DCRO passed test OutboundSecureChannels Starting test: Replications * Replications Check * Replication Latency Check DC=ForestDnsZones,DC=dri,DC=local Latency information for 4 entries in the vector were ignored. 4 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=DomainDnsZones,DC=dri,DC=local Latency information for 2 entries in the vector were ignored. 2 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=dri,DC=local Latency information for 4 entries in the vector were ignored. 4 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=dri,DC=local Latency information for 4 entries in the vector were ignored. 4 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=dri,DC=local Latency information for 2 entries in the vector were ignored. 2 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). ......................... DRI-DCRO passed test Replications Starting test: RidManager * Available RID Pool for the Domain is 5112 to 1073741823 * dri-AD.dri.local is the RID Master * DsBind with RID Master was successful * rIDAllocationPool is 4112 to 4611 * rIDPreviousAllocationPool is 4112 to 4611 * rIDNextRID: 4233 ......................... DRI-DCRO 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 ......................... DRI-DCRO passed test Services Starting test: SystemLog * The System Event log test An error event occurred. EventID: 0x00000448 Time Generated: 04/04/2022 14:48:11 Event String: The processing of Group Policy failed. Windows could not apply the registry-based policy settings for the Group Policy object LDAP://CN=User,cn={42ABB1DD-C0B9-40C1-B9E5-647A1418EB9D},cn=policies,cn=system,DC=dri,DC=local. Group Policy settings will not be resolved until this event is resolved. View the event details for more information on the file name and path that caused the failure. A warning event occurred. EventID: 0x0000043D Time Generated: 04/04/2022 14:48:12 Event String: Windows failed to apply the Group Policy Printers settings. Group Policy Printers settings might have its own log file. Please click on the "More information" link. ......................... DRI-DCRO failed test SystemLog Starting test: Topology * Configuration Topology Integrity Check * Analyzing the connection topology for DC=ForestDnsZones,DC=dri,DC=local. * Performing upstream (of target) analysis. * Performing downstream (of target) analysis. * Analyzing the connection topology for DC=DomainDnsZones,DC=dri,DC=local. * Performing upstream (of target) analysis. * Performing downstream (of target) analysis. * Analyzing the connection topology for CN=Schema,CN=Configuration,DC=dri,DC=local. * Performing upstream (of target) analysis. * Performing downstream (of target) analysis. * Analyzing the connection topology for CN=Configuration,DC=dri,DC=local. * Performing upstream (of target) analysis. * Performing downstream (of target) analysis. * Analyzing the connection topology for DC=dri,DC=local. * Performing upstream (of target) analysis. * Performing downstream (of target) analysis. ......................... DRI-DCRO passed test Topology Starting test: VerifyEnterpriseReferences ......................... DRI-DCRO passed test VerifyEnterpriseReferences Starting test: VerifyReferences The system object reference (serverReference) CN=DRI-DCRO,OU=Secondary,OU=Domain Controllers,DC=dri,DC=local and backlink on CN=DRI-DCRO,CN=Servers,CN=LOLA,CN=Sites,CN=Configuration,DC=dri,DC=local are correct. The system object reference (serverReferenceBL) CN=DRI-DCRO,CN=Topology,CN=Domain System Volume,CN=DFSR-GlobalSettings,CN=System,DC=dri,DC=local and backlink on CN=NTDS Settings,CN=DRI-DCRO,CN=Servers,CN=LOLA,CN=Sites,CN=Configuration,DC=dri,DC=local are correct. The system object reference (msDFSR-ComputerReferenceBL) CN=DRI-DCRO,CN=Topology,CN=Domain System Volume,CN=DFSR-GlobalSettings,CN=System,DC=dri,DC=local and backlink on CN=DRI-DCRO,OU=Secondary,OU=Domain Controllers,DC=dri,DC=local are correct. ......................... DRI-DCRO passed test VerifyReferences Starting test: VerifyReplicas ......................... DRI-DCRO passed test VerifyReplicas Starting test: DNS Starting test: DNS Starting test: DNS DNS Tests are running and not hung. Please wait a few minutes... See DNS test in enterprise tests section for results ......................... DRI-AD-SEC passed test DNS See DNS test in enterprise tests section for results ......................... DRI-DCRO passed test DNS See DNS test in enterprise tests section for results ......................... DRI-AD passed test DNS 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 : dri Starting test: CheckSDRefDom ......................... dri passed test CheckSDRefDom Starting test: CrossRefValidation ......................... dri passed test CrossRefValidation Running enterprise tests on : dri.local Starting test: DNS Test results for domain controllers: DC: DRI-DCRO.dri.local Domain: dri.local TEST: Authentication (Auth) Authentication test: Successfully completed TEST: Basic (Basc) The OS Microsoft Windows Server 2012 Standard (Service Pack level: 0.0) is supported. NETLOGON service is running kdc service is running DNSCACHE service is running DNS service is running DC is a DNS server Network adapters information: Adapter [00000010] Microsoft Hyper-V Network Adapter: MAC address is 00:15:5D:03:21:14 IP Address is static IP address: 192.168.99.24 DNS servers: 192.168.99.20 (DRI-AD) [Valid] 127.0.0.1 (DRI-DCRO) [Valid] The A host record(s) for this DC was found The SOA record for the Active Directory zone was found The Active Directory zone on this DC/DNS server was found primary Root zone on this DC/DNS server was not found TEST: Forwarders/Root hints (Forw) Recursion is enabled Forwarders Information: 8.8.4.4 () [Valid] 8.8.8.8 () [Valid] TEST: Delegations (Del) No delegations were found in this zone on this DNS server TEST: Dynamic update (Dyn) Test record dcdiag-test-record added successfully in zone dri.local Test record dcdiag-test-record deleted successfully in zone dri.local TEST: Records registration (RReg) Network Adapter [00000010] Microsoft Hyper-V Network Adapter: Matching CNAME record found at DNS server 192.168.99.20: cda06af1-1b57-4810-bbbc-378a98069d60._msdcs.dri.local Matching A record found at DNS server 192.168.99.20: DRI-DCRO.dri.local Matching SRV record found at DNS server 192.168.99.20: _ldap._tcp.dri.local Matching SRV record found at DNS server 192.168.99.20: _ldap._tcp.d9ed3ceb-6068-4caf-9150-d37faf4981d8.domains._msdcs.dri.local Matching SRV record found at DNS server 192.168.99.20: _kerberos._tcp.dc._msdcs.dri.local Matching SRV record found at DNS server 192.168.99.20: _ldap._tcp.dc._msdcs.dri.local Matching SRV record found at DNS server 192.168.99.20: _kerberos._tcp.dri.local Matching SRV record found at DNS server 192.168.99.20: _kerberos._udp.dri.local Matching SRV record found at DNS server 192.168.99.20: _kpasswd._tcp.dri.local Matching SRV record found at DNS server 192.168.99.20: _ldap._tcp.LOLA._sites.dri.local Matching SRV record found at DNS server 192.168.99.20: _kerberos._tcp.LOLA._sites.dc._msdcs.dri.local Matching SRV record found at DNS server 192.168.99.20: _ldap._tcp.LOLA._sites.dc._msdcs.dri.local Matching SRV record found at DNS server 192.168.99.20: _kerberos._tcp.LOLA._sites.dri.local Matching SRV record found at DNS server 192.168.99.20: _ldap._tcp.gc._msdcs.dri.local Matching A record found at DNS server 192.168.99.20: gc._msdcs.dri.local Matching SRV record found at DNS server 192.168.99.20: _gc._tcp.LOLA._sites.dri.local Matching SRV record found at DNS server 192.168.99.20: _ldap._tcp.LOLA._sites.gc._msdcs.dri.local Matching CNAME record found at DNS server 192.168.99.24: cda06af1-1b57-4810-bbbc-378a98069d60._msdcs.dri.local Matching A record found at DNS server 192.168.99.24: DRI-DCRO.dri.local Matching SRV record found at DNS server 192.168.99.24: _ldap._tcp.dri.local Matching SRV record found at DNS server 192.168.99.24: _ldap._tcp.d9ed3ceb-6068-4caf-9150-d37faf4981d8.domains._msdcs.dri.local Matching SRV record found at DNS server 192.168.99.24: _kerberos._tcp.dc._msdcs.dri.local Matching SRV record found at DNS server 192.168.99.24: _ldap._tcp.dc._msdcs.dri.local Matching SRV record found at DNS server 192.168.99.24: _kerberos._tcp.dri.local Matching SRV record found at DNS server 192.168.99.24: _kerberos._udp.dri.local Matching SRV record found at DNS server 192.168.99.24: _kpasswd._tcp.dri.local Matching SRV record found at DNS server 192.168.99.24: _ldap._tcp.LOLA._sites.dri.local Matching SRV record found at DNS server 192.168.99.24: _kerberos._tcp.LOLA._sites.dc._msdcs.dri.local Matching SRV record found at DNS server 192.168.99.24: _ldap._tcp.LOLA._sites.dc._msdcs.dri.local Matching SRV record found at DNS server 192.168.99.24: _kerberos._tcp.LOLA._sites.dri.local Matching SRV record found at DNS server 192.168.99.24: _ldap._tcp.gc._msdcs.dri.local Matching A record found at DNS server 192.168.99.24: gc._msdcs.dri.local Matching SRV record found at DNS server 192.168.99.24: _gc._tcp.LOLA._sites.dri.local Matching SRV record found at DNS server 192.168.99.24: _ldap._tcp.LOLA._sites.gc._msdcs.dri.local DC: DRI-AD-SEC.dri.local Domain: dri.local TEST: Authentication (Auth) Authentication test: Successfully completed TEST: Basic (Basc) The OS Microsoft Windows Server 2012 Standard (Service Pack level: 0.0) is supported. NETLOGON service is running kdc service is running DNSCACHE service is running DNS service is running DC is a DNS server Network adapters information: Adapter [00000010] Microsoft Hyper-V Network Adapter: MAC address is 00:15:5D:03:21:22 IP Address is static IP address: 192.168.99.55, fe80::48ef:947e:f776:44cb DNS servers: 192.168.99.20 (DRI-AD) [Valid] 127.0.0.1 (DRI-AD-SEC) [Valid] The A host record(s) for this DC was found The SOA record for the Active Directory zone was found The Active Directory zone on this DC/DNS server was found primary Root zone on this DC/DNS server was not found TEST: Forwarders/Root hints (Forw) Recursion is enabled Forwarders Information: 8.8.4.4 () [Valid] 8.8.8.8 () [Valid] TEST: Delegations (Del) No delegations were found in this zone on this DNS server TEST: Dynamic update (Dyn) Test record dcdiag-test-record added successfully in zone dri.local Test record dcdiag-test-record deleted successfully in zone dri.local TEST: Records registration (RReg) Network Adapter [00000010] Microsoft Hyper-V Network Adapter: Matching CNAME record found at DNS server 192.168.99.20: d183b5ab-921e-4861-86f5-1ede5a632382._msdcs.dri.local Matching A record found at DNS server 192.168.99.20: DRI-AD-SEC.dri.local Matching SRV record found at DNS server 192.168.99.20: _ldap._tcp.dri.local Matching SRV record found at DNS server 192.168.99.20: _ldap._tcp.d9ed3ceb-6068-4caf-9150-d37faf4981d8.domains._msdcs.dri.local Matching SRV record found at DNS server 192.168.99.20: _kerberos._tcp.dc._msdcs.dri.local Matching SRV record found at DNS server 192.168.99.20: _ldap._tcp.dc._msdcs.dri.local Matching SRV record found at DNS server 192.168.99.20: _kerberos._tcp.dri.local Matching SRV record found at DNS server 192.168.99.20: _kerberos._udp.dri.local Matching SRV record found at DNS server 192.168.99.20: _kpasswd._tcp.dri.local Matching SRV record found at DNS server 192.168.99.20: _ldap._tcp.LOLA._sites.dri.local Matching SRV record found at DNS server 192.168.99.20: _kerberos._tcp.LOLA._sites.dc._msdcs.dri.local Matching SRV record found at DNS server 192.168.99.20: _ldap._tcp.LOLA._sites.dc._msdcs.dri.local Matching SRV record found at DNS server 192.168.99.20: _kerberos._tcp.LOLA._sites.dri.local Matching SRV record found at DNS server 192.168.99.20: _ldap._tcp.gc._msdcs.dri.local Matching A record found at DNS server 192.168.99.20: gc._msdcs.dri.local Matching SRV record found at DNS server 192.168.99.20: _gc._tcp.LOLA._sites.dri.local Matching SRV record found at DNS server 192.168.99.20: _ldap._tcp.LOLA._sites.gc._msdcs.dri.local Matching CNAME record found at DNS server 192.168.99.55: d183b5ab-921e-4861-86f5-1ede5a632382._msdcs.dri.local Matching A record found at DNS server 192.168.99.55: DRI-AD-SEC.dri.local Matching SRV record found at DNS server 192.168.99.55: _ldap._tcp.dri.local Matching SRV record found at DNS server 192.168.99.55: _ldap._tcp.d9ed3ceb-6068-4caf-9150-d37faf4981d8.domains._msdcs.dri.local Matching SRV record found at DNS server 192.168.99.55: _kerberos._tcp.dc._msdcs.dri.local Matching SRV record found at DNS server 192.168.99.55: _ldap._tcp.dc._msdcs.dri.local Matching SRV record found at DNS server 192.168.99.55: _kerberos._tcp.dri.local Matching SRV record found at DNS server 192.168.99.55: _kerberos._udp.dri.local Matching SRV record found at DNS server 192.168.99.55: _kpasswd._tcp.dri.local Matching SRV record found at DNS server 192.168.99.55: _ldap._tcp.LOLA._sites.dri.local Matching SRV record found at DNS server 192.168.99.55: _kerberos._tcp.LOLA._sites.dc._msdcs.dri.local Matching SRV record found at DNS server 192.168.99.55: _ldap._tcp.LOLA._sites.dc._msdcs.dri.local Matching SRV record found at DNS server 192.168.99.55: _kerberos._tcp.LOLA._sites.dri.local Matching SRV record found at DNS server 192.168.99.55: _ldap._tcp.gc._msdcs.dri.local Matching A record found at DNS server 192.168.99.55: gc._msdcs.dri.local Matching SRV record found at DNS server 192.168.99.55: _gc._tcp.LOLA._sites.dri.local Matching SRV record found at DNS server 192.168.99.55: _ldap._tcp.LOLA._sites.gc._msdcs.dri.local DC: dri-AD.dri.local Domain: dri.local TEST: Authentication (Auth) Authentication test: Successfully completed TEST: Basic (Basc) The OS Microsoftr Windows Serverr 2008 Enterprise without Hyper-V (Service Pack level: 2.0) is supported. NETLOGON service is running kdc service is running DNSCACHE service is running DNS service is running DC is a DNS server Network adapters information: Adapter [00000013] HP Ethernet 1Gb 4-port 331i Adapter: MAC address is 9C:8E:99:4D:D3:CD IP Address is static IP address: 192.168.99.20 DNS servers: 192.168.99.20 (DRI-AD) [Valid] The A host record(s) for this DC was found The SOA record for the Active Directory zone was found The Active Directory zone on this DC/DNS server was found primary Root zone on this DC/DNS server was not found TEST: Forwarders/Root hints (Forw) Recursion is enabled Forwarders Information: 8.8.4.4 () [Valid] 8.8.8.8 () [Valid] TEST: Delegations (Del) No delegations were found in this zone on this DNS server TEST: Dynamic update (Dyn) Test record dcdiag-test-record added successfully in zone dri.local Test record dcdiag-test-record deleted successfully in zone dri.local TEST: Records registration (RReg) Network Adapter [00000013] HP Ethernet 1Gb 4-port 331i Adapter: Matching CNAME record found at DNS server 192.168.99.20: c833e342-ab4b-47c7-9a42-ed5fe6a924dd._msdcs.dri.local Matching A record found at DNS server 192.168.99.20: dri-AD.dri.local Matching SRV record found at DNS server 192.168.99.20: _ldap._tcp.dri.local Matching SRV record found at DNS server 192.168.99.20: _ldap._tcp.d9ed3ceb-6068-4caf-9150-d37faf4981d8.domains._msdcs.dri.local Matching SRV record found at DNS server 192.168.99.20: _kerberos._tcp.dc._msdcs.dri.local Matching SRV record found at DNS server 192.168.99.20: _ldap._tcp.dc._msdcs.dri.local Matching SRV record found at DNS server 192.168.99.20: _kerberos._tcp.dri.local Matching SRV record found at DNS server 192.168.99.20: _kerberos._udp.dri.local Matching SRV record found at DNS server 192.168.99.20: _kpasswd._tcp.dri.local Matching SRV record found at DNS server 192.168.99.20: _ldap._tcp.LOLA._sites.dri.local Matching SRV record found at DNS server 192.168.99.20: _kerberos._tcp.LOLA._sites.dc._msdcs.dri.local Matching SRV record found at DNS server 192.168.99.20: _ldap._tcp.LOLA._sites.dc._msdcs.dri.local Matching SRV record found at DNS server 192.168.99.20: _kerberos._tcp.LOLA._sites.dri.local Matching SRV record found at DNS server 192.168.99.20: _ldap._tcp.gc._msdcs.dri.local Matching A record found at DNS server 192.168.99.20: gc._msdcs.dri.local Matching SRV record found at DNS server 192.168.99.20: _gc._tcp.LOLA._sites.dri.local Matching SRV record found at DNS server 192.168.99.20: _ldap._tcp.LOLA._sites.gc._msdcs.dri.local Matching SRV record found at DNS server 192.168.99.20: _ldap._tcp.pdc._msdcs.dri.local Summary of test results for DNS servers used by the above domain controllers: DNS server: 192.168.99.20 (DRI-AD) All tests passed on this DNS server Name resolution is functional._ldap._tcp SRV record for the forest root domain is registered DNS server: 192.168.99.24 (DRI-DCRO) All tests passed on this DNS server Name resolution is functional._ldap._tcp SRV record for the forest root domain is registered DNS server: 192.168.99.55 (DRI-AD-SEC) All tests passed on this DNS server Name resolution is functional._ldap._tcp SRV record for the forest root domain is registered DNS server: 8.8.4.4 () All tests passed on this DNS server DNS server: 8.8.8.8 () All tests passed on this DNS server Summary of DNS test results: Auth Basc Forw Del Dyn RReg Ext _________________________________________________________________ Domain: dri.local DRI-DCRO PASS PASS PASS PASS PASS PASS n/a DRI-AD-SEC PASS PASS PASS PASS PASS PASS n/a dri-AD PASS PASS PASS PASS PASS PASS n/a ......................... dri.local passed test DNS Starting test: LocatorCheck GC Name: \\dri-AD.dri.local Locator Flags: 0xe00033fd PDC Name: \\dri-AD.dri.local Locator Flags: 0xe00033fd Time Server Name: \\dri-AD.dri.local Locator Flags: 0xe00033fd Preferred Time Server Name: \\dri-AD.dri.local Locator Flags: 0xe00033fd KDC Name: \\dri-AD.dri.local Locator Flags: 0xe00033fd ......................... dri.local passed test LocatorCheck Starting test: FsmoCheck GC Name: \\dri-AD.dri.local Locator Flags: 0xe00033fd PDC Name: \\dri-AD.dri.local Locator Flags: 0xe00033fd Time Server Name: \\dri-AD.dri.local Locator Flags: 0xe00033fd Preferred Time Server Name: \\dri-AD.dri.local Locator Flags: 0xe00033fd KDC Name: \\dri-AD.dri.local Locator Flags: 0xe00033fd ......................... dri.local passed test FsmoCheck Starting test: Intersite Skipping site LOLA, this site is outside the scope provided by the command line arguments provided. ......................... dri.local passed test Intersite