The following topics may help you resolve some problems related to Auto Profiling.
The following topics may help you resolve some problems related to Auto Profiling.
If auto-profiling multiple hosts does not complete within a reasonable amount of time and the host is configured for multiple consoles, make sure each console address is valid and available.
To validate the console addresses
On the unresponsive host, open the <Service Account Home Dir>/.quest_autoprofile/notify.rc configuration file.
Remove the entry for the unresponsive server.
Note: If the host continues to be unresponsive, here are some other things you can try:
If this has changed, re-configure the host for auto-profile.
The default is 9080.
Note: If you have customized your HTTP or SSL/TLS ports, see Customizing HTTP and SSL/TLS ports for more information.
There could be any number of things that would prevent the host from communicating with the console.
If you receive an error when auto-profiling a host after a recent upgrade from 1.0.x, verify the console host address in System Settings.
To validate the console host address
The host address in the Console host address box on the Console Information settings may have been entered as a simple address in version 1.0. To perform some tasks in version 2.x without error, such as auto-profiling, the Console host address must be a Fully Qualified Domain Name.
Note: Setting up automatic profiling on a host with Security-Enhanced Linux (SELinux) enabled will fail due to the enhanced security-related restrictions on the system. Please contact Technical Support at https://support.oneidentity.com/ for instructions on how to either work-around the issues or disable SELinux.
The following topics may help you resolve some problems related to Active Directory.
© 2024 One Identity LLC. ALL RIGHTS RESERVED. Termini di utilizzo Privacy Cookie Preference Center