I need to remove old agents from about 180 PCs. The old agents are preventing the new agents from being installed. The old agents are not communicating with the KBox. Thanks

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

1

Hi dnorwood, you can use a logon script or startup script for that, via GPO. A simple batch file would do the job best and easy enough I'd say. What version of the agent would you like to remove?

Up to 5.2 / SMMP Agent which uses kinstaller.exe to uninstall itself.
From 5.3 / AMP Agent which uses amptools.exe to uninstall itself.

Commands:
SMMP = C:\Program Files\KACE\KBOX\kinstaller.exe -display_mode=silent -uninstall
AMP = C:\Program Files\Dell\KACE\amptools.exe -uninstall

For AMP you can also use the "uninstall string" from the "Uninstall" registry key:
http://msdn.microsoft.com/en-us/library/windows/desktop/aa372105(v=vs.85).aspx
...since it is an MSI, think it started to be an MSI with 5.3 agent releases. Just find the string upfront via the registry of one machine, the key is unique per version. Use "msiexec.exe /x {xxxxxxxxxxxxxxxxxxxxxxxxx} /qn" inside the batch file.

Let us know! Cheers!

Answered 02/03/2013 by: RaSko
Purple Belt

  • This content is currently hidden from public view.
    Reason: Removed by member request
    For more information, visit our FAQ's.
Please log in to comment
1

Are you unable to do a provision and check off uninstall agents then reprovision with new agents?

Answered 02/03/2013 by: jdornan
Red Belt

  • This is how I've always uninstalled problematic agents. Just make sure you have both "Provision this platform" and "Remove K1000 Agent" checkboxes selected (along with the standard ports and credentials info).

    John
Please log in to comment
1
I just fixed an issue very similar to this. Out of about 280 clients, I only had a handful that were using the current client (6.4.522). Many had 6.4.180, some even still had 6.2.1025. I was tearing my hair out trying to figure out why the updates weren't happening like they should, until I got some help from Dell's Pro Support. They assisted me in upgrading my K1100 to the latest version, and then to get the files to allow the clients to upgrade. They also helped me track down the older install files for the 6.4.180 and 6.2.1025 clients.

I then placed these files into the SAMBA share on the K1000 (dropped 'em into \\k1000\clientdrop\agent_provisioning)

The problem I ran into, even when trying to manually uninstall the old clients was that they were looking in that directory for their original installer. When it wasn't there, the process would crap out. Once I put the installers on there, the scripts ran perfectly! Now almost all my clients are updated (still have a few stragglers, mostly PCs that haven't been on in awhile for various reasons (some are on my bench to be fixed/reimaged), or laptops that users have at home.)

tl;dr version: Get the original installers for the old versions of ampagent that aren't uninstalling, place them in \\k1000\clientdrop\agent_provisioning, then re-run your provision agent.
Answered 08/05/2016 by: darthbubba
White Belt

Please log in to comment
0

Hi, I was wondering also, we have GPO successfully installing agents.  If I have a problematic agent and I clean it off a host, should GPO reinstall it the next time the computer is rebooted?  I tried this with a virtual test machine and it wasn't pushing it out.  This would be ideal to get around firewalls and whatnot.  Thanks.

Answered 02/12/2013 by: trevzilla
Senior Yellow Belt

  • If the agent reinstalls the next time the computer is rebooted depends on the GPO. It is common to use a logon script or a startup script. Inside the script you say to "stop right here as the agent is installed" or "continue and install the agent". You should do this as the GPO will be applied during every reboot or during every gpupdate interval (Iirc by defauly 60min). Speaking of a startup script would require a reboot so it also depends here. If you got all in place with this kind of script/code it should install after the reboot yes.

    The other way via GPOs is to use "Software Installation". However, this may be really too much technology to deploy just an MSI. Personally I also preferred John's (mentioned above), use auto provisioning and "auto-deprovisioning" ;)
Please log in to comment
0

RaSko,

I am in the process of updating the agents to 5.4 from 5.3 via group policy. But 5.4 is not uninstalling the previosu version properly and hence the systems are  loosing amp connection. At this point I would have to login to the system, manually remove unfinished uninstall (using MS tool) and then reboot the system for my agent install group policy to apply. I was wondering if i could use the same startup or login script that you specified earlier and then apply the software policy too by specifying the order in which they should be applied. Is that going to work? I have about 300 systems and most of them have lost amp connectivity. Can't login to each and every system to fix the problem. would really appreciate your input.

 

Answered 05/15/2013 by: sangeeta2013
Senior White Belt

Please log in to comment
0
Good info darthbubba.
I'd ran into that some time ago and now we leave old versions on the share until all agents have been updated...
Answered 08/10/2016 by: MichAda
Orange Belt

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

Share