Privilege Management Console Settings Options

This menu has three options:

  • Auto Deactivate Settings
  • The Policy Deployment Settings tile
  • Remote Access Settings

Auto Deactivate Settings

The task to deactivate computers runs every day at 02:30 server time on the node where the job service is running. The deactivation job is audited in the Activity Log. You can filter by deactivated computers in the Computers grid.

To enable the automatic deactivation of computers, check the Enable auto deactivation of computers box. When you check this box, enter a value between 30 and 365 days. This determines the duration since the computer last contacted PMC before it is automatically deactivated.

Enable auto deactivation of computers and enter a value between 30 and 365 days.

Deactivated computers are disconnected from PMC and are no longer able to communicate with PMC. This action cannot be reversed unless you reinstall the software on the client computer.


With the release of PMC version 2.3, auto deactivate functionality is turned off by default, for both upgrades and new installations. If you want to turn on auto deactivate functionality, use the Enable auto deactivation of computers setting. The functionality remains unchanged.

You can also manually deactivate computers.

Remote Access Settings

This contains the remote access settings that are used to communicate with the Privilege Management MMC snap-in.

You need to configure PMC to allow the Privilege Management MMC snap-in to communicate with the PMC services.

  1. Click Administration > Settings > Remote Access Settings from the top menu.

The MMC Client ID GUID must match the GUID you enter in the MMC connection. The API Access ID is used in conjunction with the API, if required.

  1. Check the Enable remote MMC client access box. You need to generate a new GUID and enter it here. Use the same GUID when you configure the MMC. This is the MMC Client ID in the MMC.


There are many ways to generate a GUID. For example, you can use a PowerShell cmdlet:
  1. Check the Enable API key access box. This GUID is required if you want to use the PowerShell API. Once again, you need to generate this GUID.
  2. Click Save Changes.