@bpoindexter , it is usually TLS1.2 not enabled on the server (check
these reg keys and run HealthChecker - Microsoft - CSS-Exchange) or
network issues for outbound (point 3 in the article). Transport Layer
Security (TLS) best practices with the .NET Framework - .NET Framework |
Microsoft Docs Windo...
We are had our Exchange Delegation certificate expire. We had to remove
the federation trust and recreate it, but we are getting the error
listed in point 3: "An unexpected error occurred on a send" None of the
items listed has helped resolve the issue. It isn't particularly urgent
since we host no ...
I used Tenant to Tenant migration a year ago. Even though we prepared
source and target according to the docs, we had several issues because
of holds. And it was rather hard to find the hold that's causing the
migration to fail (Reports don't gave in detailed info about the
specific hold - maybe tha...
@andy33 The server record in the "Out-of-date connecting servers. . ."
report should show the detected build date as the build that was
out-of-date before you updated to .037. However, the Status for that
record should say "Up to date" and the Details should reference when you
updated to a compliant...
Our servers are using 15.01.2507.037 according to Healthchecker.ps1
Version: Exchange 2016 CU23 Mar24SUBuild Number: 15.01.2507.037 However,
the servers show up in the out-of-date connecting on-premises Exchange
Servers list as 15.1.2507.17. There were no throttled or blocked yet.
Should we be conce...
Latest Comments