• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2339
  • Last Modified:

SBS 2003 to SBS 2008 ntFRS SYSVOL replication error

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.

For clarification:
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:
net share
 
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.
 
 [1] FRS can not correctly resolve the DNS name FRSSERVER.FRS.local from this computer.
 [2] FRS is not running on FRSSERVER.FRS.local.
 [3] 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.
0
paldie
Asked:
paldie
  • 5
  • 3
1 Solution
 
jplatoCommented:
You can Try to put dns back to old server and try this
http://technet.microsoft.com/en-us/library/cc816926(WS.10).aspx
0
 
paldieAuthor Commented:
I have tried forcing the replication but will reset DNS back to the original server an attempt again.
0
 
jplatoCommented:
You do have to wait 15-20 Min sometimes for the replication to happen depending on size of AD
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
paldieAuthor Commented:
It did look like the SYSVOL share was created previously during the setup process but just the scripts and policies never came over. I manually copied the policies and script earlier in the day.

My concern is once I move the user share to the new server and rewrite the login script the user are able to get to the file shares via mapped network drives which they are use to using.

I'll let you know if I get any additional error after repointing DNS and allow replication to happen
0
 
jplatoCommented:
You must write a script that removes the old drive before you can replace it with another drive mapping.

You can write a batch file that removes the Drive Ex.
net use R: /delete
net use R: \\newserver\newshare
0
 
paldieAuthor Commented:
yah roger that, we write scripts that always remove the old drives first.
0
 
paldieAuthor Commented:
WE have resolved the issue for this problem.  Below is the process we used to re-initiate the  

RESOLUTION:
- We ran the command [net share]on SBS 2008 box and found that netlogon and sysvol were as we expected not shared.
- We ran the same command on the SBS 2003 box and found that netlogon and sysvol were shared as this was the source server in the migration.
- Opened event viewer on the SBS 2008 box and found NtFrs errors as listed above.
- Followed article - http://support.microsoft.com/kb/290762
- Opened registry on the SBS 2003 box and browsed to the location HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup
- Changed the burflag value to D4 on the SBS 2003 box.
- On the SBS 2008 box browsed to the location - HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup
- Changed the burflag value to D2.
- Checked in the event viewer for any error, we did not see any replication errors.
- We waited for some time and tried to check if netlogon and sysvol was shared on the SBS 2008 box.
- Found that netlogon and sysvol was shared.
- Then we shut down the SBS 2003 box and checked the behavior.
- We checked and found that the user's were successfully able to login and access the Active Directory on the SBS 2008 box.
- Issue resolved.
0
 
paldieAuthor Commented:
This solutions was developed with the help of Microsoft Commercial Technical Support team.  Corrected the issues of the initial domain synchronization
0

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now