test
36.1 C
Dubai
Monday, June 17, 2024

SYSVOL and NETLOGON Share is missing in Newly Built Domain Controllers 2008R2/2012R2.

Windows Server 2008R2 Domain Controllers where introduced in 2003 Active Directory Environment.

  • Make sure connectivity is healthy between the PDC (Primary Domain Controller) (Open Cmd prompt run – netdom query fsmo)
  • Make sure SYSVOL and NETLOGON share is accessible on PDC from Secondary Domain Controllers.

To Rebuilt it –

  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate the following subkey in Registry Editor:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
  3. In the details pane, right-click the SysvolReady flag, and then click Modify.
  4. In the Value data box, type 0, and then click OK.
  5. Again in the details pane, right-click the SysvolReady flag, and then click Modify.
  6. In the Value data box, type 1, and then click OK.

Note – In my case the Value was already 0 . So I placed it to 1 and restarted NETLOGON . Shares came up without reboot.

image

In my case ,had to Copy paste the below folder manually to the Domain Controllers to Pick it up.

Normally if you wait for some time . It has to copy the folders on its own.

image

Microsoft KB

http://support.microsoft.com/en-us/kb/947022

Satheshwaran Manoharan
Satheshwaran Manoharanhttps://www.azure365pro.com
Award-winning Technology Leader with a wealth of experience running large teams and diversified industry exposure in cloud computing. From shipping lines to rolling stocks.In-depth expertise in driving cloud adoption strategies and modernizing systems to cloud native. Specialized in Microsoft Cloud, DevOps, and Microsoft 365 Stack and conducted numerous successful projects worldwide. Also, Acting as a Technical Advisor for various start-ups.

Related Articles

11 COMMENTS

  1. Hi Satheshwaran,

    You helped me a bit :-p

    I could recover sysvol share. But what can I do to recover netlogon share?

    Regards.

  2. Hi Satheshwaran,

    Please confirm should i run following steps on PDC or newly created domain?

    Click Start, click Run, type regedit, and then click OK.
    Locate the following subkey in Registry Editor:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
    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

      • When switching from 0 to 1, won’t doing this on the secondary DC make it authoritative? Which may cause the secondary DC to replicate to the PDC?
        Or can you just change it to 1 to creat? sysvol/netlogon shares and then switch back to 0 before replicating?

  3. My solution to this was:
    – Stop NETLOGON service
    – Change the subkey value to ‘0’
    – Create the folder “scripts”
    – Change the subkey value to ‘1’
    – Start NETLOGON service
    – Run “net share” on cmd to verify

  4. My Solution was
    1.Click Start, click Run, type regedit, and then click OK.
    2.Locate the following subkey in Registry Editor:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
    3.In the details pane, right-click the SysvolReady flag, and then click Modify.
    4.In the Value data box, type 0, and then click OK.
    5.Again in the details pane, right-click the SysvolReady flag, and then click Modify.
    6.In the Value data box, type 1, and then click OK.
    Restart Netlogon Service
    both Sysvol and Netlogon share appeared.
    your solution fixed my exchange issue not connecting to DC.
    Thank you

  5. When switching from 0 to 1, won’t doing this on the secondary DC make it authoritative? Which may cause the secondary DC to replicate to the PDC?
    Or can you just change it to 1 to creat? sysvol/netlogon shares and then switch back to 0 before replicating?

LEAVE A REPLY

Please enter your comment!
Please enter your name here