On July 12 th , we announced that Exchange Server 2013 RTM CU2 contained an issue that could result in the loss of public folder permissions when the public folder mailbox is moved between Exchan...
Updated Jul 01, 2019
Version 2.0
Blog Post
Hi Exchange Team,
I have some feedback for you - installing CU2v2 has been a pretty painful experience for me.
We have 4 Exchange 2013 servers - 3 CAS+Mailbox running a DAG and 1 Mailbox with no DAG for Archive. Since installing CU2, I have been plagued with the following issues.
- All 4 exchange servers randomly blue screening and rebooting - turns out to be the following issue: http://social.technet.microsoft.com/Forums/exchange/en-US/44d1cd98-cba1-4ed0-b0e7-8aa76ee3eabc/bsod-after-creating-dag
- Microsoft Exchange Frontend Transport service wouldn't come back up on one of my 3 CAS servers - I had to disable the anti malware filter and reboot several times and then restart the frontend transport service before I could get any mail to flow through the server.
- The update has trashed my external autodiscover URL's - Error when configuring autodiscover is now "No external URL is available to access this mailbox with Exchange ActiveSync. Your Exchange server configuration needs to be changed to allow access"
I have literally wasted 2 days just trying to get the environment remotely stable and I just keep coming across more and more things that are broken. I am concerned that I now need to verify every single configuration option to make sure nothing else has gone wrong.
I must say, I am not particularly impressed but hopefully the information is useful to help with future cumulative updates.