Hello. I tried reading through all the comments first, so apologies if
this was addressed, but if you are using hybrid and have migrated 100%
of the mailboxes, you have decommissioned all servers except for 1, but
powered it off to leave attributes in AD, and you have a single Windows
2019 server th...
I wanted to piggy back off of RuffDay's comment about running the report
after performing an upgrade/update to the exchange build. Is there a way
to test or confirm that an exchange server will not be throttled in the
future, other than just looking at the server build number? I got up to
build 15.0...
Hi @KevinShaughnessy I have similar issue that Peter used to have a
while ago. I have two Exchange servers patched with the recent updates.
Health checker confirms that the build is 15.01.2507.039The problem is
that the servers appears in the report with the incorrect build:
15.1.2507.17, the same a...
@Lukas Sassl Thank you for your reply, I just disabled unpatched servers
from load balancer and left only patched server and everything worked
well, now I am sure problem will be resolved after patching all servers
@dubilava1655 make sure to update all of them to the latest version.
Exchange Server 2016 CU20 is very old and we've made many changes with
the latest version (CU23 + April 2024 HU) compared to CU20. @srfndoc
@Global_Helpdesk I can confirm that the issue with the piped cmdlet
still exists in the lat...
Latest Comments