New domain controller but not SYSVOL or NETLOGON share

[FN-GM]

Hello

 

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

 

Thanks

 

Z

 

Edit: Its done it now, would do as soon as i submit the post!

Edited April 24, 2008 by FN-Greatermanchester

[SYNACK]

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.

[FN-GM]

ah right it took a days for it to come, just me being inpatient.

[SYNACK]

There is a way to force the replication in minutes but its been a while since I migrated AD stuff.

[FN-GM]

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.

[SYNACK]

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.

[cookie_monster]

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?

 

Cheers.

[FN-GM]

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.

[SYNACK]

This may be helpful, especially the bit at the very end:

http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/distrib/dsdh_frs_ayas.mspx?mfr=true

 

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.

 

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.

Edited June 16, 2008 by SYNACK
More info