KBOX Boot Environment CD issue?

Created KBOX Boot Environment with Win PE x64. Problem here-- it cannot find KBOX 2000 server. Both computer name and actual IP address were used, but no luck. I'm able to boot into that CD with network, (can map to shared drives via network). I am unable to figure out what the last message really means. The message reads: (after the command, "wpeutil DisableFirewall")

The command completed successfully.

*** Waiting for network devices to settle

*** Checking if this is a UFD boot and an image is prepped for deployment

*** Locating KBOX IP address from DHCP option 66 or 244

x:\windows\system32>kgetdhcp 66 1>x:\windows\TEMP\kbox-ip-address

x:\windows\system32>if errorlevel 1 kgetdchp 244 1>x:\windows\TEMP\kbox-ip-address
"ERROR: Unable to determine KBOX IP address"

By the way... I went into the TEMP directory and opened kbox-ip-address file. It reads: no data

Thoughts or advices?


0 Comments   [ + ] Show comments

Answers (6)

Posted by: cserrins 13 years ago
Red Belt

What are you using for DHCP Server?

Since you are now on 3.2, you should look at the Guided Tour>Setup under Home. Scroll down to the very bottom where it dicusses setting up option 244 (also called sname) on your router.

Posted by: rob4crow 13 years ago
Yellow Belt
Um, while this is a great idea, since the KBE environment automatically locates the closest kbox, it can be a lot of work to do it for 400 subnets, furthermore, you may run into issues if you are using a Citrix PVS server to deploy end point devices in some areas. The main attractiveness of using a CD or USB stick is that you are not dependent on PXE. You can hardcode an IP into the KBE by:

-Mounting "c:\Program Files\Windows AIK\Tools\PETools\(Architecture type)\Winpe.wim" file using IMAGEX.EXE
-Create a file called "kbox-ip-address" under (image-mountpoint)\windows\temp, and type in the desired IP address or host name
-Change the NTFS permissions of the "kbox-ip-address" file so that the administrators group and the system account only have read/execute rights to the file.
-Commit the changes to the Winpe.wim file and UNMOUNT it using IMAGEX.exe
-Create the KBE environment as usual with the media manager tool.

(architecture type) = x86, IA64 or AMD 64
(image-mountpoint) = empty folder name created to mount the winpe.wim file via IMAGEX.EXE
Posted by: mdereus 12 years ago
Senior Yellow Belt
I am using KACE in a PVS environment and rob4crow's advice saved me. It works perfectly.

There are a couple things I'd like to add. You need to use /MOUNTRW with IMAGEX otherwise you won't be able to write to the image. Once the image is mounted you will need to turn off Read Only access to that directory. When changing the permission on kbox-ip-address you can't uncheck the Allow permissions, so you simply need to Deny write access for SYSTEM and Administrators. I will gladly list the exact commands I used to accomplish the entire thing if requested.
Posted by: cserrins 12 years ago
Red Belt
rob4crow and mdereus,

I have a script that will perform all of this for you automatically, let me know if you are interested.

Posted by: dmontgomery 12 years ago
Senior Yellow Belt
Getting the same message, also in a PXE environment.

PXE environment using Windows 2003 DHCP. Option 66 is set to the KBOX2000 IP address. Option 67 is set to kbox2000.0

We can deploy Scripted installation to Dell Optiplex 780 with no issues.

When we atttempted the same SI to a Dell Latitude E6410 we get the same error mentioned above, ending with:

"Error: Unable to determine KBOX IP address."

Corey - would the script that you have address this issue?


Posted by: rmeyer 12 years ago
Second Degree Blue Belt
I've had a problem like this with an old IBM/Lenovo model that was using Broadcom NIC driver.

The only solution I found to this was to make a seperate WinPE image that only contained that driver, the problem with it was that broadcom said you should use the Windows XP driver to Windows Vista/7, and since WinPE 3 is based on Windows 7, you had to remove all other broadcom drivers with referance to that hardware ID because it would fail otherwise and only have that driver in it.

I'm not saying it can't be done with the driver along with the rest of the drivers, I just been creating 50 diffrend WinPE images, and ended up giving up, since it's a model that will be replaced soon anyway.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

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