Best practices on import host drivers

D

drdmn

New Member
Messages
6
Reaction score
0
Hello

I want to make an image for a bunch of All-In-One pc's we just received. They all have Windows 11 IoT LTSC pre-installed with all the drivers they need but we need to put our own image on it. How do I "grab" those drivers from it and build my image with it on my main workstation? Or do I need to use the machine itself to make my image? I'm not sure how to use the "Import host", "Import HW list", "Export HW list", etc... Or am I misinterpreting this?

We have a Business license of NTLite and I use a portable version of it.
 
Going to answer my own question I guess: on the All-In-One machine I do a "Import host" and then I just select all the drivers and use "Export driver(s)". Makes sense. Ah well, maybe I can help some people searching for it. ;)
 
The best practices for driver management will depends on your needs.

For a work environment, it's always best to collect a set of driver files/installers and extract those drivers into folders. This way, you know exactly where you found the source drivers and which versions are part of the image.

While you can import drivers from a live host, NTLite doesn't provide details on the specific driver instance and version. Also, your NTLite host machine could be an entirely different PC model than the target machines. So importing drivers isn't helpful.

For a personal environment, it's acceptable to import from the host but I would still want to collect the driver set from outside.

Sometimes you are supporting a legacy system, where you're can't find an official set of driver files and importing them is the only option.

Beware that some driver installers may include helper tools (ie. Realtek audio add-on's), and those don't get copied over since they're not part of the base driver and DLL set. In those cases, you may have to run their installer from Post-Setup to get all the extra files.
 
You must log in or register to reply here.
Back
Top