It even runs against public folders created on Exchange Online (Office 365). You can run it against legacy public folders on an Exchange 2007 or Exchange 2010 server or against a migrated set of folders on Exchange 2013. This command will return any public folder that stores anything other than plain old mail and post items.
Set up public folder in outlook how to#
It’s better to know this kind of stuff up front rather than have users swamp the help desk demanding to know how to get to their favourite shared calendar or contact list with OWA. The problem that we face is therefore to know whether any non-mail public folders exist in a hierarchy so that we know if users need to be told that they have to use Outlook to access these folders. You can mail-enable a public folder using the Enable-MailPublicFolder cmdlet or through the Exchange Administration Center (EAC). Note that “mail public folders” are different to “mail-enabled public folders.” The former are public folders that hold mail and post items while the latter are public folders whose properties have been updated (for instance, by adding an SMTP address), so that they can receive email (you can also send messages on behalf of a mail-enabled public folder). Other folders (calendars, contacts, tasks, notes, InfoPath, and journal items) are unsupported. Second, OWA can only display “mail public folders”, or public folders that contain “mail and post items” (as they are referred to by Outlook). No access is possible to legacy public folders. I dont know if this is because I am the 'author' or some other reason. In this screen, you can see the public folder server that is servicing the outlook client. I can see the public folders in my outlook. If the problem is specific to this user - Go to the taskbar, hold CTRL key and right click onthe outlook icon, select Connection Status. We don't have an on-premise server for Exchange. That is how I set up additional users and their permissions. In other words, you have to complete your migration to Exchange 2013 and then execute a public folder migration before OWA can be used. Our public folders are listed in the exchange online admin center. First, OWA can only display modern public folders.
Microsoft upgraded OWA in Exchange 2013 CU1 to allow it to display public folders. Equally, there is no way to set the type of information for a new folder when the New-PublicFolder cmdlet is run as this will create a public folder capable of storing messages. Certainly there is no parameter in the Set-PublicFolder cmdlet to do the job.
Once set, there doesn’t seem to be a good way to change the type of information held in a public folder. I can’t remember if this was ever possible with any version OWA it certainly is not with OWA 2013 running against either the on-premises or cloud version of Exchange 2013. You define the kind of information held in a public folder when it is created with Outlook. The issue that I am having is that both the In-Place Archives and Public Folders are failing to show up in Outlook 2016 on the client desktops. Specifying what a new public folder will contain Outlook 2016 - Public Folders & In-Place Archives Hi, I have just deployed an Office 365 solution for one of my clients and migrated their email, data etc to the cloud.