/build/static/layout/Breadcrumb_cap_w.png

K1000 Not detecting registry value

Yes, I know this has been asked before. However, none of the proposed solutions have worked yet. I need to determine if machines are in a pending reboot state after updates have been applied. The goal is to script a reboot if this key is present. Here's the key I'm looking for:

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired

The script output says it does not find the key and exits. My suspicion was immediately the infamous 64 vs 32 bit reg.exe debacle that has long plagued the K1000, so I looked in 

HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired

but it does not exist. Using HKLM64 to verify also did not work. Am I just SOL until a 64-bit version of KACE arrives?

1 Comment   [ + ] Show comment
  • Are you using a custom inventory rule to look for the key or just a script? Also, since the RebootRequired key is volatile have you verified that it is actually present in the registry on your test machine? - chucksteel 8 years ago
    • I did verify it was present locally, yes. I seemed to have some success using custom inventory rule :

      ShellCommandTextReturn(REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired" /reg:64)

      But I don't want to reboot workstations based on "some success". Also, the lookup needs to be at runtime of the script. - isudothings 8 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