Privilege Authority Blog

Here I will provide some information and tips on how to go about troubleshooting rules that appear not to be working.

1. Ensure that the created rule has been saved and applied to a Group Policy Object (GPO) that has been linked to either an OU or the domain.





2. Onthe client machine,  make sure that ScriptLogic Privilege Authority Client is installed by looking in the Add/Remove Programs.





3. From the command prompt run 'GPUpdate /force' to make sure that the Group Policy has been refreshed.





4. Run 'GPResult' (or 'GPResult /R' on Windows7 or 2008), and check that the GPO the rule belongs to has been applied to that machine.





5. Check in registry for the rule. Rules are copied to the key on a x32 machine HKEY_LOCAL_MACHINE\Software\ScriptLogic Corporation\Privilege Authority\CSE\CSEHost, or on x64 HKLM\Software\Wow6432Node\ScriptLogic Corporation\Privilege Authority\CSE\CSEHost. Under this key you will see a key for each user (i.e. S-1-5-21-15….) and then a unique GUID for each rule underneath this.





6. If the rule is present in registry then it is a good idea to turn on logging.





To Turn On Logging



Under the registry key HKLM\Software\ScriptLogic Corporation\Privilege Authority\ (x64 this becomes HKLM\Software\Wow6432Node\ScriptLogic Corporation\Privilege Authority\) change ‘LogLevel’ to 3 from 0. Your log files can be found in the folder specified in the ‘LogPath’ value under this same key.



7. Run the application or target process that you have created your rule for. Then go to the log file folder and open the CSEHostEngine.log file. You should do a search for the process that you are trying to elevate.

Hope that helps troubleshooting if you have any issues.





George.