Link to home
Create AccountLog in
Avatar of thomasm1948
thomasm1948Flag for United States of America

asked on

NTDS KCC 1801

Hi,

We have remote site that I created a new site for and moved the only domain controller to.  The thing that I noticed is that now I am getting a warning message that states:

Warning NTDS KCC 1801

The partition DC=DomainDnsZones,DC=vertex,DC=local should be hosted at site CN=LAX,CN=Sites,CN=Configuration,DC=vertex,DC=local, but has not been instantiated yet. However, the KCC could not find any hosts from which to replicate this partition.

I am not sure exactly what this means being that in the past I have always created a site and then did a dcpromo to bring up the domain controller.  we have about 50 machins in that site and I am trying to do this from a remote site.

How can I resolve this issue.  Also how critical is this issue.  Will this prevent the users from logging on to the nework or have access to shared resources such as files and printers
Avatar of thomasm1948
thomasm1948
Flag of United States of America image

ASKER

Also when I run the following command in the command prompt everything seems to be ok:

repadmin /replsum /bysrc /bydest /sort:delta

I see no errors when I run it.  The only thing that I see is that I tried to install the support tools on the remote server and I get an error that I do not have permissions to install the application on the server (I did this though remote desktops in console mode)
ASKER CERTIFIED SOLUTION
Avatar of Awinish
Awinish
Flag of India image

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer
yes all of the sites are connected to their proper subnets.  I will try your recommendation after working hours.  

How critical is this warning message?  
I do not receive any event IDs 4515 in my event log
What would happen if I decide to demote the domain controller on the remote site and repromote it to a domain controller
Event id 4515 is related to dns but corruption can happen in dns, i gave you link to confirm you follow the steps properly.

You can do that nothing happens, but make sure before using same host name & IP again, make sure after demoting you clean up all the records & give time to replicate the changes to other dc else you will not able to configure the dc with same name.

Also,if you have clients pointed to that dc for dns need to make change on all the client machine.