Directory Server Diagnosis Performing initial setup: Trying to find home server... * Verifying that the local machine KBA-ADC-IN-P03, is a Directory Server. Home Server = KBA-ADC-IN-P03 * Connecting to directory service on server KBA-ADC-IN-P03. * Identified AD Forest. Collecting AD specific global data * Collecting site info. Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=domain,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=Zeralda,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Draria,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Chenoua,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Tipaza-Port,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Zeralda-agence,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Bouzereah,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Baba-hassen,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Saada,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Beni-Messous-STEP,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Tessala-El-Merdja,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Reghaia,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Birtouta-Nouvelle-Ville,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Baraki,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Rouiba-Centre,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Hussein-Dey,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Bab-Ezzouar-STEP,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Birtouta-Centre-Ass,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Fouka,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Douaouda,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Manaceur-Caisse,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=SidiAmmer-Centre,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=SidAmmer-Caisse,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Bousmail,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Chaiba,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Ahmeur-Ain-Caisse,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Hadjout-Ass,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Kolea-Centre,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Gouraya,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Bousmail-Agence,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=BabaHacene-ASS,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=RV2000,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Birkhadem-DD,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Mohamadia-DD,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Hydra-Magasin,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Ainbenian-Agence,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Sidiabdellah,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=CATO,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=FRAIS-VALLONS,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Garidi,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=AINNAADJA,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Alger-Centre,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Bachdjerah-Assainissement,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Staouali-Step,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Kolea,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Staoueli-Distribution,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Saa,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Beb-El-Oued,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Tikarouchine,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Boumati,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Baraki-Step,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Cherarba,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Dely-Ibrahim,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Didouche-Mourad,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Douera,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Rouiba,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Draria-Centre,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Cherchel-Agence,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Appreval,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Bir-Mourad-Rais,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=badjarah,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Parc-Central,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Cheraga,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Dar-El-Beida,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Birtouta,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Bab-Ezzouar,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Bordj-El-Kiffan,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Gue-Constantine,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Prise-Deau,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Boudouaou,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Appreval2,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Bentalha-Centre,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Sebala,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Taksebt-Centre,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=Reghaia-STEP,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site Looking at base site object: CN=NTDS Site Settings,CN=domain-local,CN=Sites,CN=Configuration,DC=domain,DC=local Getting ISTG and options for the site * Identifying all servers. Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=domain,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=KBA-ADC-IN-P02,CN=Servers,CN=domain-local,CN=Sites,CN=Configuration,DC=domain,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=GRD-ADC-001,CN=Servers,CN=Garidi,CN=Sites,CN=Configuration,DC=domain,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=AIN-ADC-002,CN=Servers,CN=AINNAADJA,CN=Sites,CN=Configuration,DC=domain,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=TKR-ADC-002,CN=Servers,CN=Tikarouchine,CN=Sites,CN=Configuration,DC=domain,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=CRB-ADC-001,CN=Servers,CN=Cherarba,CN=Sites,CN=Configuration,DC=domain,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=CHL-ADC-001,CN=Servers,CN=Cherchel-Agence,CN=Sites,CN=Configuration,DC=domain,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=BMR-ADC-001,CN=Servers,CN=Bir-Mourad-Rais,CN=Sites,CN=Configuration,DC=domain,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=PRC-ADC-004,CN=Servers,CN=Parc-Central,CN=Sites,CN=Configuration,DC=domain,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=BDO-ADC-001,CN=Servers,CN=Boudouaou,CN=Sites,CN=Configuration,DC=domain,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=APP-ADC-005,CN=Servers,CN=Appreval2,CN=Sites,CN=Configuration,DC=domain,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=TKS-ADC-001,CN=Servers,CN=Taksebt-Centre,CN=Sites,CN=Configuration,DC=domain,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=RGH-ADC-001,CN=Servers,CN=Reghaia-STEP,CN=Sites,CN=Configuration,DC=domain,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=KBA-ADC-IN-P03,CN=Servers,CN=domain-local,CN=Sites,CN=Configuration,DC=domain,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=BAR-ADC-003,CN=Servers,CN=Baraki-Step,CN=Sites,CN=Configuration,DC=domain,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=KBA-ADC-IN-P05,CN=Servers,CN=domain-local,CN=Sites,CN=Configuration,DC=domain,DC=local objectGuid obtained InvocationID obtained dnsHostname obtained site info obtained All the info for the server collected * Identifying all NC cross-refs. * Found 15 DC(s). Testing 3 of them. Done gathering initial info. Doing initial required tests Testing server: domain-local\KBA-ADC-IN-P02 Starting test: Connectivity * Active Directory LDAP Services Check Determining IP4 connectivity * Active Directory RPC Services Check The clock difference between the home server KBA-ADC-IN-P03 and target server KBA-ADC-IN-P02 is greater than one minute. This may cause Kerberos authentication failures. Please check that the time service is working properly. You may need to resynchonize the time between these servers. ......................... KBA-ADC-IN-P02 passed test Connectivity Testing server: domain-local\KBA-ADC-IN-P03 Starting test: Connectivity * Active Directory LDAP Services Check Determining IP4 connectivity * Active Directory RPC Services Check ......................... KBA-ADC-IN-P03 passed test Connectivity Testing server: domain-local\KBA-ADC-IN-P05 Starting test: Connectivity * Active Directory LDAP Services Check Determining IP4 connectivity * Active Directory RPC Services Check The clock difference between the home server KBA-ADC-IN-P03 and target server KBA-ADC-IN-P05 is greater than one minute. This may cause Kerberos authentication failures. Please check that the time service is working properly. You may need to resynchonize the time between these servers. ......................... KBA-ADC-IN-P05 passed test Connectivity Doing primary tests Testing server: domain-local\KBA-ADC-IN-P02 Starting test: Advertising The DC KBA-ADC-IN-P02 is advertising itself as a DC and having a DS. The DC KBA-ADC-IN-P02 is advertising as an LDAP server The DC KBA-ADC-IN-P02 is advertising as having a writeable directory The DC KBA-ADC-IN-P02 is advertising as a Key Distribution Center Warning: KBA-ADC-IN-P02 is not advertising as a time server. The DS KBA-ADC-IN-P02 is advertising as a GC. ......................... KBA-ADC-IN-P02 failed test Advertising Test omitted by user request: CheckSecurityError Test omitted by user request: CutoffServers Starting test: FrsEvent * The File Replication Service Event log test 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: 0x800034C5 Time Generated: 04/01/2021 16:06:41 Event String: The File Replication Service has enabled replication from KBA-ADC-IN-P03 to KBA-ADC-IN-P02 for c:\windows\sysvol\domain after repeated retries. A warning event occurred. EventID: 0x800034C4 Time Generated: 04/01/2021 17:47:34 Event String: The File Replication Service is having trouble enabling replication from PRC-ADC-004 to KBA-ADC-IN-P02 for c:\windows\sysvol\domain using the DNS name PRC-ADC-004.domain.local. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name PRC-ADC-004.domain.local from this computer. [2] FRS is not running on PRC-ADC-004.domain.local. [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established. A warning event occurred. EventID: 0x800034C4 Time Generated: 04/01/2021 17:47:34 Event String: The File Replication Service is having trouble enabling replication from GRD-ADC-001 to KBA-ADC-IN-P02 for c:\windows\sysvol\domain using the DNS name GRD-ADC-001.domain.local. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name GRD-ADC-001.domain.local from this computer. [2] FRS is not running on GRD-ADC-001.domain.local. [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established. A warning event occurred. EventID: 0x800034C4 Time Generated: 04/01/2021 17:47:34 Event String: The File Replication Service is having trouble enabling replication from CRB-ADC-001 to KBA-ADC-IN-P02 for c:\windows\sysvol\domain using the DNS name CRB-ADC-001.domain.local. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name CRB-ADC-001.domain.local from this computer. [2] FRS is not running on CRB-ADC-001.domain.local. [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established. A warning event occurred. EventID: 0x800034C4 Time Generated: 04/01/2021 17:47:34 Event String: The File Replication Service is having trouble enabling replication from AIN-ADC-002 to KBA-ADC-IN-P02 for c:\windows\sysvol\domain using the DNS name ain-adc-002.domain.local. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name ain-adc-002.domain.local from this computer. [2] FRS is not running on ain-adc-002.domain.local. [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established. A warning event occurred. EventID: 0x800034C4 Time Generated: 04/01/2021 17:47:34 Event String: The File Replication Service is having trouble enabling replication from BAR-ADC-003 to KBA-ADC-IN-P02 for c:\windows\sysvol\domain using the DNS name BAR-ADC-003.domain.local. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name BAR-ADC-003.domain.local from this computer. [2] FRS is not running on BAR-ADC-003.domain.local. [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established. A warning event occurred. EventID: 0x800034C4 Time Generated: 04/01/2021 17:47:34 Event String: The File Replication Service is having trouble enabling replication from TKR-ADC-002 to KBA-ADC-IN-P02 for c:\windows\sysvol\domain using the DNS name TKR-ADC-002.domain.local. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name TKR-ADC-002.domain.local from this computer. [2] FRS is not running on TKR-ADC-002.domain.local. [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established. A warning event occurred. EventID: 0x800034C4 Time Generated: 04/01/2021 17:47:34 Event String: The File Replication Service is having trouble enabling replication from BMR-ADC-001 to KBA-ADC-IN-P02 for c:\windows\sysvol\domain using the DNS name bmr-adc-001.domain.local. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name bmr-adc-001.domain.local from this computer. [2] FRS is not running on bmr-adc-001.domain.local. [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established. A warning event occurred. EventID: 0x800034C4 Time Generated: 04/01/2021 17:47:34 Event String: The File Replication Service is having trouble enabling replication from BDO-ADC-001 to KBA-ADC-IN-P02 for c:\windows\sysvol\domain using the DNS name BDO-ADC-001.domain.local. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name BDO-ADC-001.domain.local from this computer. [2] FRS is not running on BDO-ADC-001.domain.local. [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established. A warning event occurred. EventID: 0x800034C4 Time Generated: 04/01/2021 19:45:06 Event String: The File Replication Service is having trouble enabling replication from KBA-ADC-IN-P05 to KBA-ADC-IN-P02 for c:\windows\sysvol\domain using the DNS name KBA-ADC-IN-P05.domain.local. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name KBA-ADC-IN-P05.domain.local from this computer. [2] FRS is not running on KBA-ADC-IN-P05.domain.local. [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established. A warning event occurred. EventID: 0x800034C5 Time Generated: 04/01/2021 21:35:49 Event String: The File Replication Service has enabled replication from KBA-ADC-IN-P05 to KBA-ADC-IN-P02 for c:\windows\sysvol\domain after repeated retries. ......................... KBA-ADC-IN-P02 passed test FrsEvent Starting test: DFSREvent The DFS Replication Event Log. Skip the test because the server is running FRS. ......................... KBA-ADC-IN-P02 passed test DFSREvent Starting test: SysVolCheck * The File Replication Service SYSVOL ready test File Replication Service's SYSVOL is ready ......................... KBA-ADC-IN-P02 passed test SysVolCheck Starting test: KccEvent * The KCC Event log test A warning event occurred. EventID: 0x80000BE1 Time Generated: 04/02/2021 12:05:11 Event String: The security of this directory server can be significantly enhanced by configuring the server to enforce validation of Channel Binding Tokens received in LDAP bind requests sent over LDAPS connections. Even if no clients are issuing LDAP bind requests over LDAPS, configuring the server to validate Channel Binding Tokens will improve the security of this server. For more details and information on how to make this configuration change to the server, please see https://go.microsoft.com/fwlink/?linkid=2102405. A warning event occurred. EventID: 0x80000B47 Time Generated: 04/02/2021 12:05:11 Event String: During the previous 24 hour period, some clients attempted to perform LDAP binds that were either: (1) A SASL (Negotiate, Kerberos, NTLM, or Digest) LDAP bind that did not request signing (integrity validation), or (2) A LDAP simple bind that was performed on a clear text (non-SSL/TLS-encrypted) connection This directory server is not currently configured to reject such binds. The security of this directory server can be significantly enhanced by configuring the server to reject such binds. For more details and information on how to make this configuration change to the server, please see http://go.microsoft.com/fwlink/?LinkID=87923. Summary information on the number of these binds received within the past 24 hours is below. You can enable additional logging to log an event each time a client makes such a bind, including information on which client made the bind. To do so, please raise the setting for the "LDAP Interface Events" event logging category to level 2 or higher. Number of simple binds performed without SSL/TLS: 2016 Number of Negotiate/Kerberos/NTLM/Digest binds performed without signing: 0 Found no KCC errors in "Directory Service" Event log in the last 15 minutes. ......................... KBA-ADC-IN-P02 passed test KccEvent Starting test: KnowsOfRoleHolders Role Schema Owner = CN=NTDS Settings,CN=KBA-ADC-IN-P02,CN=Servers,CN=domain-local,CN=Sites,CN=Configuration,DC=domain,DC=local Role Domain Owner = CN=NTDS Settings,CN=KBA-ADC-IN-P03,CN=Servers,CN=domain-local,CN=Sites,CN=Configuration,DC=domain,DC=local Role PDC Owner = CN=NTDS Settings,CN=KBA-ADC-IN-P03,CN=Servers,CN=domain-local,CN=Sites,CN=Configuration,DC=domain,DC=local Role Rid Owner = CN=NTDS Settings,CN=KBA-ADC-IN-P03,CN=Servers,CN=domain-local,CN=Sites,CN=Configuration,DC=domain,DC=local Role Infrastructure Update Owner = CN=NTDS Settings,CN=KBA-ADC-IN-P02,CN=Servers,CN=domain-local,CN=Sites,CN=Configuration,DC=domain,DC=local ......................... KBA-ADC-IN-P02 passed test KnowsOfRoleHolders Starting test: MachineAccount Checking machine account for DC KBA-ADC-IN-P02 on DC KBA-ADC-IN-P02. * SPN found :LDAP/KBA-ADC-IN-P02.domain.local/domain.local * SPN found :LDAP/KBA-ADC-IN-P02.domain.local * SPN found :LDAP/KBA-ADC-IN-P02 * SPN found :LDAP/KBA-ADC-IN-P02.domain.local/domainlocal * SPN found :LDAP/ebad38aa-e9f7-4303-ad3b-c844c9a371a4._msdcs.domain.local * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/ebad38aa-e9f7-4303-ad3b-c844c9a371a4/domain.local * SPN found :HOST/KBA-ADC-IN-P02.domain.local/domain.local * SPN found :HOST/KBA-ADC-IN-P02.domain.local * SPN found :HOST/KBA-ADC-IN-P02 * SPN found :HOST/KBA-ADC-IN-P02.domain.local/domainlocal * SPN found :GC/KBA-ADC-IN-P02.domain.local/domain.local ......................... KBA-ADC-IN-P02 passed test MachineAccount Starting test: NCSecDesc * Security Permissions check for all NC's on DC KBA-ADC-IN-P02. * Security Permissions Check for DC=ForestDnsZones,DC=domain,DC=local (NDNC,Version 3) * Security Permissions Check for DC=DomainDnsZones,DC=domain,DC=local (NDNC,Version 3) * Security Permissions Check for CN=Schema,CN=Configuration,DC=domain,DC=local (Schema,Version 3) * Security Permissions Check for CN=Configuration,DC=domain,DC=local (Configuration,Version 3) * Security Permissions Check for DC=domain,DC=local (Domain,Version 3) ......................... KBA-ADC-IN-P02 passed test NCSecDesc Starting test: NetLogons * Network Logons Privileges Check Verified share \\KBA-ADC-IN-P02\netlogon Verified share \\KBA-ADC-IN-P02\sysvol ......................... KBA-ADC-IN-P02 passed test NetLogons Starting test: ObjectsReplicated KBA-ADC-IN-P02 is in domain DC=domain,DC=local Checking for CN=KBA-ADC-IN-P02,OU=Domain Controllers,DC=domain,DC=local in domain DC=domain,DC=local on 3 servers Object is up-to-date on all servers. Checking for CN=NTDS Settings,CN=KBA-ADC-IN-P02,CN=Servers,CN=domain-local,CN=Sites,CN=Configuration,DC=domain,DC=local in domain CN=Configuration,DC=domain,DC=local on 3 servers Object is up-to-date on all servers. ......................... KBA-ADC-IN-P02 passed test ObjectsReplicated Test omitted by user request: OutboundSecureChannels Starting test: Replications * Replications Check * Replication Latency Check DC=ForestDnsZones,DC=domain,DC=local Latency information for 257 entries in the vector were ignored. 257 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=domain,DC=local Latency information for 258 entries in the vector were ignored. 258 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=domain,DC=local Latency information for 265 entries in the vector were ignored. 265 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=domain,DC=local Latency information for 266 entries in the vector were ignored. 266 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=domain,DC=local Latency information for 264 entries in the vector were ignored. 264 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). ......................... KBA-ADC-IN-P02 passed test Replications Starting test: RidManager * Available RID Pool for the Domain is 193100 to 1073741823 * KBA-ADC-IN-P03.domain.local is the RID Master * DsBind with RID Master was successful * rIDAllocationPool is 191100 to 191599 * rIDPreviousAllocationPool is 188100 to 188599 * rIDNextRID: 188507 * Warning :There is less than 19% available RIDs in the current pool ......................... KBA-ADC-IN-P02 passed test RidManager Starting test: Services * Checking Service: EventSystem * Checking Service: RpcSs * Checking Service: NTDS * Checking Service: DnsCache * Checking Service: NtFrs * Checking Service: IsmServ * Checking Service: kdc * Checking Service: SamSs * Checking Service: LanmanServer * Checking Service: LanmanWorkstation * Checking Service: w32time * Checking Service: NETLOGON ......................... KBA-ADC-IN-P02 passed test Services Starting test: SystemLog * The System Event log test An error event occurred. EventID: 0x0000165B Time Generated: 04/02/2021 11:57:27 Event String: The session setup from computer 'domain-MGR-X7-2' failed because the security database does not contain a trust account 'domain-MGR-X7-2$' referenced by the specified computer. USER ACTION If this is the first occurrence of this event for the specified computer and account, this may be a transient issue that doesn't require any action at this time. If this is a Read-Only Domain Controller and 'domain-MGR-X7-2$' is a legitimate machine account for the computer 'domain-MGR-X7-2' then 'domain-MGR-X7-2' should be marked cacheable for this location if appropriate or otherwise ensure connectivity to a domain controller capable of servicing the request (for example a writable domain controller). Otherwise, the following steps may be taken to resolve this problem: If 'domain-MGR-X7-2$' is a legitimate machine account for the computer 'domain-MGR-X7-2', then 'domain-MGR-X7-2' should be rejoined to the domain. If 'domain-MGR-X7-2$' is a legitimate interdomain trust account, then the trust should be recreated. Otherwise, assuming that 'domain-MGR-X7-2$' is not a legitimate account, the following action should be taken on 'domain-MGR-X7-2': If 'domain-MGR-X7-2' is a Domain Controller, then the trust associated with 'domain-MGR-X7-2$' should be deleted. If 'domain-MGR-X7-2' is not a Domain Controller, it should be disjoined from the domain. An error event occurred. EventID: 0x000016AD Time Generated: 04/02/2021 12:07:09 Event String: The session setup from the computer domain-MGR-X7-2 failed to authenticate. The following error occurred: Access is denied. ......................... KBA-ADC-IN-P02 failed test SystemLog Test omitted by user request: Topology Test omitted by user request: VerifyEnterpriseReferences Starting test: VerifyReferences The system object reference (serverReference) CN=KBA-ADC-IN-P02,OU=Domain Controllers,DC=domain,DC=local and backlink on CN=KBA-ADC-IN-P02,CN=Servers,CN=domain-local,CN=Sites,CN=Configuration,DC=domain,DC=local are correct. The system object reference (serverReferenceBL) CN=KBA-ADC-IN-P02,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=domain,DC=local and backlink on CN=NTDS Settings,CN=KBA-ADC-IN-P02,CN=Servers,CN=domain-local,CN=Sites,CN=Configuration,DC=domain,DC=local are correct. The system object reference (frsComputerReferenceBL) CN=KBA-ADC-IN-P02,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=domain,DC=local and backlink on CN=KBA-ADC-IN-P02,OU=Domain Controllers,DC=domain,DC=local are correct. ......................... KBA-ADC-IN-P02 passed test VerifyReferences Test omitted by user request: VerifyReplicas Testing server: domain-local\KBA-ADC-IN-P03 Starting test: Advertising The DC KBA-ADC-IN-P03 is advertising itself as a DC and having a DS. The DC KBA-ADC-IN-P03 is advertising as an LDAP server The DC KBA-ADC-IN-P03 is advertising as having a writeable directory The DC KBA-ADC-IN-P03 is advertising as a Key Distribution Center The DC KBA-ADC-IN-P03 is advertising as a time server The DS KBA-ADC-IN-P03 is advertising as a GC. ......................... KBA-ADC-IN-P03 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 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: 0x800034C4 Time Generated: 04/01/2021 18:02:04 Event String: The File Replication Service is having trouble enabling replication from BDO-ADC-001 to KBA-ADC-IN-P03 for c:\windows\sysvol\domain using the DNS name BDO-ADC-001.domain.local. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name BDO-ADC-001.domain.local from this computer. [2] FRS is not running on BDO-ADC-001.domain.local. [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established. A warning event occurred. EventID: 0x800034C4 Time Generated: 04/01/2021 19:47:09 Event String: The File Replication Service is having trouble enabling replication from RGH-ADC-001 to KBA-ADC-IN-P03 for c:\windows\sysvol\domain using the DNS name RGH-ADC-001.domain.local. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name RGH-ADC-001.domain.local from this computer. [2] FRS is not running on RGH-ADC-001.domain.local. [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established. A warning event occurred. EventID: 0x800034C4 Time Generated: 04/01/2021 19:47:10 Event String: The File Replication Service is having trouble enabling replication from TKR-ADC-002 to KBA-ADC-IN-P03 for c:\windows\sysvol\domain using the DNS name TKR-ADC-002.domain.local. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name TKR-ADC-002.domain.local from this computer. [2] FRS is not running on TKR-ADC-002.domain.local. [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established. A warning event occurred. EventID: 0x800034C4 Time Generated: 04/01/2021 19:47:11 Event String: The File Replication Service is having trouble enabling replication from TKS-ADC-001 to KBA-ADC-IN-P03 for c:\windows\sysvol\domain using the DNS name TKS-ADC-001.domain.local. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name TKS-ADC-001.domain.local from this computer. [2] FRS is not running on TKS-ADC-001.domain.local. [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established. A warning event occurred. EventID: 0x800034C4 Time Generated: 04/01/2021 19:47:28 Event String: The File Replication Service is having trouble enabling replication from CHL-ADC-001 to KBA-ADC-IN-P03 for c:\windows\sysvol\domain using the DNS name CHL-ADC-001.domain.local. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name CHL-ADC-001.domain.local from this computer. [2] FRS is not running on CHL-ADC-001.domain.local. [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established. A warning event occurred. EventID: 0x800034C4 Time Generated: 04/01/2021 19:48:34 Event String: The File Replication Service is having trouble enabling replication from KBA-ADC-IN-P05 to KBA-ADC-IN-P03 for c:\windows\sysvol\domain using the DNS name KBA-ADC-IN-P05.domain.local. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name KBA-ADC-IN-P05.domain.local from this computer. [2] FRS is not running on KBA-ADC-IN-P05.domain.local. [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established. A warning event occurred. EventID: 0x800034C5 Time Generated: 04/01/2021 19:49:05 Event String: The File Replication Service has enabled replication from TKS-ADC-001 to KBA-ADC-IN-P03 for c:\windows\sysvol\domain after repeated retries. A warning event occurred. EventID: 0x800034C5 Time Generated: 04/01/2021 21:35:50 Event String: The File Replication Service has enabled replication from KBA-ADC-IN-P05 to KBA-ADC-IN-P03 for c:\windows\sysvol\domain after repeated retries. An error event occurred. EventID: 0xC0003502 Time Generated: 04/02/2021 03:29:27 Event String: The File Replication Service has detected that the volume hosting the path c: is low on disk space. Files may not replicate until disk space is made available on this volume. The available space on the volume can be found by typing "dir /a c:". For more information about managing space on a volume type "copy /?", "rename /?", "del /?", "rmdir /?", and "dir /?". An error event occurred. EventID: 0xC0003502 Time Generated: 04/02/2021 03:29:28 Event String: The File Replication Service has detected that the volume hosting the path C: is low on disk space. Files may not replicate until disk space is made available on this volume. The available space on the volume can be found by typing "dir /a C:". For more information about managing space on a volume type "copy /?", "rename /?", "del /?", "rmdir /?", and "dir /?". A warning event occurred. EventID: 0x80003509 Time Generated: 04/02/2021 07:01:33 Event String: File Replication Service (FRS) is deprecated. To continue replicating the SYSVOL folder, you should migrate to DFS Replication by using the DFSRMIG command. If you continue to use FRS for SYSVOL replication in this domain, you might not be able to add domain controllers running a future version of Windows Server. A warning event occurred. EventID: 0x800034C4 Time Generated: 04/02/2021 07:16:52 Event String: The File Replication Service is having trouble enabling replication from BDO-ADC-001 to KBA-ADC-IN-P03 for c:\windows\sysvol\domain using the DNS name BDO-ADC-001.domain.local. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name BDO-ADC-001.domain.local from this computer. [2] FRS is not running on BDO-ADC-001.domain.local. [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established. A warning event occurred. EventID: 0x800034C4 Time Generated: 04/02/2021 07:47:38 Event String: The File Replication Service is having trouble enabling replication from TKR-ADC-002 to KBA-ADC-IN-P03 for c:\windows\sysvol\domain using the DNS name TKR-ADC-002.domain.local. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name TKR-ADC-002.domain.local from this computer. [2] FRS is not running on TKR-ADC-002.domain.local. [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established. A warning event occurred. EventID: 0x800034C4 Time Generated: 04/02/2021 07:47:42 Event String: The File Replication Service is having trouble enabling replication from RGH-ADC-001 to KBA-ADC-IN-P03 for c:\windows\sysvol\domain using the DNS name RGH-ADC-001.domain.local. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name RGH-ADC-001.domain.local from this computer. [2] FRS is not running on RGH-ADC-001.domain.local. [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established. A warning event occurred. EventID: 0x800034C4 Time Generated: 04/02/2021 07:47:48 Event String: The File Replication Service is having trouble enabling replication from CHL-ADC-001 to KBA-ADC-IN-P03 for c:\windows\sysvol\domain using the DNS name CHL-ADC-001.domain.local. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name CHL-ADC-001.domain.local from this computer. [2] FRS is not running on CHL-ADC-001.domain.local. [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established. An error event occurred. EventID: 0xC0003502 Time Generated: 04/02/2021 08:07:58 Event String: The File Replication Service has detected that the volume hosting the path c: is low on disk space. Files may not replicate until disk space is made available on this volume. The available space on the volume can be found by typing "dir /a c:". For more information about managing space on a volume type "copy /?", "rename /?", "del /?", "rmdir /?", and "dir /?". An error event occurred. EventID: 0xC0003502 Time Generated: 04/02/2021 08:07:58 Event String: The File Replication Service has detected that the volume hosting the path C: is low on disk space. Files may not replicate until disk space is made available on this volume. The available space on the volume can be found by typing "dir /a C:". For more information about managing space on a volume type "copy /?", "rename /?", "del /?", "rmdir /?", and "dir /?". A warning event occurred. EventID: 0x80003509 Time Generated: 04/02/2021 08:27:43 Event String: File Replication Service (FRS) is deprecated. To continue replicating the SYSVOL folder, you should migrate to DFS Replication by using the DFSRMIG command. If you continue to use FRS for SYSVOL replication in this domain, you might not be able to add domain controllers running a future version of Windows Server. A warning event occurred. EventID: 0x800034C4 Time Generated: 04/02/2021 08:32:41 Event String: The File Replication Service is having trouble enabling replication from BDO-ADC-001 to KBA-ADC-IN-P03 for c:\windows\sysvol\domain using the DNS name BDO-ADC-001.domain.local. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name BDO-ADC-001.domain.local from this computer. [2] FRS is not running on BDO-ADC-001.domain.local. [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established. A warning event occurred. EventID: 0x800034C4 Time Generated: 04/02/2021 09:46:47 Event String: The File Replication Service is having trouble enabling replication from TKR-ADC-002 to KBA-ADC-IN-P03 for c:\windows\sysvol\domain using the DNS name TKR-ADC-002.domain.local. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name TKR-ADC-002.domain.local from this computer. [2] FRS is not running on TKR-ADC-002.domain.local. [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established. A warning event occurred. EventID: 0x800034C4 Time Generated: 04/02/2021 10:46:55 Event String: The File Replication Service is having trouble enabling replication from RGH-ADC-001 to KBA-ADC-IN-P03 for c:\windows\sysvol\domain using the DNS name RGH-ADC-001.domain.local. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name RGH-ADC-001.domain.local from this computer. [2] FRS is not running on RGH-ADC-001.domain.local. [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established. A warning event occurred. EventID: 0x800034C4 Time Generated: 04/02/2021 10:46:56 Event String: The File Replication Service is having trouble enabling replication from CHL-ADC-001 to KBA-ADC-IN-P03 for c:\windows\sysvol\domain using the DNS name CHL-ADC-001.domain.local. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name CHL-ADC-001.domain.local from this computer. [2] FRS is not running on CHL-ADC-001.domain.local. [3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established. ......................... KBA-ADC-IN-P03 failed test FrsEvent Starting test: DFSREvent The DFS Replication Event Log. Skip the test because the server is running FRS. ......................... KBA-ADC-IN-P03 passed test DFSREvent Starting test: SysVolCheck * The File Replication Service SYSVOL ready test File Replication Service's SYSVOL is ready ......................... KBA-ADC-IN-P03 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. ......................... KBA-ADC-IN-P03 passed test KccEvent Starting test: KnowsOfRoleHolders Role Schema Owner = CN=NTDS Settings,CN=KBA-ADC-IN-P02,CN=Servers,CN=domain-local,CN=Sites,CN=Configuration,DC=domain,DC=local Role Domain Owner = CN=NTDS Settings,CN=KBA-ADC-IN-P03,CN=Servers,CN=domain-local,CN=Sites,CN=Configuration,DC=domain,DC=local Role PDC Owner = CN=NTDS Settings,CN=KBA-ADC-IN-P03,CN=Servers,CN=domain-local,CN=Sites,CN=Configuration,DC=domain,DC=local Role Rid Owner = CN=NTDS Settings,CN=KBA-ADC-IN-P03,CN=Servers,CN=domain-local,CN=Sites,CN=Configuration,DC=domain,DC=local Role Infrastructure Update Owner = CN=NTDS Settings,CN=KBA-ADC-IN-P02,CN=Servers,CN=domain-local,CN=Sites,CN=Configuration,DC=domain,DC=local ......................... KBA-ADC-IN-P03 passed test KnowsOfRoleHolders Starting test: MachineAccount Checking machine account for DC KBA-ADC-IN-P03 on DC KBA-ADC-IN-P03. * SPN found :LDAP/KBA-ADC-IN-P03.domain.local/domain.local * SPN found :LDAP/KBA-ADC-IN-P03.domain.local * SPN found :LDAP/KBA-ADC-IN-P03 * SPN found :LDAP/KBA-ADC-IN-P03.domain.local/domainlocal * SPN found :LDAP/8d3eefc4-0ceb-41a8-b541-fa09a5b8392c._msdcs.domain.local * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/8d3eefc4-0ceb-41a8-b541-fa09a5b8392c/domain.local * SPN found :HOST/KBA-ADC-IN-P03.domain.local/domain.local * SPN found :HOST/KBA-ADC-IN-P03.domain.local * SPN found :HOST/KBA-ADC-IN-P03 * SPN found :HOST/KBA-ADC-IN-P03.domain.local/domainlocal * SPN found :GC/KBA-ADC-IN-P03.domain.local/domain.local ......................... KBA-ADC-IN-P03 passed test MachineAccount Starting test: NCSecDesc * Security Permissions check for all NC's on DC KBA-ADC-IN-P03. * Security Permissions Check for DC=ForestDnsZones,DC=domain,DC=local (NDNC,Version 3) * Security Permissions Check for DC=DomainDnsZones,DC=domain,DC=local (NDNC,Version 3) * Security Permissions Check for CN=Schema,CN=Configuration,DC=domain,DC=local (Schema,Version 3) * Security Permissions Check for CN=Configuration,DC=domain,DC=local (Configuration,Version 3) * Security Permissions Check for DC=domain,DC=local (Domain,Version 3) ......................... KBA-ADC-IN-P03 passed test NCSecDesc Starting test: NetLogons * Network Logons Privileges Check Verified share \\KBA-ADC-IN-P03\netlogon Verified share \\KBA-ADC-IN-P03\sysvol ......................... KBA-ADC-IN-P03 passed test NetLogons Starting test: ObjectsReplicated KBA-ADC-IN-P03 is in domain DC=domain,DC=local Checking for CN=KBA-ADC-IN-P03,OU=Domain Controllers,DC=domain,DC=local in domain DC=domain,DC=local on 3 servers Object is up-to-date on all servers. Checking for CN=NTDS Settings,CN=KBA-ADC-IN-P03,CN=Servers,CN=domain-local,CN=Sites,CN=Configuration,DC=domain,DC=local in domain CN=Configuration,DC=domain,DC=local on 3 servers Object is up-to-date on all servers. ......................... KBA-ADC-IN-P03 passed test ObjectsReplicated Test omitted by user request: OutboundSecureChannels Starting test: Replications * Replications Check * Replication Latency Check DC=ForestDnsZones,DC=domain,DC=local Latency information for 257 entries in the vector were ignored. 257 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=domain,DC=local Latency information for 258 entries in the vector were ignored. 258 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=domain,DC=local Latency information for 265 entries in the vector were ignored. 265 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=domain,DC=local Latency information for 266 entries in the vector were ignored. 266 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=domain,DC=local Latency information for 264 entries in the vector were ignored. 264 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). ......................... KBA-ADC-IN-P03 passed test Replications Starting test: RidManager * Available RID Pool for the Domain is 193100 to 1073741823 * KBA-ADC-IN-P03.domain.local is the RID Master * DsBind with RID Master was successful * rIDAllocationPool is 189600 to 190099 * rIDPreviousAllocationPool is 189600 to 190099 * rIDNextRID: 189684 ......................... KBA-ADC-IN-P03 passed test RidManager Starting test: Services * Checking Service: EventSystem * Checking Service: RpcSs * Checking Service: NTDS * Checking Service: DnsCache * Checking Service: NtFrs * Checking Service: IsmServ * Checking Service: kdc * Checking Service: SamSs * Checking Service: LanmanServer * Checking Service: LanmanWorkstation * Checking Service: w32time * Checking Service: NETLOGON ......................... KBA-ADC-IN-P03 passed test Services Starting test: SystemLog * The System Event log test An error event occurred. EventID: 0x0000165B Time Generated: 04/02/2021 11:29:21 Event String: The session setup from computer 'domain-MGR-X7-2' failed because the security database does not contain a trust account 'domain-MGR-X7-2$' referenced by the specified computer. USER ACTION If this is the first occurrence of this event for the specified computer and account, this may be a transient issue that doesn't require any action at this time. If this is a Read-Only Domain Controller and 'domain-MGR-X7-2$' is a legitimate machine account for the computer 'domain-MGR-X7-2' then 'domain-MGR-X7-2' should be marked cacheable for this location if appropriate or otherwise ensure connectivity to a domain controller capable of servicing the request (for example a writable domain controller). Otherwise, the following steps may be taken to resolve this problem: If 'domain-MGR-X7-2$' is a legitimate machine account for the computer 'domain-MGR-X7-2', then 'domain-MGR-X7-2' should be rejoined to the domain. If 'domain-MGR-X7-2$' is a legitimate interdomain trust account, then the trust should be recreated. Otherwise, assuming that 'domain-MGR-X7-2$' is not a legitimate account, the following action should be taken on 'domain-MGR-X7-2': If 'domain-MGR-X7-2' is a Domain Controller, then the trust associated with 'domain-MGR-X7-2$' should be deleted. If 'domain-MGR-X7-2' is not a Domain Controller, it should be disjoined from the domain. An error event occurred. EventID: 0x000016AD Time Generated: 04/02/2021 11:31:34 Event String: The session setup from the computer domain-MGR-X7-2 failed to authenticate. The following error occurred: Access is denied. An error event occurred. EventID: 0x0000165B Time Generated: 04/02/2021 11:41:05 Event String: The session setup from computer 'KBA-SOTI-IN-P01' failed because the security database does not contain a trust account 'KBA-SOTI-IN-P01$' referenced by the specified computer. USER ACTION If this is the first occurrence of this event for the specified computer and account, this may be a transient issue that doesn't require any action at this time. If this is a Read-Only Domain Controller and 'KBA-SOTI-IN-P01$' is a legitimate machine account for the computer 'KBA-SOTI-IN-P01' then 'KBA-SOTI-IN-P01' should be marked cacheable for this location if appropriate or otherwise ensure connectivity to a domain controller capable of servicing the request (for example a writable domain controller). Otherwise, the following steps may be taken to resolve this problem: If 'KBA-SOTI-IN-P01$' is a legitimate machine account for the computer 'KBA-SOTI-IN-P01', then 'KBA-SOTI-IN-P01' should be rejoined to the domain. If 'KBA-SOTI-IN-P01$' is a legitimate interdomain trust account, then the trust should be recreated. Otherwise, assuming that 'KBA-SOTI-IN-P01$' is not a legitimate account, the following action should be taken on 'KBA-SOTI-IN-P01': If 'KBA-SOTI-IN-P01' is a Domain Controller, then the trust associated with 'KBA-SOTI-IN-P01$' should be deleted. If 'KBA-SOTI-IN-P01' is not a Domain Controller, it should be disjoined from the domain. An error event occurred. EventID: 0x0000165B Time Generated: 04/02/2021 11:42:16 Event String: The session setup from computer 'WS-03-001' failed because the security database does not contain a trust account 'WS-03-001$' referenced by the specified computer. USER ACTION If this is the first occurrence of this event for the specified computer and account, this may be a transient issue that doesn't require any action at this time. If this is a Read-Only Domain Controller and 'WS-03-001$' is a legitimate machine account for the computer 'WS-03-001' then 'WS-03-001' should be marked cacheable for this location if appropriate or otherwise ensure connectivity to a domain controller capable of servicing the request (for example a writable domain controller). Otherwise, the following steps may be taken to resolve this problem: If 'WS-03-001$' is a legitimate machine account for the computer 'WS-03-001', then 'WS-03-001' should be rejoined to the domain. If 'WS-03-001$' is a legitimate interdomain trust account, then the trust should be recreated. Otherwise, assuming that 'WS-03-001$' is not a legitimate account, the following action should be taken on 'WS-03-001': If 'WS-03-001' is a Domain Controller, then the trust associated with 'WS-03-001$' should be deleted. If 'WS-03-001' is not a Domain Controller, it should be disjoined from the domain. An error event occurred. EventID: 0x000016AD Time Generated: 04/02/2021 11:46:34 Event String: The session setup from the computer KBA-SOTI-IN-P01 failed to authenticate. The following error occurred: Access is denied. An error event occurred. EventID: 0x000016AD Time Generated: 04/02/2021 11:46:34 Event String: The session setup from the computer WS-03-001 failed to authenticate. The following error occurred: Access is denied. An error event occurred. EventID: 0x0000165B Time Generated: 04/02/2021 11:48:20 Event String: The session setup from computer 'domain-VMM-BDD' failed because the security database does not contain a trust account 'domain-VMM-BDD$' referenced by the specified computer. USER ACTION If this is the first occurrence of this event for the specified computer and account, this may be a transient issue that doesn't require any action at this time. If this is a Read-Only Domain Controller and 'domain-VMM-BDD$' is a legitimate machine account for the computer 'domain-VMM-BDD' then 'domain-VMM-BDD' should be marked cacheable for this location if appropriate or otherwise ensure connectivity to a domain controller capable of servicing the request (for example a writable domain controller). Otherwise, the following steps may be taken to resolve this problem: If 'domain-VMM-BDD$' is a legitimate machine account for the computer 'domain-VMM-BDD', then 'domain-VMM-BDD' should be rejoined to the domain. If 'domain-VMM-BDD$' is a legitimate interdomain trust account, then the trust should be recreated. Otherwise, assuming that 'domain-VMM-BDD$' is not a legitimate account, the following action should be taken on 'domain-VMM-BDD': If 'domain-VMM-BDD' is a Domain Controller, then the trust associated with 'domain-VMM-BDD$' should be deleted. If 'domain-VMM-BDD' is not a Domain Controller, it should be disjoined from the domain. An error event occurred. EventID: 0x0000165B Time Generated: 04/02/2021 11:48:44 Event String: The session setup from computer 'KBA-NTB-IN-T02' failed because the security database does not contain a trust account 'KBA-NTB-IN-T02$' referenced by the specified computer. USER ACTION If this is the first occurrence of this event for the specified computer and account, this may be a transient issue that doesn't require any action at this time. If this is a Read-Only Domain Controller and 'KBA-NTB-IN-T02$' is a legitimate machine account for the computer 'KBA-NTB-IN-T02' then 'KBA-NTB-IN-T02' should be marked cacheable for this location if appropriate or otherwise ensure connectivity to a domain controller capable of servicing the request (for example a writable domain controller). Otherwise, the following steps may be taken to resolve this problem: If 'KBA-NTB-IN-T02$' is a legitimate machine account for the computer 'KBA-NTB-IN-T02', then 'KBA-NTB-IN-T02' should be rejoined to the domain. If 'KBA-NTB-IN-T02$' is a legitimate interdomain trust account, then the trust should be recreated. Otherwise, assuming that 'KBA-NTB-IN-T02$' is not a legitimate account, the following action should be taken on 'KBA-NTB-IN-T02': If 'KBA-NTB-IN-T02' is a Domain Controller, then the trust associated with 'KBA-NTB-IN-T02$' should be deleted. If 'KBA-NTB-IN-T02' is not a Domain Controller, it should be disjoined from the domain. An error event occurred. EventID: 0x000016AD Time Generated: 04/02/2021 11:51:54 Event String: The session setup from the computer domain-VMM-BDD failed to authenticate. The following error occurred: Access is denied. An error event occurred. EventID: 0x000016AD Time Generated: 04/02/2021 11:51:54 Event String: The session setup from the computer KBA-NTB-IN-T02 failed to authenticate. The following error occurred: Access is denied. ......................... KBA-ADC-IN-P03 failed test SystemLog Test omitted by user request: Topology Test omitted by user request: VerifyEnterpriseReferences Starting test: VerifyReferences The system object reference (serverReference) CN=KBA-ADC-IN-P03,OU=Domain Controllers,DC=domain,DC=local and backlink on CN=KBA-ADC-IN-P03,CN=Servers,CN=domain-local,CN=Sites,CN=Configuration,DC=domain,DC=local are correct. The system object reference (serverReferenceBL) CN=KBA-ADC-IN-P03,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=domain,DC=local and backlink on CN=NTDS Settings,CN=KBA-ADC-IN-P03,CN=Servers,CN=domain-local,CN=Sites,CN=Configuration,DC=domain,DC=local are correct. The system object reference (frsComputerReferenceBL) CN=KBA-ADC-IN-P03,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=domain,DC=local and backlink on CN=KBA-ADC-IN-P03,OU=Domain Controllers,DC=domain,DC=local are correct. ......................... KBA-ADC-IN-P03 passed test VerifyReferences Test omitted by user request: VerifyReplicas Testing server: domain-local\KBA-ADC-IN-P05 Starting test: Advertising The DC KBA-ADC-IN-P05 is advertising itself as a DC and having a DS. The DC KBA-ADC-IN-P05 is advertising as an LDAP server The DC KBA-ADC-IN-P05 is advertising as having a writeable directory The DC KBA-ADC-IN-P05 is advertising as a Key Distribution Center Warning: KBA-ADC-IN-P05 is not advertising as a time server. The DS KBA-ADC-IN-P05 is advertising as a GC. ......................... KBA-ADC-IN-P05 failed test Advertising Test omitted by user request: CheckSecurityError Test omitted by user request: CutoffServers Starting test: FrsEvent * The File Replication Service Event log test 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: 0x80003509 Time Generated: 04/01/2021 19:33:11 Event String: File Replication Service (FRS) is deprecated. To continue replicating the SYSVOL folder, you should migrate to DFS Replication by using the DFSRMIG command. If you continue to use FRS for SYSVOL replication in this domain, you might not be able to add domain controllers running a future version of Windows Server. A warning event occurred. EventID: 0x80003509 Time Generated: 04/01/2021 19:39:40 Event String: File Replication Service (FRS) is deprecated. To continue replicating the SYSVOL folder, you should migrate to DFS Replication by using the DFSRMIG command. If you continue to use FRS for SYSVOL replication in this domain, you might not be able to add domain controllers running a future version of Windows Server. A warning event occurred. EventID: 0x800034FD Time Generated: 04/01/2021 19:39:45 Event String: File Replication Service is initializing the system volume with data from another domain controller. Computer KBA-ADC-IN-P05 cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL. To check for the SYSVOL share, at the command prompt, type: net share When File Replication Service completes the initialization process, the SYSVOL share will appear. The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume, the availability of other domain controllers, and the replication interval between domain controllers. A warning event occurred. EventID: 0x80003509 Time Generated: 04/01/2021 19:55:25 Event String: File Replication Service (FRS) is deprecated. To continue replicating the SYSVOL folder, you should migrate to DFS Replication by using the DFSRMIG command. If you continue to use FRS for SYSVOL replication in this domain, you might not be able to add domain controllers running a future version of Windows Server. A warning event occurred. EventID: 0x800034FD Time Generated: 04/01/2021 19:55:30 Event String: File Replication Service is initializing the system volume with data from another domain controller. Computer KBA-ADC-IN-P05 cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL. To check for the SYSVOL share, at the command prompt, type: net share When File Replication Service completes the initialization process, the SYSVOL share will appear. The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume, the availability of other domain controllers, and the replication interval between domain controllers. ......................... KBA-ADC-IN-P05 passed test FrsEvent Starting test: DFSREvent The DFS Replication Event Log. Skip the test because the server is running FRS. ......................... KBA-ADC-IN-P05 passed test DFSREvent Starting test: SysVolCheck * The File Replication Service SYSVOL ready test File Replication Service's SYSVOL is ready ......................... KBA-ADC-IN-P05 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. ......................... KBA-ADC-IN-P05 passed test KccEvent Starting test: KnowsOfRoleHolders Role Schema Owner = CN=NTDS Settings,CN=KBA-ADC-IN-P02,CN=Servers,CN=domain-local,CN=Sites,CN=Configuration,DC=domain,DC=local Role Domain Owner = CN=NTDS Settings,CN=KBA-ADC-IN-P03,CN=Servers,CN=domain-local,CN=Sites,CN=Configuration,DC=domain,DC=local Role PDC Owner = CN=NTDS Settings,CN=KBA-ADC-IN-P03,CN=Servers,CN=domain-local,CN=Sites,CN=Configuration,DC=domain,DC=local Role Rid Owner = CN=NTDS Settings,CN=KBA-ADC-IN-P03,CN=Servers,CN=domain-local,CN=Sites,CN=Configuration,DC=domain,DC=local Role Infrastructure Update Owner = CN=NTDS Settings,CN=KBA-ADC-IN-P02,CN=Servers,CN=domain-local,CN=Sites,CN=Configuration,DC=domain,DC=local ......................... KBA-ADC-IN-P05 passed test KnowsOfRoleHolders Starting test: MachineAccount Checking machine account for DC KBA-ADC-IN-P05 on DC KBA-ADC-IN-P05. * SPN found :LDAP/KBA-ADC-IN-P05.domain.local/domain.local * SPN found :LDAP/KBA-ADC-IN-P05.domain.local * SPN found :LDAP/KBA-ADC-IN-P05 * SPN found :LDAP/KBA-ADC-IN-P05.domain.local/domainlocal * SPN found :LDAP/19013d3c-4afe-452e-9f42-8adf49b0899a._msdcs.domain.local * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/19013d3c-4afe-452e-9f42-8adf49b0899a/domain.local * SPN found :HOST/KBA-ADC-IN-P05.domain.local/domain.local * SPN found :HOST/KBA-ADC-IN-P05.domain.local * SPN found :HOST/KBA-ADC-IN-P05 * SPN found :HOST/KBA-ADC-IN-P05.domain.local/domainlocal * SPN found :GC/KBA-ADC-IN-P05.domain.local/domain.local ......................... KBA-ADC-IN-P05 passed test MachineAccount Starting test: NCSecDesc * Security Permissions check for all NC's on DC KBA-ADC-IN-P05. * Security Permissions Check for DC=ForestDnsZones,DC=domain,DC=local (NDNC,Version 3) * Security Permissions Check for DC=DomainDnsZones,DC=domain,DC=local (NDNC,Version 3) * Security Permissions Check for CN=Schema,CN=Configuration,DC=domain,DC=local (Schema,Version 3) * Security Permissions Check for CN=Configuration,DC=domain,DC=local (Configuration,Version 3) * Security Permissions Check for DC=domain,DC=local (Domain,Version 3) ......................... KBA-ADC-IN-P05 passed test NCSecDesc Starting test: NetLogons * Network Logons Privileges Check Verified share \\KBA-ADC-IN-P05\netlogon Verified share \\KBA-ADC-IN-P05\sysvol ......................... KBA-ADC-IN-P05 passed test NetLogons Starting test: ObjectsReplicated KBA-ADC-IN-P05 is in domain DC=domain,DC=local Checking for CN=KBA-ADC-IN-P05,OU=Domain Controllers,DC=domain,DC=local in domain DC=domain,DC=local on 3 servers Object is up-to-date on all servers. Checking for CN=NTDS Settings,CN=KBA-ADC-IN-P05,CN=Servers,CN=domain-local,CN=Sites,CN=Configuration,DC=domain,DC=local in domain CN=Configuration,DC=domain,DC=local on 3 servers Object is up-to-date on all servers. ......................... KBA-ADC-IN-P05 passed test ObjectsReplicated Test omitted by user request: OutboundSecureChannels Starting test: Replications * Replications Check * Replication Latency Check DC=ForestDnsZones,DC=domain,DC=local Latency information for 257 entries in the vector were ignored. 257 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=domain,DC=local Latency information for 258 entries in the vector were ignored. 258 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=domain,DC=local Latency information for 265 entries in the vector were ignored. 265 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=domain,DC=local Latency information for 266 entries in the vector were ignored. 266 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=domain,DC=local Latency information for 264 entries in the vector were ignored. 264 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). ......................... KBA-ADC-IN-P05 passed test Replications Starting test: RidManager * Available RID Pool for the Domain is 193100 to 1073741823 * KBA-ADC-IN-P03.domain.local is the RID Master * DsBind with RID Master was successful * rIDAllocationPool is 192600 to 193099 * rIDPreviousAllocationPool is 192600 to 193099 * rIDNextRID: 192600 ......................... KBA-ADC-IN-P05 passed test RidManager Starting test: Services * Checking Service: EventSystem * Checking Service: RpcSs * Checking Service: NTDS * Checking Service: DnsCache * Checking Service: NtFrs * Checking Service: IsmServ * Checking Service: kdc * Checking Service: SamSs * Checking Service: LanmanServer * Checking Service: LanmanWorkstation * Checking Service: w32time * Checking Service: NETLOGON ......................... KBA-ADC-IN-P05 passed test Services Starting test: SystemLog * The System Event log test An error event occurred. EventID: 0x0000165B Time Generated: 04/02/2021 11:24:51 Event String: The session setup from computer 'UC-12-008' failed because the security database does not contain a trust account 'UC-12-008$' referenced by the specified computer. USER ACTION If this is the first occurrence of this event for the specified computer and account, this may be a transient issue that doesn't require any action at this time. If this is a Read-Only Domain Controller and 'UC-12-008$' is a legitimate machine account for the computer 'UC-12-008' then 'UC-12-008' should be marked cacheable for this location if appropriate or otherwise ensure connectivity to a domain controller capable of servicing the request (for example a writable domain controller). Otherwise, the following steps may be taken to resolve this problem: If 'UC-12-008$' is a legitimate machine account for the computer 'UC-12-008', then 'UC-12-008' should be rejoined to the domain. If 'UC-12-008$' is a legitimate interdomain trust account, then the trust should be recreated. Otherwise, assuming that 'UC-12-008$' is not a legitimate account, the following action should be taken on 'UC-12-008': If 'UC-12-008' is a Domain Controller, then the trust associated with 'UC-12-008$' should be deleted. If 'UC-12-008' is not a Domain Controller, it should be disjoined from the domain. An error event occurred. EventID: 0x0000165B Time Generated: 04/02/2021 11:25:31 Event String: The session setup from computer 'WS-03-001' failed because the security database does not contain a trust account 'WS-03-001$' referenced by the specified computer. USER ACTION If this is the first occurrence of this event for the specified computer and account, this may be a transient issue that doesn't require any action at this time. If this is a Read-Only Domain Controller and 'WS-03-001$' is a legitimate machine account for the computer 'WS-03-001' then 'WS-03-001' should be marked cacheable for this location if appropriate or otherwise ensure connectivity to a domain controller capable of servicing the request (for example a writable domain controller). Otherwise, the following steps may be taken to resolve this problem: If 'WS-03-001$' is a legitimate machine account for the computer 'WS-03-001', then 'WS-03-001' should be rejoined to the domain. If 'WS-03-001$' is a legitimate interdomain trust account, then the trust should be recreated. Otherwise, assuming that 'WS-03-001$' is not a legitimate account, the following action should be taken on 'WS-03-001': If 'WS-03-001' is a Domain Controller, then the trust associated with 'WS-03-001$' should be deleted. If 'WS-03-001' is not a Domain Controller, it should be disjoined from the domain. An error event occurred. EventID: 0x000016AD Time Generated: 04/02/2021 11:30:31 Event String: The session setup from the computer UC-12-008 failed to authenticate. The following error occurred: Access is denied. An error event occurred. EventID: 0x000016AD Time Generated: 04/02/2021 11:30:31 Event String: The session setup from the computer WS-03-001 failed to authenticate. The following error occurred: Access is denied. An error event occurred. EventID: 0x0000165B Time Generated: 04/02/2021 11:30:31 Event String: The session setup from computer 'domain-VMM-001' failed because the security database does not contain a trust account 'domain-VMM-001$' referenced by the specified computer. USER ACTION If this is the first occurrence of this event for the specified computer and account, this may be a transient issue that doesn't require any action at this time. If this is a Read-Only Domain Controller and 'domain-VMM-001$' is a legitimate machine account for the computer 'domain-VMM-001' then 'domain-VMM-001' should be marked cacheable for this location if appropriate or otherwise ensure connectivity to a domain controller capable of servicing the request (for example a writable domain controller). Otherwise, the following steps may be taken to resolve this problem: If 'domain-VMM-001$' is a legitimate machine account for the computer 'domain-VMM-001', then 'domain-VMM-001' should be rejoined to the domain. If 'domain-VMM-001$' is a legitimate interdomain trust account, then the trust should be recreated. Otherwise, assuming that 'domain-VMM-001$' is not a legitimate account, the following action should be taken on 'domain-VMM-001': If 'domain-VMM-001' is a Domain Controller, then the trust associated with 'domain-VMM-001$' should be deleted. If 'domain-VMM-001' is not a Domain Controller, it should be disjoined from the domain. An error event occurred. EventID: 0x000016AD Time Generated: 04/02/2021 11:35:26 Event String: The session setup from the computer domain-VMM-001 failed to authenticate. The following error occurred: Access is denied. ......................... KBA-ADC-IN-P05 failed test SystemLog Test omitted by user request: Topology Test omitted by user request: VerifyEnterpriseReferences Starting test: VerifyReferences The system object reference (serverReference) CN=KBA-ADC-IN-P05,OU=Domain Controllers,DC=domain,DC=local and backlink on CN=KBA-ADC-IN-P05,CN=Servers,CN=domain-local,CN=Sites,CN=Configuration,DC=domain,DC=local are correct. The system object reference (serverReferenceBL) CN=KBA-ADC-IN-P05,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=domain,DC=local and backlink on CN=NTDS Settings,CN=KBA-ADC-IN-P05,CN=Servers,CN=domain-local,CN=Sites,CN=Configuration,DC=domain,DC=local are correct. The system object reference (frsComputerReferenceBL) CN=KBA-ADC-IN-P05,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=domain,DC=local and backlink on CN=KBA-ADC-IN-P05,OU=Domain Controllers,DC=domain,DC=local are correct. ......................... KBA-ADC-IN-P05 passed test VerifyReferences Test omitted by user request: VerifyReplicas Test omitted by user request: DNS Test omitted by user request: DNS Test omitted by user request: DNS Test omitted by user request: DNS Test omitted by user request: DNS Test omitted by user request: 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 : domain Starting test: CheckSDRefDom ......................... domain passed test CheckSDRefDom Starting test: CrossRefValidation ......................... domain passed test CrossRefValidation Running enterprise tests on : domain.local Test omitted by user request: DNS Test omitted by user request: DNS Starting test: LocatorCheck GC Name: \\KBA-ADC-IN-P03.domain.local Locator Flags: 0xe003d3fd PDC Name: \\KBA-ADC-IN-P03.domain.local Locator Flags: 0xe003d3fd Time Server Name: \\KBA-ADC-IN-P03.domain.local Locator Flags: 0xe003d3fd Preferred Time Server Name: \\KBA-ADC-IN-P03.domain.local Locator Flags: 0xe003d3fd KDC Name: \\KBA-ADC-IN-P03.domain.local Locator Flags: 0xe003d3fd ......................... domain.local passed test LocatorCheck Starting test: Intersite Skipping site Zeralda, this site is outside the scope provided by the command line arguments provided. Skipping site Draria, this site is outside the scope provided by the command line arguments provided. Skipping site Chenoua, this site is outside the scope provided by the command line arguments provided. Skipping site Tipaza-Port, this site is outside the scope provided by the command line arguments provided. Skipping site Zeralda-agence, this site is outside the scope provided by the command line arguments provided. Skipping site Bouzereah, this site is outside the scope provided by the command line arguments provided. Skipping site Baba-hassen, this site is outside the scope provided by the command line arguments provided. Skipping site Saada, this site is outside the scope provided by the command line arguments provided. Skipping site Beni-Messous-STEP, this site is outside the scope provided by the command line arguments provided. Skipping site Tessala-El-Merdja, this site is outside the scope provided by the command line arguments provided. Skipping site Reghaia, this site is outside the scope provided by the command line arguments provided. Skipping site Birtouta-Nouvelle-Ville, this site is outside the scope provided by the command line arguments provided. Skipping site Baraki, this site is outside the scope provided by the command line arguments provided. Skipping site Rouiba-Centre, this site is outside the scope provided by the command line arguments provided. Skipping site Hussein-Dey, this site is outside the scope provided by the command line arguments provided. Skipping site Bab-Ezzouar-STEP, this site is outside the scope provided by the command line arguments provided. Skipping site Birtouta-Centre-Ass, this site is outside the scope provided by the command line arguments provided. Skipping site Fouka, this site is outside the scope provided by the command line arguments provided. Skipping site Douaouda, this site is outside the scope provided by the command line arguments provided. Skipping site Manaceur-Caisse, this site is outside the scope provided by the command line arguments provided. Skipping site SidiAmmer-Centre, this site is outside the scope provided by the command line arguments provided. Skipping site SidAmmer-Caisse, this site is outside the scope provided by the command line arguments provided. Skipping site Bousmail, this site is outside the scope provided by the command line arguments provided. Skipping site Chaiba, this site is outside the scope provided by the command line arguments provided. Skipping site Ahmeur-Ain-Caisse, this site is outside the scope provided by the command line arguments provided. Skipping site Hadjout-Ass, this site is outside the scope provided by the command line arguments provided. Skipping site Kolea-Centre, this site is outside the scope provided by the command line arguments provided. Skipping site Gouraya, this site is outside the scope provided by the command line arguments provided. Skipping site Bousmail-Agence, this site is outside the scope provided by the command line arguments provided. Skipping site BabaHacene-ASS, this site is outside the scope provided by the command line arguments provided. Skipping site RV2000, this site is outside the scope provided by the command line arguments provided. Skipping site Birkhadem-DD, this site is outside the scope provided by the command line arguments provided. Skipping site Mohamadia-DD, this site is outside the scope provided by the command line arguments provided. Skipping site Hydra-Magasin, this site is outside the scope provided by the command line arguments provided. Skipping site Ainbenian-Agence, this site is outside the scope provided by the command line arguments provided. Skipping site Sidiabdellah, this site is outside the scope provided by the command line arguments provided. Skipping site CATO, this site is outside the scope provided by the command line arguments provided. Skipping site FRAIS-VALLONS, this site is outside the scope provided by the command line arguments provided. Skipping site Garidi, this site is outside the scope provided by the command line arguments provided. Skipping site AINNAADJA, this site is outside the scope provided by the command line arguments provided. Skipping site Alger-Centre, this site is outside the scope provided by the command line arguments provided. Skipping site Bachdjerah-Assainissement, this site is outside the scope provided by the command line arguments provided. Skipping site Staouali-Step, this site is outside the scope provided by the command line arguments provided. Skipping site Kolea, this site is outside the scope provided by the command line arguments provided. Skipping site Staoueli-Distribution, this site is outside the scope provided by the command line arguments provided. Skipping site Saa, this site is outside the scope provided by the command line arguments provided. Skipping site Beb-El-Oued, this site is outside the scope provided by the command line arguments provided. Skipping site Tikarouchine, this site is outside the scope provided by the command line arguments provided. Skipping site Boumati, this site is outside the scope provided by the command line arguments provided. Skipping site Baraki-Step, this site is outside the scope provided by the command line arguments provided. Skipping site Cherarba, this site is outside the scope provided by the command line arguments provided. Skipping site Dely-Ibrahim, this site is outside the scope provided by the command line arguments provided. Skipping site Didouche-Mourad, this site is outside the scope provided by the command line arguments provided. Skipping site Douera, this site is outside the scope provided by the command line arguments provided. Skipping site Rouiba, this site is outside the scope provided by the command line arguments provided. Skipping site Draria-Centre, this site is outside the scope provided by the command line arguments provided. Skipping site Cherchel-Agence, this site is outside the scope provided by the command line arguments provided. Skipping site Appreval, this site is outside the scope provided by the command line arguments provided. Skipping site Bir-Mourad-Rais, this site is outside the scope provided by the command line arguments provided. Skipping site badjarah, this site is outside the scope provided by the command line arguments provided. Skipping site Parc-Central, this site is outside the scope provided by the command line arguments provided. Skipping site Cheraga, this site is outside the scope provided by the command line arguments provided. Skipping site Dar-El-Beida, this site is outside the scope provided by the command line arguments provided. Skipping site Birtouta, this site is outside the scope provided by the command line arguments provided. Skipping site Bab-Ezzouar, this site is outside the scope provided by the command line arguments provided. Skipping site Bordj-El-Kiffan, this site is outside the scope provided by the command line arguments provided. Skipping site Gue-Constantine, this site is outside the scope provided by the command line arguments provided. Skipping site Prise-Deau, this site is outside the scope provided by the command line arguments provided. Skipping site Boudouaou, this site is outside the scope provided by the command line arguments provided. Skipping site Appreval2, this site is outside the scope provided by the command line arguments provided. Skipping site Bentalha-Centre, this site is outside the scope provided by the command line arguments provided. Skipping site Sebala, this site is outside the scope provided by the command line arguments provided. Skipping site Taksebt-Centre, this site is outside the scope provided by the command line arguments provided. Skipping site Reghaia-STEP, this site is outside the scope provided by the command line arguments provided. Doing intersite inbound replication test on site domain-local: Locating & Contacting Intersite Topology Generator (ISTG) ... The ISTG for site domain-local is: KBA-ADC-IN-P02. Checking for down bridgeheads ... Bridghead Cherarba\CRB-ADC-001 is up and replicating fine. Bridghead domain-local\KBA-ADC-IN-P03 is up and replicating fine. Bridghead Cherchel-Agence\CHL-ADC-001 is up and replicating fine. Bridghead Bir-Mourad-Rais\BMR-ADC-001 is up and replicating fine. Bridghead Taksebt-Centre\TKS-ADC-001 is up and replicating fine. Bridghead Baraki-Step\BAR-ADC-003 is up and replicating fine. Bridghead Appreval2\APP-ADC-005 is up and replicating fine. Bridghead Parc-Central\PRC-ADC-004 is up and replicating fine. Bridghead AINNAADJA\AIN-ADC-002 is up and replicating fine. Bridghead Tikarouchine\TKR-ADC-002 is up and replicating fine. Bridghead Boudouaou\BDO-ADC-001 is up and replicating fine. Bridghead Reghaia-STEP\RGH-ADC-001 is up and replicating fine. Bridghead Garidi\GRD-ADC-001 is up and replicating fine. Doing in depth site analysis ... All expected sites and bridgeheads are replicating into site domain-local. ......................... domain.local passed test Intersite