/build/static/layout/Breadcrumb_cap_w.png

KACE Product Support Question


Detecting if Custom Registry Exists on HKEY_USERS\SID

06/22/2015 2290 views

Hi - we are applying custom registry settings to users in our enviroment through Group Policy.

We would like to check if the user is getting the applied settings through the HKU hive. The problem is, I cannot find a way to target the user's SID in the HK (HKEY_USERS) hive, for multiple users at once. Ideally I'd like to be able to see whether or not the user has the registry key/value or not, what PC the key/value was applied to. Currently I can only see if the value if the user is either logged in, or if it's on a per user basis using the HKU.

I created two custom software inventories. One that is HKCU and one that is HKU.

The HKCU will only target the current user logged in, so if the user is not logged into, you cannot see if the PC is getting the applied registry keys/values.

RegistryValueEquals(HKEY_CURRENT_USERS\Software\Policies...

The HKU will target the current PC and only that user's SID. The problem with this is, we want to be able to see multiple SIDs in one custom inventory. You can create a custom inventory that detects each registry for multiple SIDs, but that won't give you an accurate answer on whose profile has the correct registry key/values on each PC.

RegistryValueEquals(HKEY_USERS\S-1-5-21-XXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXX\Software\Policies

Any thoughts on creating a more elaborate report?

0 Comments   [ + ] Show comments

Comments


Be the first to answer this question

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ