Late last night we became aware of an issue with MS13-061 security update for Exchange Server 2013. Specifically, after the installation of the security update, the Content Index for mailbox databa...
Updated Jul 01, 2019
Version 2.0
Blog Post
Brian, it appears that the default receive connectors were causing issue. Once you create new receive connectors and verify the IP space mail flows.
Also, as a side note, just had an Exchange 2007Sp3RU11 update corrupt the EWS directory yesterday as well. Had to remove-webservicesvirtualdirectory ews, iisreset, and re-add to fix the problem. Was working with no issues prior to update. Not real happy with the latest round of patches.
I would like to echo some of the other comments here about TechNet retiring. This is such a critical service for all Exchange technicians. How can we, the Exchange community MCSEs, and others still obtain the Exchange 2003, 2007, 2010, and 2013 bits in order to support and migrate the current customer base if we can't even access anything older than 2013? I cannot move a customer from Exchange 2007 to the Office 365 cloud if I cannot test or access the Exchange 2007 software anymore to verify. I can't even train someone to do it. What is the solution that the Exchange group would recommend for people in my position to continue to provide software support for our customers?