Create a Connection
Published: October 22, 2009
Updated: October 16, 2013
Applies To: Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2
This topic describes how to create a connection between members of a replication group. To create a connection by using DFS Management, use the following procedure.
|To create a connection by using Windows PowerShell, use the Add-DfsrConnection cmdlet. The DFSR Windows PowerShell module was introduced in Windows Server 2012 R2.|
To create a connection
Click Start , point to Administrative Tools , and then click DFS Management .
In the console tree, under the Replication node, right-click the replication group that you want to create a new connection in, and then click New Connection .
Specify the sending and receiving members, and specify the schedule to use for the connection. At this point, replication is one-way.
Select Create a second connection in the opposite direction to create a second connection for two-way replication between the sending and receiving members. All members must have two-way connections.
Configuration changes are not applied immediately to all members except when using the Suspend-DfsReplicationGroup and Sync-DfsReplicationGroup cmdlets. The new configuration must be replicated to all domain controllers, and each member in the replication group must poll its closest domain controller to obtain the changes. The amount of time this takes depends on AD DS replication latency and the long polling interval (60 minutes) on each member. To poll immediately for configuration changes, open a command prompt window and then type the following command once for each member of the replication group:
dfsrdiag.exe PollAD /Member:DOMAIN\Server1. To do so from a Windows PowerShell session, use the
Update-DfsrConfigurationFromADcmdlet, which was introduced on Windows Server 2012 R2.
Warning Microsoft does not support one-way connections for DFS Replication. Creating a one-way replication connection can cause numerous issues including health check topology errors, staging issues, and issues with the DFS Replication database. To create a logical one-way connection, instead make the replicated folder on the appropriate member read-only.