KACE has created a “Preinstallation Task” called “Display Device Compatibility”. The purpose of this task is to verify whether all the drivers for the hardware to be deployed are in the K2000 appliance prior to running a scripted install. If there is a discrepancy, the list of hardware with out drivers is displayed and the scripted install is halted.
Not running this, at least the first time you attempt a scripted install, may cause the scripted install to appear to have worked. However, when you enter Windows for the first time, you may find that some of your hardware is not functioning. If key drivers are missing such as mass storage, the install could fail altogether.
Just because your computer booted to KBE does not mean the driver for the NIC will be installed in Windows after the scripted install in complete. The drivers may be in the K2000 appliance, but if they are not in the directory for the OS you are trying to deploy or the All directory, Display Device Compatibility will show them as not being available.
To repair this, add the drivers in question to the driver share under the operating system you are trying to deploy and then re cache the drivers. Once this is done, re run the scripted install. If the scripted install starts, you have successfully added the drivers. While you are troubleshooting, you do not need to leave KBE. Just re-run the script until you no longer see the compatibility window.
Finally, drivers added to the K2000 appliance should be in the format CAT, SYS, or INF. These are known as textmode drivers and are the only type supported by scrited installs. Some drivers such as those for the display, may not have low level drivers. However, a postinstallation task can be used to install these drivers using the MSI or EXE files supplied by the vendor.