After going through the steps to disable TLS 1.0 and TLS 1.1, it was noted that Managed Availability was not happy with one particular component in Exchange 2013. This was …
This case illustrates the "fun" with Managed Availability a particular customer had after making changes to their servers. The servers were built back in 2014, and as such the default …
The security space is constantly evolving, and while a lot of the recent work has been on moving to TLS 1.2, a previous focus in the industry was to stop …
Previously I managed to break one of my labs when replicating a customer situation and then had to fix it as noted in this post from 2017.
This time …
Exchange 2013 introduced the Managed Availability feature, so Exchange can self monitor and perform recovery actions upon itself. While this has greatly helped Exchange become more self-healing, one of the …
When troubleshooting cross-premises calendar availability issues, it can be useful to know the name of the local on-premises endpoint which is used. By knowing the path and URL, you can …
Perhaps the best thing to come to Exchange over the last 10 years was the Hybrid Configuration Wizard (HCW). While many take this feature for granted, if you had to …
For various reasons, the aforementioned Remove-HybridConfiguration cmdlet has been something that has been something I've had to review recently.
This cmdlet is not present in Exchange 2010, it is only …
When reviewing a customer's Exchange server to appraise the current state of their certificates, they saw an "unexpected" certificate on the Exchange server.
The below is an Exchange 2010 …
Managing and maintaining an Exchange server requires multiple actions. Not only do the Exchange CU and security updates need to be installed along with the Windows OS updates, it is …