Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Safeguard Privilege Manager for Windows 4.7.1 - Administration Guide

TitlePageProxy Copyright Table of Contents About this guide What is Safeguard Privilege Manager for Windows? Installing Safeguard Privilege Manager for Windows Configuring Client data collection Configuring Instant Elevation Configuring Self-Service Elevation Configuring Temporary Session Elevation Configuring privileged application discovery Deploying rules Removing local admin rights Reporting Client-side UI customization Using Microsoft tools Maintaining a least privileged use environment Database Planning Product Improvement Program About us

Testing rules

You can test a rule to ensure that the settings you specified map to a process on a local or remote computer. You can test all types of rules, except ActiveX.

Before you test a rule, ensure the following components are set up

  1. The Client is running on the computer on which you intend to test the rule.

  2. The remote computer is switched on and is accessible from the network.

  3. The correct credentials to connect to the remote computer are provided.

  4. The following exceptions are added for remote computers with a firewall turned on:

    • Windows Management Instrumentation (WMI): dllhost.exe

    • Host process for Windows services: svchost.exe for 32-bit OS and %SystemRoot%\SysWOW64\svchost.exe for 64-bit OS.

To test a rule

  1. Within the Group Policy Settings section, select a rule, and click the Test button.

  2. Select whether to test the rule on a local or remote computer.

    A test window appears and the test starts. The window displays the initial conditions necessary for the rule to run and present its status in the Test Progress section, testing if:

    • The connection with the target computer has been established;

    • The Client is installed on your computer;

    • The Group Policy update has run successfully on the client computer;

    • The GPO with the selected rule is present on the domain; and

    • The rule exists on the client side and on the domain.

  3. If the test fails any of the steps, resolve the issue. If you encounter a "Failed to retrieve processes. Please refer to documentation for more info" error, complete the steps above before you test the rule.

  4. Click Next.

  5. When the Detecting Process window opens, manually run the process the rule applies to. Use the parameters specified in the Rule Details section of the Test File Rule window. The window shows two tabs:

    • The Started Processes tab with the processes started after you switched from the Detecting Process window.

      • The process that you start to test the will display with either a tick or a cross sign.

      • If the process is marked with the cross sign, look at Process Details and check that you started the process with the right parameters, or modify the rule settings.

    • The All Processes tab with all currently running processes.

  6. When the rule is created and distributed to clients through Group Policy, the rule is applied to the corresponding process.

Removing local admin rights

Detailed information about this topic

The last step in preparing your environment for least privileged use is to remove administrative access from users who no longer require it.

Using the Active Directory Users and Computers utility

To scrub the Domain Administrators group of users that should no longer have administrative rights to every computer in the domain, use the native Active Directory Users and Computers utility of the supported Windows Server operating systems.

To remove users from the Domain Administrators group,

  1. Select Domain Admins Properties > Members tab > Remove.

  2. To discover users and domain groups with local administrator rights, click Discover Accounts in local Administrator groups.

    NOTE: By default, the search results will only include domain users and domain groups. However, you can optionally opt to include local and built-in (for informational purposes only) users.

Using the Users with Local Admin Rights screen

Available only in Safeguard Privilege Manager for Windows Professional Edition and Professional Evaluation Edition.

Under the Discovery & Remediation tab on the Console, select the Users with Local Admin Rights screen to discover which domain users have been assigned to the local Administrators group on client computers and remove them.

Before you begin, check the following on each target computer

  1. The computer is turned on and accessible from the network; and

  2. Windows Management Instrumentation (WMI), Distributed Component Object Model (DCOM), File and Printer Sharing, and Remote Administration are allowed through the firewall.

To remove domain users from the local Administrators group on computers on your domain

  1. Within the Select Computers section, click Add and Remove to add and remove computers.

    • You cannot select a domain controller computer.

    • If the File and Printer Sharing exception is not enabled for a computer, it will not display in the list.

    • If the Windows Management Instrumentation exception is not enabled, the Class and OS columns will display the Unavailable value.

  2. Click Clear all entries to remove all computers from the list.

  3. Click Discover Accounts in local Administrator groups to discover users and domain groups with local administrator rights. By default, the search results will only include domain users and domain groups. However, you can optionally opt to include local and built-in (for informational purposes only) users.

  4. In the window that opens, specify whether to search for local Administrator groups, users, or both.

  5. Check the Only display domain accounts discovered in the results list option to restrict the search to Domain accounts only. Clear the option to include local accounts from the Administrators group on client machines.

    A window displays your progress as the list builds.

  6. Complete the following steps.

    1. If an error occurs, it will display in the Errors section with a description. The Unable to open log file... notification signifies that no users in the local Administrators group have been detected.

    2. Click Open report file to view data on detected users. The button will not be activated if no users have been found in the local Administrators group.

    3. When the discovery operation is completed, click Close.

The list of discovered users will display in the User Accounts Discovered in Local Administrators Groups section.

  1. Revise the list to only include users you are potentially going to revoke rights from then make your final selection from the remaining list.

  2. Click the Exclude selected entries from list link to remove users from this list.

  3. Select users from the remaining list, for which you want to revoke their local administrator rights.

  4. Click Remove all selected users from local Administrators groups.

  5. In the window that opens, click Yes to confirm that you want to remove the users or groups. A window displays your progress as the users are removed.

  6. Complete the following steps:

    1. If an error occurs, it will display in the Errors section with a description.

    2. Click Open report file to view the operation log.

    1. When the operation is complete, the users no longer have local administrator rights.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation