/build/static/layout/Breadcrumb_cap_w.png

KACE Product Support Question


Kace Agent "Provision Error" MSGCODE: 003] Uninstall failed: K1000 Agent NOT removed.

02/15/2019 478 views

Hi Ninjas,

Im trying to uninstall agents on some of our MIA machines using the provisioning tool with IP addresses.  The machines are active on our network as I can ping them. I have used the tool to install and uninstall agents before. I am getting the following error {MSGCODE: 003] Uninstall failed: K1000 Agent NOT removed. The firewall is not blocking any ports, I turned off UAC on some machines for testing, but still failed. The machines do have access to the sambra share.

0 Comments   [ + ] Show comments

Comments


All Answers

0

I never use these batch files to remove the agent.  Because these are MIA, I'm assuming you are not using KACE to push the scripts.

"C:\Program Files (x86)\Quest\KACE\AMPTools.exe uninstall  all-kuid"

This is the command line I use for KACE connected devices, however you can run this however you can get to the machine.  Alternatively, you can uninstall using msiexec /x if you know what product ID to target.

AMPTools uninstall [all|all-kuid]

Uninstall with no options leaves configuration and KUID

  • all: Also delete configuration, but not KUID
  • all-kuid: Deletes everything, including KUID
Answered 02/19/2019 by: worzie
Third Degree Brown Belt

0

worzie

I have tried the program files (x86)\Quest\KACE\AMPTools.exe -uninstall all  command, but the files are still showing. 

Answered 02/19/2019 by: dazman
White Belt

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

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