Recached the drivers, then created a new KBE boot environment and uploaded it using the SDA Media Manager (MM) or KBE Manipulator (KBEM). Attempting to boot a 7490 (or any other model) laptop to the newly created KBE boot environment, I get an error. Could not boot: no such file or directory (http://ipxe.org/2d0c613b)
This problem could also exist when building a KBE boot environment for any other model device. The SDA Media Manager or KBE Manipulator (KBEM) will build the boot environment without any errors and upload successfully to the SDA appliance as if there is no issue.
Navigate to . The newly built KBE boot environment file size is smaller than expected. For example, all other KBE boot environment previously built and working as expected show up as 500 MB, but the problematic new KBE boot environment file size only displays 500 KB.
PXE booting to the newly created KBE boot environment will fail.
Too many drivers are located under \\SDA IP address\drivers.
Confirm that the problem is not due to Antivirus software interferes with KBE build process (125878).
Check to see what files are located within the folders listed under the \drivers Samba share. From the \drivers Samba share, it is recommended to only place drivers under the following two subfolders (all non-KBE subfolders are legacy):
\kbe_windows_x64
\kbe_windows_x86
The \driver Samba share typically requires only the network driver, but on some circumstances a storage driver (to recognize a hard drive if it is not automatically detected) might be required addition. All other drivers (e.g. audio driver, video driver) for the hardware system or operating system(s) should be added to the \drivers_postinstall Samba share. Please review Drivers are not installing during deployment (126947), if non-Dell drivers are required to be installed during image deployment.
If there are many unnecessary drivers added under the \drivers share, it likely will cause creating a new KBE boot environment to choke and not create the proper boot environment file size. An example would be if the \drivers share contains 200 MB of drivers, then it should have no problems creating a proper KBE boot environment. If it contains large (e.g. 1.5 GB of drivers) amount of drivers, then it likely will run into problems creating new KBE boot environments.
Follow the System Imaging Best Practices for Windows (121734) and the links suggested above.
Tip: Try only adding and updating the KBE Driver Pack Boot Environments (111717) required for the OS provided by KACE support team. If the driver is confirmed not available within the existing KBE Driver Pack from KACE support team, then add only the required missing network drivers that is needed into to the proper \drivers share subfolders.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 이용 약관 개인정보 보호정책 Cookie Preference Center