We're on Landesk 9.5 SP2 and have a weird issue during provisioning. What we're seeing on some models is that after running CTOS, Landesk doesn't wait for the first startup(after sysprep) to finish. It just keeps moving on to the next tasks as soon as the network drivers are installed.
Our images are sysprepped and captured as TBI files. Our provisioning tasks removes the disk partitions, deploys the image, run HII, then CTOS, and then supposed to run some more tasks after it starts up and auto logs into an administrator Windows account. But it's not waiting for the first startup to finish. I can see by refreshing the Landesk task that it moves onto the System Configuration section even before all the drivers have finished installing and whatever it is doing is interrupting that first startup, causing it to fail with the message "The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install Windows, click 'OK' to restart the computer. and then restart the installation."
Restarting doesn't help.
We've now added Wait 300 seconds as the first task in the System Configuration section as a workaround so Windows can finish and reboot. Has anyone else seen this happening in their environment? Our call to Landesk support ended up with them saying the same thing - just add a wait time. We didn't have this issue in Landesk 9.0. It always waited until after the first startup to finish and reboot before continuing any tasks,.