If SYSVOL and NETLOGON Share is missing :
- 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.
Restart the netlogon service. copy the content of the SYSVOL from healthy DC, reboot or restart twice the NETLOGON .
You might run into a missing NETLOGON folder only after that. If so, check the folder c:\windows\sysvol\domain inside you might find
a folder called “NtFrs_PreExisting___See_EventLog“,
copy the folders inside it (Policies+Scripts) to to father folder = c:\windows\sysvol\domain.
Wait few minute and Restart the netlogon service twice again. the NETLOGON folder should re-appear again and now
the client can do login to the server !
In addition when moving the domain to windows 2016 we might need to configure value in the local GPO in order to fix the access
to NETLOGON & SYSVOL via IP address . run:
gpedit.msc -> computer configuration -> Administrative Templates ->Network-> network provider -> Hardend UNC paths ->
Click enable & show, enter the UNC server name (\\Server name) in “Value Name” field -> in the “value” field enter :
RequireMutualAuthentication=0,RequireIntegrity=0,RequirePrivacy=0
-> click O.K -> run (in cmd) gpupdate /force
The best Blog EVER!!!!!
I know the editor
I know i could trust on you 🙂
Yes this just saved us
I spent hours trying to fix this issue. This finally fixed it.
No sysvolready flag
¨My bad, issue resolved
Thank You!
Old article but this article really solved my issue.
Thank you.
“It’s simple when you know how”!!!! Fixed my issue and was REALLY simple!!!! Thanks!!!!
AMAZING. How did you even know this?
2008R2 -> 2012R2 Migration.
My dcdiag errors:
Starting test: Advertising
Warning: DsGetDcName returned information for \\OldDC, when we were trying to reach NewDC.
SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
….
Starting test: NetLogons
Unable to connect to the NETLOGON share! (\\NewDC\netlogon)
[NewDC] An net use or LsaPolicy operation failed with error 67, The network name cannot be found..
After performing these steps and then copying SYSVOL from OldDC to NewDC, everything works.
Good luck
Amazing, My Backup Domain Controller (Windows 2012 R2) was stopped showing Netlogon & Sysvol Directory.
This worked like a charm
I don’t know who wrote this article , i even don’t know this person .
But dear friend, Than my thanksssssss , my million thanks to you bro . You really saved me . God bless you , you are my hero .
Thank you
THX 🙂
Simply genius! This worked like a charm!
My friend… I have been troubleshooting my issue for a week. I’ve come across countless articles include the ones from MSFT itself. None of those worked… only yours did. You made my day! I’m bookingmarking your site and will refer friends.
Cheers
Amazing , thank you so mcu, you saved me so much time and headaches
It did work! After a dc restore the thing went crazy.
Truly appreciate it!
Cheers