/bundles/itninjaweb/img/Breadcrumb_cap_w.png
Hello everyone,

i inherited a K1100 and K2100 without any documentation from the previous sysadmin about four years ago.
These Appliances havent been correctly set up by the previous sysadmin and therefore werent in use for the time im working here.
Most of the Stuff worked with GPO's for now, but there are some issues with one application, and now management want me to push this application to all of my clients with Kace.

So far i've managed to deploy the application to multiple test machines without issues.

I uninstalled the old Kace Agent from all of my Machines in my IP - Range and then cleared the inventory and the assets for these PC's.

After installing the latest Kace Agent some devices show up in the inventory after a few minutes but most of them dont appear.
I already checked the amp - files for the correct hostname of the appliance.

i assume that the devices that dont show up were already inventoried (before i deleted them).

I did a lot of searching on google, the quest site and this site but haven't found any working solution yet.

Thanks already for reading this far and for your help.
0 Comments   [ + ] Show comments

Comments

Please log in to comment


Answers

1

I have seen where the KACE UID changed but the PC name didn't so it creates duplicate inventory items so it looks like the PC isn't talking but it is.  However, if you are not seeing the PC name at all, then that is not it.

If you can, check a few of the PCs amp.conf file (Located C:\ProgramData\Quest\Kace\) and if it is blank, you can replace it with one from a PC that is not.  You will have to copy/paste and overwrite it for best/fastest results.  Then, from an Admin command prompt, you can browse to C:\Program Files (x86)\Quest\KACE\ and run amptools.exe retrust.  This should recommunicate with the KACE server.  If this is your solution, you can setup a few settings in a GPO for startup script and file copy to correct this issue.

One tip, I would suggest for your GPO.  Before you attach the MSI file for the software distribution, rename it to include your server name.  for example, rename the file to ampagent-8.1.52-x86_K1000Server.company.com.msi.   This will automatically tell the agent which server to communicate with.

Answered 04/18/2018 by: DaveMT
Fourth Degree Black Belt

  • Thanks for the Answer. The Solution was to run "runkbot.exe 4 0" and the devices appear in the inventory. In the Settings Panel -> Agent Settings i have around 80 connected agents, but only 40 in inventory. Can i run a script on connected agents that are not in inventory?
    • You can use Group Policy and write a script to run during startup, or you can create a PowerShell script to run against PCs in your domain that are online to execute the command.
Please log in to comment