KCC report after DC removal

  • Thread starter Thread starter gjb
  • Start date Start date
G

gjb

After losing a DC (MS1A) and having to manually force over the FMSO roles
and remove the AD entries the KCC reported the following:-

Event Type: Information
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1272
Date: 14/04/2004
Time: 14:15:17
User: N/A
Computer: MS1B
Description:
No nTDSConnection object exists for inbound replication from server CN="NTDS
Settings
DEL:ba375f79-99ec-4579-ac4c-d6683397b9c0",CN="MS1A
DEL:69d04bcc-516b-43b1-8837-b2a85b09ebf6",CN=Servers,CN=Default-First-Site-N
ame,CN=Sites,CN=Configuration,DC=msg,DC=xxx,DC=yyy,DC=uk at address
ba375f79-99ec-4579-ac4c-d6683397b9c0._msdcs.msg.xxx.yyy.uk. The partition
CN=Schema,CN=Configuration,DC=msg,DC=xxx,DC=yyy,DC=uk is no longer
replicated from it.

What does the above mean and how can I ensure all MS1A entries are gone as I
intend to rebuild it with the same name and re-promote it to DC status.

Regards,

Gerry
 
If the MS1A 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've removed all references to it like the one you're seeing here.

You'll need to clean up the metadata associated with the lost server, as
listed in the following KB article:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;216498
 
Back
Top