Reset Password · PC & Mac Help and Assistance

Welcome Guest! To enable all features please Login or Register

Posted by: Lemonde - 10 March 2021 10:16:26
What can we do about this error? It was the only good DC in the domain as the other one is broken. Log Name: Directory Service Source: Microsoft-Windows-ActiveDirectory_DomainService Date: 10/03/2021 09:51:23 Event ID: 2092 Task Category: Replication Level: Warning Keywords: Classic User: ANONYMOUS LOGON Computer: dc01.domain.local Description: This server is the owner of the following FSMO role, but does not consider it valid. For the partition which contains the FSMO, this server has not replicated successfully with any of its partners since this server has been restarted. Replication errors are preventing validation of this role. Operations which require contacting a FSMO operation master will fail until this condition is corrected. FSMO Role: DC=domain,DC=local User Action: 1. Initial synchronization is the first early replications done by a system as it is starting. A failure to initially synchronize may explain why a FSMO role cannot be validated. This process is explained in KB article 305476. 2. This server has one or more replication partners, and replication is failing for all of these partners. Use the command repadmin /showrepl to display the replication errors. Correct the error in question. For example there maybe problems with IP connectivity, DNS name resolution, or security authentication that are preventing successful replication. 3. In the rare event that all replication partners being down is an expected occurance, perhaps because of maintenance or a disaster recovery, you can force the role to be validated. This can be done by using NTDSUTIL.EXE to seize the role to the same server. This may be done using the steps provided in KB articles 255504 and 324801 on http://support.microsoft.com. The following operations may be impacted: Schema: You will no longer be able to modify the schema for this forest. Domain Naming: You will no longer be able to add or remove domains from this forest. PDC: You will no longer be able to perform primary domain controller operations, such as Group Policy updates and password resets for non-Active Directory Domain Services accounts. RID: You will not be able to allocation new security identifiers for new user accounts, computer accounts or security groups. Infrastructure: Cross-domain name references, such as universal group memberships, will not be updated properly if their target object is moved or renamed. Event Xml: [code=markup]<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-ActiveDirectory_DomainService" Guid="{0e8478c5-3605-4e8c-8497-1e730c959516}" EventSourceName="NTDS General" /> <EventID Qualifiers="32768">2092</EventID> <Version>0</Version> <Level>3</Level> <Task>5</Task> <Opcode>0</Opcode> <Keywords>0x8080000000000000</Keywords> <TimeCreated SystemTime="2021-03-10T09:51:23.813750000Z" /> <EventRecordID>16180</EventRecordID> <Correlation /> <Execution ProcessID="584" ThreadID="720" /> <Channel>Directory Service</Channel> <Computer>dc01.domain.local</Computer> <Security UserID="S-1-5-7" /> </System> <EventData> <Data>DC=domain,DC=local</Data> </EventData> </Event> [/code]

Posted by: Lemonde - 10 March 2021 10:16:26

What can we do about this error? It was the only good DC in the domain as the other one is broken. Log Name: Directory Service Source: Microsoft-Windows-ActiveDirectory_DomainService Date: 10/03/2021 09:51:23 Event ID: 2092 Task Category: Replication Level: Warning Keywords: Classic User: ANONYMOUS LOGON Computer: dc01.domain.local Description: This server is the owner of the following FSMO role, but does not consider it valid. For the partition which contains the FSMO, this server has not replicated successfully with any of its partners since this server has been restarted. Replication errors are preventing validation of this role. Operations which require contacting a FSMO operation master will fail until this condition is corrected. FSMO Role: DC=domain,DC=local User Action: 1. Initial synchronization is the first early replications done by a system as it is starting. A failure to initially synchronize may explain why a FSMO role cannot be validated. This process is explained in KB article 305476. 2. This server has one or more replication partners, and replication is failing for all of these partners. Use the command repadmin /showrepl to display the replication errors. Correct the error in question. For example there maybe problems with IP connectivity, DNS name resolution, or security authentication that are preventing successful replication. 3. In the rare event that all replication partners being down is an expected occurance, perhaps because of maintenance or a disaster recovery, you can force the role to be validated. This can be done by using NTDSUTIL.EXE to seize the role to the same server. This may be done using the steps provided in KB articles 255504 and 324801 on http://support.microsoft.com. The following operations may be impacted: Schema: You will no longer be able to modify the schema for this forest. Domain Naming: You will no longer be able to add or remove domains from this forest. PDC: You will no longer be able to perform primary domain controller operations, such as Group Policy updates and password resets for non-Active Directory Domain Services accounts. RID: You will not be able to allocation new security identifiers for new user accounts, computer accounts or security groups. Infrastructure: Cross-domain name references, such as universal group memberships, will not be updated properly if their target object is moved or renamed. Event Xml: [code=markup]<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-ActiveDirectory_DomainService" Guid="{0e8478c5-3605-4e8c-8497-1e730c959516}" EventSourceName="NTDS General" /> <EventID Qualifiers="32768">2092</EventID> <Version>0</Version> <Level>3</Level> <Task>5</Task> <Opcode>0</Opcode> <Keywords>0x8080000000000000</Keywords> <TimeCreated SystemTime="2021-03-10T09:51:23.813750000Z" /> <EventRecordID>16180</EventRecordID> <Correlation /> <Execution ProcessID="584" ThreadID="720" /> <Channel>Directory Service</Channel> <Computer>dc01.domain.local</Computer> <Security UserID="S-1-5-7" /> </System> <EventData> <Data>DC=domain,DC=local</Data> </EventData> </Event> [/code]

Posted by: andrewt2m - 10 March 2021 10:38:40
try going to HKLM\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters in the registry and adding or editing the DWORD SysVolReady from 0 to 1 and reboot as this should confirm that the contents of the SysVol folder are up-to-date.

Posted by: Lemonde - 10 March 2021 10:41:08
Erm - it started working after a while but that value was already present so it may have had an affect...? Thanks anyway \:d/

Important Information: