A Kace support rep walked me through turning on debug mode on several machines recently.   I actually forgot about them, but now I wanted to go back and turn off debug, but I cannot recall how in the Interface to locate which clients have debug turned on or to remove it.   

I know that I can check the amp.conf file for debug=true, but the whole point behind having the Kace was to reduce my work load, not increase it, so I'm hoping that someone knows the process to locate and remove debugging from the UI.   I am running Model: K1000  Version: 6.0.101864. 

Thanks in advance for any assistance.   

Answer Summary:
0 Comments   [ - ] Hide Comments


Please log in to comment

Community Chosen Answer


you can create a custom software inventory to read the config file "ShellCommandTextReturn(cmd.exe /c type C:\ProgramData\Dell\KACE\amp.conf)"

then run a "if contains debug=true" report to find this.
Answered 08/29/2014 by: SMal.tmcc
Red Belt

  • Simply do it together so you have it in the CIR directly:
    ShellCommandTextReturn(cmd.exe /c "type C:\ProgramData\Dell\KACE\amp.conf|findstr debug")
    Btw: true is a bit outdated If you need all informations set debug=all (or debug=detail)
  • This did it.. To clarify for those people like me who are new to Kace...
    1.) In 'Inventory...Software' create a new 'Software Detail' (I named mine "Kace debug=true")
    1a.) In "Custome Inventory Rule" enter "ShellCommandTextReturn(cmd.exe /c type C:\ProgramData\Dell\KACE\amp.conf)"
    1b.) Save the rule.
    2.) After the rule runs on a couple of inventories, you can go to 'Inventory...Devices and perform an 'Advanced Search'
    3.) Scroll all the way to the bottom of the drop down for selections in 'Advanced Search' and you'll see 'Custom Fields'
    4.) Look for the one you just created (e.g, Kace debug=true)
    5.) Set it to 'Contains' and 'debug=true' (note it doesn't seem to be case sensitive, but don't wrap the search term in quotes, and don't include a space after or before the = sign. Just "debug=true" (without the quotes)
    6.) I created a 'Smart Label' for it and now I have it for quick checks.
Please log in to comment
Answer this question or Comment on this question for clarity


You could simply leave it on.  It doesn't add much in the way of storage space used.

That said, you could use the CIR suggested above and create a smart label to target the built in script to disable debug.
Answered 08/31/2014 by: jknox
Red Belt

Please log in to comment
It wont affect much if you concern about storage;
Still if you want to remove, use File Synchronization under Distribution tab
Upload amp.conf (which doesn't contain debug=true) through Inventory >> software
Then sync the amp.conf by selecting a particular labels or Deploy All
Answered 09/01/2014 by: anand.30hiremath
Blue Belt

Please log in to comment