Best Practices Question

Do you recommend upgrading K1000 to 7.0?

01/13/2017 2188 views
We currently have K1000 6.4 and I would like to upgrade to 7.0. I'm wondering what you guys have to say. I read a couple of negative comments on here about 7.0. How is it working for you if you've installed? What do you recommend? Should I upgrade or wait for the patch? Do you know when the next patch is being released?

Thank you
6 Comments   [ + ] Show comments


  • Not ready for Prime time for a very large environment. Issues with the LDAP Labels, Client Communication and End-User portal behaviour. We'll be waiting for the next service pack.
  • I'm just introducing K1000 to our company and did the upgrade to 7.0 last week. However, most clients still run the old Agent (6.4). I haven't configured patch management or software distribution yet, and I'm still unsure, if I should upgrade every Agent to 7.0 before I start, or manually downgrade the few 7.0 Agents I have and restore the old Version of the K1000 from our backup. So far I have 10 Clients with the 7.0 Agent and 2 of them have issues with microsoft patches. It's nothing horrible, but reading napiert's comment makes me doubt my decision to go through with the update.
  • I would also like to add that this update broke some of our custom rules in our Service Desk. I didn't realize that they were making any major changes to the DBs.
  • Are the DB changes the primary cause of what people are having issues? We are having an issue with metering in 6.4 where the support tech is telling us we need to update to 7.
  • well then I'm glad I did not upgrade. Sound's like it's better to wait for the patch before upgrading to 7.
  • We just upgraded to 7.0 about 3 weeks ago. Everything seemed to be OK, but today we just found all of our 'Location' information is no longer associated properly with other assets. Not the end of world, but here comes a LOT of extra work because of the upgrade. Sure would be nice if there was a pre-check that could take place before the upgrade to help avoid potential problems like this.

Community Chosen Answer

Absolutely not!!!! We have had nothing but problems since doing so. If you are stable on 6.4, I would very highly recommend sticking with it.
Answered 01/13/2017 by: Michael4732
Purple Belt

  • I would agree with you.

All Answers

I agree.  We still don't have all of our computers listed in inventory. 
Answered 01/30/2017 by: piobaireachd
Purple Belt

My advice use the appliance version 6.4.120822 because this version is stable.
Answered 02/06/2017 by: yos.j.linggarjati@sat.co.id
Senior White Belt

This content is currently hidden from public view.
Reason: Removed by member request For more information, visit our FAQ's.

During the upgrade there were a few issues with asset data being correctly migrated but generally the upgrade has been fairly painless, our biggest requirement was the barcode scanning of assets using the k1000-Go app and this alone has made the upgrade worthwhile.

One issues to note during the upgrade is that the process takes longer than Dell (Quest) state and as the server was offline for a couple of hours it was swamped with agents trying to check in which overloaded FreeBSD during the restart throwing up "Limiting Closed Port RST response" messages in the console: http://www.itninja.com/blog/view/kace-limiting-closed-port-rst-response-from-x-to-200-packets-sec

Answered 02/07/2017 by: PeterSmall
White Belt

I'm using V 7.1.149 with K100 agent 6.4.522 and works great so far. In order for this to work faster I had to migrate the appliance into a VM.
Answered 11/13/2017 by: ds2009dsfn
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


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