To check a PM Agent host for installation readiness
# sh preflight.sh –-pmpolicy –-policyserver <primary_policy_server>
where <primary_policy_server> is the hostname of the primary policy server.
|
NOTE: Running preflight.sh –-pmpolicy performs these tests:
|
To install an agent on a remote host
# cd agent/linux-x86_64
# rpm --install qpm-agent-*.rpm
Once you install the Privilege Manager agent package, the next task is to join the agent to the policy server.
Once you have installed a Privilege Manager agent on a remote host you are ready to join it to the primary policy server.
To join a PM Agent to the primary policy server
# /opt/quest/sbin/pmjoin <primary_policy_server>.example.com
where <primary_policy_server> is the name of the primary policy server host.
If you are not running the pmjoin command on a policy server, it requires that you specify the name of a policy server within a policy group.
|
NOTE: The pmjoin command supports many command line options. See pmjoin for details or run pmjoin with the -h option to display the help.
|
Running pmjoin performs the configuration of the Privilege Manager agent, including modifying the pm.settings file and starting up the pmserviced daemon.
Once you complete the agent configuration script (by running the pmjoin command), it:
# pmclientinfo
This returns displays configuration information about a client host. See pmclientinfo for details.
To verify the PM Agent configuration
# pmclientinfo
The pmclientinfo command displays the current configuration settings. For example:
[0][root@host1 /]# pmclientinfo - Joined to a policy group : YES - Name of policy group : polsrv1.example.com - Hostname of primary policy server : polsrv1.example.com - Policy type configured on policy group : pmpolicy [0][root@host1 /]#
The secondary server PM Agent will be joined to the secondary server. This is unique because all other PM Agent hosts must join to the primary server.
© 2021 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy