ADS Endpoint Does Not Detect Exchange - Missing Registry Key

Products

• CA Identity Manager
• CA Identity Suite

Issue/Introduction

Acquired ADS endpoint with ID with proper permissions but the ADS endpoint still does not detect an Exchange Server.

The ADS Endpoint log shows the following:

Exchange2000: License: F; EX2mdb: T; EX2servers: T

 

 

 

Environment

All Identity Manager

Cause

The reason that License: F is because there is a registry key missing.

Resolution

On the C++ Connector Server being used go to the following Windows registry location:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ComputerAssociates\Identity Manager\Provisioning Server\Components\Server\

Make sure there is a registry string called eTrust_E2K with the value of yes

Restart the C++ Connector Server services.

Additional Information

If an Exchange Server is installed after the ADS endpoint was created, you need to follow the instructions in the following KB Article to update the ADS endpoint and have it recognize the Exchange Server.

https://knowledge.broadcom.com/external/article?articleId=42531