Jul 09 2020 09:30 AM
Jul 10 2020 11:53 AM
@danielkaliel You can get a detailed view of the error message if you are using the following cmdlet:
Jul 16 2020 11:45 AM
@Dominik Hoefling We needed the DAG functioning at 100% quickly, so I restarted one of the Exchange servers and that forced the DAG to establish the connection over the replication network once again. If there is a command that will do the same, I'd appreciate knowing what it is so that a server restart is not required.