This section describes items you should consider when using CA Access Control server components (CA Access Control Endpoint Management, CA Access Control Enterprise Management, and Enterprise Reporting).
Valid on Solaris
Currently, the Enterprise Management Server does not support Solaris.
The following CA Access Control components rely on communications with the CA Access Control Message Queue for some functionality:
These components may not be able to communicate with the Message Queue if it is not running, the configuration options are not set correctly for the Message Queue host or queue, or a generic network error is present.
If communication between any of these components and the Message Queue cannot be established or breaks down, the communication does not resume automatically when the problem is fixed. To work around this issue you must fix the communication issue and then restart the CA Access Control component.
XUSER and XGROUP related details are not displayed in the CA Access Control Account Management Reports.
The host name of the CA Access Control endpoint must be 15 characters or less. If the host name of the CA Access Control computer exceeds 15 characters, you cannot use CA Access Control Endpoint Management to log into the endpoint.
When you undeploy a policy that does not have an associated undeploy script, CA Access Control automatically generates the required script to remove the policy. This script is based on the deployment script.
If you want to remove the policy but keep the policy rules (from the deployment script), provide an undeployment script with a rule that does not modify anything (for example, er GPOLICY policyName).
In this version, CA Enterprise Log Manager does not include PUPM nor UNAB reports.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |