Post-Setup script location

[Kombowz]

Good day everyone,

I hope your day is going well so far.

The Post-Setup section is great, but I was wondering where the scripts are stored after you render the image.
I would like to modify the file(s) manually as writing a script would be faster for myself and others that are use to the task in question.
The After-Login script seems to be in the OEM folder but I wasn't sure where the other is.

As always, I appreciate your time.

 

[tistou77]

The file is located (in the image directory) :

Before logon => \sources\$OEM$\$$\Setup\Files\Scripts
After logon => \sources\$OEM$\$$\Setup\FilesU\Scripts

 

[Kombowz]

I appreciate the reply,

But I only have a "SetupComplete.cmd" in \sources\$OEM$\$$\Setup\Scripts

This is the script for before logon, and even though the image does have after logon operations that work fine, I don't see the script file...

Any ideas would be great as I'm confused as to why this is....

 

[Kombowz]

So even after trying to remove and add new after login scripts I still don't see it there.
Are you sure it's not a task or something else that's created?

 

[tistou77]

I don't know, I've never done "After Logon"
Maybe in install.wim, in Windows\Setup directory or somewhere else

 

[garlin]

Post-Setup (Before logon) tasks are written to \sources\$OEM$\$$\Setup\Scripts\SetupComplete.cmd

- submitted executables and scripts are copied to Setup\Files​

This follows the normal Windows step of calling C:\Windows\Setup\Scripts\SetupComplete.cmd as a supported post-OOBE task. Later versions of Windows will skip SetupComplete.cmd (even if it exists), when it finds an OEM product key in the BIOS.

NTLite now has a postoobe task reg key which guarantees SetupComplete.cmd gets called on every Windows system.

(After logon) tasks are created as a set of sequentially numbered RunOnceEx tasks. As individual tasks, there is no single file to edit but a series of registry entries.

- submitted executables and scripts are copied to Setup\FilesU​

If you're a more experienced programmer, it's often faster to manually edit SetupComplete.cmd. But the drawback is modding the file outside of NTLite's control means your manual changes don't get correctly synced back into the preset. This isn't really a huge problem if you're mostly done with image mods, and only fixing (Before logon) tasks.

Because there is no (After logon) equivalent to SetupComplete.cmd, it's easier to call one master script and then put all your commands in there. Then you can edit the master script as many times as you like without disturbing Post-Setup configs again.