/build/static/layout/Breadcrumb_cap_w.png

KACE AGENT UPDATE to 7.0.763 not completing inventory

I pushed the Kace agent 7.0.763 go a few machines for testing. When I view these machines in inventory they have not reported for several days and still states the agent is on version 6.4.522. But when I view the machines in device detail individually the agent version is correct 7.0.763. The force inventory tab is gone, but I do get the option to refresh. When refresh it stays on  Agent has been asked for updated inventory information. Any ideas?

3 Comments   [ + ] Show comments
  • Hi Alacsina,

    I created a SR for you and going to have it assigned to an agent to assist you. There's been some issues with the agents checking in with 7.0 and they should be able to help you find out what issue you're running into. - KACE_Irwin 7 years ago
  • Did you get any fixes for this issue? We have this same issue after upgrading our server to version 7 and have a mix of 7.0.643 and 6.4.522 PCs that will not complete an inventory. We have had a SR open for a while and have applied one KB they sent us but have had no resolution to this. I'd be curious to see what your resolution was for this. - DaveMT 7 years ago
    • Our anti-virus application control was blocking Windows PowerShell. The Kace agent 7.0.643 needs PowerShell in order to run correctly. - alacsina 7 years ago
      • Interetesting. What exclusions did you add to your Antivirus software to get past the issue? - DaveMT 7 years ago
    • We excluded PowerShell for only few users for testing and the agent is working correctly. We are working with the vendor only to exclude PowerShell or konea.exe for Kace. - alacsina 7 years ago
      • Thank you for the info! We will try that as well. - DaveMT 7 years ago
  • We got our issue with this resolved. We had Quest remote in and check the database integrity and they found no issues there. The only other things we did was:

    Our Asset Type for Device had the Mapped Inventory Field set to None. We changed this to System Name.
    Quest also restarted the services (Though we have done this 3 times in troubleshooting) and now everything appears to be working.

    Hopefully you can look at those two options for yours and it'll get you in the right direction. Good Luck. - DaveMT 7 years ago

Answers (0)

Be the first to answer this question

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