SBS 2003 to SBS 2008 ntFRS SYSVOL replication error
Posted on 2010-11-17
Recently we completed a SBS 2003 to SBS 2008 Migration. We are in the middle of finalizing the process. We are running into an issue with the new SBS 2008 server.
In attempting to move user file share and re-writing login scripts it was determined the SYSVOL and NETLOGON directories have not replicated to the new SBS server from the old SBS 2003 server.
I recent changed the DNS setting to point to the new server.
We are seeing the following error in the event log on the SBS 2008 server.
FRSSERVER = SBS 2003
FRS-SRV-01 = SBS2008
File Replication Service is scanning the data in the system volume. Computer FRS-SRV-01 cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.
To check for the SYSVOL share, at the command prompt, type:
When File Replication Service completes the scanning process, the SYSVOL share will appear.
The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume.
The File Replication Service has detected an enabled disk write cache on the drive containing the directory c:\windows\ntfrs\jet on the computer FRS-SRV-01. The File Replication Service might not recover when power to the drive is interrupted and critical updates are lost.
The File Replication Service is having trouble enabling replication from FRSSERVER.FRS.local to FRS-SRV-01 for c:\windows\sysvol\domain using the DNS name FRSSERVER.FRS.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.
 FRS can not correctly resolve the DNS name FRSSERVER.FRS.local from this computer.
 FRS is not running on FRSSERVER.FRS.local.
 The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
I have seen these previous on migration but they usually clear within a few minutes and the AD syncs and the servers start talking.
Any thought on the issue would be helpful.