Installation guide

Troubleshooting Identity Manager 81
updates the connected system. If these attributes are modified before the engine
reads them from the Identity Vault, the modified value is updated in the
connected system and the intermediate change might be lost.
Action: If the attribute is changed frequently, use an appropriate syntax other than
SYN_STREAM.
For example, if an XML object is stored in the STREAM attribute, use XMLData
syntax instead of SYN_STREAM.
lcache issue during Identity Manager upgrade
Source: After upgrading Identity Manager, the Platform Agent might not log events as
desired. This problem occurs because Platform Agent is not upgraded during
the Identity Manager upgrade on Linux. On Solaris, the Platform Agent is
upgraded to the latest version but the new Platform Agent has different default
ports, which requires restarting lcache.
Action: You must manually stop lcache before starting the upgrade.
Upgrading Identity Manager requires the correct Administrator account to avoid
losing Challenge Response answers
Source: When you upgrade from an earlier version of Identity Manager on the Windows
platform, you should use the same Administrator account that was used to
install eDirectory.
Explanation: For example, if a domain Administrator account was used to install eDirectory,
use the domain Administrator account again when installing Identity Manager.
Do not use a local Administrator account.
Action: If you do not use the same Administrator account, users’ answers for their
Challenge Response questions are no longer accessible. This occurs because the
tree key is re-created during the installation (because of the different
Administrator accounts) and the new tree key does not provide the correct
access to the stored answers. Users are prompted for new Challenge Response
answers when they log in.