I've tried to delay the next item with some suggestions in the forums (ping commands, opening default programs) but rebooting during a post install with windows 7 is hit or miss. I don't have a K1 appliance (i'm working on mgmt). I mean it is rather crazy that you can't reboot with the number of program installs and drivers going into the scripted image. Has anyone had any success?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Crazy question, but have you tried a reboot as a PostInstallation task?
Answered 04/14/2011 by: scottlutz
Orange Senior Belt

Please log in to comment
1
yes

reboot script:

/start wait Shutdown -r -f -t 60

then i do a dummy ping to delay the next post install task (i found it would start the next once before the reboot occured)

start /wait ping 127.0.0.1 -n 20
Answered 04/14/2011 by: ngbrown24
Blue Belt

Please log in to comment
1
also tried to reduce the reboot time from 1 or 10 seconds. same results. it works only part of the time
Answered 04/14/2011 by: ngbrown24
Blue Belt

Please log in to comment
1
With windows 7, you need to initiate a run once command after a reboot to guarantee that post install tasks kick off.
Answered 04/19/2011 by: ngbrown24
Blue Belt

Please log in to comment
1
Do you mean the remaining post install tasks in the KACE GUI will continue to run after reboot, or do you mean that you have to create a run once command for each post install task to be done after reboot?
Answered 04/20/2011 by: CraigEmmottOLSH
Senior Yellow Belt

Please log in to comment
1
Essentially I'm installing my applications, scripted events and file copies (including all the drivers I want to install) with kace post installs, then putting one run once command to point to a batch file that installs all the drivers after reboot.
Answered 04/21/2011 by: ngbrown24
Blue Belt

Please log in to comment
0
Thats what we have had to resort to as well. I hope there is an offical solution to this soon.
Answered 04/26/2011 by: CraigEmmottOLSH
Senior Yellow Belt

Please log in to comment
0
I'm a little confused as to how your doing this could you shed some light on it for me a little? Here is what my scripted install currently does postinstallation:
1. Basic Windows Applications Bundle (Adobe Reader, Flash, Shockwave, JRE, Firefox)
2. Change Workstation Name using WSNAME
3. Install Office 2010
4. Install K1000 agent
5. Reboot
6. Join Domain (Using a Powershell script)

I seem to get all the way to the reboot and sometimes it will join the other times it doesn't do I need to do something different?
Answered 05/24/2011 by: jrscribner
Purple Belt

Please log in to comment
0
jrscribner, I was having problems with the domain join as well and I discovered that it was because the powershell was running before the network was up and running, so it won't find the domain.

Put this in your powershell script before the domain join

Start-Sleep -s 20

(change the number to number of seconds you want) and it should join every time.
Answered 05/25/2011 by: dogfish182
Orange Belt

Please log in to comment
1
I have a script that we've been working on that should help with tasks not waiting properly or not surviving reboots. Please shoot me a PM if you'd like to try it out.
Answered 02/07/2012 by: warmep
Second Degree Green Belt

Please log in to comment
Answer this question or Comment on this question for clarity