EdgeSync synchronization to {0} is in a fatal state, and may have completely stopped. See the "Detail" section for more information. Run the {1} command and examine the EdgeSync log to diagnose the problem.
EdgeSync failed to synchronize because it only supports Cryptographic API certificates. The local Hub Transport server's ...
EdgeSync failed to synchronize the following address %1 to MSERV with permanent error %2. EdgeSync could not retry this item. ...
EdgeSync requires that the Mailbox servers in Active Directory site {0} be able to resolve the IP address for {1} and be ...
EdgeSync synchronization to {0} has encountered failures. Please see "Detail" section for more information. Run the {1} command ...
EdgeSync synchronization to {0} is in a fatal state, and may have completely stopped. See the "Detail" section for more information. ...
EdgeSync synchronization to {0} isn't operating normally, although it may still recover from this condition. This will delay ...
edgeSyncSvc = get-service MSExchangeEdgeSync* | where {$_.name -eq "MSExchangeEdgeSync"}; if ($RoleIsDatacenter -eq $true) ...
Either a protocol command was issued out of order or an unsupported protocol command was attempted. You can try sending the ...
Either Exchange can't find the default TLS certificate attribute for server {0} in Active Directory, or the attribute is ...