HKEY_CURRENT_USER\Software\Microsoft\Exchange] “MapiHttpDisabled”=dword:00000001įor more detailed explanation of the process of how you can revert back to RPC/HTTP please see this post or watch this video to know the working process. Based on my knowledge, we would need to move the public folder proxy mailbox to the Public Folder Server with the CAS Role and set the public folder database for the Exchange 2016 mailboxes to point to that Public Folder Server. Once you have done this, the public folder (s) will appear. You have to revert back to RPC/HTTP by setting up the registry key values To view Public Folders in OWA you have to right-click on Favorites and select add public folder: Next select the folder you want to add anc click add: Unfortunately, public folders can only be added one at a time, so you will have to do this for every public folder you want to add. If you only have one Public Folder mailbox configured in O365 you can copy/paste: Powershell. Outlook cant access public folders hosted on legacy Exchange serversxecuting the following cmdlet on an Exchange 2016 hosted mailbox displays the DefaultPublicFolderMailbox field as being blank: After a bit more searching with different strings, I managed to find the solution in the following KB: In the File name entry field, enter the PST file name of your choice. Update-PublicFolderMailbox -Identity PUBLICFOLDERNAME -SuppressStatus -Fullsync -InvokeSynchronizer. If an email is sent to them, an NDR is returned stating the recipient cannot be found. Take that Name and use it in the -Identity Parameter in: Powershell. Solution: There is a workaround to this issue and you can disable and stop this issue from coming up again. The mail-enabled public folders that arent returned by Get-PublicFolder dont display in Outlook or in the EAC. 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. Why the error “on-premise public Folder not accessible” is in Outlook 2016 but not in Outlook 2010 or 2013 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. This tutorial will guide you to method to fix the issue that you encounter when connecting with Exchange Server and Outlook 2016.
#UNABLE TO VIEW PUBLIC FOLDERS IN OUTLOOK 2016 UPDATE#
With more update I guess Microsoft will take of this but as of now there is a simple patch.
Modified: December 8th, 2017 | 2 Minutes ReadingĪfter 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.