ADS Endpoint Detection of Exchange Server - Identity Manager

Products

• CA Identity Manager
• CA Identity Suite

Issue/Introduction

This article addresses scenarios where an ADS endpoint fails to detect an Exchange Server during acquisition or refresh operations.

Environment

Identity Manager 14.5

Cause

Failure to detect an Exchange Server is typically caused by insufficient permissions for the user account used to acquire the ADS endpoint. Specifically, the account lacks access to the Microsoft Exchange Services configuration branch.

Resolution

To resolve detection failures, ensure the acquisition account has appropriate privileges and refresh the endpoint configuration:

1. Verify Permissions: Ensure the account used for acquisition has read/browse permissions for the following path in Active Directory: CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=xxx,DC=yyy

2. Refresh AD Endpoint: After confirming permissions, perform a refresh of the Active Directory endpoint to force a re-detection of the Exchange Server.

3. Handle Post-Acquisition Installations: If the Exchange Server was installed after the ADS endpoint was created, manually trigger a refresh to update the endpoint schema and recognize the new server installation.

Additional Information

If an Exchange Server is installed after the ADS endpoint was created, you need to follow the instructions in this article Updating Active Directory Endpoint with New Exchange Server Details and have it recognize the Exchange Server.

For further information about Exchange, see documentation Privileges Required to Connect to Exchange Server

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on your respective region.