サポートと今すぐチャット
サポートとのチャット

Identity Manager 9.1 - 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

System requirements for the Microsoft Exchange synchronization server

To set up synchronization with a Microsoft Exchange environment, a server has to be available that has the following software installed on it:

  • Windows operating system

    The following versions are supported:

    • Windows Server 2022

    • Windows Server 2019

    • Windows Server 2016

    • Windows Server 2012 R2

    • Windows Server 2012

  • Microsoft .NET Framework version 4.8 or later

    NOTE: Take the target system manufacturer's recommendations into account.

  • Windows Management Framework 4.0

IMPORTANT: The Microsoft Exchange One Identity Manager connector uses Windows PowerShell to communicate with the Microsoft Exchange server. For communication, extra configuration is required on the synchronization server and the Microsoft Exchange server.

Related topics

Installing One Identity Manager Service with a Microsoft Exchange connector

The One Identity Manager Service must be installed on the synchronization server with the Microsoft Exchange connector. The synchronization server must be declared as a Job server in One Identity Manager.

Table 3: Properties of the Job server
Property Value
Server function Microsoft Exchange connector
Machine role Server | Job Server | Active Directory | Microsoft Exchange

NOTE: If several target system environments of the same type are synchronized under the same synchronization server, it is recommended that you set up a Job server for each target system for performance reasons. This avoids unnecessary swapping of connections to target systems because a Job server only has to process tasks of the same type (re-use of existing connections).

Use the One Identity Manager Service to install the Server Installer. The program runs the following steps:

  • Sets up a Job server.

  • Specifies machine roles and server function for the Job server.

  • Remotely installs One Identity Manager Service components corresponding to the machine roles.

  • Configures the One Identity Manager Service.

  • Starts the One Identity Manager Service.

NOTE: The program performs a remote installation of the One Identity Manager Service. Local installation of the service is not possible with this program.

To remotely install the One Identity Manager Service, you must have an administrative workstation on which the One Identity Manager components are installed. For more information about installing a workstation, see the One Identity Manager Installation Guide.

NOTE: To generate processes for the Job server, you need the provider, connection parameters, and the authentication data. By default, this information is determined from the database connection data. If the Job server runs through an application server, you must configure extra connection data in the Designer. For more information about setting up Job servers, see the One Identity Manager Configuration Guide.

To remotely install and configure One Identity Manager Service on a server

  1. Start the Server Installer program on your administrative workstation.

  1. On the Database connection page, enter the valid connection credentials for the One Identity Manager database.

  2. On the Server properties page, specify the server on which you want to install the One Identity Manager Service.

    1. Select a Job server from the Server menu.

      - OR -

      To create a new Job server, click Add.

    2. Enter the following data for the Job server.

      • Server: Name of the Job server.

      • Queue: Name of the queue to handle the process steps. Each Job server within the network must have a unique queue identifier. The process steps are requested by the Job queue using this exact queue name. The queue identifier is entered in the One Identity Manager Service configuration file.

      • Full server name: Full server name in accordance with DNS syntax.

        Syntax:

        <Name of servers>.<Fully qualified domain name>

      NOTE: You can use the Extended option to make changes to other properties for the Job server. You can also edit the properties later with the Designer.

  1. On the Machine roles page, select Microsoft Exchange.

  2. On the Server functions page, select Microsoft Exchange connector.

  3. On the Service Settings page, enter the connection data and check the One Identity Manager Service configuration.

    NOTE: The initial service configuration is predefined. If further changes need to be made to the configuration, you can do this later with the Designer. For more information about configuring the service, see the One Identity Manager Configuration Guide.

    • For a direct connection to the database:

      1. Select Process collection > sqlprovider.

      2. Click the Connection parameter entry, then click the Edit button.

      3. Enter the connection data for the One Identity Manager database.

    • For a connection to the application server:

      1. Select Process collection, click the Insert button and select AppServerJobProvider.

      2. Click the Connection parameter entry, then click the Edit button.

      3. Enter the connection data for the application server.

      4. Click the Authentication data entry and click the Edit button.

      5. Select the authentication module. Depending on the authentication module, other data may be required, such as user and password. For more information about One Identity Manager authentication modules, see the One Identity Manager Authorization and Authentication Guide.

  4. To configure remote installations, click Next.

  1. Confirm the security prompt with Yes.

  2. On the Select installation source page, select the directory with the install files. Change the directory if necessary.

  3. If the database is encrypted, on the Select private key file page, select the file with the private key.

  4. On the Service access page, enter the service's installation data.

    • Computer: Enter the name or IP address of the server that the service is installed and started on.

    • Service account: Enter the details of the user account that the One Identity Manager Service is running under. Enter the user account, the user account's password and password confirmation.

    The service is installed using the user account with which you are logged in to the administrative workstation. If you want to use another user account for installing the service, you can enter it in the advanced options. You can also change the One Identity Manager Service details, such as the installation directory, name, display name, and the One Identity Manager Service description, using the advanced options.

  5. Click Next to start installing the service.

    Installation of the service occurs automatically and may take some time.

  6. Click Finish on the last page of the Server Installer.

    NOTE: In a default installation, the service is entered in the server’s service management with the name One Identity Manager Service.

Configuring participating servers for remote access through Windows PowerShell

IMPORTANT: Run the configuration steps on the Microsoft Exchange server and the synchronization server.

To configure a server for remote access using Windows PowerShell

  1. Run Windows PowerShell with administrator credentials from the Run as Administrator context menu.

  2. Enter this command at the prompt:

    winrm quickconfig

    This command prepares for remote access usage.

  3. Enter this command at the prompt:

    Set-ExecutionPolicy RemoteSigned

    This command permits the Windows PowerShell commands (Cmdlets) to be carried out. The script must be signed by a trusted publishers.

  4. Enter this command at the prompt:

    Set-Item wsman:\localhost\client\trustedhosts * -Force

    This command modifies the list of trusted hosts to enable authentication.

    The value * allows all connections. One Identity Manager uses the server's fully qualified domain name for the connection. You can limit the value.

To test remote access through Windows PowerShell from the synchronization server to the Microsoft Exchange server (sync.)

  1. Run Microsoft Exchange on the Windows PowerShell synchronization server.

  2. Enter this command at the prompt:

    $creds = New-Object System.Management.Automation.PSCredential ("<domain>\<user>", (ConvertTo-SecureString "<password>" -AsPlainText -Force))

    - OR -

    $creds = Get-Credential

    This command finds the access data required for establishing the connection.

  3. Enter this command at the prompt:

    $session = New-PSSession -Configurationname Microsoft.Exchange -ConnectionUri http://<ServerName as FQDN>/powershell -Credential $creds -Authentication Kerberos

    This command creates a remote session.

    NOTE: One Identity Manager establishes a connection using the fully qualified domain name of the Microsoft Exchange server. The server name must therefore be in the list configured with trusted hosts.

  4. Enter this command at the prompt:

    Import-PsSession $session

    This command imports the remote session so that the connection can be accessed.

  5. Test the functionality with any Microsoft Exchange command. For example, enter the following command at the prompt:

    Get-Mailbox

Testing Active Directory domain trusts

For synchronization with a Microsoft Exchange environment, Active Directory domain trusts must be declared in One Identity Manager. Users can access resources in other domains depending on the domain trusts.

  • Explicit trusts are loaded into Active Directory by synchronizing with One Identity Manager. Domains which are trusted by the currently synchronized domains are found.

  • To declare implicit two-way trusts between domains within an Active Directory forest in One Identity Manager, ensure that the parent domain is entered in all child domains.

To enter the parent domain

  1. In the Manager, select the Active Directory > Domains category.

  2. Select the domain in the result list.

  3. Select the Change main data task.

  4. Enter the parent domain.

  5. Save the changes.

    Implicit trusts are created automatically.

To test trusted domains

  1. In the Manager, select the Active Directory > Domains category.

  2. Select the domain in the result list.

  3. Select Specify trust relationships.

    This shows domains that trust the selected domain.

For more information, see the One Identity Manager Administration Guide for Connecting to Active Directory.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択