Problems/Symptoms:
When booting a machine via DOS PXE, one of the following errors may occur.
HTGET: Could not get connected, retry 0
Causeway 9
3510:255 Image stream corrupt (image process aborts mid-operation)
Type the name of the Command Interpreter (e.g., C:\WINDOWS\COMMAND.COM)
"Hanging" on "Waiting for command"
Fix:
Download the updated LANDesk DOS PXE Boot Images:
http://community.landesk.com/downloads/patch/PXE_BOOT_4.5.0.zip
The updated PXE DOS Boot Images will work with any version of LANDesk.
Before any work can be done with the boot images, it is necessary to download the Winimage utility and install on the Core Server.
WinImage can be downloaded here:
http://america.winimage.com/download/winima81.exe
How to fix Name Resolution Issues:
Download the updated DOS Boot Images and copy them to the core server.
1. Open CoreServer\Program Files\LANDesk\Managementsuite\LANDesk\Files\DOSUNDI.1 with Winimage.
2. Extract the file STARTENV. BAT from the root of the boot image. This can be done by dragging it to the desktop.
3. Open the STARTENV.BAT and change SET COREHOST= [YourCoreServer] to SET COREHOST=[coreserver ip address]
4. Save the modified STARTENV.BAT file and re-inject into the root of the image. Remember to save the image after injecting the new STARTENV.BAT file.
5. Using WinImage, navigate to the \NET directory of the image.
6. Extract the LMHOSTS file from the image
7. Edit the LMHOSTS file with notepad and add entries for ANY server that will be referred to in OSD tasks
Example:
# x.x.x.x This entry is the core server where the image utility is stored
# x.x.x.x This entry is for an image store other than the core server
8. Save the LMHOSTS file, and re-inject into the \NET directory of the DOSUNDI.1 image. Remember to save after injecting
9. Make the same changes listed above to CoreServer\Program Files\LANDesk\Managementsuite\LANDesk\Files\BOOTMENU.1
NOTE: Do not forget to update the BOOTMENU.1 file with the same changes. A DOS PXE Boot uses the BOOTMENU.1 as the boot image, and the name resolution issues must be fixed here as well.
Adding Drivers to the boot images
1. Download the manufacturer driver(s) from the appropriate vendor
2. On the core server, open the \Program Files\LANDesk\Managementsuite\LANDesk\Files\DOSUNDI.1 boot image using Winimage.
3. Navigate to the \NET directory of the image. Extract the net.zip file from the image
4. Open net.zip with preferred tool (WinZip, WinRar, etc.) and add the *.DOS driver file downloaded from the vendor
5. Save the changes to NET.ZIP and inject back into the \NET directory of the boot image
6. Navigate to the \NET directory of the image. Extract the nic.txt file from the image
7. Copy nicinfo.exe from [Your_Core_Server]\ldmain\landesk\vboot directory to a machine with desired NIC running Windows.
This will generate a file "dosnic.ini" in the same directory as the executable with the vendor and PCI device information of the network card.
8. Open the nic.txt and verify the information returned in the nicinfo.ini is listed. If not, add the vendor and/or deviceid following the existing
format.
9. Save the nic.txt file and inject into \net directory of the DOSUNDI.1 boot image using the Winimage utility.
10. Make the same changes listed above to CoreServer\Program Files\LANDesk\Managementsuite\LANDesk\Files\BOOTMENU.1
NOTE: DRIVER WILL NOT BE USED IF MAPPING DOES NOT EXIST IN NIC.TXT
Note that the Intel Universal NDIS Driver (UNDI) is loaded. If a manufaturer specific driver was desired and the undi driver still
loaded, double check the steps above.
Note: Re-deploy PXE representatives for changes to take effect