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!
↧