none
fix the "scripts" directory within SYSVOL to fix Netlogon share failure

    Question

  • The scripts folder got renamed. Can I just rename it on one machine and let it replicate or is there some special procedure? I can't seem to find anything other than talk about D2s and D4s and restores that don't seem like restores...

    I have added a server 2008 R2 domain controller to my domain and when running dcdiag I get an error:

    Starting test: NetLogons
       Unable to connect to the NETLOGON share! (\\MYSERVER\netlogon)
       [MYSERVER] An net use or LsaPolicy operation failed with error 67,
       The network name cannot be found..

    That error only happens on this machine, but all domain controllers have the following in their system event log:

    Source:        NETLOGON
    Event ID:      5706
    Level:         Error
    Description:
    The Netlogon service could not create server share C:\Windows\SYSVOL\sysvol\MYDOMAIN.NAME.COM\SCRIPTS.  The following error occurred:
    The system cannot find the file specified.

    That is because at some point NTFRS renamed the scripts folder to scripts_NTFRS_4aa45cc8. I think if I just change that folder name back everything will be fine. The folder exists on all domain controllers and the files are there. It's just that the Netlogon share is not created. It exists on two domain controllers. I suspect a previous sysadmin just manually shared the folder as Netlogon. I'd rather fix the actual problem.


    • Edited by notRoman Tuesday, April 23, 2013 7:50 AM
    Tuesday, April 23, 2013 7:48 AM

Answers

  • Ok, it looks like I was right in the first place. Since any duplicate had already long ago been removed and the problem was just the name of the folder, all I had to do was rename it. That change replicated instantly to the other domain controllers.

    Then, to get the Netlogon share, I just toggled the registry entry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Netlogon\Parameters\ DWORD SysVolReady. That is, I changed it to 0 then back to 1 which immediately caused the Netlogon service to successfully attempt to create the Netlogon share. Voilà.

    • Marked as answer by notRoman Wednesday, April 24, 2013 6:20 AM
    Wednesday, April 24, 2013 6:19 AM

All replies