How do I configure the KBE to include the video drivers necessary to detect the native resolution of the monitor in a PXE boot scenario?
Based on what I've read about WinPE, in UEFI mode, the native resolution of a monitor will be detected automatically. Source I've been messing with SDA Media Manager (7.1.18.9) trying to get the native resolution of our monitors to be detected, but have been unsuccessful. However, if I copy and boot the KBE from a USB stick, the KBE loads in the native resolution of the monitor.
Here is what I've tried:
- Copying video drivers to the KBE driver folder on the SDA prior to creating KBE - This caused the creation of the KBE to fail.
- Rebuilt KBE multiple times ensuring that UEFI ISO is checked.
Here is a screenshot of my SDA Media Manager settings. Any ideas?
1 Comment
[ + ] Show comment
Answers (2)
Please log in to answer
Posted by:
cserrins
3 years ago
\\KACE-SDA\drivers\kbe_windows_x64\
folder, recache all drivers and Build a new KBE. But this will not work, because the Video drivers are too heavy.
I think there is a limit in iPXE, in regards the amount of MBs a payload can have.
Being honest, to me is not worth it at call, its just a cosmetic issue, Unless you're telling me the menu is not visible, or you're unable to operate with the KBE as it is right now - Channeler 4 years ago
The folder was about 2GB and the KBE would fail each time. Maybe I need to slim down the drivers.
And you're right, it is cosmetic, but it does cut off the footer.
Off topic, but do you know what use cases I'd need to add more scratch space and enable the ISO size restriction override? The manual isn't clear as to exactly why I'd need these features. - robertsj 4 years ago
https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/winpe-mount-and-customize
search for: "Temporary storage (scratch space)".
This is to reserve some space to be used by an application, it will not help here though... - Channeler 4 years ago