Loading...

Prerequisites for Office 365 with Exchange for the Exchange Mailbox (Classic) Agent

Table of Contents

Microsoft Outlook Requirements

Connecting a Remote PowerShell Session to Office 365 with Exchange

Assigning Full Access to Service Accounts

Verifying the Windows PowerShell Execution Policy

Disabling MAPI Over HTTP

Creating a Service Account Profile for Microsoft Outlook

Exchange Server Requirements

Important:

On October 31, 2017, Microsoft ended support for RPC over HTTP for Office 365. For more information, see the Microsoft support article: "RPC over HTTP reaches end of support in Office 365 on October 31, 2017", https://support.microsoft.com/en-us/help/3201590/rpc-over-http-reaches-end-of-support-in-office-365-on-october-31-2017.

After December 15, 2018, Commvault will not support backup nor archiving operations using Office 365 (Exchange Online) for the Exchange Mailbox (Classic) Agent nor OnePass for Exchange Mailbox (Classic).

Transition to the Exchange Mailbox Agent. The Exchange Mailbox Agent uses EWS for backup and archiving instead of MAPI.

For information, see Transitioning to the Exchange Mailbox Agent.

Microsoft Outlook Requirements

  • Microsoft Outlook 2013 Service Pack 1 or later.
  • Either of the following:
    • For Microsoft Outlook 32-bit installation, install the 32-bit version of the agent.
    • For Microsoft Outlook 64-bit installation, install the 64-bit version of the agent.

      Note: Use only the traditional Windows Installer-based (MSI) method to install Microsoft Office. Other methods, such as Click-to-Run, are not supported.

Other Considerations for Microsoft Outlook

You must use a static profile. To change the profile from dynamic to static, set the value in the CreateProcessSpecificProfile additional setting to 0.

Connecting a Remote PowerShell Session to Office 365 with Exchange

For some tasks related to Office 365 with Exchange, you must use Windows PowerShell to create a remote PowerShell session to Office 365 with Exchange. For more information about how to create the session, see the Microsoft TechNet article "Connect to Exchange Online PowerShell", https://technet.microsoft.com/library/jj984289(v=exchg.160).aspx.

Important: Before you perform any tasks that use the remote PowerShell session, you must run the following cmdlet:

Enable-OrganizationCustomization

You only need to run this cmdlet once. If you run it again later, you will receive an error.

For more information, see the Microsoft TechNet article "Enable-OrganizationCustomization", https://technet.microsoft.com/en-us/library/jj200665(v=exchg.160).aspx.

Assigning Full Access to Service Accounts

The service account must have full access rights to all mailboxes on the server.

In an Office 365 with Exchange environment, you can assign full access only to mailboxes that currently exist. As you add mailboxes, you must assign full access to the new mailboxes individually. Failure to assign access to newly added mailboxes causes backups of those mailboxes to fail. To prevent backup failures, you can assign full access to one mailbox at a time.

The Office 365 with Exchange Administrator Account must meet the following requirements:

  • Must have the Office 365 Exchange Administrator role.
  • Must be an online mailbox.
  • The Exchange Administrator Service Account (Windows user) must be a member of the Local Administrator Group.

Note: In a hosted-only environment, the Office 365 with Exchange Administrator Account and the Exchange Administrator Service Account are two different accounts.

Procedure

  1. Open Windows PowerShell and create a remote PowerShell session to Office 365 with Exchange.
  2. Assign full access to all existing mailboxes or to one newly added mailbox.
    • To assign full access to all existing mailboxes, type the following command:

      Get-Mailbox -ResultSize unlimited | Add-MailboxPermission -User "<service_account>" -AccessRights FullAccess -InheritanceType all -AutoMapping: $false

    • To assign full access to one mailbox, type the following command:

      Add-MailboxPermission -Identity "<mailbox_name>" -User "<service_account>" -AccessRights FullAccess -InheritanceType all -AutoMapping:$false

    Where:

    service account is the Office 365 with Exchange (Exchange Online) Administrator Account (Office 365 with Exchange user).

    mailbox name is the name of a mailbox on the server that you want to back up.

    Note:The AutoMapping:$false parameter disables the Exchange automapping ability. For more information, see the Microsoft support article KB 2646504: "How to remove automapping for a shared mailbox in Office 365".

  3. To verify that a mailbox has been assigned Full Access Permissions, type the following command:

    Get-MailboxPermission -Identity "<mailbox_name>"

Verifying the Windows PowerShell Execution Policy

Verify the execution policy.

Procedure

  1. Open Windows PowerShell and create a remote PowerShell session to Office 365 with Exchange.
  2. To verify that the current execution policy is RemoteSigned, run the following cmdlet:

    get-ExecutionPolicy

  3. If the current execution policy is not RemoteSigned, run the following cmdlet:

    set-ExecutionPolicy RemoteSigned

Disabling MAPI Over HTTP

Office 365 with Exchange backups require RPC over HTTP. You must disable MAPI over HTTP before you configure accounts for Office 365 with Exchange.

Procedure

  1. Log on as the service account to the access node.
  2. In Windows on the client computer, click Start, and then type regedit in the Search programs and files box.
  3. Press Enter.

    The Registry Editor appears.

  4. Expand HKEY_CURRENT_USER > Software > Microsoft > Exchange.
  5. Right-click Exchange, and then click New > DWORD.

    A new DWORD entry appears in the right pane.

  6. Right-click the new DWORD entry, and then click Rename.
  7. Type MapiHttpDisabled.
  8. Right-click the MapiHttpDisabled entry, and then click Modify.

    The Edit DWORD Value dialog box appears.

  9. In the Value box, type 00000001, and then click OK.
  10. Close the Registry Editor.
  11. Verify that the protocol has been changed to RPC over HTTP.
    1. Restart Microsoft Outlook.
    2. Press Ctrl and right-click the Microsoft Outlook icon in the notification area at the far right of the task bar.
    3. Click Connection Status.

      The Microsoft Exchange Connection Status dialog box appears.

    4. Verify that the value in the Protocol column is RPC/HTTP.
    5. If the value is HTTP, delete the Microsoft Outlook profile, and then recreate it using the same service account.

Creating a Service Account Profile for Microsoft Outlook

Procedure

  1. Log on to the proxy client where you plan to locate the agent.

    Use the credentials for the Windows account that you defined in the mailbox agent properties.

  2. In Windows, open the Control Panel program, and then click Mail.

    The Mail Setup dialog box appears.

  3. Click Show Profiles.

    The Mail dialog box appears.

  4. Click Add.

    The New Profile dialog box appears.

  5. In the Profile Name box, type the same profile name that you specified in the agent properties, and then click OK.

    The Add New Account wizard appears.

  6. If necessary, change the E-mail Address value to the Office 365 with Exchange service account, and then click Next.
  7. After the account is configured, select the Manually configure server settings check box, and then click Next.
  8. Clear the Use Cached Exchange Mode check box, and then click Finish.

    You are returned to the Mail dialog box.

  9. Select Prompt for a profile to be used, and then click OK.
  10. Open Microsoft Outlook and choose the new profile.
  11. When you are prompted to enter the password, select the Remember my credentials check box, type the password, and then click OK.
  12. Make sure that Microsoft Outlook opens the correct email account.
  13. Close Microsoft Outlook, and then reopen it with the same profile to make sure that you are not prompted to enter a password.

Exchange Server Requirements

  • The agent must be located off-host. That is, it must be located on a different computer than the computer where the Exchange server is installed.
  • If you use both Office 365 with Exchange and an on-premises server, you cannot use the same agent to back up data for both types of servers. You can do either of the following:
    • Use the same off-host proxy, but different instances for each server type.
    • Use a different off-host proxy for each server type.
  • Locate the agent and Microsoft Outlook on the same computer.
  • Install .NET Framework 3.5 on the Office 365 with Exchange agent computer.

    You can install version 3.5 and later versions of .NET Framework on the same computer.

The following Commvault features are not supported for Office 365 with Exchange:

  • Auto Discover options:
    • Active Directory User Group Affinity
    • Database Affinity
  • Mailbox-level delegation
  • Mailbox Quota Rules
  • Exchange Offline Mining
  • Exchange Archive mailbox
  • Retention Tags

Last modified: 4/12/2018 3:08:31 PM