Safeguard for Sudo 2.0 - Administrators Guide

Remove Configurations

You can remove the Privilege Manager Server, PM Agent, or Sudo Plugin configurations by using the –u option with the pmsrvconfig, pmjoin, and pmjoin_plugin commands respectively.

Take care when you remove the configuration from a policy server, particularly if the policy server is a primary server with secondary policy servers in the policy group, as agents joined to the policy group will be affected.

Uninstall the Privilege Manager Software Packages

To uninstall the Privilege Manager packages

1. Log in and open a root shell.
2. Use the package manager for your operating system to remove the packages:

Uninstalling Privilege Manager for Sudo on Mac OS X

To uninstall Privilege Manager for Sudo on Mac OS X^®

1. Open /Applications and click QPM4Sudo_Uninstaller.
2. When it asks if you want to delete the pmclient user, enter yes or no.

To uninstall Privilege Manager for Sudo from the command line

1. Enter:

   /opt/quest/qpm4u/bin/uninstall

2. To delete the pmclient user, enter:

   dscl . -delete /Users/pmclient

Upgrading Privilege Manager

The Privilege Manager software in this release is provided using platform-specific installation packages. Privilege Manager for Unix version 5.6 and Privilege Manager for Sudo 1.0 also used platform-specific packages. Prior to this, Privilege Manager for Unix used a shell-based installation and configuration script.

If you are currently running Privilege Manager for Unix 5.6 or Privilege Manager for Sudo 1.0, it may be possible to perform a direct upgrade installation depending on the package management software on your platform (Note: direct upgrade installations are not possible with Solaris^® .pkg packages). If you perform a direct upgrade installation, your previous configuration details are retained. Where a direct upgrade is not possible, you must first remove the previously installed package, and install and configure Privilege Manager as a new product installation.

If you are currently running Privilege Manager for Unix 5.5, follow the installation and configuration instructions in Upgrading to Privilege Manager for Unix 6.0. If you are running Privilege Manager for Unix prior to version 5.5, Quest recommends that you backup important data and uninstall the previously installed version of Privilege Manager prior to installing version 6.0.

If you are upgrading a Privilege Manager master or policy server, please note that this version of Privilege Manager uses a new database format for event log files. You must import preexisting log files into the new database format in order to access the log data from these files using the upgraded software. If your policy uses the eventlog variable to change the location of where the policy server writes event logs, rename the existing event log files so that the policy server can create the new database-formatted log files with the existing name.