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

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.
jasonbrandt3Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jasonbrandt3Author Commented:
All but the ReplicationDagNetwork01 have empty IP settings.

Cumulative update 6 for Exchange 2013 SP1 is installed.

I have (2) iscsi connections to mount volumes for the database and log directories.  Those connections attach to a single SAN network and I disabled replication . (I have "ManualDagNetworkConfiguration" set to "True".

I cannot delete these extra ReplicationDagNetworks in ECP, nor can I disable replication over the MAPI network via ECP

Since I ran the command:
 Set-DatabaseAvailabilityGroupNetwork -Identity DAG2\DAGNetwork02 -ReplicationEnabled:$false -IgnoreNetwork:$true

I am now able to see info when I do a get--databaseavailabilitygroupnetwork as it looks like it opened a new powershell session with more permissions.

The remove command seems to have quite a delay when I try to remove the networks.  Even after specifying a domain controller that is NOT read-only.
Remove-DatabaseAvailabilityGroupNetwork -Identity DAG1\DAGNetwork04 -domaincontroller mydc.mydomain.lcl

I'll try removing all the invalid ones and waiting a few minutes, this problem may be resolved.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.