

exe to extract the contents to a folder called PFDAVAdminĭouble click PFDAVAdmin.exe to start the GUIįrom here you can change permissions on all your public folders, and correct problems such as no owner being defined. And while companies are moving their stuff into the cloud, Public Folders still need to be accessed by cloud-located mailboxes. My real concern was that I couldn't administrate the public folders through ESM - setting permissions and the like.įINALLY I found a tool that will let me administrate them with out using ESM - PFDAVAdmin I'm not really worried about the "error" - the public folders work FINE inside Outlook and OWA. But I couldn't find much about MY error: c0072746Īn existing connection was forcibly closed by the remote host. I cannot see any public or shared folders in Outlook that I know I have access to Symptoms When viewing Outlook from within the Mail view, you cannot see the public folders you have access to, although you can see a folder, which looks like it would be the parent folder of the public or shared folders. There is TONS of errors that may crop up when you try to expand public folders in the Exchange System Manager (ESM).

This issue occurs if the mailbox for the user was created in Exchange Online and doesn't have an associated on-premises user object for authentication to the.

This folder cannot be deleted using the method above. If the Exchange Organisation you are migrating has been on Exchange 2000 and then later 2003 you will have an Internet Newsgroups folder. Network problems are preventing connection to Microsoft Exchange. Select each public folder in the middle pane and right click and select Remove. Process is create as 'Office 365' user on prem, let sync up, assign licence and should be able to access public folders but get the message in outlook 'cannot expand the folder. In this scenario, a user who was created in Exchange Online receives the following error message when they try to access the legacy public folders: Cannot expand the folder. recently noticed that any new 365 user account created in on prem Exchange 2013 management server cant access Public folders which are still on prem. FINALLY!!! This has been bugging me for AGES!!! These folders are also known as legacy public folders.
