During a recent KACE Agent upgrade using GPO the amp.conf was created with no parameters therfore those clients are no longer connected. I am asking for help with creating a script that will replace the amp.conf file with a known good one. I dont want to start/stop services to activate the new file I'll let the normal shutdown process take care of that. I know there are file location differences between XP and Win 7 and the files are more than likley hidden. Any suggestions would be greatly appreciated.
Answer Summary:
The files aren't hidden, but the location and process are different depending on the Agent version. If these machines are running agent v5.3 and up, the easiest way would be to call the amp tool (called AMPTools.exe) with the following syntax/parameters: AMPTools.exe -resetconf host=kboxservername.com This tool is located at C:\Program Files\Dell\KACE or C:\Program Files(x86)\Dell\KACE as appropriate, so you'd probably want to check for 32bit or 64bit first and specify the appropriate directory. As an aside, this can also be done on Macs through the following (similar) command: /Library/Application\ Support/Dell/KACE/bin/Amptools -resetconf host=kboxservername.com
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

1
The files aren't hidden, but the location and process are different depending on the Agent version.

If these machines are running agent v5.3 and up, the easiest way would be to call the amp tool (called AMPTools.exe) with the following syntax/parameters:


AMPTools.exe -resetconf host=kboxservername.com


This tool is located at C:\Program Files\Dell\KACE or C:\Program Files(x86)\Dell\KACE as appropriate, so you'd probably want to check for 32bit or 64bit first and specify the appropriate directory.



As an aside, this can also be done on Macs through the following (similar) command:

/Library/Application\ Support/Dell/KACE/bin/Amptools -resetconf host=kboxservername.com
Answered 03/19/2012 by: jaredv
Fourth Degree Green Belt

  • WARNING!: Running this on version 5.3.53177 appears to overwrite the amp.conf file, resulting in a dead agent. The only line left in amp.conf, after running this command, is host=kboxservername.com., which causes it to no longer communicate with the KBox.
Please log in to comment
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
For me the lasthost name wasn't resolving so I updated settings\network and changed it from a hostname to its IP address and saved and rebooted the machine.

The machines started getting their conf files updated which I could see in the amp log files on the hosts that the name was being replaced with the IP.  Even though they weren't connected for days.  If you reconfigure your settings, it should push the updates to the amp.conf files. If anyone knows how to force this to happen I would appreciate it as it would speed it up.  Maybe it's a black box service, I'm not sure.  
Answered 05/18/2015 by: trevzilla
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity