New domain controller do not replicate sysvol
joined new server existing domain, dcdiag fine sysvol not replicating. new , old server sysvol path not same, going problem.
as retire old server, can manually copy sysvol new server? or can do? tks.
if joined server domain isn't turned domain controller. have dcpromo make dc? if sysvol isn't replicating definitiely have issues. copying sysvol isn't solution since replication 2 way flow, both dc's need replicate , forth changes.
it helpful if post event log messages might see related issue errors in diagnostics below:
if don't have support tools installed, install them server install disk.
d:\support\tools\setup.exe
run dcdiag , repadmin in verbose mode.
-> dcdiag /v /c /d /e /s:yourdcname > c:\dcdiag.log
-> repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt
-> ntfrsutl ds your_dc_name > c:\sysvol.log
-> dnslint /ad /s "ip address of dc"
**note: using /e switch in dcdiag run diagnostics against dc's in forest. if have significant numbers of dc's test generate significant detail , take long time. want take account slow links dc's add testing time.
if download gui script wrote should simple set , run (dcdiag). has option run individual tests without having learn switch options. details output in notepad text files pop automagically.
the script located on website @ http://www.pbbergs.com/windows/downloads.htm
just select both dcdiag , netdiag make sure verbose set. (leave default settings dcdiag set when selected)
when complete search fail, error , warning messages.
description , download dnslint
http://support.microsoft.com/kb/321045
--
paul bergson
mvp - directory services
mcitp: enterprise administrator
mcts, mct, mcse, mcsa, security+, bs csci
2008, vista, 2003, 2000 (early achiever), nt4
http://www.pbbergs.com twitter @pbbergs
please no e-mails, questions should posted in newsgroup this
posting provided "as is" no warranties, , confers no rights.
Windows Server > Directory Services
Comments
Post a Comment