Search Engine: Elastic

Article ID: 115697, created on Mar 12, 2013, last review on Jul 14, 2018

  • Applies to:
  • Operations Automation

Exchange 2013 Support in POA 5.4

Table of Contents

1. Overview
2. Deployment recommendations
3. POA packages
4. Offline Address Books management
5. Public folders management
6. Autodiscover
7. Branding
8. Provisioning scheme
9. Resource Types and Service Templates
10. Additional services
11. Useful EMS cmdlets
12. Known issues

Refer to the following Microsoft Technet articles for details about the changes in the Microsoft Exchange 2013 which are most important for integration with POA:

Exchange 2013 Server Roles
     Mailbox Server
     Client Access Server (CAS)
Mail Flow in Exchange 2013
Exchange Management Shell
Exchange Administration Center
Hierarchical Address Books
Offline Address Books
Public Folders


1. Overview

Exchange 2013 support is implemented in POA 5.4 in the same way as support of previous Exchange versions - via Hosted Exchange Service Controller.

All current Exchange features supported for Exchange 2007/2010 are supported for Exchange 2013 (except for branding).

The major changes:

  • New deployment recommendations
  • New set of packages
  • New Exchange version in Provider and Customer CP
  • New Exchange version support in WPE (Windows Provisioning Engine) providers

2. Deployment recommendations

Exchange 2013 deployment recommendations:

  • Several CAS servers in NLB (Network Load Balancer) cluster with Internet access
  • Several Mailbox servers in DAG (Database Availability Group) without Internet access
  • POA Agent should be installed on all Exchange servers
  • DAG should not be registered in POA as cluster! Each DAG member should be registered as separate Exchange Mailbox server instead.

3. POA packages

The same set of POA packages is available for Exchange 2013 as for Exchange 2007/2010.

POA packages to be installed on Exchange 2013 CAS servers:

  • Exchange2013Protocols
  • Exchange2013Autodiscover
  • Exchange2013POP3
  • Exchange2013IMAP4
  • Exchange2013SMTP
  • Exchange2013SMTPAuth

POA packages to be installed on Exchange 2013 Mailbox servers:

  • Exchange2013Mailstore
  • Exchange2013OAB

4. Offline Address Books management

No need to install the POA Exchange2013OAB package on multiple mailbox servers because one server will generate all OABs.

The Exchange2013OAB package should be installed on a server where Organization Mailbox with OAB capability is located.

5. Public folders management

Public Folder stores still exist in POA, however they mapped to Mailbox databases. The same Mailbox database can be registered as Mailbox Store and Public Folder store in POA.

Public folder mailboxes are being created automatically on demand. Public folders are distributed across Public Folder mailboxes automatically.

All types of Public folders are supported in Exchange 2013 unlike Exchange 2010.

POA creates root hierarchy Public Folder mailbox with the name 'POA-PublicFolderHierarchy' in the 'Users' Active Directory container during the first Exchange2013Mailstore POA package installation.

In POA 5.4.x content of all public folders of one customer's subscription is stored in one public folder mailbox.

Public folder mailbox for each subscription is being created right before the very first public folder is created for subscription. This mailbox is created with the name pfmbx_ROOT_FOLDER_NAME in subscription Organizational Unit (OU) in AD.

Each mailbox in Exchange organization (PA subscription) is associated with the default public folder mailbox which is:
- the POA-PublicFolderHierarchy mailbox before creation the first public folder for subscription
- the dedicated pfmbx_ROOT_FOLDER_NAME mailbox of a subscription after creation the first public folder for subscription

6. Autodiscover

To support Autodiscover functionality for Exchange 2007/2010/2013 POA uses configuration recommended by Microsoft in HMC 4.0/4.5 solution for Exchange 2007.

This solution is based on the special redirect website which handle all Autodiscover requests and redirects these requests to Autodiscover service. To support this solution POA registers 'autodiscover' DNS CNAME record in all domains with 'Hosted Exchange' mail hosting service. This record points to Autodiscover redirect site.

POA Autodiscover redirect site redirects Autodiscover request to the special AutodiscoverProxy URL. Custom application installed in AutodiscoverProxy virtual directory performs local connection to Exchange Autodiscover service and substitute domain names in Exchange Autodiscover service response with FQDNs of the proper branded service.

Autodiscover redirection with SRV-records is not supported by POA currently.

7. Branding

Branding for Exchange 2013 services not supported in POA 5.4.

8. Provisioning scheme

Exchange 2013 provisioning is performed via WPE (Windows Provisioning Engine) only. The same WPE providers are used to manage Exchange 2010 and 2013.

WPE providers detect Exchange version by version of the destination Exchange server provided in each request (the remoteAccess node).

Exchange 2013 Management Tools should be installed on WPE node(s). If Exchange 2010 Management Tools are installed on WPE server they must be removed before installing those of Exchange 2013.

9. Resource Types and Service Templates

POA uses the same 'Hosted Exchange' Resource Class to provision Exchange 2013 services as for all previous Exchange versions.

Use '2013' in the 'Exchange Version' activation parameter in Resource Type or Service Template:

10. Additional services

The following services are not supported in POA 5.4 for Exchange 2013:

  • Unified Messaging
  • Blackberry
  • GoodMobole

The following services are supported in POA 5.4 for Exchange 2013:

  • Spam filtering services  - Postini, MessageLabs and MXLogic
  • Global Relay

11. Useful EMS cmdlets

Public Folders management

Get root hierarchy public folder Mailbox: Get-OrganizationConfig | fl RootPublicFolderMailbox
Get list of all public folder mailboxes: Get-Mailbox –PublicFolder
Get public folder mailbox of subscription: Get-Mailbox -PublicFolder -OrganizationalUnit "SUBSCRIPTION_OU_DN"
Get public folder mailbox where public folder data is stored: Get-PublicFolder -Identity "PF_PATH" | fl ContentMailbox*
Get public folder mailbox associated with user mailbox: Get-Mailbox -Identity  "MAILBOX_IDENTITY" | fl DefaultPublicFolderMailbox

Public Folders mailboxes management

Check synchronization status of PF mailbox: (Get-PublicFolderMailboxDiagnostics -Identity PF_MAILBOX_IDENTITY).SyncInfo
Force PF mailbox synchronization: Update-PublicFolderMailbox -Identity PF_MAILBOX_IDENTITY -InvokeSynchronizer

Offline Address Books management

Find Organization Mailbox with OAB capability: Get-Mailbox -Arbitration | where {$_.PersistedCapabilities -like "*oab*"}

12. Known issues

Exchange 2013 Public Polder creation failed: 'Could not load file or assembly Microsoft.Exchange.Data.dll'

Logon failure on attempt to access mailbox via POP3, IMAP and SMTP in case UPN and primary email address are different

Outlook 2010/2013 cannot access Exchange 2013 Public Folders: 'Can not expand the folder'

caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF