Closed andykimpe closed 5 months ago
I know about the $OEM$ mechanism, and I have used it myself quite extensively. However, using a single, self-contained autounattend.xml
file has significant advantages:
• You do not need to modify .iso oder .wim files. This is particularly important when installing virtual machines – just attach a pristine Windows image (such as Win11_23H2_English_x64v2.iso
) and the unattend.iso
generated by my service.
• You can easily choose between several answer files at runtime by using the setup.exe /unattend:…
switch.
• SetupComplete.cmd
does not offer a mechanism to run commands when a user logs on. My service does.
If you need to target Windows Vista, this service is obviously not for you.
except that it is possible to do the same thing with an unattended iso you can place the OEM folder not the windows iso but in the unattended iso the windows installer copy in C:\windows everything found in the OEM folders of each hard drive cd player and removable device present during the installation
there is too much in your form
there is no need for that much
the rest is configured in the OEM setup
whether in the form or in the output file
there is too much useless information
there is no need for so much in it in my case here is what generated 132 lines for me
the same thing in 118 line (ntlite.com generator)
there is no need for more
the rest is configured in
sources\$OEM$\$$\Setup\Scripts\SetupComplete.cmd
if have add other files here
sources\$OEM$\$$\Setup\Files
example add a registry key +firefox install + windows 10 pro activation by kms server
file sources\$OEM$\$$\Setup\Scripts\SetupComplete.cmd
by generating the files this way it also makes them compatible with old windows
because this configuration is identical in all other versions since windows vista
which means that generating this way is compatible from Windows vista to Windows 11
the only line that changes is the following (and the serial number must always be empty)