ANSWERED: Unable to PXE boot Lenovo Laptops
I'm attempting to use an existing boot environment and scripted installation to deploy some new Lenovo laptops (450/450s/460s) we've purchased. However, when attempting to connect to the boot environment, the machine fails to determine the server IP address from DHCP. After attempting to use the hardcoded fallback address and mounting the KBOX install shares, Error 1231 occurs (The network location cannot be reached)
ERROR: Unable to mount KBOX share at \\(hardcode IP)\peinst
I had thought that it may be an issue with Ethernet drivers, but I installed windows and downloaded drivers on a machine, and then placed them into KACE using Driver Feed Builder.
It doesn't seem like this corrected the issue.
I believe I've seen somewhere that doing this doesn't load the drivers into existing boot environments. I attempted to create a new one, but I still receive the same error.
Any help would be appreciated.
0 Comments
[ + ] Show comments
Answers (2)
Answer Summary:
Please log in to answer
Posted by:
SMal.tmcc
8 years ago
Top Answer
You need the winpe drivers for the version you are using. Place them in \\ikbox\drivers\kbe_windows_x64 or \\ikbox\drivers\kbe_windows_x86 then build a new kbe,
Test it from the boot menu, if it works. From the k2 menu make it default in settings so then it will be the default pxe choice
Test it from the boot menu, if it works. From the k2 menu make it default in settings so then it will be the default pxe choice
Comments:
-
I actually ended up finishing this process right at the time of this comment. This works perfectly for me.
For reference, the post install drivers would not work either. I discovered that this is due to Lenovo having a different naming format. Running the Driver Feed Discovery tool allowed me to reformat the file path to have them load correctly. - NJ@V 8 years ago
Posted by:
SMal.tmcc
8 years ago
If you use the KBEM
http://www.itninja.com/blog/view/k2000-kbe-manipulator
or use the link on your k2 tools page
the KBEM will create KBE's with a built in utility that tells you what the name of the directory that the driver feed will be looking for if enabled.
http://www.itninja.com/blog/view/k2000-kbe-manipulator
or use the link on your k2 tools page
the KBEM will create KBE's with a built in utility that tells you what the name of the directory that the driver feed will be looking for if enabled.