Loading...

Prerequisites - Exchange Mailbox (Classic) Agent

Table of Contents

Microsoft Outlook Requirements

  • Microsoft Outlook 2007, 2010, or 2013.
  • 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.

      Notes:

      • Use only the traditional Windows Installer-based (MSI) method to install Microsoft Office. Other methods, such as Click-to-Run, are not supported.
      • If you archive PST files, you must install the 64-bit version of the agent.

If you install the agent on an off-host proxy computer, do the following:

  • Make sure that the proxy computer is added to the same domain where the Exchange server is located.
  • Install Microsoft Outlook 2007, 2010, or 2013 on the off-host proxy computer so that the software drivers that are required for the agent to function in an off-host proxy configuration are installed.

Note: If you use Exchange 2016, you must install Microsoft Outlook 2013 SP1 or later service packs.

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.

Assigning Full Access to Service Accounts

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

Exchange Server 2007 or Later

If the agent is installed on an off-host proxy computer, the service account must be in the Local Administrator Group on the proxy computer.

The service account must be a member of:

  • The Organization Management group (Exchange 2010 or later) or the Exchange Organization Administrators group (Exchange 2007).
  • The Local Administrator Group on the proxy servers.

    If the agent is installed on an off-host proxy computer, the service account must be in the Local Administrator Group on the proxy computer.

Disclaimer: This procedure is performed using the Microsoft ADSI Edit snap-in. The snap-in is subject to change without notice. Consult the Microsoft documentation before you perform this procedure.

Procedure

  1. From the ADSIEDIT snap-in, connect to the domain controller.
  2. In Connection Settings, click Select a well known Naming Context and select Configuration from the list.
  3. Expand Services > Microsoft Exchange.
  4. Right-click the appropriate organization name, and then click Properties.

    The Properties dialog box appears.

  5. Click the Security tab.
  6. Under Permissions, verify that all the permissions for the Organization Management group (Exchange 2010 or later) or the Organization Administrators group (Exchange 2007) are set to Allow.

    Tip: Selecting the Allow for Full Control check box selects Allow for all the permissions. The Deny check box for all permissions must be cleared.

  7. Click OK, and then wait for replication.
  8. To grant Receive As permissions to the service account, open Exchange PowerShell, and then type the following cmdlet:

    Get-MailboxDatabase | Add-ADPermission -user "<service account>" -ExtendedRights Receive-As

    You must include the Receive As permissions to protect archive mailboxes.

    Note: Run the Get-MailboxDatabase cmdlet each time you add a new database.

Office 365 with Exchange

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 (Exchange Online) Administrator Account (Office 365 with Exchange user) must be:
    • a member of Global Admin group
    • an online mailbox
  • The Exchange Administrator Service Account (Windows user), must be a member of the Local Administrator Group.
  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.

    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>"

Exchange Server Requirements

Exchange Server 2013 or Later

  1. Before you run backups, verify that Outlook is running on the client computer and that it is configured to use the same user that is specified in the mailbox agent properties.
  2. On each Exchange server with a Client Access Server (CAS) role:
    1. In PowerShell, run the following command:

      Set-OutlookAnywhere –identity "<Exchange Client Access Server name>\rpc (Default Web Site)" -InternalClientAuthenticationMethod ntlm

    2. In Windows, open the Command Prompt window, and then run IISRESET.
  3. To manage the performance of your Exchange environment and to enforce connection bandwidth limits, set the following throttling policy:
    1. In Windows, on the taskbar, click Start, and then click All Programs > Microsoft Exchange Server version_number.
    2. Click Exchange Management Shell.
    3. Run the following commands:

      New-ThrottlingPolicy CVThrottlingPolicy

      Set-ThrottlingPolicy CVThrottlingPolicy -RCAMaxConcurrency unlimited -RcaMaxBurst unlimited -RcaRechargeRate unlimited -RcaCutoffBalance unlimited –IsServiceAccount:$true

      Set-Mailbox <service account> -ThrottlingPolicy CVThrottlingPolicy

      Where:

      service account is the Exchange Administrator Service Account.

  4. For the throttling policy to take effect immediately, restart the Exchange RPC service.

    Note: If the Exchange Remote Procedure Call (RPC) service is not restarted, it might take the throttling policy up to two hours to take effect.

Exchange Server 2010

To manage the performance of your Exchange environment and enforce connection bandwidth limits, set the throttling policy.

Procedure

  1. On the Exchange Server, from the Windows Start menu, click All Programs > Microsoft Exchange Server 2010.
  2. Click Exchange Management Shell.
  3. Type the following commands:

    New-ThrottlingPolicy –name CVThrottlingPolicy

    Set-ThrottlingPolicy –identity CVThrottlingPolicy –RCAMaxConcurrency $null –RCAPercentTimeInAD $null –RCAPercentTimeInCAS $null –RCAPercentTimeInMailboxRPC $null

    Set-Mailbox –Identity <service account> –ThrottlingPolicy CVThrottlingPolicy

    Where:

    service account is the Exchange Administrator Service Account.

  4. For the throttling policy to take effect immediately, restart the Exchange Remote Procedure Call (RPC) service.

    Note: If the Exchange RPC service is not restarted, it might take the throttling policy up to two hours to take effect.

Office 365 with Exchange

  • The agent must be installed off-host. That is, it must be installed 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.
  • Install the agent and 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 SnapProtect 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

Considerations for Exchange 2016

If you use Exchange 2016, prepare the environment accordingly.

Selecting the Exchange Version for 2016

Wherever you are asked to specify an Exchange version in the SnapProtect software, use Exchange 2013.

Disabling MAPI Over HTTP

Applies to: Exchange 2013 or later

For Exchange 2013 or later, backups require RPC over HTTP. If you have MAPI over HTTP enabled, you must disable it before you configure accounts for Exchange 2013 or later.

Procedure

  1. Log on to the proxy client where you installed the agent.

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

  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 Outlook.
    2. Press Ctrl and right-click the 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 Outlook profile, and then recreate it.
  12. Note: Make sure to use the same Exchange service account name for the new profile and disable cache mode.

Mixed Mode Exchange Server Environments

Applies to: Exchange 2007, Exchange 2010, and Exchange 2013

In a mixed mode environment, Exchange 2013 coexists with Exchange 2010 or 2007, or both. You must set the nMixedMode additional setting so that jobs can be processed using a single service account that is hosted on the Exchange 2013 server.

For more information about Exchange 2013 and mixed mode environment requirements, see the Microsoft TechNet article: "Upgrade from Exchange 2010 to Exchange 2013", https://technet.microsoft.com/en-us/library/jj898583(v=exchg.150).aspx.

Before You Begin

Procedure

  1. From the CommCell Browser, expand Client Computers.
  2. Right-click the client, and then click Properties.

    The Client Computer Properties dialog box appears.

  3. Click Advanced.

    The Advanced Client Properties dialog box appears.

  4. Click the Additional Settings tab.
  5. Click Add.

    The Add Additional Settings dialog box appears.

  6. In the Name box, type nMixedMode.
  7. In the Value box, type 1.
  8. Click OK.
  9. Restart the services.