• Extract drivers from the machine:

Export-WindowsDriver -Online -Destination c:\Drivers

• Zip these into an archive (such as Drivers.zip) and upload these into a file copy module.
• On your image, create an image profile and enable the file copy module you created.
• On your setupcomplete.cmd file you will need:

pnputil.exe /add-driver c:\drivers\*inf /subdirs /install

• You may need to recapture your image with this setting. Now all you do for new models is extract drivers, create a file copy module and a new image profile.

First of all, theopenem is great! We're happy to pay for a support plan.

• Active Computers page - is it possible to select all computers (or multiple at a time) to force a check in? Could be important if there's an important policy change that needs to be updated ASAP to all machines.
• File Copy Modules - is it possible to link a Google Drive file? Essentially have the file downloaded from Google Drive instead of storing it on the server? I was able to make a script module to download the file, but it would be far simpler to be able to paste in the drive ID for a file.
• Script Modules - is it possible to call a script from another (to say pass parameters)?
• Reports - Is is possible to save a report template for other users to use?

Just a few questions on the WINPE module and the scripts that theopenem uses.

When the imaging client is ran, it pulls scripts from theopenem that are "ImagingClient Powershell" types, but where at in this process are these scripts pulled? Can the "wie_builder\Optional\ExtraFiles\WinPE 10 x64" assist in this?

My goal is to integrate Microsoft's user state migration tools for TOEC deployments only, so that essentially a remote machine can be configured via policy, and redeployed with a new image and image profile.

Any suggestions?