Problems getting Sysvol to replicate on new Domain Controllers

[BH337]

When adding a new domain controller to the domain, the Sysvol will not
replicate. This error has occurred on three Servers I promoted to test.
Sysvol is replicating fine between the other 8 dc’s (4 in 1 site, each of the
other 4 in their own site).

I have done the following.

Run dcdiag /v
Issues that came up in the log are the failed advertising and sysvol tests
(since no sysvol, this is to be expected). Under the FSMOCheck I noticed the
PDC emulater is not the primary time server…..may not be anything since the
tests passed.
tarting test: FsmoCheck
GC Name: \\server 1
Locator Flags: 0xe00001fc
PDC Name: \\serverpdc
Locator Flags: 0xe00001fd
Time Server Name: \\server1
Locator Flags: 0xe00001fc
Preferred Time Server Name: \\server4
Locator Flags: 0xe00001fc
KDC Name: \\server 9
Locator Flags: 0xe00001fc

dcdiag /test:dns /v
Everything checked out ok except there is a line:
“root zone on this DC/DNS server was not found”

repadmin /showrepl
Everything Checks out ok

Ntfrsutl ds

There are not NULL reference objects for the servers BUT the Primary Member
of the DOMAIN SYSTEM VOLUME (SYSVOL SHARE) is NULL. Also the FRS
DOMAINCONTROLLERNAME is NULL.
“SUBSTITUTE DCINFO FOR DC
FRS DomainControllerName: (null)
Computer Name : 000-7200-DC11
Computer DNS Name : 000-7200-dc11.kleinisd.loc

ET: DOMAIN SYSTEM VOLUME (SYSVOL SHARE)
DN : cn=domain system volume (sysvol share),cn=file replication
service,cn=system,dc=domain,dc=loc
Guid : 1493008d-7b4b-476f-9d2d84f380161efb
Type : 2
Primary Member: (null)
File Filter : *.tmp, *.bak, ~*
Dir Filter : (null)
FRS Flags : (null)
WhenCreated : 1/5/2003 11:59:4 Central Standard Time Central Daylight
Time [360]
WhenChanged : 2/26/2010 0:9:11 Central Standard Time Central Daylight
Time [360]

Also, in ADSI Edit, I had three DCs that have long since been decomisioned
listed under the FRS Service DC list. I have removed them. AND…the root
domain has domainReplica value set to an old DC that no longer exists.

Any suggestions are apprectiated.

[Meinolf Weber [MVP-DS]]

Hello BH337,

Which OS versions are you talking about? Additional please post the unedited
ipconfig /all of your DCs and the complete dcdiag /v from them.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> When adding a new domain controller to the domain, the Sysvol will not
> replicate. This error has occurred on three Servers I promoted to
> test. Sysvol is replicating fine between the other 8 dc's (4 in 1
> site, each of the other 4 in their own site).
>
> I have done the following.
>
> Run dcdiag /v
> Issues that came up in the log are the failed advertising and sysvol
> tests
> (since no sysvol, this is to be expected). Under the FSMOCheck I
> noticed the

> PDC emulater is not the primary time server...may not be anything

> them. AND.the root domain has domainReplica value set to an old DC

[BH337]

Figured it out. AV software had locked onto a script in the sysvol and did
not want to move it to the new DCs. Once this was fixed, everything flowed
fine.

"Meinolf Weber [MVP-DS]" wrote:

> .
>

[Meinolf Weber [MVP-DS]]

Hello BH337,

Nice to hear, see hear some recommendations for AV:
http://support.microsoft.com/kb/822158

http://technet.microsoft.com/en-us/library/cc780637(WS.10).aspx

http://technet.microsoft.com/en-us/library/cc816917(WS.10).aspx