Ntlite import unattend11/27/2023 ![]() The 2 biggest space hogs are winsxs and file repository so if i can get rid of them, uneeded kb's languages and fonts i can get a slimmed down os but with all the major components intact. Or, if its actually possible, keep the drivers outside of a wim and just have them on the install media. Alternatively, certain operations are available for automation via the command-line as well, more info on that. Also accessible is the Tools tab in the toolbar, more info below. This page contains an Image list on the left and a Preset list on the right. The full complete FileRepository can be kept on dvd/blu-ray drive or as an iso and any driver i need later on can be added by search or have disk. After starting the program, first page to open is the Start Image page. When you make a new ISO, autounattend will be included. When not using a preset, NTLite scans the ISO folder to recreate the previous unattend and. NTLite cant import existing autounattend files to the preset, but you can copy it to the ISO folder. NTLite doesnt auto-import it back into the preset (for technical reasons), but if its on the root of the ISO. I am thinking(hoping) that during Setup windows will search everywhere for availible drivers, not just in System32\DriverStore\ FileRepository so it will find the required drivers in C:\Windows\Setup\ Files and just add those to FileRepository.Ĭ:\Windows\Setup\ Files will be deleted by an NTLite generated setupcomplete.cmd or i can delete that folder later on manually. NTLite will copy anything not overwritten to the new autounattend. Copy back the autounattend.xml from wherever. Move all the driver files to x:\sources\$OEM$\$$\Setup\ Files. I dont want to make a certain hardware specific image, 1 image to do them all. For my hardware combinations i only need w10s built in drivers, i dont need to add any.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |