System requirements
Before you begin using Safeguard Privilege Manager for Windows, make sure that you meet the minimum hardware, software, network and permission requirements of the product. For more information, see System Requirements in the Safeguard Privilege Manager for Windows Release Notes.
Components
There are three software components included with Safeguard Privilege Manager for Windows:
Console
The Safeguard Privilege Manager for Windows Console, installed via PAConsole_Pro.msi, is a management application. It is installed on a domain computer (server or workstation) and is used to create and manage rules within the Group Policy. Any user who has permission to edit a GPO can use the Console to set privileges.
Server
The Safeguard Privilege Manager for Windows Server, installed through the Console, is a service which has several functions. It can deploy the Client, collect and report on data, and discover and process applications that require elevated privileges.
Client
The Safeguard Privilege Manager for Windows Client, installed through PAClient.msi, is a service that runs on each client computer. It applies the rules created in the Console by monitoring processes as they are launched on the Client and elevates or lowers the privileges for processes that are configured to be monitored. This is done by injecting an administrative token into the process or revoking it.
Microsoft Active Directory and Group Policy are used to distribute Safeguard Privilege Manager for Windows rules to client computers.
Privilege Manager can modify privileges only for a standard user account, not a guest account. Elevated privileges can be revoked even if the user is a local admin.
Preparing your environment for least privileged use
Preparing your environment for least privileged use
Product Licensing
For information on editions and applying a license, refer to the Safeguard Privilege Manager for Windows Administration Guide.
Safeguard Privilege Manager for Windows licenses are compatible with only a single major version of the product (for example, 3.x or 4.x). This means that existing 3.x licenses are not valid after upgrading to a 4.x build.
Therefore, when upgrading to a new major version, existing customers must obtain a new license file using the License Assistance portal to properly register the product after upgrade.
NOTE: Safeguard Privilege Manager for Windows does not phone home for product licensing.