Has anyone gotten a Dell Optiplex 990 to pxe boot to the kbox 2000? I can pxe all my other models...except the 200+ new 990's I just bought. It gets to the point just before the scripted, imaging, recovery, etc screen and says that it cannot determined the kbox IP address.

As I said all my other computers can pxe just fine except for this particular model.

Anyone have an idea on how to get around this?

Answer Summary:
You do not have to build KBE on the 990 for this to work, as long as the appropriate drivers are in \\k2ip\drivers\os_arch, you recache the drivers and build a kbe, it will work from any machine model that is supported by WAIK and has Media Manager installed.
0 Comments   [ + ] Show Comments


Please log in to comment

Community Chosen Answer

[font="microsoft sans serif"]That system model uses an updated NIC chipset/drivers that are not in your KBE driver share.
[font="microsoft sans serif"]
[font="microsoft sans serif"]These systems share the same NIC chipset:
Latitude E6320
Latitude E6420
Latitude E6420 ATG
Latitude E6520
OptiPlex 790
OptiPlex 990
Dell Precision WorkStation T1600
[font="microsoft sans serif"]
[font="microsoft sans serif"]Here are the drivers you'll need:
[font="microsoft sans serif"]https://support.kace.com/packages/hd_attachments/683016/Intel_825xx-Gigabit-Platform_A00_R291627_win7.zip

[font="microsoft sans serif"]You can also get them from the KBE driver pack, which includes those drivers as well:
[font="microsoft sans serif"]http://downloads.kace.com/support/downloads/drivers/3.2/KBE_driver_pack.zip

[font="microsoft sans serif"]Access the driver share of your K2000 through the UNC path \drivers">[font="microsoft sans serif"]\\<k2000>\drivers[font="microsoft sans serif"], where <k2000> is either the IP address of the K2000 or the DNS name. Your user name will be <k2000>\admin, password by default is "admin", but can be changed from the General Settings section of the Control Panel.

[font="microsoft sans serif"]If you are running version 3.2 of the K2000:
[font="microsoft sans serif"]Copy the "WINDOWS7-x86" folder into "kbox_winpe3_x86" or copy the "WINDOWS7-x64" folder into "kbox_winpe3_x64", depending on the driver architecture you're wanting to use.

[font="microsoft sans serif"]If you are running version 3.3 of the K2000:
[font="microsoft sans serif"]Copy the "WINDOWS7-x86" folder into “kbe_windows_x86” or copy the "WINDOWS7-x64" folder into "kbe_windows_x64", depending on the driver architecture you're wanting to use. Do not place both x86 and x64 drivers into either of the shares.

[font="microsoft sans serif"]Once these are copied over, you will need to first re-cache the drivers, and then build a new KBE boot environment using the Media Manager. This new KBE boot environment will include the new drivers that were added above. Here is how to create a KBE pre-boot environment:
[font="microsoft sans serif"]http://www.kace.com/support/kb/index.php?action=artikel&cat=70&id=1058&artlang=en
[font="microsoft sans serif"]
[font="microsoft sans serif"]That should take care of the issue.
Answered 07/13/2011 by: warmep
Second Degree Green Belt

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.


Man I'm glad I asked on here now. That was exactly the issue. Thanks a million.
Answered 07/14/2011 by: dazormiq
Orange Senior Belt

Please log in to comment
You could also download the latest Dell WinPE driver cab version A05. This is what I grabbed when I was having trouble with my E6420s.
Answered 07/14/2011 by: Tentacle Master
Fourth Degree Black Belt

Please log in to comment

Boot fix for Optiplex 990 not connecting to KACE 2000 server. (Error 1231 when PXE or UFD booting)

As stated by others, the issue is that the KBE environments included by KACE don’t have the network drivers for the newer Optiplex 990s.
To ensure that you are using a boot environment with the appropriate network drivers for the Optiplex 990 you must build out an Optiplex 990 computer with a base OS (Windows 7 or Vista), then using that same computer upload a NEW boot environment to your KACE server.

To build out this new compatible Boot Environment do the following:
1. Install the OS on a Optiplex 990
Note: Use Windows 7 or Vista, won’t work off an XP OS. This is only to create the boot environment, this does not mean you can’t capture and deploy XP OS with this boot environment.
2. Install all needed drivers (Especially the network ones)
3. Ensure computer can communicate to the KACE server via the network
4. Install Windows AIK (This is needed by the K2000 Media Manager in order to create the Boot Environment)
5. Download and install the “K2000 Media Manager” from your KACE server home tab.
6. Using the “Create K2000 Boot Environment” tab, input your KACE server IP, name for the new boot environment, and select either the 32-bit or 64-bit.
(After the wizard runs you will see your new boot environment under Development/Boot Environments on your KACE Server)

7. Once listed on the KACE Server, simply click on the new Boot Environment and:
a. Check the “Create bootable USB flash drive image for this Boot Environment” and hit “save”.
( This will take you to a “Boot Environment Detail” screen with a status line above the “notes” area.
b. Once the Status reads “Completed” Click back on the “Boot Environment” tab and once again click on your new Boot Environment.
c. This time, click on the “Download bootable USB flash drive image for this Boot Environment”.
(A dialog window will prompt you to either, Run, Save, or Cancel the ZIP file)
d. Choose “Save” and designate a location when prompted.
Note: The generated file is in a .zip format and will need to be un-compressed.

e. After the files are un-compressed, simply run the “Install.exe”.
Note: This wizard will reformat the selected UFD. You will lose any other info store on this device.

When comparing the total size of the files copied to the UFD, using the provided “KBE 32-bit” or “KBE-64 Bit” Environments produces around 190MBs.
Following all the previously stated steps should produce around 350MBs of information.

Creating and using the new Boot Environment will now also allow you to Boot via PXE

Hope this helps – It worked for me!!!

Answered 08/14/2011 by: guillermomeraz
Yellow Belt

Please log in to comment
Hello from a newbie to Kace,

In warmep's post, I see the 'copy the "WINDOWS7-x64" folder into "kbe_windows_x64"'...

Where do I find a "WINDOWS7-x64" folder in de KBE_driver_pack.zip?

Answered 08/18/2011 by: frs
Senior Yellow Belt

Please log in to comment
frs: There is an updated driver pack available, you can get it here: http://www.kace.com/support/kb/index.php?action=artikel&cat=70&id=1020&artlang=en

You won't find a "WINDOWS7-x64" folder in the KBE driver pack, that was actually referencing the Intel drivers I had posted above that link. In the driver pack, you'll see kbe_windows_x64 and kbe_windows_x86, just put the contents of each into the respective folders on the K2000 driver share, recache, and rebuild the boot environment.
Answered 08/18/2011 by: warmep
Second Degree Green Belt

Please log in to comment
Thx! Image of the 790 works fine now! Last step : creating an answer file, my challenge of the day :-)
Answered 08/19/2011 by: frs
Senior Yellow Belt

Please log in to comment

I run it on the 990 with no problems.

Answered 05/30/2012 by: ohiosoundguy
Eighth Degree Black Belt

Please log in to comment

I had a 990 that wouldn't PXE boot into kbox this morning. The bios was revision A14. After upgrading the BIOS to A16, it booted into kbox just fine and imaged without a problem. A similar issue happened with our Latitude D630 laptops and a bios update was required then too to get the units to PXE boot to kbox properly.

I recommend using the DOS boot method of updating the bios. Download the HP USB Storage Format Tool (easily found from google) and then you can copy as many bios files (the .exe files) as you like to the USB drive.

Answered 10/17/2012 by: jmatthewf
White Belt

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