Windows Thread, New domain controller but not SYSVOL or NETLOGON share in Technical; Hello
I have just setup or new Server and added it to the domain as a domain controller. Active Directory ...
24th April 2008, 03:24 PM #1
New domain controller but not SYSVOL or NETLOGON share
I have just setup or new Server and added it to the domain as a domain controller. Active Directory and DNS have replicated over but the new server does not have the SYSVOL or NETLOGON share.
Im not sure why, anyone any thoughts please. I have googeled it but not come up with anything useful
Edit: Its done it now, would do as soon as i submit the post!
Last edited by FN-GM; 24th April 2008 at 03:27 PM.
24th April 2008, 04:11 PM #2
Yeap, it takes a while to replicate all of the information across and it won't bring up the net logon service and the associated shares until the replication is complete.
24th April 2008, 05:18 PM #3
ah right it took a days for it to come, just me being inpatient.
24th April 2008, 05:30 PM #4
There is a way to force the replication in minutes but its been a while since I migrated AD stuff.
24th April 2008, 05:32 PM #5
Yes you can do it an Active Directory of Sites & Services and a command line option. I have the command line one written down somewhere.
24th April 2008, 05:37 PM #6
If I remember correctly the way that I did it was to create the connector manually in AD sites and trusts, then right click on the new connector and hit sync now (or something similar). This would usually result in it syncing and the automatic connector showing up at which point you can kill the manual connector and just let it handle it from then on.
16th June 2008, 06:07 PM #7
Sort to revive the thread
@ FN-Greatermanchester: did it really take nearly a day over a fast LAN connection? Did the shares just appear or did it need a reboot at some point?
16th June 2008, 07:15 PM #8
Yes took ages!, I did a few reboots but it didn’t come. Then it suddenly came. I thought there may have been replication problems after that but everything has been ok since.
16th June 2008, 07:21 PM #9
This may be helpful, especially the bit at the very end:
This is of course assuming that the connection objects have already been automatically generatd in ctive Directory Sites and Services, if not which may be the case this is what is causing your delay. Usually I create these manually on each server, force a replication and leave it half an hour. This will almost always bring up netlogon and create the automatic connectors. I then delete the manual connectors that I made and everything is how it should be. Forcing Replication Between Sites
The only way to force replication by FRS is to enable its schedule (assuming that it is off). The Replicate Now
button in the Active Directory Sites and Services console pertains to directory replication only.
Last edited by SYNACK; 16th June 2008 at 07:26 PM.
Reason: More info
Thanks to SYNACK from:
cookie_monster (16th June 2008)
By binky in forum Windows
Last Post: 3rd April 2008, 11:23 PM
By armadillo in forum Windows
Last Post: 31st August 2007, 10:00 AM
By fox1977 in forum Windows
Last Post: 17th August 2007, 04:52 PM
By Dos_Box in forum Windows
Last Post: 13th June 2007, 06:17 PM
By Oops_my_bad in forum Windows
Last Post: 19th April 2007, 06:54 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)