Dcpromo Error: No Other Active Directory Controllers?

KB ID 0001453


I was trying to demote a domain controller yesterday morning, it was a 2008 R2 Domain controller, (in fact it was SBS 2011). I’d already added a nice new Server 2016 Domain Controller to the domain, and transferred all the FSMO roles, so I was surprised when I tried to gracefully demote the old DC and got this;

DCpromo no other domain controllers can be contacted

You did not indicate that this Active Directory domain controller is the last domain controller for the domain {domain-name}. However, no other Active Directory domain controllers for that domain can be contacted.

Do you want to proceed anyway?

If you click Yes, any Active Directory Domain Services changes that have been made on this domain controller will be lost.

Well, that’s a scary error, and pretty much made me cancel the demotion right away.


Well I could ping the other domain controller, by name and by IP address, and it was listed in ‘Sites and Services’, and I could replicate Active Directory? (Very Strange). It was not until I ran dcdiag that I saw some warnings about ‘sysvol replication‘. that steered my in the right direction.

On the ‘outgoing’ Domain Controller, run regedit, then navigate to the following location;

HKEY LOCAL MACHINE > SYSTEM > CurrentControlSet > services > Netlogon > Parameters

Locate the SysvolReady value, (it’s probably set to 0 (Zero)).

Change it to 1 (one) then click OK, (this sort of ‘kicks windows up the backside’, and re-shares Sysvol with the correct permissions). Then after you have changed it, change it back to ZERO. You don’t need to restart any services, just change it, then change it back. Repeat the process on your other domain controllers. Have a coffee, then attempt to demote your Domain Controller again.

Related Articles, References, Credits, or External Links


Author: PeteLong

Share This Post On


  1. Hi Pete, thanks for very valuable tip – it pointed me to good direction.
    I’m not sure the statement “after you have changed it, change it back to ZERO” is true, I think zero value causes all theese problems – I briefly checked some other sources and it looks like value 1 is a proper and it should stay with 1, not 0.
    Thanks a lot!
    Best reards,
    Andrzej Angielski

    Post a Reply
  2. Yes, it the registry value should stay with 1 and should not be put back to Zero.

    This was very valuable suggestion and was very useful to me.

    Thanks a lot Pete.

    Post a Reply
  3. You Rock; however, I have to agree with leaving the Value at 1. 🤘🤘

    Post a Reply
  4. Thanks Pete. I really appreciate this post and found it helpful.

    Post a Reply

Submit a Comment

Your email address will not be published. Required fields are marked *