Post-Setup User - Execution queue

F

FrankH

New Member
Messages
3
Reaction score
0
Files, Installer, Commands in Post Setup - Machine Execution queue are copied to sources\$OEM$\$$\Setup\Files, and are added to sources\$OEM$\$$\Setup\Scripts\SetupComplete.cmd by NtLite. It works flawlessly.


Files, Installer, Commands in Post Setup - User Execution queue are copied to sources\$OEM$\$$\Setup\FilesU, but are not added to SetupComplete.cmd or any other batch/cmd file as for as I see. It does not work.

Any ideas? How should it work?
 
Normal way of running User Execution tasks is to schedule them as RunOnce commands in the registry.

Usually by creating a registry file or adding "reg add" commands inside SetupComplete.cmd. User Execution queue automates this process of creating reg entries. When NTLite edits an image, the registry appears under HKLM\NLTmp*\SOFTWARE\Microsoft\Window\CurrentVersion.

Actions are created under RunOnceEx, including a post-exit cleanup of the Setup folder. There will be no trace in any batch file, because everything is written inside the registry. Unless you open it with regedit, NTLite's changes won't be visible on-disk.
 
garlin said:
Normal way of running User Execution tasks is to schedule them as RunOnce commands in the registry.

Usually by creating a registry file or adding "reg add" commands inside SetupComplete.cmd. User Execution queue automates this process of creating reg entries. When NTLite edits an image, the registry appears under HKLM\NLTmp*\SOFTWARE\Microsoft\Window\CurrentVersion.

Actions are created under RunOnceEx, including a post-exit cleanup of the Setup folder. There will be no trace in any batch file, because everything is written inside the registry. Unless you open it with regedit, NTLite's changes won't be visible on-disk.
Click to expand...
Garlin, are these post-setup user commands always executed in the sequential order I configured in NTLite? As it would be in a .bat with the start /wait command, for example.

I ask this because I want to install some programs and then run a simple script with some settings for these programs. But for that I need these commands to always follow the order I defined in NTLite. In order to ensure that the settings are only applied when the programs are already installed.

thanks
 
User tasks are executed in sequential order, unless a program "backgrounds" itself to make Windows think it's done.
If you wanted to verify this works in order, run:

cmd /c echo "1" >> %USERPROFILE%\Documents\log.txt
cmd /c echo "2" >> %USERPROFILE%\Documents\log.txt
cmd /c echo "3" >> %USERPROFILE%\Documents\log.txt
cmd /c echo "4" >> %USERPROFILE%\Documents\log.txt
 
garlin said:
User tasks are executed in sequential order, unless a program "backgrounds" itself to make Windows think it's done.
If you wanted to verify this works in order, run:

cmd /c echo "1" >> %USERPROFILE%\Documents\log.txt
cmd /c echo "2" >> %USERPROFILE%\Documents\log.txt
cmd /c echo "3" >> %USERPROFILE%\Documents\log.txt
cmd /c echo "4" >> %USERPROFILE%\Documents\log.txt
Click to expand...
nice, i think it will work then, thank you very much.
 
Sorry for reviving this thread, but is the runonceex key added to the default user?
Meaning, will all users created on this device execute the installation procedure when they first log in?

If yes, is it possible to only make the first created user execute it when they first log in?
 
RunOnce or RunOnceEx is executed by whichever user is the first to logon, and then removed from the registry ("Once").
It's not inherited through the Default user's NTUSER.DAT, but a global setting.
 
garlin said:
RunOnce or RunOnceEx is executed by whichever user is the first to logon, and then removed from the registry ("Once").
It's not inherited through the Default user's NTUSER.DAT, but a global setting.
Click to expand...
Thanks for the quick reply, that's pretty much what I'm looking for.
 
You must log in or register to reply here.
Back
Top