Result :
If you didn’t notice this and use a such image to install Windows, here is what happens.
NTLite deletes C:\Windows\Setup\Scripts\SetupComplete.cmd and replaces it with the commands above. As a result, after Windows installation, although C:\Windows\Panther\UnattendGC\Setupact.log reports setupcomplete.cmd has run, your script didn’t work as expected because it never ran as a batch.
Workaround:
Copy your $OEM$ folder in Windows source after NTlite processes the image but before your create an ISO.
Expectation:
Why NTLite just don’t leave all what is in $OEM$ folder alone? NTLite uses the very same setupcomplety.cmd for post-setup commands, and to allow for easier setupcomplete management.
However, what you experienced is not expected and should be fixed once confirmed.
Are you saying that if I put any setupcomplete.cmd in $OEM$ it will be deleted?
But that is simply not so, can you please attach your setupcomplete if you confirm it with the latest version?
And the preset used would be best, so I have full environment for testing.
Thanks, and sorry for the inconvenience. Interesting. Did you post a bug report about that ? If is still reproductible in last release, you should. yes i did post a bug about that via threads and private messages.
i think this is the reason: ntlite will use setupcomplete.cmd if you integrate updates just like it uses setupcomplete.cmd if you use post setup.
So when you put a setupcomplete.cmd file that you made manually to oem folder or directly iso's setup folder. and use postsetup or integratingupdates part. ntlite will try to edit or create setupcomplete which will not directly copy and paste your codes, and will not add its own codec to the end of the script, it will just edit and break your codes.
so thats why i never enter postsetup part after i place my own setupcomplete.cmd and never integrate updates.

I new have commands called REM

My SCHTASKS.EXE commands are gone

My XML file now have parameters

For a newbie like me, it seems like NTLite trashes the Post-Setup commands For this i can tell:
rd has been detected in that line and has been removed as rd command is being used for scripts folder removal, NTLite doesn't allow RD duplicated.
For some tasks i use oobe.cmd instead (not all tasks can run in oobe.cmd). Kasual We need a decent explanation of setupcomplete v oobe, what each one does, their limitations and which one is the best for certain tasks. The difference is that oobe.cmd is run at earlier stage than setupcomplete.cmd, when some services aren't running yet.
Other than that, both are simply batch files. Right, ok. Do you put an oobe.cmd in the same folder as setupcomplete.cmd? Yes, that's it!
Drop the oobe.cmd in the same 'scripts' folder and it will do the magic.
Don't know if adding time (timeout command) would wait 'til the services are running (never tested), once oobe.cmd has run, a second or a minute later (depending on your steamroller) setupcomplete.cmd runs. yes i did post a bug about that via threads and private messages.
i think this is the reason: ntlite will use setupcomplete.cmd if you integrate updates just like it uses setupcomplete.cmd if you use post setup.
So when you put a setupcomplete.cmd file that you made manually to oem folder or directly iso's setup folder. and use postsetup or integratingupdates part. ntlite will try to edit or create setupcomplete which will not directly copy and paste your codes, and will not add its own codec to the end of the script, it will just edit and break your codes.
so thats why i never enter postsetup part after i place my own setupcomplete.cmd and never integrate updates. Hi ege914, didn't we went over your changes and fixed it?
If not, please send me a PM pointing to our chat where it's unresolved to the end, or here if it's a public link. Thanks. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies. Accept Learn more…