• Search

  • Pages

  • Archives

  • Categories

  • Meta

  • Troubleshooting Process Elevation in Privilege Manager

    12/10/16 3:09 AM

    Here are some tips when trying to discover why the process elevation feature is not working as expected.

    • Ensure that the rule has been created, has been saved and applied to a Group Policy Object (GPO). Ensure this GPO has been linked to either an OU or the domain.
    • Ensure that the Privilege Authority Client is installed on the client machine by looking in the Add/Remove Programs applet. If WMI is available, you can query the machine by dropping into a command prompt and typing “wmic /node: <fqdn of machine> product get name,version “.  If you need PowerShell, there is a great script located here.
    • From the command prompt, run ‘GPUpdate /force’ to make sure that the Group Policy has been refreshed.
    • Run ‘GPResult’ (or ‘GPResult /R’ on Windows7 or 2008), and check that the GPO the rule belongs to has been applied to that machine.  You can also use the Resultant Set of Policy (RSoP) feature or Group Policy Modeling on the Group Policy Console.  For more info, see here.
    • Check in the registry for the rule. Rules are copied to the key –

    HKEY_LOCAL_MACHINE\Software\ScriptLogic Corporation\Privilege Authority\CSE\CSEHost\Host. Under this key you will see a key which is the SID for each user (i.e. S-1-5-21-15….) and then a unique GUID for each rule underneath this. To match the SID to a user account, navigate to HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList and look at the data in the ProfileImagePath value or use the script provided below.

    You can also create a VB Script using the following script:

    Set oShell = CreateObject( “WScript.Shell” )



    strComputer = “.”

    Set objWMIService = GetObject(“winmgmts:\\” & strComputer & “\root\cimv2”)

    Set objAccount = objWMIService.Get(“Win32_UserAccount.Name='” & User & “‘,Domain='” & UserDomain & “‘”)

    DisplayString = UserDomain & “\” & User & ” = ” & objAccount.SID

    Wscript.Echo DisplayString

    Wscript.Echo objAccount.SID

    • If the rule is present in the registry, enable logging to troubleshoot further.

     To Enable Logging


    Under the registry key HKLM\Software\ScriptLogic Corporation\Privilege Authority\ change ‘LogLevel’ from the default value of 0 to 3 and restart the ScriptLogic Privilege Authority Host Service.  The log files can be found in the folder specified in the ‘InstallPath’ value under this same key. The default log location is C:\ProgramData\Privilege Authority\Logs.

    • Run the application or target process that you have created your rule for. Then go to the log file folder (by default – C:\ProgramData\Privilege Authority\Logs) and open the CSEHostEngine.log file. Every process that is being run by the user will be displayed.  To the right of each process, you will see a “MATCH” or “NO MATCH” status indicating whether or not the process matched a given Privilege Authority rule. Then, do a search for the process that you are trying to elevate and see if there is a match or not.
    Posted by bc-admin | in Uncategorized | Comments Off on Troubleshooting Process Elevation in Privilege Manager

    Comments are closed.