LabMice.net - The Windows 2000\XP\.NET Resource Index
Home | About Us | Search

Last Updated December 10, 2003

File Management
  Compression
  Dfs
  EFS
  FRS
  Offline Folders
  WFP
  Utilities

Disk Management
  Where to Start
  Defragmentation
  Disk Drives
  Disk Management
  Disk Recovery
  Dynamic Disks
  File Systems
  RAID
  Remote Storage
  Removable Storage
  Storage (SANS)
  Troubleshooting

 

 

 

 

Windows 2000 File Replication Service (FRS)

The File Replication service (FRS) is a multi-threaded, multi-master replication engine that replaces the LMREPL (LAN Manager Replication) service in Microsoft Windows NT versions 3.x and 4.0. Windows 2000 domain controllers and servers use FRS to replicate system policies and login scripts for Windows 2000 and down-level clients. FRS can also replicate content between Windows 2000 servers hosting the same fault-tolerant Distributed File System (DFS) roots or child node replicas. 

Where to Start...

Changes to the File Replication Service 
Microsoft Knowledge Base Article: 307319 - This article describes changes to the File Replication Service (FRS) in a Windows 2000 Post-Service Pack 2 (SP2) hotfix that improve the robustness of the service. These changes address behavior that may cause FRS to stop replicating. The changes also include manageability improvements and minor problem fixes. A supported feature that modifies the product's default behavior is now available from Microsoft, but it is only intended to modify the behavior described in this article and should be applied only to systems having a specific need for it. This feature may receive additional testing at a later time, to further ensure product quality. Therefore, if you are not severely affected by the lack of this feature, Microsoft recommends that you wait for the next Windows 2000 service pack that contains this feature 

Description of FRS Entries in the Registry
Microsoft Knowledge Base Article: 221111 - This article describes the registry entries for FRS 

Description of the FRS Replication Protocol, Notification and Schedule for DFS Content
Microsoft Knowledge Base Article: 220938 -  This article discusses the replication protocol, notification, and schedule used by FRS for replicating DFS content. 

File Replication Service
Sample Chapter from the Windows 2000 Server Resource Kitexplains how the File Replication service (FRS) replicates system policies and logon scripts stored in System Volume (SYSVOL) and replicates data for Distributed file system (Dfs).

How FRS Works
Explains how the File Replication service (FRS) replicates system policies and logon scripts stored in System Volume (SYSVOL) and replicates data for Distributed file system (Dfs). Source: Microsoft.com

Introduction to FRS
Explains how the File Replication service (FRS) replicates system policies and logon scripts stored in System Volume (SYSVOL) and replicates data for Distributed file system (Dfs). Source: Microsoft.com

Windows 2000 Does Not Support Windows NT 4.0 Directory Replication (LMRepl)
Microsoft Knowledge Base Article: 248358 - You can configure Microsoft Windows NT 4.0 and earlier to synchronize the contents of the Netlogon shares on each of the domain controllers (DCs) in a domain. This functionality is called LanMan Directory Replication (LMRepl). Windows 2000 is not backwards compatible with this functionality. It has been replaced with the File Replicator service (FRS). FRS and LanMan Directory Replication cannot be configured to replicate or synchronize with each other. In a Mixed-mode environment, you may need to keep data synchronized between new Windows 2000-based DCs and the remaining down-level DCs. A Microsoft Windows 2000 Resource Kit utility named Lbridge.cmd is available to perform this function. 

Windows 2000 File Replication Service Update 
This update resolves the "File Replication Service Creates Unneeded Directories in Distributed File System Root Alternates" in Windows 2000. The Distributed File System DFS is a network server component that makes it easy for you to find and manage data on your network. If the File Replication Service (FRS) is enabled at the root of a DFS, each time a new DFS link is added it will replicate the creation of this directory. Download now to prevent extraneous directories in your DFS.

WebCast: Introduction to and Administration of the File Replication Service
Level:100 During this session, we will discuss what the File Replication Service (FRS) is. We will talk about how it works in regard to Active Directory and Distributed File System. In addition, we will review the administration of FRS.

Additional Articles worth reading....

Advancing Time on Production Computers and the Effect on Active Directory and FRS 
Microsoft Knowledge Base Article: 289668 -
In the course of troubleshooting Active Directory or File Replication Service (FRS - replication issues, as the administrator, you may want to advance the system time of a computer to make the content of one computer have authority over another, or to force deletion of tombstoned objects in Active Directory. 

Design Decisions, Defaults and Behavior for FRS File and Folder Filters in DFS and SYSVOL Replica Sets 
Microsoft Knowledge Base Article: 229928 - The File Replication service (FRS - is a multi-threaded, multi-master replication engine that replaces the LMREPL service in Microsoft Windows NT versions 3.x and 4.0. Windows 2000 domain controllers and servers use FRS to replicate system policy and login scripts for Windows 2000 and down-level clients.

FileReplicaConn Counter Objects Do Not Log Values in System Monitor
Microsoft Knowledge Base Article: 255007 - File Replication counters are not recorded in the System Monitor logs. These counters are for the FileReplicaConn object. All values are reported as 0, even though file replication is obviously taking place on the computer that is being monitored. 

File-Change Notification Not Generated on FRS Replica Target Share
Microsoft Knowledge Base Article: 271751 - The File Replication service (FRS) can replicate files from a source share to a target share when a new file is added or an existing file is modified. A program can post a file-change notification on a folder to monitor the folder and receive notification when there is a file change in the folder. However, if the monitored folder is the target share of an FRS replica, the program may not receive the file-change notification. 

File Replication Service Improvements in Windows 2000 Service Pack 2
Microsoft Knowledge Base Article: 272567 - Windows 2000 Service Pack 2 (SP2) includes enhancements to the File Replication service (FRS). These changes improve scalability and supportability in large Windows 2000-based domain deployments.

FRS Builds Full-Mesh Replication Topology for Replicated DFS ROOT and Child Replicas
Microsoft Knowledge Base Article: 224512 - This article describes the replication topology generated by FRS and how to modify the default topology. 

FRS Does Not Compress for Replication as Directory Service Does 
Microsoft Knowledge Base Article: 296971 - When you use File Replication Service (FRS) for replication between sites (like directory service replication), the file is not compressed if you use FRS on a computer that runs Windows 2000 or Windows 2000 Service Pack 1. 

FRS File and Folder Filters Apply to New Files Only
Microsoft Knowledge Base Article: 229928 - This article describes the application of file and folder filters for FRS replicated content 

FRS May Create Duplicate File IDs on High-Performance Computers, Preventing Full Replication of Sysvol and DFS Replicas
Microsoft Knowledge Base Article: 250978 - Windows 2000-based member servers and domain controllers that join an existing File Replication service (FRS) replica set may never be fully synchronized. FRS replica sets include newly promoted Windows 2000-based domain controllers that source the system volume (Sysvol), containing Windows 2000 policies or Distributed File System-replicated root and child nodes. Not fully sourcing Sysvol prevents the creation of the Sysvol share; the promoted computer does not become a fully functioning domain controller in the domain. 

FRS Replication Protocol and Topology for SYSVOL Content
Microsoft Knowledge Base Article: 220140 - This article describes the replication topology used by FRS for replicating SYSVOL content throughout an enterprise.

How to Relocate the NTFRS Jet Database and Log Files
Microsoft Knowledge Base Article: 221093 - NT File Replication Service (NTFRS) transactions are stored in the Ntfrs.jdb Jet database and in a set of log files in the default paths %SystemRoot%\Ntfrs\Jet and %SystemRoot%\Ntfrs\Jet\Log. Administrators can relocate the Ntfrs.jdb and log files to another logical partition or physical drive as necessary. 

How to Replicate RIS Images Using DFS and NTFRS 
Microsoft Knowledge Base Article: 273594 - This article describes how to use Windows NT File Replication Service (NTFRS) with Distributed File System (DFS) to replicate your Remote Installation Services (RIS) images. 

How to Restrict FRS Replication Traffic to a Specific Static Port 
Microsoft Knowledge Base Article: 319553 - This article describes how to configure a static port for File Replication service (FRS) traffic.

HOW TO: Set Up File and Folder Replication for IIS 5.0 Using the Most Common Method 
Microsoft Knowledge Base Article: 311398 -
This article describes how to set up replication of your Internet data between servers. The procedures cover the most common method, which is to use Distributed File System (DFS - and File Replication Service (FRS). 

HOW TO: Use File Replication Service File and Folder Filters
Microsoft Knowledge Base Article: 296944 -
This article describes how to use file and folder filters for content that is replicated by the File Replication service (FRS).

How to View Saved Directory Service, DNS Server, and File Replication Service Event Logs from Another Windows 2000-Based Computer
Microsoft Knowledge Base Article: 235427 - Windows 2000 Event Viewer includes three new event logs: 

Improvements in the Post-SP2 Release of Ntfrs.exe That Is Packaged with an Updated Ntfs.sys Driver 
Microsoft Knowledge Base Article: 321557 - The File Replication service (FRS) is a multi-threaded, multi-master replication engine that replaces the LANMan Directory Replication service (LMRepl service) in Microsoft Windows NT versions 3.x and 4.0. Windows 2000-based domain controllers

Mapping Events in NTFRS Service Logs to Threads in Performance Monitor
Microsoft Knowledge Base Article: 224554 - FRS creates detailed service logs in the %SystemRoot%\Debug folder that can be useful when troubleshooting or optimizing the NTFRS service. This article describes how to match FRS threads in the service logs to those in Performance Monitor. 

NT File Replication Service Log File Size and Verbosity Settings
Microsoft Knowledge Base Article: 221112 - The NT File Replication Service (NTFRS) service creates text-based log files in the %Systemroot%\Debug folder for troubleshooting NTFRS replication problems.
This article discusses how the Frs_000n.log files are built and describes the registry entries that control log size and information detail. 

Overview of Active Directory Objects That Are Used by FRS 
Microsoft Knowledge Base Article: 296183 - This article describes File Replication service (FRS) objects in Active Directory. FRS is a multiple-threaded, multiple-master replication engine that replaces the LMREPL service in Microsoft Windows NT 3.x and 4.0. Windows 2000 domain controller

Pre-staging the File Replication Service Replicated Files on SYSVOL and Distributed File System Shares for Optimal Synchronization
Microsoft Knowledge Base Article: 266679 - This article describes the pre-staging process for the File Replication service (FRS) replicated files on System Volume (SYSVOL) and on Distributed file system (Dfs) shares for optimal synchronization.

Replicating Logon Scripts and the Directory Replicator Service
Microsoft Knowledge Base Article: 271650 - In the Help files for Microsoft Windows 2000 Server and Microsoft Advanced Server, the "Setting up replication of logon scripts" topic refers to the Directory Replicator service and gives information about placing logon scripts into an export directory for replication. This topic refers to Microsoft Windows NT 4.0 technology that is updated for Microsoft Windows 2000. In Windows 2000, replication of logon scripts is handled by File Replication Service (FRS), a multi-threaded, multi-master replication engine. In Windows 2000, logon scripts are stored in the Sysvol folder which is replicated automatically to all domain controllers by FRS.

The Effects of Setting the File System Policy on a Disk Drive or Folder Replicated by the File Replication Service 
Microsoft Knowledge Base Article: 279156 - This article describes the some of the effects that occur when you set a file system policy on a disk drive or folder that has been replicated by the File Replication service (FRS).

Troubleshooting Journal_Wrap Errors on Sysvol and DFS Replica Sets 
Microsoft Knowledge Base Article: 292438 - This article describes how FRS uses and relies on the NTFS file system USN change journal. 

Troubleshooting Missing SYSVOL and NETLOGON Shares on Windows 2000 Domain Controllers
Microsoft Knowledge Base Article: 257338 - This article describes troubleshooting steps to use on Windows 2000 domain controllers that are missing netlogon and sysvol shares. 

Troubleshooting FRS: Known Bugs and Issues

How to Troubleshoot the File Replication Service and the Distributed File System 
Microsoft Knowledge Base Article: 272279 - This article discusses how to troubleshoot the File Replication service (FRS) and the Distributed file system (Dfs). The main emphasis, however, of this article is to discuss a general procedure which can help you to troubleshoot FRS problem.

"Access Denied" Error Message When You Attempt to Set Dfs Replication Policy
Microsoft Knowledge Base Article: 261015 - When you try to set a replication policy for the domain Distributed file system (Dfs) link, the policy may not be set and the following error message may be displayed: The following error occurred while creating the staging path \\servername\drive$\Frs-Staging for subscriber object: Access Denied

Antivirus Problems May Modify Security Descriptors Causing Excessive Replication of FRS Data in Sysvol and DFS
Microsoft Knowledge Base Article: 284947 -
This article describes the symptoms that occur when antivirus programs perform virus scans on directories hosting FRS-replicated files including. Additional symptoms include: One program that is known to reset security descriptors during virus scan is Norton AntiVirus (NAV) versions 7.0 and 7.5. Other virus checking programs that modify security descriptors during virus scans will result in the same symptoms. 

Disk Defragmentation Causes Excessive FRS Replication Traffic
Microsoft Knowledge Base Article  Q282791 - When you use disk defragmentation utilities to optimize logical drives that host File Replication service (FRS) replicated content, the following symptoms may occur:

Error Message: Error Compressing Data
Microsoft Knowledge Base Article: 288160 - The File Replication service (FRS) log files located in the \Winnt\Debug folder log the following error and the replication for that file is unsuccessful: 

Event ID1000 and Event ID 1202 Messages Are Reported When You Set Security on the File Replication Service by Using Group Policy
Microsoft Knowledge Base Article: 284461 - If you configure the Startup mode and security settings on the File Replication service (FRS) through Group Policy, the following error messages may be logged in the Application event log in Event Viewer:

File-Change Notification Not Generated on FRS Replica Target Share
Microsoft Knowledge Base Article: 271751 - The File Replication service (FRS) can replicate files from a source share to a target share when a new file is added or an existing file is modified. A program can post a file-change notification on a folder to monitor the folder and receive notification when there is a file change in the folder. However, if the monitored folder is the target share of an FRS replica, the program may not receive the file-change notification.

File Replication Does Not Work As You Expect When You Configure Disk Quotas
Microsoft Knowledge Base Article: 816945 - When you enable disk quotas in a domain where a domain-based Microsoft Distributed File System (DFS) topology with automatic replication is configured, you may experience one or both of the following symptoms: Files are not replicated. Inconsistent replicas are generated.

File Replication Service Stops Responding When Staging Area is Full
Microsoft Knowledge Base Article: 264822 - The File Replication Service (FRS) for Microsoft Windows 2000 uses a "staging area" for replication. The default size of the staging area for FRS is approximately 660 megabytes (MB). If you want to replicate data that exceeds this amount, you may need to configure the FRS staging area to accommodate additional drive space. In addition, the volume that contains the staging area must also have this same amount of additional drive space available.

Files in NETLOGON Share Moved During Windows 2000 Upgrade
Microsoft Knowledge Base Article: 229679 - In Microsoft Windows NT versions 3.x and 4.0, domain controllers maintain a NETLOGON share in which administrators typically keep logon scripts and system policy files. After a computer is upgraded to Windows 2000 and promoted to a domain controller, the NETLOGON share and its contents are moved to a new location known as SYSVOL that is part of an automatically replicated folder structure that is replicated amongst domain controllers in the same domain.

Files in Single Instance Storage Replicate When Running NTBackup Against a Replicated Dfs Share 
Microsoft Knowledge Base Article: 271363 - When you use the Microsoft Windows NTbackup.exe program to back up a Distributed File System (Dfs - share that is synchronized with the FRS (File Replication service), the replication process to the other partners occurs as the files are backed up. 

Folders Are Created Once an Hour If FRS Is Enabled in a DFS Root 
Microsoft Knowledge Base Article: 259281 - Multiple redundant folders may appear in the root of a Distributed File System (DFS - share if the File Replication service (FRS - is enabled at the DFS root. 

FRS Creates Unneeded Folders in DFS Root Alternates
Microsoft Knowledge Base Article: 265365 - Each time a Distributed File System (DFS) link is added, a morphed folder is created if the File Replication service (FRS) is enabled at the root of a distributed file system. This occurs because DFS creates the folders and FRS determines that the names collide on each of the root alternates. The extraneous folders have a suffix of the form "NTFRS_xxxxxxxx" added to the end of the folder name.

FRS May Create Duplicate File IDs on High-Performance Computers, Preventing Full Replication of Sysvol and DFS Replicas
Microsoft Knowledge Base Article: 250978 - Windows 2000-based member servers and domain controllers that join an existing File Replication service (FRS) replica set may never be fully synchronized. FRS replica sets include newly promoted Windows 2000-based domain controllers that source the system volume (Sysvol), containing Windows 2000 policies or Distributed File System-replicated root and child nodes. Not fully sourcing Sysvol prevents the creation of the Sysvol share; the promoted computer does not become a fully functioning domain controller in the domain. 

FRS Service Does Not Rebind to the DS if the Binding Handle Becomes Invalid
Microsoft Knowledge Base Article: 253859 - The File Replication Service may log the following event error message: Event ID:13526 The file replication service cannot replicate d:\winnt\sysvol\domain with the computer DC1 because the computer SID cannot be determined from the distinguished name "cn=dc1,ou=domain controller,dc=corp,dc=com" The file Replication Service will try later.
SYSVOL and DFS content is not being replicated. For new replica domain controllers, FRS replication failures can prevent the sharing of netlogon and sysvol shares, the application of policy, and the machine registering itself in the Active Directory as a domain controller. For existing computers, files and folders in SYSVOL or DFS replica set are inconsistent between replica members.

"Last Writer Wins" Algorithm May Cause Loss of Data for FRS-Replicated Content
Microsoft Knowledge Base Article: 221089 - This article describes the impact of a multi-master replication model for files and folders replicated between Windows 2000 servers and domain controllers. 

Link to NFS Share Through DFS Server Is Missing
Microsoft Knowledge Base Article: 254330 - After you set up a Microsoft Windows NT Network File System (NFS) share on a Windows NT-based computer that is reachable by a Distributed File System (DFS) server, you find that the link to the NFS share is not set up.

Moving FRSStagingPath Requires Non-Authoritative Restoration 
Microsoft Knowledge Base Article: 265085 -  This article describes the relocation of the FRS staging directory for existing FRS replica sets. 

NTFRS Event ID 13557 Is Recorded When Duplicate NTDS Connection Objects Exist
Microsoft Knowledge Base Article: 251250 - Event error 13557 may be recorded in the File Replication service (FRS) event logs on domain controllers or member servers. In addition, files and folders on DFS and Sysvol replica members may be inconsistent. 

SYSVOL Directory Is Slow to Synchronize, Delays Creation of SYSVOL Share and Domain Controller Registration
Microsoft Knowledge Base Article: 250545 - Replica or backup Windows 2000 domain controllers may be slow to synchronize the contents of the system volume, which may delay the registration of a promoted computer as a domain controller.

Uplevel NTFRS Replication Members Ignore Inter-Site Replication Schedule 
Microsoft Knowledge Base Article: 302982 - When you add, delete, or modify a file, File Replication Service (FRS - may ignore the inter-site replication schedule and replicates content in the SYSVOL tree between DCs in different sites instead of waiting for the schedule to open. 

Entire contents
© 1999-2003 LabMice.net and TechTarget
All rights reserved

This site and its contents are Copyright 1999-2003 by LabMice.net. Microsoft, NT, BackOffice, MCSE, and Windows are registered trademarks of Microsoft Corporation. Microsoft Corporation in no way endorses or is affiliated with LabMice.net. The products referenced in this site are provided by parties other than LabMice.net. LabMice.net makes no representations regarding either the products or any information about the products. Any questions, complaints, or claims regarding the products must be directed to the appropriate manufacturer or vendor.