freMea
Member
Hi,
Steps to reproduce :
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?
Steps to reproduce :
1. Copy your $OEM$ folder in Windows source
2. Load your image with NTLite
3. Check Automate Post-Setup section.
NTLite parsed my setupcomplete.cmd and divided in multiple commands
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?