<div>
Can you run the following command from a PowerShell console (need admin rights): 
 

<pre><code class="code-1 nolinks" id="code-20-42048956-1">1. Import-Module DFSR
2. Get-DfsrBacklog | sort ReplicationGroup, sendingmember | ft -a
</code></pre>
 
This there any backlog? 
 
Also, those DFSR targets may be missing a primary member. &nbsp;Here is an article explaining the process to correct. 
 
Link: &nbsp;<a href="http://gsilt.blogspot.de/2016/06/dfs-waiting-for-initial-replication.html" rel="ugc">http://gsilt.blogspot.de/2016/06/dfs-waiting-for-initial-replication.html</a> 
 
Dan
</div>

<div>
Thanks for the response - I have run the command suggested from an elevated command prompt and it prompts for the source and destination server: 
 
Entering the primary server as the source and the receiving server as the destination - the command returns no output, just returns to the Powershell prompt. 
 
Entering the receiving server as the source and the primary server as the destination - this generates an error &quot;Get-DfsrBacklog : &nbsp;Skipping the replicated folder because it has an invalid version vector. Replicated folder: &quot;NAME&quot;&quot; 
 
I have tried running the other command suggested to set the primary - the command completes, but there is still no data being replicated across any of these folders.
</div>

<div>
The &quot;Get-DfsrBackLog&quot; command usually does not require a source or destination server in the command. &nbsp;But the user running the command needs to be a domain admin, no need to use &quot;Run As Admin&quot; &nbsp;But it does need to be run from a computer with the DFSR PowerShell module installed. 
 
1. &nbsp;Do you have a domain in place? 
2. &nbsp;Are these servers domain member servers? 
3. &nbsp;Is there a DFS Namespace in use? 
4. &nbsp;Are the directories to be replicated exist on both servers? 
5. &nbsp;Are the shares associated with the directories in #4 setup on both servers? 
6. &nbsp;Do the NTFS permissions match on both servers? 
7. &nbsp;Do the Share permissions match on both servers? 
 
Can you post the output of the following commands? 
 
1. &nbsp;Get-DfsrMember 
2. &nbsp;Get-DfsrFolder 
 
Dan
</div>

<div>
I am running these commands logged on as a domain administrator and using the 'run as administrator' option to launch Powershell to cover off most permission related issues. 
 
1. Yes, there is a domain in place. 
2. These servers are member of the domain. 
3. I have not deployed and DFS Namespaces yet, but I have added this role to these servers. 
4. The directories exist primarily on the source server. As part of adding the folders to DFS I selected the option for this wizard to create the required folders on the destination server. This has added the top level folder for each of these folders to the destination server, but these remain empty. 
5. The folders are shared from the source server and users still connect to this using \\servername\share but there is not a lot of data change. The folders are not shared on the destination server at this time. 
6. The DFS wizard is set to copy the existing permissions as part of the sync (and this works for the 2 folders that are working) - the 3 problematic folders have no contents as of yet. 
7. As above, the folders are only current shared from the primary server until we get the initial replication completed. 
 
Get-DfsrMember returns: 
 
GroupName &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: CIC-PFB RG 
ComputerName &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : SERVER1 
DomainName &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : domain.local 
Identifier &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : f097870a-6df3-4f0c-b7a2-27165d9d288e 
Description &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: 
DnsName &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: SERVER1.domain.local 
Site &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : Default-First-Site-Name 
NumberOfConnections &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: 2 
NumberOfInboundConnections &nbsp; : 1 
NumberOfOutboundConnections &nbsp;: 1 
NumberOfInterSiteConnections : 2 
NumberOfIntraSiteConnections : 0 
IsClusterNode &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: False 
State &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: Normal 
 
GroupName &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: CIC-PFB RG 
ComputerName &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : SERVER2 
DomainName &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : domain.local 
Identifier &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : bff50003-807c-45a6-806d-52a9ebf6cacc 
Description &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: 
DnsName &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: SERVER2.domain.local 
Site &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : PFB 
NumberOfConnections &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: 2 
NumberOfInboundConnections &nbsp; : 1 
NumberOfOutboundConnections &nbsp;: 1 
NumberOfInterSiteConnections : 2 
NumberOfIntraSiteConnections : 0 
IsClusterNode &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: False 
State &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: Normal 
 
Get-DfsReplicatedFolder returns: 
 
 
GroupName &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: CIC-PFB RG 
FolderName &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : ATLAS 
DomainName &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : domain.local 
Identifier &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : 4e85511b-baaa-4896-bbf6-9ac52e33a3f7 
Description &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: 
FileNameToExclude &nbsp; &nbsp; &nbsp;: {~*, *.bak, *.tmp} 
DirectoryNameToExclude : {} 
DfsnPath &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : 
IsDfsnPathPublished &nbsp; &nbsp;: False 
State &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: Normal 
 
GroupName &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: CIC-PFB RG 
FolderName &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : PUBLIC 
DomainName &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : domain.local 
Identifier &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : 93f7ad37-e8f5-4f8f-b1ed-3dbf8997fcd1 
Description &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: 
FileNameToExclude &nbsp; &nbsp; &nbsp;: {~*, *.bak, *.tmp} 
DirectoryNameToExclude : {} 
DfsnPath &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : 
IsDfsnPathPublished &nbsp; &nbsp;: False 
State &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: Normal 
 
GroupName &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: CIC-PFB RG 
FolderName &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : POSEIDON 
DomainName &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : domain.local 
Identifier &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : a69c2a2d-06a4-4510-9e12-f1b1e6b3999a 
Description &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: 
FileNameToExclude &nbsp; &nbsp; &nbsp;: {~*, *.bak, *.tmp} 
DirectoryNameToExclude : {} 
DfsnPath &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : 
IsDfsnPathPublished &nbsp; &nbsp;: False 
State &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: Normal 
 
GroupName &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: CIC-PFB RG 
FolderName &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : ScheduledTasks 
DomainName &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : domain.local 
Identifier &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : ae98b4d4-4da4-4931-b50f-65690ac3dbb4 
Description &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: 
FileNameToExclude &nbsp; &nbsp; &nbsp;: {~*, *.bak, *.tmp} 
DirectoryNameToExclude : {} 
DfsnPath &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : 
IsDfsnPathPublished &nbsp; &nbsp;: False 
State &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: Normal 
 
GroupName &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: CIC-PFB RG 
FolderName &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : Network 
DomainName &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : domain.local 
Identifier &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : 3916329a-6869-43db-89bb-ec2f1859f4ba 
Description &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: 
FileNameToExclude &nbsp; &nbsp; &nbsp;: {~*, *.bak, *.tmp} 
DirectoryNameToExclude : {} 
DfsnPath &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : 
IsDfsnPathPublished &nbsp; &nbsp;: False 
State &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: Normal 
 
GroupName &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: CIC-PFB RG 
FolderName &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : Users 
DomainName &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : domain.local 
Identifier &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : 5469d90c-6839-479e-9b79-6bb9b54c40fa 
Description &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: 
FileNameToExclude &nbsp; &nbsp; &nbsp;: {~*, *.bak, *.tmp} 
DirectoryNameToExclude : {} 
DfsnPath &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : 
IsDfsnPathPublished &nbsp; &nbsp;: False 
State &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: Normal
</div>

<div>
I would verify the following on both servers: 
** I rarely trust wizards... 
 
1. &nbsp;That the physical directories exist on both servers. 
2. &nbsp;That the NTFS permission match on both servers. 
3. &nbsp;That the shares are setup the same on both servers. 
4. &nbsp;That the Share permissions are the same on both servers. 
5. &nbsp;The shares can be accessed via UNC paths on both servers. 
 
The directory structures must be properly setup (physical folders and shares) before DFSR will function properly. &nbsp;My experience has always to verify everything manually before enabling DFSR. 
 
Dan
</div>

<div>
I get the reluctance to trust wizards fully :) I have checked this now and added the shares for these folders just to ensure that this is configured as suggested. 
 
1. The root directories exist on the destination server. 
2. The root directories have inherited the correct NTFS permissions from the source and these are identical on both servers. 
3. There are identical shares on both the source and destination server to all of the folders configured in DFS. 
4. The share permissions in both the source and destination locations are identical. 
5. I have checked that these shares are accessible via UNC from a couple of different servers on the network.
</div>

<div>
What does the output of this command say for the Replication Groups? 
 

<pre><code class="code-1 nolinks" id="code-20-42049130-1">dfsradmin membership list /rgname:&lt;YourReplicationGroupName&gt; /attr:RfName,MemName,LocalPath
</code></pre>
 
Dan
</div>

<div>
Running that command returns: 
 
RfName &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; MemName &nbsp; &nbsp; LocalPath 
ATLAS &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;SERVER1 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;D:\Data\ATLAS 
ATLAS &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;SERVER2 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;D:\Data\ATLAS 
Network &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;SERVER1 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;D:\Network 
Network &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;SERVER2 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;D:\Network 
POSEIDON &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;SERVER1 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;D:\Data\POSEIDON 
POSEIDON &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;SERVER2 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;D:\Data\POSEIDON 
PUBLIC &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;SERVER1 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;D:\Data\PUBLIC 
PUBLIC &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;SERVER2 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;D:\Data\PUBLIC 
ScheduledTasks &nbsp;SERVER1 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;D:\ScheduledTasks 
ScheduledTasks &nbsp;SERVER2 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;D:\ScheduledTasks 
Users &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;SERVER1 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; D:\Users 
Users &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;SERVER2 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; D:\Users
</div>

<div>
Are there any errors or warnings in the &quot;DFS Replication&quot; Event Log, on either server? &nbsp; 
 
Its under Computer Management &gt;&nbsp;Event Viewer &gt;&nbsp;Applications and Services Logs &gt;&nbsp;DFS Replication. 
 
Dan
</div>

<div>
There may also be more information in the DFSR debug log. &nbsp;It is located at the following location: 
 
C:\Windows\debug\Dfsrxxxxx.log 
 
Dan
</div>

<div>
The only non-informational entries in the Event Viewer are on the destination server are warnings that appear when the image based backup runs on the source server: 
 
The DFS Replication service is stopping communication with partner SERVER1 for replication group CIC-PFB RG due to an error. The service will retry the connection periodically. 
&nbsp; 
Additional Information: 
Error: 9036 (Paused for backup or restore) 
Connection ID: F38D38AD-F017-4674-BF7C-F3A9D23A98D2 
Replication Group ID: 4A6D9514-F8C3-419B-8FD5-7C1AECBC5BD3 
 
This occurs twice a day when the VSS portion of the backup runs on SERVER1 and is immediately followed by: 
The DFS Replication service successfully established an inbound connection with partner SERVER1 for replication group CIC-PFB RG. 
 
There are no warnings or errors on the source server at all.
</div>

<div>
That is to be expected. &nbsp;In the debug logs? 
 
Dan
</div>

<div>
In the DFSR debug log there are some recurrence of errors that look like the following: 
 
20170314 12:16:49.186 6196 ISYN &nbsp; &nbsp;68 InitialSyncManager::ReturnToken InitialSync sync step not finished yet. Wake up other session tasks. 
20170314 12:16:49.186 6408 DOWN &nbsp;4062 DownstreamTransport::EstablishSession Failed on connId:{F38D38AD-F017-4674-BF7C-F3A9D23A98D2} csId:{4E85511B-BAAA-4896-BBF6-9AC52E33A3F7} rgName:CIC-PFB RG Error: 
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4055 6408 C A failure was reported by the remote partner] 
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[Error:9028(0x2344) DownstreamTransport::EstablishSession downstreamtransport.cpp:4055 6408 C The content set was not found] 
20170314 12:16:49.186 6408 INCO &nbsp;7114 InConnection::RestartSession Retrying establish contentset session. connId:{F38D38AD-F017-4674-BF7C-F3A9D23A98D2} csId:{4E85511B-BAAA-4896-BBF6-9AC52E33A3F7} csName:ATLAS 
20170314 12:16:49.186 6408 INCO &nbsp;1021 [WARN] SessionTask::Step (Ignored) Failed, should have already been processed. Error: 
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[Error:9027(0x2343) InConnection::TransportEstablishSession inconnection.cpp:7701 6408 C A failure was reported by the remote partner] 
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4076 6408 C A failure was reported by the remote partner] 
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4055 6408 C A failure was reported by the remote partner] 
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[Error:9028(0x2344) DownstreamTransport::EstablishSession downstreamtransport.cpp:4055 6408 C The content set was not found] 
20170314 12:16:49.186 6408 ISYN &nbsp; &nbsp;68 InitialSyncManager::ReturnToken InitialSync sync step not finished yet. Wake up other session tasks. 
20170314 12:18:09.193 6408 DOWN &nbsp;4062 DownstreamTransport::EstablishSession Failed on connId:{F38D38AD-F017-4674-BF7C-F3A9D23A98D2} csId:{93F7AD37-E8F5-4F8F-B1ED-3DBF8997FCD1} rgName:CIC-PFB RG Error: 
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4055 6408 C A failure was reported by the remote partner] 
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[Error:9028(0x2344) DownstreamTransport::EstablishSession downstreamtransport.cpp:4055 6408 C The content set was not found] 
20170314 12:18:09.193 6408 INCO &nbsp;7114 InConnection::RestartSession Retrying establish contentset session. connId:{F38D38AD-F017-4674-BF7C-F3A9D23A98D2} csId:{93F7AD37-E8F5-4F8F-B1ED-3DBF8997FCD1} csName:PUBLIC 
20170314 12:18:09.193 6408 INCO &nbsp;1021 [WARN] SessionTask::Step (Ignored) Failed, should have already been processed. Error: 
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[Error:9027(0x2343) InConnection::TransportEstablishSession inconnection.cpp:7701 6408 C A failure was reported by the remote partner] 
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4076 6408 C A failure was reported by the remote partner] 
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4055 6408 C A failure was reported by the remote partner] 
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[Error:9028(0x2344) DownstreamTransport::EstablishSession downstreamtransport.cpp:4055 6408 C The content set was not found] 
20170314 12:18:09.193 6408 ISYN &nbsp; &nbsp;68 InitialSyncManager::ReturnToken InitialSync sync step not finished yet. Wake up other session tasks. 
20170314 12:18:09.194 1980 DOWN &nbsp;4062 DownstreamTransport::EstablishSession Failed on connId:{F38D38AD-F017-4674-BF7C-F3A9D23A98D2} csId:{4E85511B-BAAA-4896-BBF6-9AC52E33A3F7} rgName:CIC-PFB RG Error: 
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4055 1980 C A failure was reported by the remote partner] 
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[Error:9028(0x2344) DownstreamTransport::EstablishSession downstreamtransport.cpp:4055 1980 C The content set was not found] 
20170314 12:18:09.194 1980 INCO &nbsp;7114 InConnection::RestartSession Retrying establish contentset session. connId:{F38D38AD-F017-4674-BF7C-F3A9D23A98D2} csId:{4E85511B-BAAA-4896-BBF6-9AC52E33A3F7} csName:ATLAS 
20170314 12:18:09.194 1980 INCO &nbsp;1021 [WARN] SessionTask::Step (Ignored) Failed, should have already been processed. Error: 
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[Error:9027(0x2343) InConnection::TransportEstablishSession inconnection.cpp:7701 1980 C A failure was reported by the remote partner] 
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4076 1980 C A failure was reported by the remote partner] 
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4055 1980 C A failure was reported by the remote partner] 
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[Error:9028(0x2344) DownstreamTransport::EstablishSession downstreamtransport.cpp:4055 1980 C The content set was not found]
</div>

<div>
Thanks for that, I'll run through those steps later today and see if that improves things. 
 
Thanks for your help on this so far.
</div>

<div>
Any additional information on this question? 
 
Dan
</div>

<div>
<div class="content wysiwyg-content">
We have installed and configured DFS on two servers, setting up 5 different folders to be included in the Replication Group. Both servers are running Windows Server 2012 R2. 
 
2 of these folders have completed the initial synchronisation and seem to be working correctly. The other 3 look to be stuck in the &quot;Awaiting Initial Sync&quot; stage with the message &quot;This member is waiting for initial replication for replicated folder NAME.&quot; from the health diagnostic report for these three folders. 
 
We have tried removing the DFS role, rebooting and re-adding the DFS role but the situation remains the same. There are no errors in the Event Viewer, just informational messages stating that everything is working. Running the &quot;Verify Topology&quot; option in DFS Management reports that &quot;The topology for replication group NAME is fully connects. Data can replicate throughout the topology&quot;. 
 
Making changes to DFS settings in the DFS Management console correctly replicates to other servers relatively quickly - it is just the contents of these folders that do not seem to start. 
 
Any suggestions on troubleshooting this to get the initial replication complete greatly received!
</div>
</div>

We have installed and configured DFS on two servers, setting up 5 different folders to be included in the Replication Group. Both servers are running Windows Server 2012 R2.

2 of these folders have completed the initial synchronisation and seem to be working correctly. The other 3 look to be stuck in the "Awaiting Initial Sync" stage with the message "This member is waiting for initial replication for replicated folder NAME." from the health diagnostic report for these three folders.

We have tried removing the DFS role, rebooting and re-adding the DFS role but the situation remains the same. There are no errors in the Event Viewer, just informational messages stating that everything is working. Running the "Verify Topology" option in DFS Management reports that "The topology for replication group NAME is fully connects. Data can replicate throughout the topology".

Making changes to DFS settings in the DFS Management console correctly replicates to other servers relatively quickly - it is just the contents of these folders that do not seem to start.

Any suggestions on troubleshooting this to get the initial replication complete greatly received!

DFS Replication Setup Issues

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.