G
Gary M
I am getting ready to move us to windows 2003 from 2000 in the near future.
I ran dcdiag and get this error:
"There are errors after the SYSVOL has been shared. The SYSVOL can prevent
the AD from starting."
the only errors I see in FRS are one instance of this:
Event Type: Information
Event Source: NtFrs
Event Category: None
Event ID: 13516
Date: 8/21/2006
Time: 11:07:45 AM
User: N/A
Computer: myserver1
Description:
The File Replication Service is no longer preventing the computer myserver1
from becoming a domain controller. The system volume has been successfully
initialized and the Netlogon service has been notified that the system
volume is now ready to be shared as SYSVOL.
Type "net share" to check for the SYSVOL share.
and a MANY instances of this:
Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13567
Date: 10/5/2006
Time: 9:42:27 AM
User: N/A
Computer: myserver1
Description:
File Replication Service has detected and suppressed an average of 15 or
more file updates every hour for the last 3 hours because the updates did
not change the contents of the file. The tracking records in FRS debug logs
will have the filename and event time for the suppressed updates. The
tracking records have the date and time followed by :T: as their prefix.
Updates that do not change the content of the file are suppressed to prevent
unnecessary replication traffic. Following are common examples of updates
that do not change the contents of the file.
[1] Overwriting a file with a copy of the same file.
[2] Setting the same ACLs on a file multiple times.
[3] Restoring an identical copy of the file over an existing one.
Suppression of updates can be disabled by running regedit.
Click on Start, Run and type regedit.
Expand HKEY_LOCAL_MACHINE, SYSTEM, CurrentControlSet, Services, NtFrs,
Parameters, and create or update the value "Suppress Identical Updates To
Files" to 0 (Default is 1) to force identical updates to replicate.
What should I be looking at?
gary
I ran dcdiag and get this error:
"There are errors after the SYSVOL has been shared. The SYSVOL can prevent
the AD from starting."
the only errors I see in FRS are one instance of this:
Event Type: Information
Event Source: NtFrs
Event Category: None
Event ID: 13516
Date: 8/21/2006
Time: 11:07:45 AM
User: N/A
Computer: myserver1
Description:
The File Replication Service is no longer preventing the computer myserver1
from becoming a domain controller. The system volume has been successfully
initialized and the Netlogon service has been notified that the system
volume is now ready to be shared as SYSVOL.
Type "net share" to check for the SYSVOL share.
and a MANY instances of this:
Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13567
Date: 10/5/2006
Time: 9:42:27 AM
User: N/A
Computer: myserver1
Description:
File Replication Service has detected and suppressed an average of 15 or
more file updates every hour for the last 3 hours because the updates did
not change the contents of the file. The tracking records in FRS debug logs
will have the filename and event time for the suppressed updates. The
tracking records have the date and time followed by :T: as their prefix.
Updates that do not change the content of the file are suppressed to prevent
unnecessary replication traffic. Following are common examples of updates
that do not change the contents of the file.
[1] Overwriting a file with a copy of the same file.
[2] Setting the same ACLs on a file multiple times.
[3] Restoring an identical copy of the file over an existing one.
Suppression of updates can be disabled by running regedit.
Click on Start, Run and type regedit.
Expand HKEY_LOCAL_MACHINE, SYSTEM, CurrentControlSet, Services, NtFrs,
Parameters, and create or update the value "Suppress Identical Updates To
Files" to 0 (Default is 1) to force identical updates to replicate.
What should I be looking at?
gary