SetupComplete.cmd: "Client non-Enterprise OS edition detected with OEM license; will not run user-provided scripts."

[bseklecki_ge]

Not really an NTLite question, but OOBE Question:

Apparently if one customizes a Win10Pro image, and the target hardware happens to have an embedded OEM key, then the OOBE system will disable SetupCompelted.cmd ?

But maybe there is some creative way to work-around this?

This is like a product engineering decision made over a decade ago .

From:

An OS deployment task sequence doesn't continue - Configuration Manager

Describes an issue in which a task sequence doesn't continue after Windows Setup or the in-place upgrade finishes if an OEM product key is used during Windows deployment.

learn.microsoft.com

(*) To be a fly on the wall at Microsoft when they lawyers and product engineers cooked up this convolution.

 

[garlin]

This restriction has been well known for a decade (least in OEM/VAR partner community). They're expected to use a different workflow to install add-on packages and software. MS requires them to do that, as part of the OEM agreement.

NTLite works around it by calling SetupComplete, from inside autounttend.xml (if you check OEM SetupComplete).

This isn't a real surprise to the OSD, SCCM, WSIM community running on Dell or HP gear.

 

[bseklecki_ge]

> NTLite works around it by calling SetupComplete, from inside autounttend.xml (if you check the OEM SetupComplete box

Oh I love you sending hugs and chocolates ; passe un bonne week-end!

 

[garlin]

OEM SetupComplete & Post-Setup (User Execution) have both removed the need for most RunOnce hacks, you see in old forum replies.
Unfortunately it's too much work to mark old threads as obsolete.

 

[APiUser]

is there a way to run the batch file or *.exe file after the user logs in?
SetupComplete.cmd is started when the SYSTEM is the user.
perhaps with Windows installed?
But where to?

 

[garlin]

Post-Setup (Machine) runs commands (from SetupComplete.cmd) under SYSTEM user -- right after OOBE.
Post-Setup (User) runs commands (from a RunOnce scheduled task) under the first logon user's identity.

Top half of Post-Setup -> Machine
Bottom half -> User

 

[APiUser]

to be added to the 7 oobeSystem section?
I don't understand what.
Unfortunately I am not very well informed..

 

[garlin]

We're talking about NTLite's own features. You're posting a picture of WSIM, which is a different app.
This is available for all free users.

 

[APiUser]

unfortunately none of them start at login, I need them afterwards, to install and configure other programs..
And I don't know powershell.. I never needed it. I told you I'm not a great ace... but, I'm trying. I wasn't born with it..

 

[garlin]

The lines are just examples of how to fill out the screen. I copied them from another thread.

Follow post #2 and check the OEM SetupComplete box under the Unattended menu bar to force run Post-Setup commands. This applies to Dell/HP/OEM systems that have Windows product keys in BIOS.

If you insist on using WSIM, add the same commands in the audit System and User passes if you've already created the primary user.

 

[junrey]

Heya guys just a quick question, Does the machine needs to be online for "OEM SetupComplete" work? It seems to be stuck when it's offline.

 

[garlin]

OEM SetupComplete runs regardless of the network status.

NTLite substitutes an unattended call to run SetupComplete, since the normal workflow skips over SetupComplete whenever an OEM license is located. OEM's have to run their post-setup actions using a different approved workflow.

One of your Post-Setup installers may have a network dependency.

Remove all Post-Setup commands, and replace with:
cmd /c echo "Hello world" > C:\log.txt

If your install is still hanging, there is another dependency which hasn't been addressed.