Jul 03 2020 10:18 AM
Hi,
i am trying to start a Windows Setup with a /postoobe x:\script.bat as parameter.
For example:
works:
Z:\setup.exe /AddBootMgrLast /noreboot /unattend:X:\autounattend.xml
works not:
Z:\setup.exe /AddBootMgrLast /noreboot /postoobe "x:\finish.bat" /unattend:X:\autounattend.xml
It does not work and says /postoobe is not allowed.
If i do "setup.exe /?" i see /postoobe among the variables it supports.
Was here something changed in the last years?
Thanks.
Thomas
Jul 03 2020 06:23 PM
@Thomas_Toka Probably the script must be named setupcomplete.cmd (or sppecify a folder path that contain it)
X: is not physical path, it's only used during WinPE stage
Jul 03 2020 11:37 PM
@abbodi1406i already tried nameing it setupcomplete.cmd.. did not work.. but i did not try to put it in a subfolder.. will try.
Jul 03 2020 11:47 PM
Sep 24 2020 08:40 PM - edited Sep 24 2020 08:43 PM
If you're starting the Setup from WinPE, that option isn't available:
See Applicability
If you're deploying an Image (vs running setup), you can slip in a SetupComplete.cmd File into the c:\Windows\Setup\Scripts folder, and the Setup Engine will run that for you. However, is you're kicking off the setup engine manually from WinPE.. you'd have to come up with something creative to trigger that file.
Sep 25 2020 12:08 AM
Thanks for the information.
Meanwhile i fixed this with some creative scripting with powershell to make my final "installation ready, reboot" webrequest to our deployment server.
Good to know that this is the preferred way inside winpe.