Release Notes › Known Issues › Installation Known Issues › UNAB Endpoint Installation Known Issues

UNAB Endpoint Installation Known Issues

This section describes installation known issues for UNAB endpoints.

UNAB Restarts Twice When Installing CA Access Control

Valid on IBM AIX

When installing CA Access Control on IBM AIX and UNAB is already running, UNAB restarts twice. This behavior is because AIX performs additional Kernel checks.

Uninstalling Fails When Native Installation Is Customized to Install CA Access Control and UNAB in The Same Non-Default Location [UNAB]

Valid on AIX, and HP-UX

Symptom:

Uninstalling UNAB fails after I installed CA Access Control and UNAB using native installation and customized the installation directory to the same path on a nondefault location.

Solution:

Uninstalling CA Access Control corrupts and fails the UNAB installation. Uninstalling fails as both CA Access Control and UNAB are installed on the same directory. While customizing native installation to a nondefault destination folder, we recommend that you concatenate the product name (uxauth or UNAB) to the destination path.

Installing SElinux Extensive Policy Twice Shows An Incorrect Message

Symptom:

If you install the SElinux extensive policy over an existing SElinux extensive policy on UNAB, then the following message appears:

Policy successfully installed

Solution:

The message is incorrect as UNAB has already installed the SElinux extensive policy.

UNAB Does Not Support CA Access Control r8.0 SP1 and r12.0 SP1

Currently, you cannot install UNAB on CA Access Control r8.0 SP1 and r12.0 SP1 endpoints. Also, UNAB and CA Access Control must be of identical version or service pack.