Hosted Exchange Service Deployment

Hosted Exchange Service Deployment

Objective

This article provides a guide to installing the Hosted Exchange service into the Atria Platform.

Web Service and Schema Installation

The first step for deployment of any new Service is to install the Web Service (if required) and its associated Service Schema.  Some services will only require a scheme installation to be perform.  Please refer to the Services section of the following article for deploy instructions:  Atria v12 Deployment Guide

Once installation of your Service is completed successfully you can proceed to the next section.

Configure the Service

To configure the Hosted Exchange service:
  1. Enable the service (top level) and create user and customer plans:
    1. From the Atria menu bar, select Configuration > System Manager > Service Deployment and then expand Hosted Exchange.
    2. Click User Plans, enter a Name for the user plan, and then click Create.
    3. Click Customer Plans, create a customer plan, click Create, and then click Save.
  2. Enable the service (location level):
    1. Under Service Filter, select Active Directory Location Services and choose a Location Filter, if applicable.
    2. Expand Hosted Exchange and then click Save.
  3. Verify credentials:
    1. From the context menu, select Credentials.
    2. Verify that the service account for the Hosted Exchange service exists. If it does not, create the account.
  4. Enable the server:
    1. From the context menu, select Servers.
    2. If the server where the Exchange web service is installed is not listed, click Refresh Server List.
    3. Expand the entry for the server and verify that Server Enabled is selected.
  5. Assign server roles:
    1. From the context menu, select Server Roles and then expand the entry for the server.
    2. Under Server Connection Components, select Hosted Exchange and then click Save.
  6. Add a server connection:
    1. From the context menu, select Server Connections, select a Location Filter if applicable, click New Connection, and then specify the following information for the Hosted Exchange service:
      1. Server Role: Hosted Exchange.
      2. Server: Choose the server where the Exchange Web Service is installed.
      3. Credentials: Choose the credentials for the Exchange web service.
      4. URL Base: Defaults to /ExchangeWS/HostedExchange.asmx.
      5. Protocol: Defaults to http.
      6. Port: Defaults to 8095 (If you change the port here, make sure it matches the bindings in IIS for the Exchange Web Service.)
      7. Timeout: Defaults to 200000 milliseconds.
      8. Version: Select the Exchange version that you are configuring.
    2. Click Save.
    3. Click the icon in the Test column for the Exchange server. The icon turns green for a successful connection. A red icon indicates an unsuccessful connection. Mouse over it for information about the failed connection.
  7. Update service settings as needed:
    1. From the context menu, select Service Deployment, select Active Directory Location Services, and then choose a Location Filter if applicable.
    2. Expand Hosted Exchange and then click Service Settings.
    3. Configure the following required settings:
      1. Any setting that includes the value [ExchangeServer] Replace with the Exchange server's name.
      2. System Domain: If this is not set to the correct domain, provisioning will fail. This should match the default Accepted Domain within Exchange
      3. Public Folders > Public Folders Enabled: Select the check box to provision Public Folders..
      4. Public Folders > Public Folder Server: Select this check box, click Reload to replace the default public folder server, and then select the check box for the public folder server.
      5. Offline Address Book (OAB): OABs can be distributed using public folders (prior to Exchange 2013 only) or web-based virtual directories. To distribute OABs using public folders:
        1. Expand Offline Address Book (OAB) and then select the Public Folder Distribution check box.
        2. Select the Public Folder Servers check box and the check box for the server (if the correct server is not listed, click Reload).
      6. Click the Server check box and the check box for the server (click Reload if needed). To distribute OABs using virtual directories:
        1. Expand Offline Address Book (OAB) and verify that the Public Folder Distribution and Public Folder Servers check boxes are cleared.
        2. Click the Server check box and the check box for the server (click Reload if needed).
        3. Select the Virtual Directory check box, click Reload, select the check box for the server, and then click Enable web-based distribution.

Configure personal archives

Personal archives are a feature made available from Exchange 2010 and beyond that allow users to store older messages in a server-side mailbox instead of in a .pst file that is stored locally. Users can access their personal archive mailbox through their Outlook Client or the Outlook Web App.

Enabling personal archives includes the following tasks:

Enable support in Atria. Because support for personal archives is not enabled by default, you must enable it for each applicable Hosted Exchange user plan you intend to provision. If support is not enabled, personal archives are not available to the user when the Hosted Exchange service is provisioned.

Enable personal archives for each user in Exchange. If personal archives are not enabled in Exchange for the user when the Hosted Exchange service is provisioned, Atria enables the feature automatically. If no mailbox database is specified when the user plan is configured, Atria selects the appropriate mailbox database automatically when the user is provisioned.

To enable support for personal archives:
  1. From the Atria menu bar, click Configuration > System Manager > Service Deployment.
  2. Under Service Filter, select Active Directory Location Services and choose a Location Filter, if applicable
  3. Expand Hosted Exchange and then click User Plans.
  4. Select an existing user plan for which you want enable support for personal archives.
  5. Expand the Mail Archiving Exchange 2010 / 2013 category and select the Enabled checkbox.
  6. n Mailbox Database, select the mailbox database that Atria will use for personal archives. If no database is selected, one will be automatically chosen when the user is provisioned.
  7. Click Apply Changes and then click Save.

Configure PST File Import and Export

Configure PST file import and export to enable Atria to import and export Exchange personal store mailboxes using a network share or an FTP server.

How to store imported and exported PST files:

Create a network shared folder with share name "WebHosting" on a file server in your environment. This shared folder is where Exchange will save exported PST and seek during PST import. Security permission for the shared folder is described in Steps 2b-2d of To configure the FTP server for PST import and export. 

If you offer customers to export and import PST without Service Provider assistance, set up an FTP server in your environment. The FTP server will enable access to the "WebHosting" shared folder where exported and imported PST are stored. Access to a customer's folder on the FTP server is limited to that customer's users who have the Hosted Exchange Service Administrator security role.

To configure the FTP server for PST import and export:
  1. In Active Directory, perform the following actions:
    1. Create a new user account called servername_pst in the CortexSystem OU.
    2. Grant Read permissions of the servername_pst account to the Customers OU.
    3. Add the servername_pst account to the CortexAdmins group.
  2. For the FTP server, perform the following actions:
    1. On the FTP server, create a new folder for use by Atria. The default path is C:\CortexFTP.
    2. Share the folder as Webhosting and grant Full Control of the share to Everyone.
    3. In the folder properties, on the Security tab, verify that inheritance is disabled and, when prompted, click Add to copy the current permissions to the folder.
    4. Add the domain security group ServiceAdmins HE to the ACL of the folder and grant List Folder Contents permissions.
    5. Add the servername_pst account to the ACL of the folder and grant it List Folder Contents permission.
    6. Add domain security group Exchange Trusted Subsystem and grant Full Control permission.
  3. Add and configure the FTP site in IIS:
    1. On the FTP server, open the IIS Management Console and then navigate to the Sites container.
    2. Right-click the Sites container, choose Add FTP Site, and configure it.
      1. Site Information
        1. FTP site name: A name such as "Atria PST FTP Site"
        2. Physical path: The path configured above
      2. Binding and SSL Settings
        1. Binding IP Address: An IP address and port or All Unassigned
        2. SSL: Allow SSL
      3. Authentication and Authorization Information
        1. Authentication: Basic
        2. Authorization:
          1. Allow access to: Specified roles or user groups Authorization (credentials): domain\ServiceAdmins HE
          2. Permissions: Read and Write
    3. Select the FTP site node in the console's left pane and, in the Features view, perform the following actions:
      1. Double-click FTP User Isolation and choose FTP home directory configured in Active Directory.
      2. Click Set to specify the credentials in Domain\Username format for the servername_pst account set up earlier.
      3. Click Apply to save your changes.
    4. Select the FTP site node in the console's left pane and, in the Features view, perform the following actions:
      1. Double-click FTP Authentication.
      2. Disable Anonymous Authentication and enable Basic Authentication.
      3. With Basic Authentication selected, click Edit and set the Default domain to the fully-qualified domain name. 
      4. Restart the FTP site.
      5. Restart the Microsoft FTP Service.  
* servername_pst account is used to contact the Active Directory to read user's msIIS-FTPDir and msIIS-FTPRoot attribute 

For details about FTP User Isolation see here.
For details about FTP over SSL click here. On IIS 10, "Explicit FTPS" is the default encryption. This should be the specified on the FTP client. 


To configure PST file import and export in Atria.

The steps below assumes the Hosted Exchange service has been enabled and configured. If not, see Web Service and Schema Installation together with Configure Service
  1. Additional service settings:
    1. From the Atria menu bar, choose Configuration > System Manager > Service Deployment.
    2. Under Service Filter, select 
      , and expand Hosted Exchange.
    3. Click Service Settings, expand Mailbox Import/Export, and then select the Enabled check box.
    4. Configure the following settings:
      1. Bad Item Limit: Enter a value for the number of corrupt messages to skip during an export. Default = 0.
        1. To set a value greater than 50, edit the NewMailboxExportRequest.ps1 and NewMailboxImportRequest.ps1 scripts and add the -AcceptLargeDataLoss parameter, setting it to $true. Typically, these scripts are located on the server hosting the Exchange web service at C:\Inetpub\CortexServices\ExchangeWS\Scripts.
      2. Export File Pattern: The pattern for the filename of the PST file. Default = {username}.pst
      3. Export Path Pattern: The pattern for the export folder name that Services Manager creates for the customer. Default = MailboxExport\
      4. FTP Message: If using FTP, the message that is displayed on the Import/Export page in the control panel.
      5. FTP Root: The FTP root folder. Default = \\LocalHost\WebHosting
      6. Import Export Server: The name of the server where the PST files reside for import and export. This value is used to form the Root Path Pattern value.
      7. Import Path Pattern: The pattern of the import folder name that Services Manager creates for the customer. Default = MailboxImport\
      8. Root Path Pattern: The full path to the customer's import and export location. The Export Path Pattern and Import Path Pattern values are appended Root Path Pattern value to form the complete path. Default = \\[FTP-Server]\WebHosting\{CustomerShortName}
        1. Example: \\MyFTPServer\WebHosting\{CustomerShortName}                                                                                                                                * {CustomerShortName} is a variable were a new folder will be created with the Customer's code. 
      9. Zip Files: (Optional) Select this option to export PST files as ZIP archive files. We recommend clearing this option for mailboxes larger than 2 GB.
    5. Click Save.
  2. Reprovision the Hosted Exchange service to existing customers. This action creates a folder for each customer and ensures all required permissions are applied to the folder

Configure Unified Messaging

  1. From the main menu, choose Configuration > System Manager > Service Deployment, expand Hosted Exchange or Hosted Exchange Multi-tenanted, and then click Service Settings.
  2. Expand Unified Messaging and complete the settings. Use the Exchange Management Console to look up the Mailbox Policy name under Organizational Configuration > Unified Messaging > UM Mailbox Policies.
  3. From Category Filter, choose User and then expand Unified Messaging.
  4. In Extensions, enter the starting point for the auto-generated extensions. Use the same number of digits configured in Exchange for extensions.
  5. Click Apply Changes and then click User Plans.
  6. Expand the user, expand Unified Messaging, and then complete the applicable settings. Required: Select the Unified Messaging check box to enable the feature for a mailbox.

    • Related Articles

    • Hosted Exchange Version Migration

      Overview Atria supports multi-Exchange version coexistence. There will be a time where you may want to upgrade/migrate a customer’s assigned version to a higher one. This article gives an overview of how Atria interacts with Exchange, considerations ...

    • Atria and CPSM impacted by Microsoft Exchange April Update

      Overview This issue impacts any version of CPSM or Atria used to manage Exchange 2013, 2016 or 2019 which have received the April Microsoft security update. Last week Microsoft released a set of critical security fixes to Exchange ...

    • Planned Retirement of Hosted Apps and Desktops Service

      Overlap between existing Atria service modules Atria has two core service modules used for managing Desktops, Applications and associated Resources.  These are known as “Citrix” Service, (CITRIX) and “Hosted Apps and Desktops” Service (HAAD) These ...

    • How to Migrate from Hosted Exchange to Exchange Online

      Overview This article provides an example of how to migrate from the Atria Hosted Exchange Service to the Microsoft Online Service.  It will cover the change in service as well as data migration.  The process will use the following free Microsoft ...

    • Microsoft Online Service Deployment

      Objective This article provides a guide to installing the Microsoft Online (MSOL) service into the Atria Platform. Web Service and Schema Installation The first step for the deployment of any new Service is to install the Web Service (if required) ...