/build/static/layout/Breadcrumb_cap_w.png

Reboots chained into Scripted Installation

[font="times new roman"]What I am trying to do seems rather simple in theory and I also noticed that another user (mlathrop) posted a similar question but there were no responses to the post.
ISSUE:
I am running a scripted installation of Windows 7 (using Kace K2000 deployment center) and up to this point it is working. I am attempting to deploy drivers to a Lenovo laptop and they are not only required to be installed in a particular order but a few of them need reboots before I can continue to the next driver.
Simply adding a batch file post installation task and using the shutdown command doesn't seem to get the job done because the behavior is that sometimes it will reboot and other times it will not.
What is the best way to be able to control between what applications to reboot between during post installation? I want to be able to place these reboots throughout my scripted installation without disrupting the flow of the installation.

Thanks in advance!

D

0 Comments   [ + ] Show comments

Answers (1)

Posted by: jkatkace 11 years ago
Purple Belt
0
Do the installers themselves have a reboot flag?

It may be that they can be chained (you'd have to check them individually), in which case you can just have the last one do the reboot.

Have you looked at a deployment where you've used the shutdown command to see why it's failing sometimes? Seems strange that it's so intermittent.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ