After the release of Outlook 2016 there is lot of curiosity among the user and many people already have started using it in their day to day life but with new technology there is always something missing though what we are discussing today is not some technical error rather a technical advancement that was made to simplify Outlook connectivity with the Exchange Server. With more update I guess Microsoft will take of this but as of now there is a simple patch.
This tutorial will guide you to method to fix the issue that you encounter when connecting with Exchange Server and Outlook 2016. The prima facie evidence suggests that the problem lays with the Microsoft engineer dumping the RPC/HTTP standard over the more resilient and diverse MAPI/HTTP standard which was first implemented in Outlook 2013 and Exchange Server 2013.
Why the error “on-premise public Folder not accessible” is in Outlook 2016 but not in Outlook 2010 or 2013
The explanation of this can be attributed to the fact that the pervious build prior to 2016 requires serverDN property (by RPC/HTTP) to connect and log on to the public folder BUT since the Outlook 2016 is trying to connect your primary mailbox with the Exchange Server using MAPI/HTTP protocol there is no serverDN which is a required property in order to connect and log on to your public folders.
Solution: There is a workaround to this issue and you can disable and stop this issue from coming up again.
You have to revert back to RPC/HTTP by setting up the registry key values