Article ID: 883272
Article Last Modified on 10/30/2006
APPLIES TO
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
- Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
- Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
INTRODUCTION
Administrators can use the Microsoft Distributed File System (DFS) to organize shares on different servers into a single logical namespace. Administrators can also use the File Replication service (FRS) to replicate the contents of DFS replica sets between designated servers and to replicate the contents of the Sysvol folder between domain controllers.
Active Directory uses FRS to replicate the contents of the SYSVOL folders between domain controllers. Replication of Sysvol folder content is mandatory and occurs on the same schedule as Active Directory. DFS uses FRS to automatically synchronize replica content between servers. Administrators can schedule the replication of DFS roots and links when servers are available or network conditions are favorable. You can also use FRS to include or to exclude specific files in a replication schedule.
Note You can deploy DFS with or without FRS. You can also use third-party products to replicate content between DFS roots.
The FRS staging folder is a temporary store for files that are replicated to downstream partners of Sysvol or DFS replica sets. This article describes how FRS chooses the location of the staging folder for files to be replicated.
MORE INFORMATION
When you start the Distributed File System snap-in (Dfsgui.msc) to create and manage DFS namespaces, the program:
- Enumerates all shareable disks on the computer.
- Selects the disk with the most free space as the location for the FRS staging folder.
During the disk enumeration process, Dfsgui.msc enumerates shares according to the following:
- Dfsgui.msc ignores the volume where the replica is located.
- Dfsgui.msc ignores the system volume.
- Single character hidden shares such as \\
servername\c$ or \\servername\d$ are considered available staging area locations as long as the share letter does not match the system drive letter. This is true even though both may be on the same physical hard disk. In this situation, FRS assumes that the server is a remote server.
For example, if a server has a single character share such as \\servername\1$ on a system drive, FRS enumerates this share, and then selects it as the staging area if it has the most free space of all drives enumerated because it is also a non-system drive.
For additional information about how to reset the FRS staging folder to a different logical drive, click the following article number to view the article in the Microsoft Knowledge Base:
291823 How to reset the File Replication service staging folder to a different logical drive
For additional information about configuring staging area space, click the following article number to view the article in the Microsoft Knowledge Base:
329491 Configuring Correct Staging Area Space for Replica Sets
Keywords: kbfileprintservices kbfilesystems kbtshoot kbinfo KB883272
