Each machine that runs requests using Privilege Manager for Unix must run a pmlocald daemon. Typically you will run pmlocald on all your machines. See pmlocald for more information.
After you make sure your primary policy server host meets the system requirements, you are ready to install the Privilege Manager packages.
To install the Privilege Manager packages
# rpm –-install qpm-server-*.rpm
NOTE: The Solaris server has a filename that starts with QSFTpmsrv.
When you install the qpm-server package, it installs all three Privilege Manager components on that host: the Privilege Manager Policy Server, the PM Agent, and the Sudo Plugin.
For details instructions on installing and configuring Privilege Manager for Sudo, see the One Identity Privilege Manager for Sudo Administration Guide.
After you install the primary policy server, you may want to update your PATH to include the Privilege Manager commands.
To modify the user's PATH environment variable
Once you install the Privilege Manager for Unix server packages, the next task is to configure the primary policy server.
NOTE: The first policy server you setup is the primary policy server.
To configure the primary policy server for a pmpolicy type
# /opt/quest/sbin/pmsrvconfig -m pmpolicy
NOTE: The pmsrvconfig command supports many command-line options; see pmsrvconfig for details or run pmsrvconfig with the -h option to display the help.
When you run pmsrvconfig with the -i (interactive) option, the configuration script gathers information from you by asking you a series of questions. During this interview, you are allowed to either accept a default setting or set an alternate setting.
Once you have completed the policy server configuration script interview, it configures the policy server.
The configuration process: