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
See Unconfiguring a service account for details.
See Activating policy groups for details.
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 Setting the Privilege Manager software path or Setting Authentication Services software path for details.)
Note: The path to the software packages must point to the directory containing the preflight file.
By default, Quest Identity Manager for Unix version 1.0.x was installed at:
%SystemDrive%:\Program Files\Quest Software\Identity Manager for Unix
%SystemDrive%:\Program Files (x86)\Quest Software\Identity Manager for Unix
When upgrading from version 1.0.x, by default, One Identity Management Console for Unix is installed at:
%SystemDrive%:\Program Files\Quest Software\Management Console for Unix
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:
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
See Installing and uninstalling the console on Windows for instructions.
See the Quest Identity Manager for Unix 1.0.x Administrator's Guide for instructions.
The console may appear to "stick" in the data collection phase while generating reports.
To troubleshoot this issue, consider these possible reasons: