You will have seen the multiple posts and communications around the Hafnium Exchange security issue. One of the most disconcerting issues has been the number of Exchange installs that …
The below are a series of links, tips and some very brief thoughts on Hafnium. I will purposefully not include the content of the other locations as it is changing …
Security updates were released today for Exchange 2010, 2013, 2016 and 2019. Attacks were detected which leveraged these vulnerabilities, so an out of band set of updates was released
This …
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 …
In most enterprise customers there is a segregation of duties between multiple teams. This could be networking and desktop. Or Windows Server platform and messaging. It was the split in …
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 …