Blog Post

Exchange Team Blog
4 MIN READ

Released: August 2022 Exchange Server Security Updates

The_Exchange_Team's avatar
The_Exchange_Team
Icon for Microsoft rankMicrosoft
Aug 09, 2022
Microsoft has released security updates (SUs) for vulnerabilities found in: Exchange Server 2013 Exchange Server 2016 Exchange Server 2019 IMPORTANT: Updates are released in a self-extrac...
Updated Aug 11, 2022
Version 8.0
announcements
security
setup
Timo_'s avatar
Timo_
Copper Contributor
Dec 02, 2022

In case someone else also has problems with PublicFolder permission changes via Outlook after activating EP and gets the error message: "The modified permissions could not be saved".

 

This error only seems to occur when the primary hierarchy PublicFolder mailbox is on a different server than the user's secondary hierarchy mailbox. The RPC cross-server hierarchy call is currently made over HTTP instead of HTTPS. Since EP sets "Require SSL" on the RPC backend, the HTTP cross-server call will fail. This issue has already been reported to Microsoft.

 

Possible workarounds:

- Make the desired changes for your user using PowerShell (Add-PublicFolderClientPermission still works)

- Make sure the PublicFolder primary hierarchy mailbox is on the same server as your secondary hierarchy mailboxes -> avoids RPC cross-server call over HTTP

- Disable "Require SSL" on the RPC backend of the server, which hosts the primary hierarchy mailbox (Disables EP on this vDir)