Before you can deploy DFS Replication, you must configure your servers as follows:
-
Extend (or update) the Active Directory Domain Services (AD DS) schema to include Windows Server 2003 R2, Windows Server 2008, or Windows Server 2008 R2 schema additions. To use read-only replicated folders, the schema must include the Windows Server 2008 or newer schema additions. For information about extending the AD DS schema, see the Microsoft Web site at (
https://go.microsoft.com/fwlink/?LinkId=93051 ).
- Ensure that all servers in a replication group are located in the same forest. You cannot enable replication across servers in different forests.
-
Verify that all members of the replication group are running Windows Server 2008 R2, Windows Server 2008, or Windows Server 2003 R2. DFS Replication is supported on all x64 editions of Windows Server 2008 R2 and all x64 and x86 editions of Windows Server 2008. DFS Replication is not available for Itanium-Based Systems.
-
Install DFS Replication on all servers that will act as members of a replication group.
-
Install the DFS Management snap-in on a server to manage replication. This server cannot run a Server Core installation of the Windows Server 2008 operating system.
-
Contact your antivirus software vendor to check that your antivirus software is compatible with DFS Replication.
-
Store replicated folders on NTFS volumes.
-
To include a failover cluster in a replication group, the failover cluster must be running Windows Server 2008 R2. Install and configure the failover cluster feature and then use the High Availability Wizard to create a clustered File Server instance before adding the instance as a replication group member. For more information, see Add a Failover Cluster to a Replication Group.
On a server that is running a version of Windows older than Windows Server 2008 R2, locate replicated folders for failover clusters in the local storage of a node. Versions of the DFS Replication service older than Windows Server 2008 R2 are not designed to coordinate with cluster components, and the service will not fail over to another node.