For some time now I've been provisioning windows 7 machines according to some of the landesk prescribed methods. What used to happen is that Sysprep would run and generalize my target machines then reboot before the provisioning agent would kick off. That is to say that sysprep would run, the system would reboot and would autologin with the local admin account before the provisioning agent would launch and continue with the final steps of the provisioning template.
Recently I've noticed that the provisioning agent is kicking off concurrent with sysprep and this is causing some problems. I have sysprep being called in the audit user pass of my unattend file. I've never known where the provisioning agent was set to launch because its never been part of my unattend file..it was part of the setupcomplete.cmd file.
Any thoughts on how to delay the provisioning agent so that it doesn't interfere with the sysprep cycle?