Best Practices Question

Any one have problems with upgrading to K1000 7.0 or K2000 4.0

12/13/2016 2999 views
Just wanting to see if any groups have completed latest upgrade to the K1000 and/or K2000 and if there are any problems, issues with the latest version...We are planning an upgrade soon, thought I would check on here to see peoples reactions, comments.  
1 Comment   [ + ] Show comment


  • We have recently renewed out license for KACE and currently have version 6.3.113399. We are planning on upgrading to 7.2. Have more issues been solved with this version.
    Also, what is the upgrade path we would need to follow? Do we need to increment from 6.3>6.4>...7.2?

Community Chosen Answer

There are good things as well as drawbacks to both actually. 

Pros : 
  • The ability to View your ServiceDesk tickets without having to take the long way around to check your ticket queue.
  • The RUN NOW ability on software distribution.
  • Added information for Users under settings
  • The ability to have a 3 TB virtual device
  • Archiving computers.  You will be able to save device information of old computers without using precious licenses
  • Better security.  My K1000 went from a C+ to an A+ on a security site.
There are other Pros, but these are the things that I can focus on now.

Cons : 
  • The Asset, Device, and Submitter fields have all been moved to the left side of the queue, and move to the right after the ticket has been submitted.  That will cause a lot of changing of the ticket layout.
  • Extra Location added to Assets.  You will have to set a new location on Assets because of the new field.

  • 64Bit for better security and more speed
  • Faster imaging of devices through the imaging function
  • Being able to capture images through a RSA
  • RSA devices take a minimum of 1TB.
It's all up to you on what you want to use.  If you don't have the datacenter space, don't upgrade the K2000 yet.  If you have a lot of Service Desk queues, give yourself some time to think out the upgrade of the K1000.  

Good luck!

Answered 12/14/2016 by: zgillette
Second Degree Green Belt

  • Is the new 1TB requirement for RSA's documented somewhere? Everything I'm able to find online says 250GB minimum.

All Answers

Upgraded K1000 from 6.4 to 7.0 a couple weeks ago.  Last week I deployed the 7.0 agent.  Since then I've noticed the following...
  • Occasionally I lose connection to the web console for a minute or two.  I can't connect.  If I keep refreshing the page it comes back
  • I've noticed several times on the Home dashboard, the number of connections drops to near zero machines, as if all the agents simply stop communicating all at once.  Over the next couple of minutes they all come back online.
  • Patching does not seem to be working.  I just noticed this today.  Looking into this more to try to figure out if it's a real problem.  
Answered 03/15/2017 by: rcubed
Senior Yellow Belt

  • Any update on your issue? We are trying to decide if we should upgrade w/ 8 active queues and 2500 endpoints.Have things ironed out or are you still having problems?
    • Our problem may have been several scheduled scripts that were running every 30 to 60 minutes. I noticed the performance impacts were occurring on the hour and half hour. I reviewed the logs and found that the database was being hammered at the top of every hour. I spent most of yesterday adjusting and disabling scheduled scripts. Today, so far, things seem to be running much more smoothly. Today is a heavy patch day, so I should know soon If the adjustments made a difference I'll post an update later.
  • We upgraded back in January both our K1000 and K2000 to the latest version. On the K2000 side of the house, for our setup, seems to be ok, we can't find any problems. In regards to the K1000..... patching.. patching... patching. I have been working for the past month and a half regarding why my patching no longer works. Every since the upgrade regardless the patch size job ( rather number of machines, or number of patches deployed) well over half fail. We had to increase both the detect and deploy times both to five hours each just to get the barely 50 percent success rate. This was not the case with 6.4. Something for sure changed/broke with the patching setup with the upgrade to 7.0. We had to do a fresh install of our K1000 and do a re-import of our backup because the upgrade from 6.4 to 7.0 kept failing and support couldn't figure out why. As of yet support has been unable to offer an explanation as to what is causing the patching issues I am told that an update for the k1000 is coming out sometime in April, so I am hopeful. Good to know we aren't the only ones who are having this problem. Support said we are the only customer who has called in saying that there was any patching problems with 7.0
    • We have experienced the same issues with patching. With 6.4 we patched 1800 machines weekly with very few issues. After upgrading to 7.0, patching completion rates fell dramatically, with many ending with errors or suspended. I tried increasing the detect and deploy times but did not notice any improvement. I just upgraded to 7.1 with the hopes of seeing overall improvements. I was talking with a colleague who used to manage the K1000 appliance. He said he noticed the similar problems after upgrading from 5.x to 6.x. He was able to fix the issue by backing up the data, downloading and installing a new .ovl file and then restoring the data into the new. If I don't see any improvement with 7.1 I will give that a try. I may also try to bump up the resources on the virtual appliance.
Just upgraded the k2000, the boot menu password doesnt work, but that is in the known issues with the new version, so will have to decide if that is an issue or not. second, the speed for loading the iso is a LOT faster than the previous version. third, my previous boot environments didnt work correctly, so had to recreate them.
Answered 12/14/2016 by: timbot18
Senior White Belt

  • just updated to 7.0 for k1000 and it changed our custom assets for buildings by merging all of the locations with it, so we went from 28 to 2112 assets for buildings. have a ticket open with support about it.
Upgrading caused major ticket email loops to become a issue again. We had everything ironed out. Updated Friday night. The K1000 stopped sending emails until Wednesday then we got a flood all at once. 

They changed SMTP authentication. Our external SMTP server does not require a UN/PW to connect but now the UN/PW is required.

We have major ticket creation delay now. After sending a ticket in it can take up to a hour for a ticket to be created and a confirmation email to be sent.

We are upgrading to 7.1 today in the hopes it resolves some of the looping we are seeing with emails.
Answered 05/02/2017 by: DirtySoc
Senior Yellow Belt

  • Upgrading to 7.1 resolved all of the issues we had. The K1000 now runs dare I say quickly. The web interface is faster and searches return results more quickly.
We only upgraded our K1000. We have been having constant agent issues ever since. 
  • About 20% of our computers had the agent go missing (uninstalled) with the Agent Update provisioning. 
  • The scheduled provisioning no longer works to reinstall those agents (worked previously).
  • We have had all computers agents just randomly lose their amp connection at the same time and no longer check in. The agent is still installed and running but no amp connection. You need to restart the computer or manually stop and start the "konea" service to fix it.
  • Users no longer can download software for computers that aren't "assigned" to them. ie - can't install software on conference room pc for training/meeting
Answered 12/14/2016 by: troyr
Yellow Belt

Since I have upgraded K2000 to Version: 4.1.182 and using latest pcs, seems the pre & post installation script runs so fast that nothing happens and skips to next script.

And seems ignores any script which contains start /wait.

in following Diskpart script:
select disk 0
create partition primary
select partition 1
format fs=ntfs quick
assign letter C
detail partition

I had to put the above red labelled texts to slow it down so that the current script finishes what it has started.
And in the following Post-installation script:
wsname /RDF:MACtoPCName.txt /DFK:$MAC
timeout /T 5

Answered 10/23/2017 by: haseebiqbal
Orange Senior 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