Under which header do you have the CTOS action?
My CTOS action appears as the last entry under "OS installation" - could you try that?
CTOS is supposed to be the last item listed in the Post-OS installation section.
Is it possible that being included in an embedded template is causing the issue? Try taking it out of the "Post-OS Common HII x64" template and adding it to the main template and see if that fixes it.
Thanks for your replies! I will test this as soon as I can. I'll be away for a few weeks but will test it when I get back and post results.
I Seriously doubt that the ctos being in a child template matters at all. Any template that is executed basically gets flattened anyway, so this is probably not the issue. The basic problem is one of timing. Sysprep is not completing before provisioning fires up again, so it steps on whatever is left to do by sysprep. The wait timer bit in the beginning of the system configuration phase is a common solution/workaround. It basically guarantees a redo of that step should it not reach its full time consumption. The hope is that sysprep gets completely done and/or reboots before the timer completes for this initial wait command. If a reboot happens before the timer finishes, then provisioning should repeat the wait command again after the system comes up again. At least this is what I've experienced in the past. If the timer runs out before sysprrep, the same problem will happen, in which case you simply increase the wait time even more, until you no longer experience the issue. That's why 5 minutes is a good amount, though it slows down the whole process. You could try a shorter amount, but it's a lot of effort to save some seconds figuring out what the shortest wait that works will be. Your real solution is to review your sysprep process and consider moving whatever post steps that sysprrep is doing (ie.. Anything being done with auto admin logon and running scripts, etc..) into provisioning steps if that's possible. By the time a windows system is performing an auto admin logon, provisioning is already running for sure, and in reality it's firing up very soon in the services starting phase of the OS. Otherwise, keep this wait time solution, but whatever you decide, good luck with your efforts on it!
I use the following:
"Create default partitions" in the Pre-OS installation section
"Deploy Image" in the OS installation section
"Run BCDBoot" in the Post-OS installation -
Execute File action - target path: bcdboot.exe
Command Line parameters: C:\Windows /s S:
"Bootable" in the Post-OS installation
Action Type: Make Bootable
Partition id: 1
Checkbox Bootable checked
"Inject Script" in the Post-OS installation - unattend.xml file
"HII" in the Post-OS installation
"Configure Target OS" in the Post-OS installation
"Install Provisioning LANDESK Agent" - very lightweight agent for software deployment tasks later in the System Configuration section
Hope that helps!
Hi, I just wanted to followup on this discussion. We were only seeing this on some models and for those, nothing has worked aside from adding the Wait time as the first action in the System Configuration pass.