KACE Product Support

sarjent,

This depends on what you are deploying from the kbox and what operating system you are deploying.

If XP
If scripted install
Post Installation tasks run as runonceex, this is after logging in, but before the desktop is shown and before runonce.
If an image
Post Installation tasks run as runonce (putting a tick mark in sysprep integration will append your sysprep file under GUIRUNONCE so that a post_install.bat file calls each task.

If Windows 7
Post Installation task run under Firstlogon


So the only case where inserting a reboot will help is in an xp scripted install. Otherwise you will have to script the items to run under runonce.

I hope this helps, but if you need more clarification on something, please let me know.

Thank you,

Corey

I can't answer the first part of your question because I honestly don't know.

The post installation tasks will continue to run, as long as your "Number of Boots" parameter is set properly. It may take some time to fine tune how many boots you will need for the selected deployment. More information can be found under "Setting Boot Actions" in the Administrator Guide Release 3.1, page 116 for the document and 126 for PDF reader.

Let me know if this points you in the right direction.

Windows 7 scripted installation. So, I might have to set the number of boots to 2 in my XML file. During the first phase, call out my installers that work, make a reg change for run once, reboot, then autologin again and a final reboot.

sarjent,

Yes, this would be accurate, you can accomplish this by setting the autologon count in your unattend file, then making a script that puts an item in runonce (or whatever you need to do) and reboot. At that point the computer would autologin and finish the task. You'll want another reboot so that the finished state of the machine ends at the logon screen.

Corey