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

Reset Custom Configuration Settings

When upgrading from version 1.0.x to 2.x or higher, there are some steps you must take to reset any custom configuration settings you had in the previous version.

The upgrade procedure makes a .bak copy of your configuration file (jvmargs.cfg.bak) at the root of your installation directory. After you upgrade the mangement console from version 1.0.x, to reset any custom configuration settings you may have made in the previous version, compare the jvmargs.cfg.bak file with the new jvmargs.cfg file to see if you had any custom settings. For example, if you had increased the JVM Memory size in the previous version, you must add the JVM Memory setting argument to the custom.cfg file. (See Setting Custom Configuration Settings for more information about customizing configuration settings for the mangement console.)

Note: Do not change the jvmargs.cfg directly; the settings in the custom.cfg file always take precedence over the default settings in jvmargs.cfg. And, next time you upgrade Management Console for Unix, changes in the jvmargs.cfg file will be overwritten.

Upgrade Management Console for Unix

The process for upgrading Management Console for Unix from an older version is similar to installing it for the first time. The installer detects an older version of the console and automatically upgrades the components.

Note: The procedures in this topic assume you have Management Console for Unix 2.0.x or greater installed.

Before you begin the upgrade procedure, close the console and make a backup of your database, as explained in step 1.

To upgrade Management Console for Unix

  1. Backup the database files:
    1. Shutdown the service. (See Start/Stop/Restart Management Console for Unix Service for details.)

      Management Console for Unix uses a HSQLDB (Hyper Structured Query Language Database) to store its data such as information about the hosts, settings, users, groups, and so forth.

    2. Copy the /var/opt/quest/mcu data directory to a backup location.

      Refer to Database Maintenance for more information about the database locations and filenames.

    3. After backup is complete restart the service. (See Start/Stop/Restart Management Console for Unix Service for details.)

      Once you backup the database files, you are ready to start the upgrade.

  2. To start the upgrade, follow the instructions for a first-time installation. (See the Installing and Uninstalling topic for your platform under Installing the Management Console to start the installation procedure.)

    When the installer detects a previous version of the mangement console is already installed, it asks if you want to continue.

  3. Click Yes at the Install Management Console for Unix dialog.
  4. Accept the terms of the license agreement and click Next.
  5. Modify the default SSL (https) and Non-SSL (http) port numbers, if necessary, and click Install.

    The installation wizard uninstalls the old version and configures the server database and service.

  6. On the Complete dialog, select the Launch the Management Console option and click Finish.

Note: After an upgrade from any version of Management Console for Unix, it is important to re-profile all managed hosts.

Preparing Unix Hosts

The mangement console provides a central management and reporting console for local Unix users and groups.

Whether you have the core version of the mangement console or are managing hosts with Authentication Services or Privilege Manager for Unix, once you have successfully installed Management Console for Unix, you must first add your hosts to the console, and then profile them to gather system information. Once a host is added and profiled you can then manage users and groups on the hosts and run reports.

Note: Installing Authentication Services on hosts that you manage with the console unlocks many additional features for managing Unix systems with Active Directory, such as Active Directory user management and Access and Privileges reports.

Installing Privilege Manager on hosts that you manage with the console allows you to view and edit centrally stored policies, as well as search and replay keystroke logs. (See to What Are the Core Features of the Console? for a list of these additional features.)

Add Host(s) to the Management Console

In order to manage a Unix host from the mangement console, you must first add the host. Go to the Hosts tab of the mangement console to either manually enter hosts or import them from a file.

To add host(s) to the mangement console

  1. Click the Add Hosts tool bar button to display the Add Hosts dialog.

  2. To manually add one or more hosts, enter the FQDN, IP address, or short name of a host you want to add to the mangement console and either click the Add button or press Enter.

    Once added, the Host column displays the value you enter. The mangement console uses that value to connect to the host. You can rename the host if it has not been profiled using the Rename Host command on the Host panel of the tool bar. After a host is profiled the only way to change what is displayed in the Host column is to remove the host from the console and re-add it. For example, if you add a host by its IP address, the IP address displays in the Host column (as well as in the IP Address column); to change what is displayed in the Host column, you must use the Remove from console tool bar button to remove the host from the console; then use the Add Hosts button to re-add the client by its host name. If you had profiled the host before removing it, you will have to re-profile it after re-adding it.

  3. To add hosts from a known_hosts file, click the Import button.

    1. On the Import hosts from file dialog, browse to select a .txt file containing a list of hosts to import.

      Once imported, the host addresses display in the Add Host dialog list.

      Note: The valid format for an import file is:

      • .txt file - contains the IP address or DNS name, one per line
      • known_hosts file - contains address algorithm hostKey (separated by a space), one entry per line

      (See Known_hosts File Format for more information about the supported known_hosts file format.)

  4. Once you have a list of one or more hosts to add, if you do not wish to profile the host(s) at this time, clear the Profile hosts after adding option.

    Note: If you add more hosts to the list than selected in the Rows to show drop-down menu in the View panel of the tool bar, this option is disabled.

  5. If you do not clear the Profile hosts after adding option on the Add Hosts dialog, when you click OK, the Profile Host dialog prompts you to enter the user credentials to access the host(s). (Refer to Profile Host(s) which walks you through the host profile steps.)

  6. If you clear the Profile hosts after adding option on the Add Hosts dialog, when you click OK, the Add Hosts dialog closes and control returns to the mangement console.

    The mangement console lists hosts that were successfully added on the All Hosts view by the FQDN, IP address, or short name of the hosts you entered on the Add Hosts dialog.

Related Documents