@george1421 said in Assistance with unattend script:
@jemerson93 said in Assistance with unattend script:
windows could not finish configuring the system. to attempt to resume configuration, restart the computer
Yeah that one is a pain to solve. There are logs in c:\windows\panther that should explain what it is having issues with.
I can say from past experiences that
- Having the wrong product key in the unattend.xml causes problems. I’ve removed that stanza from my unattend.xml and activate windows post setup with a first run command.
- Having the unattend.xml in the wrong place or where windows setup can’t find it will cause a problem. ALWAYS, put the unattend.xml file in c:\windows\panther that is the first place that windows setup will look. If you notice in my previous link I also call out the exact location of the unattend.xml file when I run sysprep.
- Having 2 unattend.xml files will cause unexplained issues.
- Having a bad driver that causes the winsetup to spontaneously reboot causes an issue. I haven’t seen this much of a problem in Win10 over Win7.
- Having the fog client enabled when the system is sysprepped will cause a similar issue. The fog client (if used) should be installed in your golden image but configured as a disabled service, then in your setupcomplete.cmd file reenabled and started. This is to prevent the fog client from changing the system name and rebooting before winsetup and oobe have finished. ref: https://wiki.fogproject.org/wiki/index.php/FOG_Client#FOG_Client_with_Sysprep
I took some time to manually re-create my unattend.xml following your advice above and managed to fix all of the issues. Convientely, I also no longer need to have separate unattend scripts for Windows 7 and Windows 10 MBR and Windows 10 GPT.
The new script lacks all of the manual partitioning and only contains the amd64 edits (I didn’t think I needed the x86).
After a few days of testing, everything seems to be working perfect!
Thank you for the assistance, this is resolved.