
To clear all of the privileges in the Custom Token before applying privileges, check the Remove all existing privileges in access token before applying privileges box. You can also select multiple privileges and use the following options on the right-click menu: If you want to remove a privilege from the Custom Token, check the Remove box for the relevant privilege. If you want to add a privilege to the Custom Token, then check the Add box for the relevant privilege. The Privileges section of the Custom Token specifies the privileges that are added to or removed from the Custom Token.
CUSTOM TOKENS UPDATE
For instance, if you are using an elevated logon script to update the local Privilege Management for Windows policy. Under normal circumstances, this option should remain enabled, except in scenarios where elevated tasks require access to protected areas. If you want to disable anti-tamper protection, uncheck the Enable anti-tamper protection box. Therefore, Privilege Management for Windows cannot offer the Anti-Tamper feature for Domain Controllers. It also prevents any elevated process from reading or writing to the local Privilege Management for Windows policy cache.ĭomain Controllers don't have the Local Users and Groups databases once they're promoted to a Domain Controller.

Anti-Tamper Protectionīy default, Privilege Management for Windows prevents elevated processes from tampering with the files, registry, and service that make up the client installation. If you want the user to be the owner, regardless of the presence of the administrators group, check the Ensure the User is always the Token Owner box. If the administrators group is not present in the Custom Token, then the user is set as the owner. Setting the Token Ownerīy default, the owner of a Custom Token that includes the administrators group has the owner set to the administrators group. Local Account appears in the SID column of the groups list for local groups. For local groups, the name is used by Privilege Management for Windows, and the SID is looked up when the Custom Token is created by the client. The SID is used by Privilege Management for Windows, which avoids account lookup operations. If you want to remove the group from the Custom Token, check the Remove box instead.ĭomain and well-known groups display a Security Identifier (SID).

Create a token which removes Administration rights.Create a token which adds Administrator rights.


You can optionally define any number of Custom Tokens. For more advanced configurations, Custom Tokens can be created where group memberships, privileges, permissions, and integrity can be manually specified. A passive access token is also available that does not change the privileges of the activity, but still applies anti-tamper protection.Īccess tokens are assigned to applications or content through rules within a Workstyle. Privilege Management for Windows includes a set of built-in access tokens that can be used to add administrator rights, remove administrator rights, or enforce the users default privileges. Within an access token is a collection of settings that specify the group memberships, associated privileges, integrity level, and process access rights. Access tokens (and Custom Tokens) are assigned to an application, or when content is being edited, to modify the privileges of that activity.
