<div>
<div class="content wysiwyg-content">
We have Exchange 2010 in place, trying to install Exchange 2013 in a 2 node DAG. &nbsp; Running Exchange 2013 on Server 2012 R2 as a Hyper-V guest on a 2008 R2 Hyper-V host.<br />
<br />
In my ECP under database availability groups for my DAG on my new Exchange 2013 nodes it show 65 ReplicationDagNetworks. &nbsp;I actually only have one replication network and have verified in powershell that replication is using the correct network.<br />
<br />
Also the command get-databaseavailabilitygr<wbr />oupnetwork<wbr /> fails with a &quot;could not load file or assembly&quot; error.<br />
<br />
Not sure if that is related.
</div>
</div>


We have Exchange 2010 in place, trying to install Exchange 2013 in a 2 node DAG.   Running Exchange 2013 on Server 2012 R2 as a Hyper-V guest on a 2008 R2 Hyper-V host.

In my ECP under database availability groups for my DAG on my new Exchange 2013 nodes it show 65 ReplicationDagNetworks.  I actually only have one replication network and have verified in powershell that replication is using the correct network.

Also the command get-databaseavailabilitygroupnetwork fails with a "could not load file or assembly" error.

Not sure if that is related.

Exchange 2013 2 node DAG, why are 65 ReplicationDagNetwork showing up in the ECP?

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.

Windows Server 2012

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.