How to use $OEM$ correctly.

[MaKaNu]

From what I understand, I can use the $OEM$ folder to provide drivers and stuff.

For Example, If I want to deploy for Dell systems (I do not advertise them here, don't buy this crap), I want to provide drivers at least for network, so I am able to maintain the system's remotely.

While WindowsPE works perfect on the systems, they're causing trouble later. So my idea is to provide the drivers while installing.

From the Section "Windows PE operation", I saw a few hints in the example using the $OEM$, but I don't get every point of the example, since we used "Generate a .cmd script using the form's other settings and also these options".

So would be a starting point to analyze the generated script (location in the xml?) and extend it with silent installations of the dell drivers?

[cschneegans]

The $OEM$ folder does not necessarily contain drivers. Instead, it contains files that Windows Setup (setup.exe) will simply copy to the target partition. When you use the Generate a .cmd script… setting, setup.exe is only used to run that .cmd script. Therefore, the .cmd script has to replicate the behavior, and this is what the

rem Copy $OEM$ folder if present
set "ROBOCOPY_ARGS=/E /XX /COPY:DAT /DCOPY:DAT /R:0"
if defined OEM_FOLDER (
    if exist "%OEM_FOLDER%\$$" robocopy.exe "%OEM_FOLDER%\$$" W:\Windows %ROBOCOPY_ARGS%
    if exist "%OEM_FOLDER%\$1" robocopy.exe "%OEM_FOLDER%\$1" W:\ %ROBOCOPY_ARGS%
    @for %%d in (C D E F G H I J K L M N O P Q R S T U V W Y Z) do @(
        if exist "%OEM_FOLDER%\%%d" robocopy.exe "%OEM_FOLDER%\%%d" %%d:\ %ROBOCOPY_ARGS%
    )
)

block is for.

To install drivers, you should look into the $WinPEDriver$ folder instead. Also see #288 for a related discussion. Again, the .cmd script has to replicate the behavior usually provided by setup.exe, and this is what the

rem Install drivers from $WinPEDriver$ folder
if defined PEDRIVERS_FOLDER (
    for /R %PEDRIVERS_FOLDER% %%f IN (*.inf) do drvload.exe "%%f"
)

…

if defined PEDRIVERS_FOLDER (
    dism.exe /Add-Driver /Image:W:\ /Driver:"%PEDRIVERS_FOLDER%" /Recurse
)

block is for. Note that the generated .cmd script calls both drvload.exe and dism.exe /Add-Driver on the same folder. The former call adds driver to the running PE session, and the latter one adds them to the target installation.