All things Exchange
Almost 10 years ago I ran into a customer deployment where they were unable to run some of the Exchange PowerShell commands. Funnily enough, this bubbled up the other week.
As a recap, tenants are created in a dehydrated state to minimise resouce consumption. That means they can not be customised things like Role Based Access Control (RBAC) assignments are read-only and can not be customised. Th… Read the rest “Tenant Hydration – Still A Thing”
Exchange 2019 CU14 will enforce the use of Extended Protection (EP) by default. This is the desired security configuration as we need to harden the traffic to help prevent Attacker In the Middle (AiTM) style attacks. This is not a new thing, and the Exchange team added support for EP in the previous releases as an optional (but strongly recommended) feature. The intent was that customers would … Read the rest “Exchange 2019 CU14 – Extended Protection New Setup Command Line Options”
Want some updates to go with your updates? That’s pretty much what you are getting with the April 2024 Exchange updates. We can split the features which are part of the April 2024 release into two main areas:
The April 2024 HU is available for the following builds of Exchange Server:
You want to run the Exchange Hybrid Configuration Wizard (HCW) and after clicking the link to the HCW in the admin portal or manually browsing to the shortcut URL you are unable to either launch or install the HCW. Despite using Edge, the HCW application just does not install and/or launch. All you get is the initial prompt to open the file and nothing else.
For example, if we go to the shortcut … Read the rest “Unable To Install or Launch Exchange HCW”
With the release of Exchange 2019 CU14 today, a separate announcement was added to the release post to highlight that only CU23 is supported for Exchange 2016. Exchange Server 2016 is supported until the end of its support in 2025, however in order to receive support and to obtain Security Updates (SUs) you must be running CU23. CU22 and all older releases of Exchange 2016 are no longer supporte… Read the rest “Exchange 2016 – CU23 Now Required”
Exchange 2019 CU14 has been released to the Microsoft Volume Licensing Center and the public Microsoft Download site! Exchange 2019 has a different servicing strategy than Exchange 2007/2010 and utilises Cumulative Updates (CUs) rather than the Rollup Updates (RU/UR) which were used previously. CUs are a complete installation of Exchange 2019 and can be used to install a fresh server or to upd… Read the rest “Exchange 2019 CU14 Released (2024 H1)”
Below is a repro of a customer situation where the Exchange Healthcheck script was unable to connect to a remote Exchange server. The Healthcheck script would run locally with no issues, and reported a clean bill of health.
Note that the expected output log was not present after running the script.
In the command below, we are trying to remotely assess sever Exch-2019-1
It wa… Read the rest “Exchange Healthcheck Script– Unable to Connect to Server”
Today marks the end of Exchange 2019’s mainstream support. This will likely resurface the discussion about what do we do with on-premises Exchange, where is the next version and do we even still need Exchange Server if all mailboxes are in Exchange Online? While there is a solution to removing the last Exchange Server from on-premises it does have it's caveats and considerations. Please ensure … Read the rest “End of Exchange 2019 Mainstream Support”
After upgrading Web Application Proxy (WAP) to Windows Server 2019 you may run into an issue with certain applications that are published via WAP to the Internet.
In the below example the AD FS upgrade went well with no issues. The AD FS farm and WAP servers were upgraded to Windows Server 2019 and all appeared to be going well. Too well that was, as when the external tests were validated against… Read the rest “Unable To Access OWA Externally Via WAP 2019”
Reviewing the output of an environement's CAS Namespaces showed that there was an unexpecte URL present for the version of Exchagne that was installed. With Exchange 2013 onwards InternalNLBBypassURL is not something that we need to set. That was an Exchange 2007 and 2010 thing.
In the environment below note that there are couple of things that pique my interest.
Any thoughts?
What is interesting i… Read the rest “Exchange Unexpected InternalNLBBypass URL – RecoverServer”