Below is a brief description of the key files that make up the OS deployment process. There are many files not mentioned here that, while integral to OSD (and the DOS boot process in particular), are configured by LDMS and don't need to be tweaked unless you're doing something like building a boot image from scratch. That sort of thing has been documented well enough by Bart and Others . This list focuses on files that are either inherently unique to the LANDesk process or are dealt with uniquely by the LANDesk process. If you think there is something glaringly obvious that we haven't defined here, let us know.

bootmenu.1: DOS boot image that is loaded when you boot a client machine via PXE and select the LANDesk (R) Boot Menu option. This file is copied to the PXE representative when you deploy osdrep.msi. As such, changes you make to bootmenu.1 will have no effect until you re-deploy osdrep.msi (unless of course you modify the bootmenu.1 on the PXE rep directly, in which case it will have an immediate effect). This boot image, as well as dosundi.1, use a DOS UNDI (universal network driver) vs. a manufacturer-specific NIC driver.

dconnect: the LANDesk DOS CBA (common base agent). Dconnect is loaded during any imaging process and is used to execute script commands (remexec and the like) as well as communicate status messages to the LANDesk application server. When it loads it displays the MAC address of the NIC and the IP address the client has been assigned (whether statically or via DHCP). Dconnect uses the network settings contained in the wattcp.cfg file.

dosundi.1: DOS boot image that is loaded when you boot a client machine via PXE and select the Managed Boot option. This file is copied to the PXE representative when you deploy osdrep.msi. As such, changes you make to dosundi.1 will have no effect until you re-deploy osdrep.msi (unless of course you modify the dosundi.1 on the PXE rep directly in, which case it will have an immediate effect). This boot image, as well as bootmenu.1, use a DOS UNDI (universal network driver) vs. a manufacturer-specific NIC driver.

ldvboot.img: DOS boot image that is used when you execute a virtual boot against a client machine. This file is copied from the core server to the client machine using sdclient.  Three files are injected into the boot image before the client is rebooted: dosnic.ini, lmhosts and startnet.bat. One distinction between the vboot process and the PXE process is that manufacturer-specific drivers are used. The correct driver for the client is (hopefully) determined using PNP within Windows.

protocol.ini: defines several network settings, including your NIC driver, your network transport (i.e., TCP/IP) and standard stuff like IP address, gateway, etc. It supports both dynamic (DHCP) addressing and static addressing. The same default protocol.ini exists in all three default LANDesk boot images, however this file is modified during the boot process by the htget -i command that's called from startnet.bat. The settings in this file are used to bind the NIC. They are also used by the DOS TCP stack, including things like the net command. Other DOS networking applications, like trout.exe, sshdos.exe or (most importantly) dconnect.exe do not use it.

startnet.bat: located in the ldvboot.img DOS boot image. It is called by autoexec.bat and it predictably starts the various DOS networking components, such as loading NIC drivers, loading the TCP stack, defining network configuration, etc. From a LANDesk perspective it also sends an inventory mini-scan to the core server (htget -s) and loads the DOS common base agent, dconnect.

wattcp.cfg: defines several network settings like IP address, gateway, subnet mask, etc. While for other DOS networking applications this file may be very complex, the one LANDesk creates is very basic. You'll notice that this file is nowhere to be found in the default boot images. It is actually created on the fly when the htget -i command is called from startnet.bat (at the same time protocol.ini network settings are written). DOS networking applications like trout.exe, sshdos.exe all generally look to wattcp.cfg for network settings, as does dconnect.exe.