Chat now with support
Chat with Support

Identity Manager 8.1.5 - Administration Guide for Connecting to Microsoft Exchange

Managing Microsoft Exchange environments Setting up Microsoft Exchange synchronization Basic data for managing a Microsoft Exchange environment Microsoft Exchange structure Microsoft Exchange mailboxes Email users and email contacts Mail-enabled distribution groups Dynamic distribution groups 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

Users and permissions for synchronizing with Microsoft Exchange

The following users are involved in synchronizing One Identity Manager with Microsoft Exchange.

Table 2: Users for synchronization
User Permissions
User for accessing Microsoft Exchange You must provide a user account with at least the following authorizations for full synchronization of Microsoft Exchange objects with the supplied One Identity Manager default configuration.

  • Member of the View-only organization management role group

  • Member of the Public folder management role group

  • Member of the Recipient management role group

  • The Security Group Creation and Membership role

    In Microsoft Exchange, create a new role group and assign the role and the user account to this role group.

For more detailed information about managing permissions in Microsoft Exchange, see the Microsoft documentation.

User for creating linked mailboxes The user account is required for adding linked mailboxes. The user account requires read access in Active Directory.

One Identity Manager Service user account

The user account for One Identity Manager Service requires permissions to carry out operations at file level. For example, assigning permissions and creating and editing directories and files.

The user account must belong to the Domain users group.

The user account must have the Login as a service extended user permissions.

The user account requires access permissions to the internal web service.

NOTE: If One Identity Manager Service runs under the network service (NT Authority\NetworkService), you can issue access permissions for the internal web service with the following command line call:

netsh http add urlacl url=http://<IP address>:<port number>/ user="NT AUTHORITY\NETWORKSERVICE"

The user account needs full access to the One Identity Manager Service installation directory in order to automatically update One Identity Manager.

In the default installation, One Identity Manager is installed under:

  • %ProgramFiles(x86)%\One Identity (on 32-bit operating systems)
  • %ProgramFiles%\One Identity (on 64-bit operating systems)
User for accessing the One Identity Manager database

The Synchronization default system user is provided to execute synchronization with an application server.

Setting up the synchronization server

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

  • Windows operating system

    The following versions are supported:

    • Windows Server 2008 R2 (non-Itanium based 64-bit) service pack 1 or later

    • Windows Server 2012

    • Windows Server 2012 R2

    • Windows Server 2016

    • Windows Server 2019

  • Microsoft .NET Framework Version 4.7.2 or later

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

  • Windows Management Framework 4.0

  • One Identity Manager Service, Microsoft Exchange connector
    • Install One Identity Manager components with the installation wizard.
      1. Select Select installation modules with existing database.
      2. Select the Server | Job server | Microsoft Exchange machine role.

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. For more information, see Configuring participating servers for remote access through Windows PowerShell.

All One Identity Manager Service actions are executed against the target system environment on the synchronization server. Data entries required for synchronization and administration with the One Identity Manager database are processed by the synchronization server. The synchronization server must be declared as a Job server in One Identity Manager.

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 executes 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: 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 detailed information about setting up Job servers, see the One Identity Manager Configuration Guide.

NOTE: The program performs a remote installation of the One Identity Manager Service. Local installation of the service is not possible with this program. Remote installation is only supported within a domain or a trusted domain.

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

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

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

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

  3. 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 One Identity Manager Service within the network must have a unique queue identifier. The process steps are requested by the Job queue using this unique queue identifier. 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.

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

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

  6. 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 detailed 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 detailed information about the One Identity Manager authentication modules, see the One Identity Manager Authorization and Authentication Guide.

  7. To configure remote installations, click Next.

  8. Confirm the security prompt with Yes.

  9. On the Select installation source page, select the directory with the install files.

  10. On the Select private key file page, select the file with the private key.

    NOTE: This page is only displayed when the database is encrypted.

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

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

    • Service account: User account data for the One Identity Manager Service.

      • To start the service under the NT AUTHORITY\SYSTEM account, set the Local system account option.

      • To start the service under another account, disable the Local system account option and enter the user account, password and password confirmation.

    • Installation account: Data for the administrative user account to install the service.

      • To use the current user’s account, set the Current user option.

      • To use another user account, disable the Current user option and enter the user account, password and password confirmation.

    • To change the install directory, names, display names, or description of the One Identity Manager Service, use the other options.

  12. Click Next to start installing the service.

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

  13. 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.

Related topics

Configuring participating servers for remote access through Windows PowerShell

NOTE: 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 context menu Run as Administrator.
  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 execution of Windows PowerShell commands (Cmdlets). 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 customizes the list of trusted hosts to activate authentication.

    The value * permits 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 making 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 to 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 master 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 which trust the selected domain.

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

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating