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 www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
|Source: NTDS KCC|
No nTDSConnection object exists for inbound replication from server CN="NTDS Settings",CN="<DC>",CN=Servers,CN=<DC>,CN=Sites,CN=Configuration,DC=<DC>,DC=net at address <address>. The partition CN=Schema,CN=Configuration,DC=<DC>,DC=net is no longer replicated from it.
|English: Request a translation of the event description in plain English.|
From a newsgroup post: "If a DC failed and you were unable to gracefully dcpromo it out of your AD infrastructure, you should run metadata cleanup to make sure that you have removed all references to it like the one you are seeing here. You will need to clean up the metadata associated with the lost server, as listed in ME216498".
See the link to "EventID 1272 from source Active Directory" for additional information on this event.
|Private comment: Subscribers only. See example of private comment|
|Links: ME216498, EventID 1272 from source Active Directory|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated