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
@Briam (and others), if you are impacted by any particular issue I strongly suggest opening a case with support. This is one of the ways we can (let us assume it is a true code defect) judge the impact of a particular issue and help triage if/when different it should be fixed compared with others we may already be working on. If one person opens a case and then everyone they talk to on Internet message boards sits back and waits to see the outcome it does not provide us with the same data if everyone impacted were to open a case. Leaving comments on this blog is nice and we certainly read all of them, but it does not provide us the full impact view if you were to open a support case. With a case we gather/track additional data linked back to the same issue such as affected customers, seats affected, etc... to help triage against the other work items.
Regarding the meeting forwards item Briam mentions, I would not expect a public hotfix. The Exchange 2013 servicing model only releases Cumulative Updates (on roughly a quarterly basis) and stand-alone security updates. This particular item would not fall under the security update category.