Scripting Question

Kace agent cannot edit HKLM:\SOFTWARE registry or use Custom Inventory Field in %SystemRoot\System32?!?

11/08/2017 1207 views
Hi All,

New to the Community but having Kace in our office for about 4 years, we faced 2 issues lately (we are now on version 7.2):
- When trying to deploy a registry key on Windows clients, we can't do it using scripting with a reg key or deploying a Powershell script for HKLM:\SOFTWARE container. However deploying a key in HKLM:\SYSTEM is working fine
- When trying to make a Custom Inventory Field that check if a Directory (or Folder) Exists in %SystemRoot%\System32 (of check the content of the file there), it is not working. Doing so in another folder like C:\Users\Public is working fine

At first sight, it seems that Kace agent (the service is running as LocalSystem) does not have the relevant access rights to perform action in those containers/directories.
What can we do to change that?

Thank you

1 Comment   [ + ] Show comment


  • Does the agent work on other tasks. ..? or has it stopped working completely. ??
    • They agent works for the tasks and does not stop running (no crash or anything). Just when trying to perform one of the above mentioned tasks, it says it was performed successfully but nothing occurred.

All Answers

The KACE agent is still a 32bit application, so it doesn't have access to 64bit parts of the registry, e.g. HKLM\Software. When using the reg command you can specify the /reg:64 flag to get around that limitation. This is also the case for certain parts of the file system. We discovered this when preparing to deploy MBAM. Specifically, c:\windows\system32\bdehdcfg.exe is not visible from the 32bit space, so you need to instead use c:\windows\sysnative\bdehdcfg.exe.

Answered 11/09/2017 by: chucksteel
Red Belt

  • Thanks for the info, that is interesting. But I still have 2 issues with that:
    1- I have a tool that install itself in %SystemRoot%\System32 and cannot be customized to another directory. How to do in that case?
    - For the 64-bits reg key, how should I write it in a Powershell script using the command Set-Item and Set-ItemProperty?

    Thank you
    • c:\windows\sysnative is a redirect to c:\windows\system32, so adjusting the path should give you access to those files.

      I don't use PowerShell extensively, but this looks like a good place the start:
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