On a server I have noticed that after it was promoted to a domain controller or after you seize all the roles (using force), the NETLOGON share was not created. This has happened on a Windows 2008 onwards machine.
After you seize the roles, you might get an error saying:
Naming Information cannot be located because: The specified domain either does not exist or could not be contacted.
Of course one must assume all the meta data cleanup processes have been done. You might also notice that the
netdom /query fsmo might fail.
This can be solved with a registry modification. Please note to make a backup of your registry keys and of course don’t hold me responsible of any issues you have if this doesn’t work for you.
In the details pane, right-click the
SysvolReady flag, and then click Modify. In the Value data box, type 0, and then click OK.
Again in the details pane, right-click the
SysvolReady flag, and then click Modify. In the Value data box, type 1, and then click OK.
Restart the machine and it will re-create the NETLOGON process including the share.