KACE Product Support

I had a similar issue when we purchased some new PCs from Dell. I contacted KACE and here was there reply. After I followed the instructions below, I connected just fine.

copy the appropriate drivers (from the supplemental driver pack) to the corresponding folder on the driver share. i.e. copy the x86 drivers to the kbox_winpe_x86 folder and the x64 to the corresponding x64 folder. Supplemental Driver Pack: http://downloads.kace.com/support/downloads/drivers/3.2/KBE_driver_pack.zip then you will need to re-cache the KBE x86 Drivers from the Drivers Tab. Third, re-build KBE via the Media Manager: install the WAIK and the media manager (from the Library tab of the kbox) onto a Windows 7 System. 1) Library > Overview > Download Media Manager. 2) choose > Download for Windows (Requires .NET 2.0), from a windows client. 3) Download the WAIK for Windows 7: http://www.microsoft.com/downloads/details.aspx?familyid=696DD665-9F76-4177-A811-39C26D3B3B34&displaylang=en 4) Install the WAIK onto the Windows Box. 5) From the Media Manager, choose: a) create Kbox boot environment. b) input kbox hostname or ip c) input name for new KBE boot environment, for ex: KBE (x86) Boot Environment 6) choose 32 bit 7) input path of WAIK, normally: C:\Program Files\Windows AIK - you can do the same for the 64 bit build. Finally, set the new boot environments as the default PXE boot options from the: KBox Settings and Maintenance > General (tab). Lastly, delete the previous KBE Boot Environment.

Mark,

Do an ipconfig at this command prompt to determine if you have an IP address. If you don't, then we need a driver for the NIC. If you do, then something else is going on.

Type kgetdhcp 66 and tell us what you get.

Type kgetchp 244 and tell us what you get.

I look forward to your reply,

Corey

'no data' from either command.

I had a sucspicion it might be due to dual NIC cards, only one was connected to the LAN. I connected the second one and the kgetdhcp 66 found the IP of the kbox. startnet.cmd got it going again.

I've installed on two other similar devices with dual NIC cards only using one 'live' one with no issue, guess this might be hit or miss.

If it was a driver issue how would you go about uploading the new driver onto the KACE 2000?

ZT

Thanks, I was able to get it going as well.

Thanks for the Dell file, was there a KBE driver pack ever built for HP or IBM PCs? I have some HP 8440p and HP 8740w boxes that are having this exact same issue. I think the Dell drivers will repair this, but I was just making sure there wasn't an HP driver pack.

I have a similar problem, Dell workstation is able to PXE boot fine to the point its able to locate the kbox 2000 on the network.

Workstation is getting an ip and am able to ping the kbox as well.

When i choose the boot driver KBE (Windows x86) driver from boot list, getting : 'no data' for both 66 and 244

Could this be related to Option 67: Bootfile name, does this always needs to be set to "kbox2000.0" or the "dnsname.0" of kbox 2000?

Appreciate any suggestion, Thanks.

I receive this error with a new Lenovo T410 I have. I was looking at adding the drivers from both of the zip files - but I noted that when I extracted the zip files locally structure is exactly the same for each - will one overwrite the other - should I only use the supplemental? The original zip file took much longer to obtain and seems larger.
And I added drivers (or thought I added drivers) the other day, and recached and created a new boot environment - but I don't see the drivers I added. When I look at the driver listing and sort by INF I don't see the folder I created - anyone have thoughts on that?

Thanks much!
Anne

ORIGINAL: kace_user

I have a similar problem, Dell workstation is able to PXE boot fine to the point its able to locate the kbox 2000 on the network.

Workstation is getting an ip and am able to ping the kbox as well.

When i choose the boot driver KBE (Windows x86) driver from boot list, getting : 'no data' for both 66 and 244

Could this be related to Option 67: Bootfile name, does this always needs to be set to "kbox2000.0" or the "dnsname.0" of kbox 2000?

Appreciate any suggestion, Thanks.



Your KBE will likely need to have the drivers for the NIC. If the driver pack from kace support site doesn't solve it, download the win7 driver from the manufacturers site and copy the drivers (not the installer) to \\yourkbox2000\drivers\kbox_winpe3_x86 (or x64), recache, then rebuild your KBE.

RE Option 67- This is always "kbox2000.0". Option 66 is the IP or hostname of your box, option 67 is the name of the file the client is supposed to request when it reaches the server.

ORIGINAL: netty2667

I receive this error with a new Lenovo T410 I have. I was looking at adding the drivers from both of the zip files - but I noted that when I extracted the zip files locally structure is exactly the same for each - will one overwrite the other - should I only use the supplemental? The original zip file took much longer to obtain and seems larger.
And I added drivers (or thought I added drivers) the other day, and recached and created a new boot environment - but I don't see the drivers I added. When I look at the driver listing and sort by INF I don't see the folder I created - anyone have thoughts on that?

Thanks much!
Anne



The driver pack from Kace is pretty good, but if it's missing something specific that you need download the Windows 7 driver from the manufacturer and copy the driver files (not the installers) into the appropriate KBE folder(s). We shouldn't necessarily replace all of the drivers though, ecpecially if most of them are working. I almost never overwrite drivers in the KBE unless I'm having problems with one- in which case only overwrite that one, not the whole folder structure. When in doubt create a subfolder and copy your new stuff into there. Or better yet, set up a substructure in each KBE folder to separate NIC, HDD Controllers, Etc. into hardware classifications; Then you're only keeping one version of drivers, limiting the possibility of duplicate (conflicting) drivers.

I have same exact problem and I tried SuperGenuis' method. It didn't work. Laptop model is HP ProBook 4730s.

Thanks,
Sam

update drivers and re-cache. Rebuild KBE would fix the problem.

Thanks!

We are having the same issue, we are trying to upload an image for a HP Pro Book 4530s, I updated all my drivers, rebuilt the KBE. Still will not connect. I get an error 1231 unable to connect to k2000 share. I also tried to upload drivers from the harvest utility, does this add them correctly? I figure a driver issue, because I get no ip address with the ipconfig. Thanks for any help

Jon,

Try looking at the KB article on Kace's website:

KBE stops at a command prompt while booting and doesn't continue
http://www.kace.com/support/resources/kb/article/KBE-stops-at-a-command-prompt-while-booting-Boot-Environments

This should help.
The latest driver pack for KBE can be found on this page:
http://www.kace.com/support/resources/kb/solutiondetail?sol=SOL111717