This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(278.4, 24%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
Hi,
We are migrating from Exchange Server 2013 to Exchange 2019. Everything has gone pretty smooth and now i'm in the process of setting up redundancy with a DAG. I've built my DAG and added the member servers to it. The DAG network configuration doesn't auto-configure everything like it's supposed to. For instance, it places the same network for replication in with MAPI. So, I decided to try to manually set things straight, HOWEVER, any sort of DAG Network cmdlet that I try to run ends up in the error below:
A server-side administrative operation has failed. Operation failed with message: Error 0xe0434352 (Unknown error (0xe0434352)) from
cli_SetDagNetwork [Server: EX01.mydomain.com]
The only thing I can find is another forum for Exchange 2016 that has no answer... and the Error code 0xe0434352 in regards to .NET Framework to which I don't know if it's related.
I've turned up logging to Expert level and i'm not getting anything back regarding except an eventlog error source MSExchange CmdletLogs which tells me it fails. Not much help there.
Any other ideas or debugging options to try?
JB
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 22%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKY%3C/text%3E%3C/svg%3E)
Hi @JBerg712
I am writing here to confirm with you how thing going now?
Did the issue get resolved?
Does the auto config work? Its preferred to just have one network and let both MAPI and REPL networks use that one network. Just wondering if there is a technical reason you want to separate it out
Hi Andy,
Initially, the autoconfig did not set things correctly. I remember having to do this in my Exchange 2013 environment.
I'm primarily following the Exchange 2013 best practice for Mailbox servers in a DAG.... or rather that were once best practices since this article seems to suggest otherwise by using a single NIC on each server. It is nice though to have the replication traffic segmented.
Once the NICs were configured with a static metric, they do auto-configure properly... however, to have replication traffic over one NIC and client connectivity over the other in the scenario, in order to disable replication on the client connectivity network can't be done because of this error OR if i have to exclude a network for compliance reasons, I can't do it.
Jonathan
Things have improved enough in 2016 and 2019, that I just use one NIC and let it auto configure and have never seen any issues.
That error looks like the an error thrown when the certs arent set correctly but seems odd to be thrown here.