/build/static/layout/Breadcrumb_cap_w.png

Registry Script Fails with K1000

I've been trying a few ways to script searching for the registry key:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\

I've tried to use the Verify a registry key exists. I've tried with both HKLM and I've seen other mention of using HKLM64. Neither of which will go any further than the key listed before failing out.

To try and solve the problem a different way, I created a batch file using reg query HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18.

When I try and execute that command I get the following in the KAgent.log which I can't find any reference to:
[runkbot:DoesTokenHaveLSAPriviled] DoesTokenHaveLSAPriviledges returning: 1

Could any one assist me with pulling information from that registry key?

3 Comments   [ + ] Show comments
  • You must have updated the agent to 6.3.314!!!!!!!!!!

    BE AWARE EVERY K1000 Administrator!!!

    My Script which has Verify a registry key exists... is not working even if I put HKLM64 or HKLM after I upgraded to this Agent version.
    I can set Value in HKLM64 but cannot ready or Verify...... - haseebiqbal 9 years ago
  • http://www.itninja.com/question/custom-inventory-rule-not-working - haseebiqbal 9 years ago
  • http://www.itninja.com/question/don-t-update-to-kace-agent-6-3-31-if-you-have-script-to-verify-hklm-or-hklm64-or-custom-inventory-rule-registry - haseebiqbal 9 years ago

Answers (0)

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

View more:

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