-
Title
Why does my sysprepped image not run its post-install tasks? -
Description
After deploying a sysprepped Windows image, the system does not appear to have executed any post-install tasks. -
Cause
The post-install tasks are either not starting at all (Scenario 1 or 2) or they are failing due to an issue with a post-install task (Scenario 3). -
Resolution
Scenario 1 (Windows XP)
There is an existing [GuiRunOnce] section in your sysprep.inf file. The K2000 adds this section itself to the sysprep.inf file to run the post-install tasks, but doesn't check to see if one already exists, therefore only one [GuiRunOnce] section will run.
Solution: Remove the [GuiRunOnce] section from your sysprep.inf file and include those commands as post-install tasks.
Scenario 2 (Windows 7/8/10)
There is an existing %systemdrive%\windows\setup\scripts\setupcomplete.cmd file included in your image. The K2000 creates this file and starts the post-installation process with it, an existing script could conflict with the process and has the potential to keep all of the post-install tasks from running.
Solution: Remove the setupcomplete.cmd file from your image and include those commands as post-install tasks.
Scenario 3 (any Windows version)
A post-install task is failing or rebooting the system and keeps the other tasks from completing.
Solution: Check your post-install task list and determine if any of the items completed. If not, start with the first task and make sure the command is correct and doesn't initiate a reboot. Include 'start /wait' in the command line (e.g. start /wait install.exe -s) if it is an executable task or include 'call' if you are using an uploaded BAT script (e.g. call install.bat). Reordering or removing the task altogether may help as well.
For more tips and tricks, see the presentation attached to this article on troubleshooting post-installation tasks.
-
Attachments