Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 2093 Source: NTDSReplication

The remote server which is the owner of a FSMO role is not responding. This server has not replicated with the FSMO role owner recently.

Operations which require contacting a FSMO operation master will fail until this condition is corrected.

FSMO Role: CN=RID Manager$CN=SystemDC=<name>DC=<name>DC=<name>
FSMO Server DN: CN=NTDS SettingsCN=DC2CN=ServersCN=Default-First-Site-NameCN=SitesCN=ConfigurationDC=<name>DC=<name>DC=<name>
Latency threshold (hours): 24
Elapsed time since last successful replication (hours): 40

User Action:

This server has not replicated successfully with the FSMO role holder server.
1. The FSMO role holder server may be down or not responding. Please address the problem with this server.
2. Determine whether the role is set properly on the FSMO role holder server. If the role needs to be adjusted utilize NTDSUTIL.EXE to transfer or seize the role. This may be done using the steps provided in KB articles 255504 and 324801 on
3. If the FSMO role holder server used to be a domain controller but was not demoted successfully then the objects representing that server are still in the forest. This can occur if a domain controller has its operating system reinstalled or if a forced removal is performed.  These lingering state objects should be removed using the NTDSUTIL.EXE metadata cleanup function.
4. The FSMO role holder may not be a direct replication partner. If it is an indirect or transitive partner then there are one or more intermediate replication partners through which replication data must flow. The total end to end replication latency should be smaller than the replication latency threshold or else this warning may be reported prematurely.
5. Replication is blocked somewhere along the path of servers between the FSMO role holder server and this server.  Consult your forest topology plan to determine the likely route for replication between these servers. Check the status of replication using repadmin /showrepl at each of these servers.

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 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.
The following conditions may cause this event to occur:
1.Operations master role holder is not set or is not readable
2.Operations master role is set to a domain controller that is deleted
3.Operations master self-ownership is not valid
4.The operations master role owner does not respond
See ME914032 for more information on this issue.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.