UPDATED 5/28/2015: This guide gives step by step instructions to the entire process of adding drivers and rebuilding the WinPE based KBox Boot Environment (KBE)

I wanted to make this mini guide because this is a common problem people experience here at ITNINJA. Often times we get the latest, greatest hardware that requires new drivers and a new KBE to get working. People will often get told what the problem is or the rough idea of how to fix it, but little more than that. This just basically throws everything together so that people can find the sum of the parts and for helpful people to link to. I welcome criticism or recommendations to make the guide more helpful. A few of these steps link to KACE knowledge base articles that are kept up to date by the staff.

So your (new) Dell machine won't finish/start loading the KBE, due to network errors i.e.
"ERROR: Unable to mount K2000 share at \\\peinst"
These issues are (most likely) caused from missing drivers in your current KBE (WinPE 3.0)
To fix these issues follow these steps.


How to Build a New KBOX Boot Environment


Obtain Your Missing Drivers:
Here are the drivers issued by KACE for WinPE 3,4,5 (Includes Most Dell WinPE drivers but not latest revisions) These include very useful drivers besides Dell ones, so it is strongly recommended you get this. You will need to login with your Dell Software Account to download these; the same account you use to download KBOX updates. This KB article will tell you delete everything in your kbe_windows_x64 and ...x86 folders. Obviously if you have custom KBE drivers you uploaded earlier do not delete them.
http://www.kace.com/support/resources/kb/solutiondetail?sol=SOL111717

And for all Dell machines, the latest, greatest Dell WinPE 3,4,5 CABs can be found here: http://www.delltechcenter.com/page/Dell+Business+Client+Operating+System+Deployment+-+The+.CAB+Files

If you use the latest Dell drivers be sure to delete the duplicate Dell WinPE driver pack out of the KACE supplied pack you downloaded earlier.


Upload, and re-cache the drivers:
This is the easiest step:
Navigate to your K2000's samba share \\-k2000_ip-\drivers . The username is "admin" and the password is the same one you use to access the PXE KBE boot menu on computers you image; what you set it as in your K2000 settings.
There are 2 folders that you will be working with: kbe_windows_x64 & kbe_windows_x86. Be sure to place your drivers in the correct folders. It is highly recommended that you delete drivers from these two folders that you no longer need/duplicates, i.e. old Dell and KACE driver packs.

Now, in your K2000 management console, navigate to the "Drivers" tab. In the "Actions" drop down select "Recache Drivers". This will navigate you to the recache page where you can select to recache all drivers (This is slow!) in the K2000 or just those drivers in the individuals folders such as kbe_windows_x64 & kbe_windows_x86. 


Then compile and upload the new KBE:

Before you begin:
-Media Manger and WAIK/ADK installs only needs to be done once on each computer you use to build new KBEs.
-It is recommended to name your KBE with date and intended OS deployment.
-When you click "Start Upload" your computer will pop up a command prompt that will look like its not doing anything for 2 mins.
-You must compile and upload a separate KBE for both x86 and x64 systems. 

Follow the steps here to compile and upload your new KBE: http://www.kace.com/support/kb/index.php?action=artikel&cat=70&id=1058&artlang=en

Remember to select your new default KBE under Settings and Maintenance -> General Settings

2 Comments   [ + ] Show Comments

Comments

  • Updated 5/52014 cause you know what, there's always new drivers to rebuild your KBE with ;)
  • Great work! Thank you for the guide. I was able to resolve my driver issues with this.
Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
I'm sure some new users will find this usefull =)

If you need the error message from WinPE when the drivers is missing the last message is:

"ERROR: Unable to mount K2000 share at \\[IP address]\peinst"
Answered 07/26/2011 by: rmeyer
Second Degree Blue Belt

Please log in to comment
0
ORIGINAL: rmeyer

I'm sure some new users will find this usefull =)

If you need the error message from WinPE when the drivers is missing the last message is:

"ERROR: Unable to mount K2000 share at \\[IP address]\peinst"



thanks I added that
Answered 07/26/2011 by: Tentacle Master
Fourth Degree Black Belt

Please log in to comment
0

I could remember how to do this today, but I remembered I wrote this guide lol

Answered 08/15/2012 by: Tentacle Master
Fourth Degree Black Belt

Please log in to comment
0

Hi Guys,

I have completed what you advised but I am still getting the same error.
When I ping the machine it works fine, when I try to map the drive it gives the error "User context not supported"

Any ideas? 

Answered 04/28/2013 by: cdalley
Seventh Degree Black Belt

Please log in to comment
0
Updated Today
Answered 05/28/2015 by: Tentacle Master
Fourth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity