I've upgraded to 3.4, now what?

So you have applied the 3.4 update, or are about to, and want to know what changes should be expected?


If you have not already installed the update we recommend you follow the procedure outlined here for a smooth update.

  1. Have a backup of your images, scripted installs, media, pre/mid/post install tasks, etc.
  2. Under Settings & Maintenance | Security, enable “Allow SSH Root Login (KACE Support).”  This will allow support to login the box should anything wrong happen.
  3. Reboot the K2000 prior to installing the update.
  4. Apply the update.


If your driver/restore share password is anything other than admin, you should start by creating a new KBE with the latest version of the KACE Media Manager, available for download from your k2000 library tab.  This update locks down the petemp and peinst shares that were open in the past and now require authentication to access them.
Also if you have any Mac NetBoot environments you will need to create new ones to access these shares, or if you want to add a Lion NetBoot environment. Again, the 3.4 media manager is required to build these environments.
For instructions on how to create a KBE refer to your admin guide, or this knowledgebase article.


The driverfeed has been updated to version 2. Drivers that have been downloaded them from the feed will automatically get installed on your scripted installs.
There are a few changes though that you should be aware.  If you had implemented driverfeed in the past then you should refer to this knowledgebase article [http://www.kace.com/support/resources/kb/article/K2000-3-4-Drivers-Postinstallation-Structure ] to straighten out your driver feed.
If you have models other than Dell, you can implement those into the drivers_postinstall directory manually, just follow this knowledgebase article [http://www.kace.com/support/resources/kb/article/K2000%20-Setting-up-Driver-Feed-with-non-Dell-Systems-in-3-4].
The driverfeed is not automatic with your images, but you can still use the driverfeed workaround with your images, look at this itninja post.

The drivers_postinstall directory now will automatically sync with your RSAs, so if you created this directory on petemp in the past, you can now remove them.  Don't forget to upgrade your RSAs though.  You can do this right from the K2000.  Browse to Deployments | Remote Sites.  Click on the detail page of an RSA, then click on "Check for Update." Once it reports an update is available, you can then click on "Apply Update."  Remember this will reboot the RSA.


If you've been waiting for SSL, then you’ll find the ability to add certificates under Settings & Maintenance | Security.


If you want to explore the KACE Native Imaging Toolkit, check out those videos to get started and implement the limited feature on your system.


Are you running out of space on your K2000? Or afraid you will after implementing the KACE Native Imaging Toolkit? Then you’ll be interested in using our offboard storage feature in 3.4.  Review this knowledgebase article for additional information.


Want to add features to KBE? Or upload a custom boot environment, check out the KBE Manipulator add-on application and videos on how to use it.


Unfortunately, we did find a bug or two with the 3.4 update, but they are minor, dealing only with sysprepped image, and we have fixes that you can implement if needed.

  1. KCleanup does not run in a 3.4 Sysprepped image
  2. K2000_deployment_info.conf file is not copied in a sys prepped image


What else is new with 3.4? Here is a mini video tour demonstrating the tweaks that we made to the K2000.


This post is locked

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