Export (0) Print
Expand All

Configure legacy public folders where user mailboxes are on Exchange 2013 servers

 

Topic Last Modified: 2014-05-23

In Exchange Server 2013, you’ll need to perform this task to make sure that users can access public folders if you have Exchange 2013 users accessing Exchange 2010 or earlier public folders (also known as legacy public folders).

Users whose mailboxes are on Exchange Server 2013 won’t be able to access legacy public folders from Outlook Web App or Outlook for Mac.

  1. If your public folders are on Exchange 2010 or later servers, then you need to install the Client Access Server role on all mailbox servers that have a public folder database. This allows the Microsoft Exchange RpcClientAccess service to be running, which allows for all clients to access public folders. The client access role isn’t required for Exchange 2007 public folder servers, and this step isn’t necessary. For more information, see Install Exchange Server 2010.

    NoteNote:
    This server doesn’t have to be part of the Client Access load balancing. For more information, see Understanding Load Balancing in Exchange 2010.
  2. Create an empty mailbox database on each public folder server.

    For Exchange 2010, run the following command. This command excludes the mailbox database from the mailbox provisioning load balancer. This prevents new mailboxes from automatically being added to this database.

    New-MailboxDatabase -Server <PFServerName_with_CASRole> -Name <NewMDBforPFs> -IsExcludedFromProvisioning $true 
    

    For Exchange 2007, run the following command:

    New-MailboxDatabase -StorageGroup "<PFServerName>\StorageGroup>" -Name <NewMDBforPFs>
    
    NoteNote:
    We recommend that the only mailbox that you add to this database is the proxy mailbox that you’ll create in step 3. No other mailboxes should be created on this mailbox database.
  3. Create a proxy mailbox within the new mailbox database and hide the mailbox from the address book. The SMTP of this mailbox will be returned by AutoDiscover as the DefaultPublicFolderMailbox SMTP, so that by resolving this SMTP the client can reach the legacy exchange server for public folder access.

    New-Mailbox -Name <PFMailbox1> -Database <NewMDBforPFs> 
    
    Set-Mailbox -Identity <PFMailbox1> -HiddenFromAddressListsEnabled $true
    
  4. For Exchange 2010, enable AutoDiscover to return the proxy public folder mailboxes. This step isn’t necessary for Exchange 2007.

    Set-MailboxDatabase <NewMDBforPFs> -RPCClientAccessServer <PFServerName_with_CASRole>
    
  5. Repeat the preceding steps for every public folder server in your organization.

The final step in this procedure is to configure the user mailboxes to allow access to the legacy on-premises public folders.

Enable the Exchange Server 2013 on-premises users to access the legacy public folders. You will point to all of the proxy public folder mailboxes that you created in Step 1: Make the Exchange 2010 public folders discoverable. Run the following command from an Exchange 2013 server with the CU5 or higher update.

Set-OrganizationConfig -PublicFoldersEnabled Remote -RemotePublicFolderMailboxes ProxyMailbox1,ProxyMailbox2,ProxyMailbox3
NoteNote:
You must wait until ActiveDirectory synchronization has completed to see the changes. This process may take several hours.

Log on to Outlook for a user whose mailbox is on an Exchange Server 2013 CU5 or higher server and perform the following public folder tests:

  1. Make sure that the Outlook client is running.

  2. Hold down the CTRL key, and then right-click on the Outlook icon in the notification area on the right side of the Windows task bar.

  3. Select Test E-Mail Auto Configuration…

  4. Make sure the Text E-mail Auto Configuration tool returns the following information in the XML tab:

    • <PublicFolderInformation>

    • <SmtpAddress><SMTP Address for public folder mailbox</SmtpAddress>

    • </PublicFolderInformation>

  5. In the Outlook client, peform the following tasks:

    • View the public folder hierarchy.

    • Check permissions.

    • Create and delete public folders.

    • Post content to and delete content from a public folder.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft