KACE Product Support

You'll need to update your K2000 Boot Environment.

If you are running the latest release of K2000 go to the Library Tab, then Driver Feed. You'll then want to download and install the x86 and/or x64 (depending on what KBE architecture you are booting into) drivers for Windows PE (dated Wed Jan 20 20:30:48 2010) (they're on the second page at the very end).

Once you've done that make sure you have The Windows Automated Installation Kit Supplement for Windows 7 SP1 (WAIK SP1) installed on your computer, then install and run the K2000 Media Manager using the 'Create K2000 Boot Environment' tab. Once the Media Manager has uploaded the applicable KBE (x86 or x64) you'll then want to set that new KBE as the default KBE by going to:
Settings & Maintenance - Control Panel - General Settings - Default K2000 Boot Environments

Does that help you?

Sincerely,
Eric

@Eric

Thanks worked great! I have the KBE Feeds turned on but did not build a new KBE using the Media Manager.

I had the same problem with the same system. You would think if you are subscribed to KBE drivers the box would be smart enough to use them.

Feature request....

ORIGINAL: jrscribner

@Eric

Thanks worked great! I have the KBE Feeds turned on but did not build a new KBE using the Media Manager.

There are no KBE feeds; the Driver feed makes drivers available to the installed OS, not KBE. You still need to provide drivers for KBE and build as usual.

Hi,

We are having the exact same problem as jrscribner with the same computer model. Our KBE is updated with the latest Windows PE Drivers, but still we experience the same issue.

This model is fairly new, so would you think there might be some compatibility issues with the hardware in here and the Windows PE Drivers?

Thanks!

Scheller:

As I've successfully deployed both Scripted Installs and images to the E6520 using our K2000 I would have to say that are not hardware issues.

I blew-away my driver feed drivers, except for my Windows PE Drivers, recached my drivers from my K2000, and upgraded my WAIK to SP1 on the machine I then created a new KBE for x86 (as well as x64) on. My E5420, E6420, and E6520 machines now PXE boot just fine to the K2000 and took Scripted Installs and images just fine.

Have you cleaned your drivers share of excess drivers such as from driver harvesting in not only the kbe_windows_x86 directory, but also the windows_7_x86 directory as well? Did you recache drivers immediately after that?

Sincerely,
Eric

Yes, but it's not logical that we as administrators are not informed when new KBE Driver packages are available. You would think that this would be an easy integration into the system.


ORIGINAL: dyehardfan

I had the same problem with the same system. You would think if you are subscribed to KBE drivers the box would be smart enough to use them.

Feature request....

ORIGINAL: jrscribner

@Eric

Thanks worked great! I have the KBE Feeds turned on but did not build a new KBE using the Media Manager.

Eric,

Thank you for the information. I manually put in the network and storage drivers into the list of KBE drivers. resolved the issue by taking the following steps:

-Installed WAIK SP1
-went to the Dell website to download the hard drive and network driver for my E6520.
-extracted the exe files using 7zip to the following location:
\\kace2100\drivers\kbe_windows_x64\feed\dell\winpe\winpe\x64\<network or storage>
-recached my drivers (located in Library>Driver Feed>Manage Driver Settings)
-rebuild my KBE

After all that, I was able to boot. Hopefully this helps someone else experiencing this issue. Thanks guys for the help and guidance.