• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1054
  • Last Modified:

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
0
thomasm1948
Asked:
thomasm1948
  • 4
  • 3
1 Solution
 
thomasm1948Author Commented:
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)
0
 
AwinishCommented:
You have linked all the sites properly with their subnet.

If its fine then there can be Domaindnszones & forestdnszones are in corruption.

Change all the AD-Integrated DNS zone to Primary(Non-AD-Integrated) in forward lookup zone as well as in reverse lookup zone

Stop the dns service on problem dc,
Open ADSIEDIT.MSC from run, locate configuration partition
Expand configuration partition>Partitions> remove Domaindnszones & forestdnszones only which is on the right side.
Start the dns service & you will find those two partitions will be recreated.
Convert the zone back to AD-Integrated,

Note: Delete the Domaindnszones & forestdnszones only after you have converted all the zone under forward & reverse lookup zone to non AD-integrated.If you delete the Domaindnszones & forestdnszones w/o converting the zone Non AD-Integrated, it will delete all the zones under forward & reverse lookup zone.

If you are not sure take backup before doing it.
0
 
AwinishCommented:
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell┬« is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
thomasm1948Author Commented:
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?  
0
 
thomasm1948Author Commented:
I do not receive any event IDs 4515 in my event log
0
 
thomasm1948Author Commented:
What would happen if I decide to demote the domain controller on the remote site and repromote it to a domain controller
0
 
AwinishCommented:
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.

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell┬« is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now