Chat now with support
Chat with Support

Safeguard Authentication Services 4.1.5 - Management Console for Unix Administration Guide

One Identity Privileged Access Suite for Unix Introducing One Identity Management Console for Unix Installing Management Console for Unix Preparing Unix Hosts Working with Host Systems Managing Local Groups Managing Local Users Active Directory Integration Authentication Services Integration Privilege Manager Integration Reporting Setting Preferences Security Troubleshooting Tips
Auto Profile Issues Active Directory Issues Auditing and Compliance Cannot Create a Service Connection Point Check Authentication Services Agent Status Commands Not Available CSV or PDF Reports Do Not Open Database Port Number Is Already in Use Elevation Is Not Working Hosts Do Not Display Import File Lists Fakepath Information Does Not Display in the Console Java Applet Failures License Info in Report is not Accurate Out of Memory Error Post Install Configuration Fails on Unix or Mac Privilege Manager Feature Issues Profile Task Never Completes questusr Account was Deleted Readiness Check Failed Recovering From a Failed Upgrade Reports Are Slow Reset the Supervisor Password Running on a Windows 2008 R2 Domain Controller Service Account Login Fails Setting Custom Configuration Settings Single Sign-on (SSO) Issues JVM Memory Tuning Suggestions Start/Stop/Restart Management Console for Unix Service Tool Bar Buttons Are Not Enabled UID or GID Conflicts
System Maintenance Command Line Utilities Web Services Database Maintenance

Profile Task Never Completes

If the host remains in a profiling state, it is likely that SSH is improperly configured on that host. Verify that you can SSH to the host manually. (See SSH to Host for details.)

If the host does not reset its profiled state to either Profiled or Not Profiled within a reasonable time, restart the Management Console for Unix service (mcu_service) to reset its profile state. (See the Start/Stop/Restart Management Console for Unix Service for details.)

questusr Account was Deleted

The questusr account is the user service account, a non-privileged account created when you configure a service account from the mangement console. This account is used by the console to gather information about existing policy server in a read-only fashion.

Note: The questusr account does not require root-level permissions, and, the mangement console does not use questusr account to make changes to any configuration files.

To recreate the questusr account

  1. Re-profile the host.
  2. Unconfigure the service account.

    (See Unconfigure a Service Account for details.)

  3. Configure the service account again.

    See Activate Policy Groups for details.

Readiness Check Failed

If you run a readiness check and in the Task Progress windows you see an error message that says, "Failed to find software at: ....", verify that the path to the software is correctly set in System Settings. (See Set Privilege Manager Software Path or Set Authentication Services Software Path for details.)

Note: The path to the software packages must point to the directory containing the preflight file.

Recovering From a Failed Upgrade

By default, Quest Identity Manager for Unix version 1.0.x was installed at:

  • On Windows 32-bit platforms: 
    %SystemDrive%:\Program Files\Quest Software\Identity Manager for Unix
  • On Windows 64-bit platforms: 
    %SystemDrive%:\Program Files (x86)\Quest Software\Identity Manager for Unix
  • On Unix/Mac platforms: 
    /opt/quest/imu

When upgrading from version 1.0.x, by default, One Identity Management Console for Unix is installed at:

  • On Windows 32-bit platforms: 
    %SystemDrive%:\Program Files\Quest Software\Management Console for Unix
  • On Windows 64-bit platforms: 
    %SystemDrive%:\Program Files (x86)\Quest Software\Management Console for Unix
  • On Unix/Mac platforms: 
    /opt/quest/mcu

When you install One Identity Management Console for Unix 2.x, it detects if Quest Identity Manager for Unix version 1.0.x is already installed.

If for some reason the upgrade procedure fails, make note of the step in the upgrade procedure where the failure occurred.

Here are the steps it takes:

  1. Stops the old IMU service.
  2. Disables the autostart flag.
  3. Installs version 2.x
  4. Migrates the data from the IMU database to the MCU database.
  5. Starts the new MCU service.
  6. Uninstalls IMU 1.0.x (if you selected this option)

If a failure occurs during the upgrade procedure that prevents the upgrade from completing successfully and you have not opted to uninstall the database, the original database will be intact.

To recover from a failed upgrade

  1. Copy the backup of the application database to the Quest Identity Manager for Unix version 1.0.x data directory.
  2. Uninstall Management Console for Unix.

    (See Installing and Uninstalling the Console on Windows for instructions.)

  3. Reinstall the IMU version 1.0.x.

    (See the Quest Identity Manager for Unix 1.0.x Administrator's Guide for instructions.)

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating