I have a powershell script that will move the drivers from one boot image to another. It is not good powershell, you have to use a SQL query and Excel to actually make the powershell commands, but I can give you what I have.
On Wed, Aug 10, 2016 at 9:58 AM, Adam Juelich <[email protected]> wrote: > One thing you will find with most new boot images, is that you won't have > to re-import a lot of the drivers for older models of machines. You would > probably have to test each model and see what you need. It is usually > recommended to just add what is needed, don't inundate it with every NIC > and Storage Driver from all your models from the get-go. > > Somebody else may have documentation on what is injected into that boot > image standard. > > On Wed, Aug 10, 2016 at 9:49 AM, Mawdsley R. <[email protected]> > wrote: > >> Afternoon All, >> >> >> >> With Windows 10 1607 released, I’m currently scoping out the work >> required to get us there, 1 job of which is the new ADK, which will entail >> new Boot Images. >> >> >> >> I’ve 30ish drivers in my main Boot Image, and other than searching for >> the exact name and version manually of each one, I can’t find an easy way >> just to identify all drivers being used in the Wim. >> >> >> >> In other words, what is the easiest way for me once I have a new boot >> image, to import the identical set of drivers into it that is in my current >> Wim? >> >> >> >> Thank you >> >> Rich Mawdsley >> >> >> >> > >
