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

UID or GID Conflicts

Management Console for Unix does not automatically pick up changes to the host made externally to the console unless you configure the host for auto-profiling.

For example, when you install Privilege Manager software on a remote host, it creates a new user and group named pmclient, assigning a UID and GID accordingly. If you do not profile the host after installing the Privilege Manager packages, the mangement console will not recognize the new user name and group name. If you attempt to configure that host for auto-profiling or automatic QAS status updates without profiling, you might encounter a UID conflict, such as this:

Or, if you attempt to add a new local group to that host without profiling, you might encounter a GID error like this:

If you encounter a UID or GID conflict, profile the host and try the action again before you troubleshoot the problem further.

NoteS:

  • As a best practice, configure newly added hosts for auto-profiling before you perform any other actions so that the mangement console dynamically updates user and group information. (See Profile Hosts Automatically for details.)
  • If Authentication Services is installed you may also get these errors because of UID/GID conflicts with Active Directory accounts. In this case, because the mangement console does not check for Active Directory conflicts, you will have to manually create the user with a different ID.

System Maintenance

It is important to safeguard your data. One Identity recommends that you maintain copies of the most important files so you're always prepared for the worst.

This appendix provides general information and guidelines for maintaining or backing up your data.

Backup Procedure

It is necessary to perform a backup when the service is not running. You can use normal backup methods, such as archiving the files in a compressed bundle.

To backup the Management Console for Unix program files

  1. Shutdown the service.
  2. Copy the application data directory to a backup location.

    By default, the application data directory is:

    • On Windows XP/2003 Server: 
      %SystemDrive%:\Documents and Settings\All Users\Application Data\Quest Software\Management Console for Unix
    • On Windows 2008 Server/Vista/7: 
      %SystemDrive%:\ProgramData\Quest Software\Management Console for Unix
    • On Unix/Mac: 
      /var/opt/quest/mcu
  3. Restart the service.

    Note: For more information on stopping and restarting the service, see Start/Stop/Restart Management Console for Unix Service.

Restore Procedure

It is necessary to restore your files when the service is not running.

To restore the Management Console for Unix program files

  1. Shutdown the service.
  2. Replace the application data directory files with the ones you previously backed up.

    By default, the application data directory is:

    • On Windows XP/2003 Server: 
      %SystemDrive%:\Documents and Settings\All Users\Application Data\Quest Software\Management Console for Unix
    • On Windows 2008 Server/Vista/7: 
      %SystemDrive%:\ProgramData\Quest Software\Management Console for Unix
    • On Unix/Mac: 
      /var/opt/quest/mcu
  3. Once you have replaced the files, restart the service.

    Note: For more information on stopping and restarting the service, see Start/Stop/Restart Management Console for Unix Service.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating