To create linked mailboxes in a Microsoft Exchange resource forest, you must declare the user account with which the linked mailboxes are going to be created as well as the Active Directory domain controller for each Active Directory client domain.
To edit master data for a domain
- In the Manager, select the Active Directory | Domains category.
- Select the domain in the result list and run the Change master data task.
- Enter the following information on the Exchange tab.
Table 3: Domain master data for generating linked mailboxes
| User (linked mailboxes) |
User account that is used to create linked mailboxes. |
| Password |
Password for the user account. |
| Password retry |
Repeat entry of the password for the user account. |
| DC (linked mailbox) |
Active Directory domain controller for creating linked mailboxes. |
- Save the changes.
Related topics
Use the Synchronization Editor to configure synchronization between the One Identity Manager database and Microsoft Exchange environment. The following describes the steps for initial configuration of a synchronization project.
IMPORTANT: Each Microsoft Exchange environment should have its own synchronization project.
After the initial configuration, you can customize and configure workflows within the synchronization project. Use the workflow wizard in the Synchronization Editor for this. The Synchronization Editor also provides different configuration options for a synchronization project.
IMPORTANT: It must be possible to reach Microsoft Exchange servers by DNS query for successful authentication. If the DNS cannot be resolved, the target system connection is refused.
Prerequisites for setting up a synchronization project
- Synchronization of the Active Directory system is carried out regularly.
- The Active Directory forest is declared in One Identity Manager.
- Explicit Active Directory domain trusts are declared in One Identity Manager
- Implicit two-way trusts between domains in an Active Directory forest are declared in One Identity Manager
- User account with password and domain controller on the Microsoft Exchange client domain are entered to create linked mailboxes within an Active Directory resource forest topology
Have the following information available for setting up a synchronization project.
Table 4: Information required for setting up a synchronization project
| Microsoft Exchange version |
One Identity Manager supports synchronization with Microsoft Exchange 2010 Service Pack 3 or later, Microsoft Exchange 2013 with Cumulative Update 23, Microsoft Exchange 2016, and Microsoft Exchange 2019 with Cumulative Update 1. |
| Server (fully qualified) |
Fully qualified name (FQDN) of the Microsoft Exchange server to which the synchronization server connects to access Microsoft Exchange objects.
Example:
Server.Doku.Testlab.dd |
|
User account and password for logging in |
Fully qualified name (FQDN) of the user account and password for logging in on the Microsoft Exchange.
Example:
user@domain.com
domain.com\user
Make a user account available with sufficient permissions. For more information, see Users and permissions for synchronizing with Microsoft Exchange. |
|
Synchronization server for Microsoft Exchange |
The One Identity Manager Service with the Microsoft Exchange connector must be installed on the synchronization server.
Table 5: Additional properties for the Job server
| Server function |
Microsoft Exchange connector |
| Machine role |
Server | Job server | Active Directory | Microsoft Exchange |
For more information, see Setting up the synchronization server. |
| One Identity Manager database connection data |
-
Database server
-
Database
-
SQL Server login and password
-
Specifies whether integrated Windows authentication is used. This type of authentication is not recommended. If you decide to use it anyway, ensure that your environment supports Windows authentication. |
| Remote connection server |
To configure synchronization with a target system, One Identity Manager must load the data from the target system. One Identity Manager communicates directly with the target system to do this. Sometimes direct access from the workstation, on which the Synchronization Editor is installed, is not possible. For example, because of the firewall configuration or the workstation does not fulfill the necessary hardware and software requirements. If direct access is not possible from the workstation, you can set up a remote connection.
The remote connection server and the workstation must be in the same Active Directory domain.
Remote connection server configuration:
-
One Identity Manager Service is started
-
RemoteConnectPlugin is installed
-
Microsoft Exchange connector is installed
The remote connection server must be declared as a Job server in One Identity Manager. The Job server name is required.
TIP: The remote connection server requires the same configuration as the synchronization server (with regard to the installed software and entitlements). Use the synchronization as remote connection server at the same time, by simply installing the RemoteConnectPlugin as well.
For more detailed information about setting up a remote connection, see the One Identity Manager Target System Synchronization Reference Guide. |
NOTE: The following sequence describes how to configure a synchronization project if the
Synchronization Editor is both:
If you execute the project wizard in expert mode or directly from the Synchronization Editor, additional configuration settings can be made. Follow the project wizard instructions through these steps.
To set up initial synchronization project for Microsoft Exchange
-
Start the Launchpad and log in to the One Identity Manager database.
NOTE: If synchronization is executed by an application server, connect the database through the application server.
-
Select the Target system type Microsoft Exchange entry and click Start.
This starts the Synchronization Editor's project wizard.
- Select the connector on the Select target system page.
-
To synchronize a Microsoft Exchange 2010 environment, select the Microsoft Exchange 2010 connector.
-
To synchronize a Microsoft Exchange 2013 environment, select the Microsoft Exchange 2013 connector.
-
To synchronize a Microsoft Exchange 2016 environment, select the Microsoft Exchange 2016 connector.
-
To synchronize a Microsoft Exchange 2019 environment, select the Microsoft Exchange 2019 connector.
-
On the System access page, specify how One Identity Manager can access the target system.
-
If access is possible from the workstation on which you started the Synchronization Editor, do not change any settings.
-
If access is not possible from the workstation on which you started the Synchronization Editor, you can set up a remote connection.
Enable the Connect using remote connection server option and select the server to be used for the connection under Job server.
- Enter the information about the Microsoft Exchange server on the Select Microsoft Exchange server page to which the synchronization server connects to access Microsoft Exchange objects.
- Under Server, enter the fully qualified name (FQDN) of the Microsoft Exchange server. To check the data, click DNS query.
NOTE: If you only know the IP address of the server, enter the IP address in the Server field and click DNS query. The server's fully qualified name is found and entered.
- Under Max. concurrent connections, enter the number of connections that can be used at the same time.
A maximum 4 simultaneous connection are recommended. Synchronization tries to use this many connections. The number may not always be reached depending on the load. Warnings are given respectively.
A default timeout is defined for connecting. The timeout is 5 minutes long for the first connection and 30 seconds for all following connections. The connections are closed if the connection is idle for the duration.
-
To use the Basic authentication method, enable Basic authentication (requires SSL).
NOTE: Microsoft Exchange does not support this authentication type by default. You must configure support for this method in Microsoft Exchange. In addition, an SSL connection is used to authenticate using the Basic method. By default, Kerberos for authentication.
-
Enter login data on the Enter connection credentials page to connect to Microsoft Exchange.
-
To use a defined user account, select the Use following account option and enter the following data:
-
Select the Use account of One Identity Manager Service service option if the user account to use is that of the current user. In the case of synchronization, this is the user account that the One Identity Manager Service is running under. The user account requires the permissions described under Users and permissions for synchronizing with Microsoft Exchange.
NOTE: If this setting is used, the current user account is also used in the Synchronization Editor during configuration.
The user account used with the Synchronization Editor may differ from the One Identity Manager Service's user account. In this case, it is recommended you use the RemoteConnectPlugin. This ensures that the same user account is used during configuration with the Synchronization Editor as is used in the service context.
- On the Recipient scope page, specify whether the recipient of any domain or complete Microsoft Exchange organization should be taken into account.
- To synchronize the recipients of the Microsoft Exchange organization, select the Entire organization option (recommended). As a prerequisite, the trusted domains of the Active Directory domains must be declared in One Identity Manager.
- Select the Only recipients of the following domain option to synchronize recipients with specific domains and select a domain. The target system domain is listed as a minimum.
-
On the One Identity Manager Connection tab, test the data for connecting to the One Identity Manager database. The data is loaded from the connected database. Reenter the password.
NOTE: If you use an unencrypted One Identity Manager database and have not yet saved any synchronization projects to the database, you need to enter all connection data again. This page is not shown if a synchronization project already exists.
-
The wizard loads the target system schema. This may take a few minutes depending on the type of target system access and the size of the target system.
- On the Restrict target system access page, specify how system access should work. You have the following options:
Table 6: Specify target system access
|
Read-only access to target system. |
Specifies that a synchronization workflow is only to be set up for the initial loading of the target system into the One Identity Manager database.
The synchronization workflow has the following characteristics:
- Synchronization is in the direction of One Identity Manager.
- Processing methods in the synchronization steps are only defined for synchronization in the direction of One Identity Manager.
|
|
Read/write access to target system. Provisioning available. |
Specifies whether a provisioning workflow is to be set up in addition to the synchronization workflow for the initial loading of the target system.
The provisioning workflow displays the following characteristics:
- Synchronization is in the direction of the Target system.
- Processing methods are only defined in the synchronization steps for synchronization in the direction of the Target system.
- Synchronization steps are only created for such schema classes whose schema types have write access.
|
- On the Synchronization server page, select a synchronization server to execute synchronization.
If the synchronization server is not declared as a Job server in the One Identity Manager database yet, you can add a new Job server.
-
Click 
to add a new Job server.
-
Enter a name for the Job server and the full server name conforming to DNS syntax.
- Click OK.
The synchronization server is declared as a Job server for the target system in the One Identity Manager database.
NOTE: After you save the synchronization project, ensure that this server is set up as a synchronization server.
- To close the project wizard, click Finish.
This creates and allocates a default schedule for regular synchronization. Enable the schedule for regular synchronization.
The synchronization project is created, saved, and enabled immediately.
NOTE: If enabled, a consistency check is carried out. If errors occur, a message appears. You can decide whether the synchronization project can remain activated or not.
Check the errors before you use the synchronization project. To do this, in the General view on the Synchronization Editor‘s start page, click Verify project.
NOTE: If you do not want the synchronization project to be activated immediately, disable the Activate and save the new synchronization project automatically option. In this case, save the synchronization project manually before closing the Synchronization Editor.
NOTE: The connection data for the target system is saved in a variable set and can be modified in the Configuration | Variables category in the Synchronization Editor.
To configure the content of the synchronization log
-
Open the synchronization project in the Synchronization Editor.
- To configure the synchronization log for target system connection, select the Configuration | Target system category.
- To configure the synchronization log for the database connection, select the Configuration | One Identity Manager connection category.
- Select the General view and click Configure.
- Select the Synchronization log view and set Create synchronization log.
- Enable the data to be logged.
NOTE: Some content generates a particularly large volume of log data. The synchronization log should only contain data required for troubleshooting and other analyses.
- Click OK.
To synchronize on a regular basis
-
Open the synchronization project in the Synchronization Editor.
- Select the Configuration | Start up configurations category.
- Select a start up configuration in the document view and click Edit schedule.
- Edit the schedule properties.
- To enable the schedule, click Activate.
- Click OK.
To start initial synchronization manually
-
Open the synchronization project in the Synchronization Editor.
-
Select the Configuration | Start up configurations category.
-
Select a start up configuration in the document view and click Execute.
- Confirm the security prompt with Yes.
Related topics
Synchronization results are summarized in the synchronization log. You can specify the extent of the synchronization log for each system connection individually. One Identity Manager provides several reports in which the synchronization results are organized under different criteria.
To display a synchronization log
-
Open the synchronization project in the Synchronization Editor.
-
Select the Logs category.
-
Click 
in the navigation view toolbar.
Logs for all completed synchronization runs are displayed in the navigation view.
-
Select a log by double-clicking it.
An analysis of the synchronization is shown as a report. You can save the report.
To display a provisioning log
-
Open the synchronization project in the Synchronization Editor.
-
Select the Logs category.
-
Click 
in the navigation view toolbar.
Logs for all completed provisioning processes are displayed in the navigation view.
-
Select a log by double-clicking it.
An analysis of the provisioning is shown as a report. You can save the report.
The log is marked in color in the navigation view. This mark shows you the status of the synchronization/provisioning.
TIP: The logs are also displayed in the Manager under the <target system> | synchronization log category.
Synchronization logs are stored for a fixed length of time.
To modify the retention period for synchronization logs
The following scenarios for synchronizing Microsoft Exchange are supported.
Scenario: synchronizing Microsoft Exchange infrastructure including all Microsoft Exchange organization recipients
It is recommended on principal that you synchronize the Microsoft Exchange infrastructure including all Microsoft Exchange organization recipients.
The Microsoft Exchange infrastructure elements (server, address lists, policies, for example) and recipients (mailboxes, mail-enabled distribution groups, e-mail users, email contacts) of the entire Microsoft Exchange organization are synchronized.
- Set up a synchronization project and use the Complete organization recipient scope.
For more information, see Creating a synchronization project for initial synchronization of a Microsoft Exchange environment.
Scenario: synchronizing Microsoft Exchange infrastructure and recipients of a select Active Directory domain in the Microsoft Exchange organization.
It is possible to synchronize Microsoft Exchange infrastructure and recipients separately if synchronization of the entire Microsoft Exchange organization is not possible due to the large number of recipients.
First the Microsoft Exchange infrastructure elements (server, address lists, policies, for example) are loaded. Then recipients (mailboxes, mail-enabled distribution groups, e-mail users, email contacts) are synchronized from the given Active Directory domain in the Microsoft Exchange organization.
The following synchronization project configuration is recommended in this case:
NOTE: Use the Synchronization Editor expert mode for the following configurations.
- Set up the synchronization project for synchronizing the entire Microsoft Exchange infrastructure.
- Select the recipient Complete organization.
- Customize the synchronization workflow.
- Disable synchronization steps of all schema types representing recipients. These are:
| Mailbox |
| MailContact |
| MailUser |
| DistributionList |
| DynamicDistributionList |
| MailPublicFolder |
- Check that all schema types, not representing recipients, are synchronized. These are:
| ActiveSyncMailboxPolicy |
| DatabaseAvailabilityGroup |
| MailboxDatabase |
| ManagedFolderMailboxPolicy (Microsoft Exchange 2010) |
| OfflineAddressBook |
| Organization |
| PublicFolder |
| PublicFolderDatabase (Microsoft Exchange 2010) |
| RetentionPolicy |
| RoleAssingmentPolicy |
| Server |
| SharingPolicy |
| AddressList |
| GlobalAddressList |
- Set up the synchronization project for synchronizing recipient of an Active Directory domain.
- Select the recipient scope Only recipients of the following domain and select a domain of the Microsoft Exchange organization.
- Customize the synchronization workflow.
- Disable synchronization steps of all schema types that do not represent recipients. These are:
| ActiveSyncMailboxPolicy |
| DatabaseAvailabilityGroup |
| MailboxDatabase |
| ManagedFolderMailboxPolicy (Microsoft Exchange 2010) |
| OfflineAddressBook |
| Organization |
| PublicFolder |
| PublicFolderDatabase (Microsoft Exchange 2010) |
| RetentionPolicy |
| RoleAssingmentPolicy |
| Server |
| SharingPolicy |
| AddressList |
| GlobalAddressList |
- Check that all schema types not representing recipients are synchronized. These are:
| Mailbox |
| MailContact |
| MailUser |
| DistributionList |
| DynamicDistributionList |
| MailPublicFolder |
- Specify more base objects for the remaining Active Directory domains.
- Customize the synchronization schedule.
IMPORTANT: Set up the synchronization schedules such that the Microsoft Exchange infrastructure is synchronized before Microsoft Exchange recipients.
Several synchronization runs maybe necessary before all the data is synchronized depending on references between the Microsoft Exchange organization domains.
