Post-Setup order of operations

hobart_symms

New Member
No matter what I do, I cannot get Post-Setup tasks to complete in the order which they are set in NTLite. Is there a file or config I can edit somewhere to ensure these happen in order? It's ruining my day.
Version 2.3.7.8826
 
Machine - Execution tasks are run by SetupComplete.cmd.

By default, NTLite uses "call [command or script]" to run each command in parallel.
To force sequential order, use the Command "start /wait [command or script]".

User - Execution tasks are run as individual scheduled tasks after first logon. There is no way to force execution order, unless you combine all actions inside a single script.

If you know CMD scripting, it's just faster to edit sources\$OEM$\$$\Setup\Scripts\SetupComplete.cmd
 
OK, thanks for the heads up. The ability to change the order from within NTLite threw me off the trail. I assumed since you could change the order, it would honor the order.
 
&& can be used to force two sequential actions in the same line. This is useful when the commands are related to each other.

Code:
cmd /c cd \change\path\before\execution && app.exe
cmd /c 1st_app.exe && 2nd_app.exe
 
OK, thanks for the heads up. The ability to change the order from within NTLite threw me off the trail. I assumed since you could change the order, it would honor the order.
When OEM key is detected, oobe.cmd and setupcomplete.cmd are skipped.

Go to index forums, open Legacy forums and search for RunOnceEx and follow the guide.
You can make a reg file and integrate when needed.
 
Back
Top