Chatee ahora con Soporte
Chat con el soporte

Identity Manager 9.0 LTS - Administration Guide for Connecting to Microsoft Exchange

Managing Microsoft Exchange environments Synchronizing a Microsoft Exchange environment
Setting up initial synchronization with Microsoft Exchange Customizing the synchronization configuration Running synchronization Tasks following synchronization Troubleshooting Ignoring data error in synchronization Pausing handling of target system specific processes (Offline mode)
Basic data for managing a Microsoft Exchange environment Microsoft Exchange structure Microsoft Exchange mailboxes Microsoft Exchange mail users and Microsoft Exchange mail contacts Microsoft Exchange mail-enabled distribution groups Microsoft Exchange dynamic distribution groups Microsoft Exchange mail-enabled public folders Extensions for supporting Exchange hybrid environments Error handling Configuration parameters for managing a Microsoft Exchange environment Default project template for Microsoft Exchange Processing methods of Microsoft Exchange system objects Microsoft Exchange connector settings

Advice for synchronizing remote mailboxes

Take the following into account when synchronizing Exchange hybrid remote mailboxes:

  • The mapping for remote mailboxes is part of the Microsoft Exchange project template. Remote mailboxes are synchronized using the Microsoft Exchange connector.

  • If an Exchange hybrid environment already exists but there is no Exchange hybrid module installed, a warning appears when you synchronize. Install the Exchange hybrid module and create a new synchronization project.

  • The following order for is recommended for synchronizing the target systems.

    1. Azure Active Directory

    2. Local Active Directory (in parallel with Azure Active Directory possible)

    3. Exchange Online

    4. Local Microsoft Exchange (if possible, according to Exchange Online)

  • In One Identity Manager, the connection must be defined between the local Microsoft Exchange organization (EX0Organization) and the corresponding Azure Active Directory tenant (AADOrganization).

    This connection is normally created automatically when the synchronization project is created for local Microsoft Exchange. This assumes that Azure Active Directory was already loaded in to the One Identity Manager at the time. You can establish this link manually at any time.

    To declare the Azure Active Directory tenant in a Microsoft Exchange organization

    1. In the Manager, select the Active Directory > Exchange system administration category.

    2. Select the organization from the result list.

    3. Select the Change main data task.

    4. On the Hybrid configuration tab, under Azure Active Directory tenant, select the Azure Active Directory tenant to which your local Microsoft Exchange is connected.

    5. Save the changes.

Related topics

Advice for migrating mailboxes

You cannot move mailboxes between local One Identity Manager and Microsoft Exchange with Exchange Online. Microsoft offers migration scenarios for moving mailboxes. For more information, see your Microsoft documentation.

Synchronizing Microsoft Exchange after moving a mailbox from local Exchange Online to Microsoft Exchange in One Identity Manager results in:

  • A remote mailbox being created

  • The local mailbox being marked as outstanding.

After successful migration, delete outstanding mailboxes in One Identity Manager.

  1. Check whether the mailbox was migrated and whether the Active Directory user account is connected with the local mailbox and a remote mailbox.

    Migrated mailboxes are displayed in the Manager in the Active Directory > Troubleshooting > Mailboxes migrated to Exchange Online category.

    • Select the mailbox and switch to the Active Directory user account overview. Here you can see whether the user account is connected with a local mailbox and a remote mailbox.

  2. Delete the outstanding mailbox.

If you apply an account definition to local mailboxes, create a new account definition for remote mailboxes.

  • If the mailbox account definition currently in use, expects an account definition for Active Directory user accounts, enter this account definition as prerequisite for the remote mailbox account definition.

    IMPORTANT: The remote mailbox account definition may not be distributed automatically to everybody. Otherwise One Identity Manager creates new remote mailboxes.

Example of exchanging account definitions for migrated mailboxes

The following is an example explaining how you can replace account definitions with migrated mailboxes

NOTE: The workflows described here are only for orientation. Always take your customized workflows into account while replacing.

You always required a custom migration scenario if the account definitions are requested through the IT Shop.

Example:

Local mailboxes are managed through an account definition. This account definition requires an account definition for Active Directory user accounts.

The account definition is directly assigned to employees.

After migration, remote mailboxes are also managed through account definitions.

  1. Create an account definition for remote mailboxes. Enter the Active Directory user account's account definition as prerequisite.

  2. After migrating a local mailbox:

    1. Make sure that the remote mailbox exists in One Identity Manager and is linked to the Active Directory user account.

    2. In One Identity Manager, delete the outstanding local mailbox.

    3. Assign the account definition for remote mailboxes to the employee.

    4. Remove the account definition for local mailboxes from the employee.

Example:

Local mailboxes are managed through an account definition. This account definition requires an account definition for Active Directory user accounts.

The account definition is inherited by the employees through it's department relation.

After migration, remote mailboxes are also managed through account definitions.

  1. Create a parallel structure to the department and assign the account definition for local mailboxes to this parallel structure.

    The purpose of this parallel structure is to retain the local mailboxes' account definition assignment to an employee until the mailbox has been successfully migrated.

    • Configure a dynamic role for this parallel structure, to include all employees who:

      • Belong to the department and do not have a remote mailbox.

        or

      • Belong to the department and own a remote mailbox and an outstanding local mailbox.

  2. After completing DBQueue Processor processing, you can remove the account definition for local mailboxes from the department.

  3. Create an account definition for remote mailboxes. Enter the Active Directory user account's account definition as prerequisite.

  4. Create another parallel structure and assign the account definition for remote mailboxes to it..

    The purpose of this parallel structure is to assign the remote mailboxes' account definition to employees after mailbox migration and to retain the assignment of the required account definition for Active Directory.

    • Configure a dynamic role for this parallel structure, to include all employees who:

      • Belong to the department and own a remote mailbox.

  5. Delete the outstanding mailbox after migrating the local mailbox successfully.

  6. After migrating all the department's local mailboxes, you can:

    1. Assign a department to the remote mailboxes' account definition.

    2. Remove the parallel structure.

Creating remote mailboxes

To create a remote mailbox

  1. In the Manager, select the Active Directory > Remote mailboxes category.

  2. Click in the result list.

  3. On the main data form, enter the main data of the mailbox.

  4. Save the changes.

To create a mailbox for an Active Directory user account manually

  1. In the Manager, select the Active Directory > User accounts category.

  2. In the result list, select the user account then select the Change main data task.

  3. Select the Create remote mailbox task.

  4. Enter the following information:

    • Active Directory user account: The user account is already selected.

    • Exchange organization: The exchange organization is already selected. Check the setting.

    • Alias: Unique alias for further identification of the mailbox.

  5. Click OK.

NOTE: After creation of a new remote mailbox, it takes until the next synchronization of your Azure Active Directory tenant in Azure Active Directory Connect until a corresponding mailbox is created in the Exchange Online environment. Up to this point, the mailbox is acknowledged in the local Microsoft Exchange environment but is not yet available for use.

NOTE: After new remote mailboxes of Remote user type have been created by Azure Active Directory or Exchange Online internal processes, an appropriate Exchange license must be assigned for the resulting Azure Active Directory user account.

To display remote mailboxes without Exchange licenses

  • In Manager, select the Active Directory > Exchange system administration > <organization> > Recipient configuration > Remote mailboxes > Remote user mailbox > Without assigned licenses category.

Related topics

Editing remote mailboxes

To edit a mailbox

  1. In the Manager, select the Active Directory > Remote mailboxes category.

  2. In the result list, select the remote mailbox then select the Change main data task.

  3. Edit the remote mailbox's main data.

  4. Save the changes.

Related topics
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación