Netlogon Share Missing from 2K8R2 Promoted DC
Hi
I have a existing domain with a 2003 and 2008R2 AD / DNS Servers already promoted.
Needed to add a new dedicated AD DC to allow me to remove the others.
Promotion worked with no issue however no Sysvol and Netlogon shares created.
Carried out http://support.microsoft.com/kb/947022
Syslogon Share Appeared.
Tried http://support.microsoft.com/kb/316790
No Changes
DCDIAG Attached.
Have read lots of articles however no joy.
I have a existing domain with a 2003 and 2008R2 AD / DNS Servers already promoted.
Needed to add a new dedicated AD DC to allow me to remove the others.
Promotion worked with no issue however no Sysvol and Netlogon shares created.
Carried out http://support.microsoft.com/kb/947022
Syslogon Share Appeared.
Tried http://support.microsoft.com/kb/316790
No Changes
DCDIAG Attached.
Have read lots of articles however no joy.
Venkat Suresh
You need to check various things in this case. Check the DNS settings on new DC where Netlogon shares are not available. Check the logonserver status, ping any other DC and see if it resolves NetBios name as DC1.domain.local. What DCDiag /v says on new DC. also post us ipconfig /all and repadmin /replsum
Hi Michael334,
check the FRS log for event ID 13516, it means sysvol replication is completed and now the server will be acting as domain controller.
Unless the event ID 13516 is not there in FRS log means the sysvol replication is not yet over. Unless the SYSVOL is replicated properly the server won't advertise itself as domain controller.
If the Event ID is not available then check for any errors in the FRS log also navigate to the path c:\windows\debug\dcpromo.l
You can also check for netlogon.log for any errors.
Perform the above check and share the status..,
check the FRS log for event ID 13516, it means sysvol replication is completed and now the server will be acting as domain controller.
Unless the event ID 13516 is not there in FRS log means the sysvol replication is not yet over. Unless the SYSVOL is replicated properly the server won't advertise itself as domain controller.
If the Event ID is not available then check for any errors in the FRS log also navigate to the path c:\windows\debug\dcpromo.l
You can also check for netlogon.log for any errors.
Perform the above check and share the status..,
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the details, the above has resolved the issues with both shares now available and replicating.
Glad to see that your issue has been resolved
How long do you have to wait for the File Replication event ID 13516 ?
I am waiting for 2 hours and do not see anything yet?
I am waiting for 2 hours and do not see anything yet?