No Sysvol or Netlogon Shares

Question

Good Evening experts,
I have a Windows 2003 Standard DC which will soon be replaced with a Windows 2008 DC.  I have given the 2008 box the DC role but I have noticed neither the sysvol nor netlogon share have appeared on the new DC.  When I looked into this further,
I found this error on the 2003 server:
"The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.    Replica set name
is    : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"  Replica root path is   : "c:\windows\sysvol\domain" Replica root volume is : "\\.\C:"  A Replica set hits JRNL_WRAP_ERROR when the record that it
is trying to read from the NTFS USN journal is not found.  This can occur because of one of the following reasons.    [1] Volume "\\.\C:" has been formatted.  [2] The NTFS USN journal on volume "\\.\C:" has been deleted.
 [3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal.  [4] File Replication Service was not running on this computer for a long time.  [5]
File Replication Service could not keep up with the rate of Disk IO activity on "\\.\C:".  Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically
recover from this error state.  [1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs"
to restart the File Replication Service.  [2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.   WARNING: During the recovery process data in
the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.
I don't have another DC to pull the sysvol/netlogon details from and wanted some advice.
Bud

Answer 1

BHeld,
Cheers for your reply, I was going to go down this road but wanted to ensure I was on the correct path.  In addition, this particular domain is part of an overall forest but the other child domains are fine, its just this one that won't replicate. 
Do I need to do anything on the domains in the other child domains or just what you had specified above? cheers
Dinesh,
Polices and Script folder is still there.  Cheers
Bud
You only need to modify one of the DC in the problem domain. There is noting to be done in all other domains which are working fine. BTW, Sysvol/Netlogon shares are not replicated to other domains.
Restoring The SYSVOL (Non-)Authoritatively When Either Using NTFRS Or DFS-R
(2010-08-12) Restoring The SYSVOL (Non-)Authoritatively When Either Using NTFRS Or DFS-R (Part 1)
(2010-08-12) Restoring The SYSVOL (Non-)Authoritatively When Either Using NTFRS Or DFS-R (Part 2)
(2010-08-12) Restoring The SYSVOL (Non-)Authoritatively When Either Using NTFRS Or DFS-R (Part 3)
(2011-06-22) Restoring The SYSVOL (Non-)Authoritatively When Either Using NTFRS Or DFS-R (Part 4)
Awinish Vishwakarma - MVP
My Blog: awinish.wordpress.com
Disclaimer This posting is provided AS-IS with no warranties/guarantees and confers no rights.