/build/static/layout/Breadcrumb_cap_w.png

Kace Inventory not updating suddenly

Ran into something today which is really weird, I was doing some tests with the GP to push out Kace 1.5.10 and I added a new PC to the GP, Kace installed itself in the background the AMP service was running yet it still didn't appear in the Inventory. 

Any ideas on how I might go about troubleshooting this? 

 

*Just to add, machines currently on the inventory seem to be updating fine, it's just new machines.

 


0 Comments   [ + ] Show comments

Answers (3)

Answer Summary:
Posted by: Mobzy 10 years ago
Third Degree Blue Belt
5

Ahh, I think I found the issue. I havn't configured the new .MSI and the amp.conf doesn't have the correct server details thus It's unable to communicate with the Kace Server.


Comments:
  • possible solution here: Copy a working amp.conf to all affected machines or run AMPTools.exe -resetconf host=CORRECT_K1 - Nico_K 10 years ago
    • This should work too assuming the hostname can be resolved:

      ampagent.exe -host=HOST_NAME - jknox 10 years ago
  • It's only a few machines that have this issue and they are only used for tests but that is handy to know.

    Question is, I'm going to roll it out to a lot of machines soon so what's the best way to resolve this issue? I don't know what I'm doing wrong with the .msi for it not to have the correct Kace server details? - Mobzy 10 years ago
    • Rename the ampagent-5.x.xxxxx-x86.msi to include your host name. e.g. ampagent-5.3.44367-x86_hostname.company.com.msi

      http://www.kace.com/support/resources/kb/article/installing-the-kace-k1000-agent-through-windows-group-policy - jknox 10 years ago
    • What's your full command line you are using to install? - dugullett 10 years ago
Posted by: SMal.tmcc 10 years ago
Red Belt
3

if you want to use the GP to push it out you can use the host switch with the MSI or rename the msi to include the host name.

ampagent-5.4.10622-x86.msi HOST=kbox.company.com

ampagent-5.4.10622-x86_kbox.company.com.msi

http://blog.kace.com/2012/05/24/options-for-deploying-the-k1000-agent/


Comments:
  • Yeah, that's been done but it still doesn't seem to work which is weird. - Mobzy 10 years ago
Posted by: k4rl@TES 10 years ago
Senior Purple Belt
2

If your not running DHCP within your infrastructure you can update the inventory as follows:

K1000 > Settings >K1000 Agent > Advanced Provisioning

Specify the IP range that you give your users and ensure that you wish to push down the correct and upto date K1000 Agent. You can either run this on a schedule or run one time. Perhaps im missing the point but if you simply want to update the inventory then this should do it.


Comments:
  • Infact what am I talking about. Ofocurse you can do this if you have DHCP implemented. Just state the specific range. Had a moment there. My bad :) - k4rl@TES 10 years ago
  • Ah great! That will come in handy! :) Thanks - Mobzy 10 years ago

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