Im using NTLITE Paid with Win11 22H2 and wanted to do a full unattended install but I did want to be prompted for the computer name.
When I got to the unattend tab, I pressed fill in and then changed computer name using the dropdown list box to %prompt. I did NOT manually type in anything as to avoid any typo related issues.
Setup seems to be installing just fine, but very late in the install it throws an error. Shift F10 and looking in the setupact.log file indicates that autounattend is invalid and that there is an issue with the shell-setup section of the specialize phase and then references an empty computer name.
Looking @ \windows\panther\... and \windows\setup\... the files and scripts directories are empty except for a 0 byte setupcomplete.cmd file.
That makes sense since I never see the GUI pop up to ask me to enter one.
Looking at ntlite.log I dont really see any entries related to this section
For debugging purposes, I changed %prompt% to %serial% again using the drop down dialog box. This time I see an entry in setupcomplete.cmd that deletes nlcomputername.vbs and I see an entry in autounattend.xml. But it still blows.
Thats better, but where the nlcomputername.vbs file?
I think NTLITE isnt adding the shell-setup area in autounattend under some wierd condition that I see to have set.
Is there a way to crank up logging level in ntlite?
How should I proceed?
I have enclosed an autounattend.xml file and ntlite.log and preset files for %prompt% and %serial% tests.
Any help would be appreciated.
When I got to the unattend tab, I pressed fill in and then changed computer name using the dropdown list box to %prompt. I did NOT manually type in anything as to avoid any typo related issues.
Setup seems to be installing just fine, but very late in the install it throws an error. Shift F10 and looking in the setupact.log file indicates that autounattend is invalid and that there is an issue with the shell-setup section of the specialize phase and then references an empty computer name.
Looking @ \windows\panther\... and \windows\setup\... the files and scripts directories are empty except for a 0 byte setupcomplete.cmd file.
That makes sense since I never see the GUI pop up to ask me to enter one.
Looking at ntlite.log I dont really see any entries related to this section
For debugging purposes, I changed %prompt% to %serial% again using the drop down dialog box. This time I see an entry in setupcomplete.cmd that deletes nlcomputername.vbs and I see an entry in autounattend.xml. But it still blows.
Thats better, but where the nlcomputername.vbs file?
I think NTLITE isnt adding the shell-setup area in autounattend under some wierd condition that I see to have set.
Is there a way to crank up logging level in ntlite?
How should I proceed?
I have enclosed an autounattend.xml file and ntlite.log and preset files for %prompt% and %serial% tests.
Any help would be appreciated.