Resume an already started script at reboot
Have a script start running, restart the computer, and then continue to run
Jay Harrell commented
This is definitely something needed
Keith V commented
this one really needs to get on someone list at Quest. remember to have all your co-works to vote on this one too!!
Joe Pyrczak commented
Needed this today
Seems very hard to believe that this is not already a feature.
i too would like this feature, i am in need of this feature today. but ultimately trying to figure out a work around.
Kent West commented
So we've been asking for this feature for at least six years....
Craig Andersen commented
This is a great idea, unfortunately, i am out of votes. If there was a script using the patching reboot mechanism that would be great, reboot if no one is logged in/count down. We have a huge environment with 110k nodes and we patch our systems on one day and reboot weekly on another day.
Evan Clay commented
While there are ways around this problem (writing a RunOnce reg key, creating a scheduled task for startup, doing a powershell workflow see this article https://technet.microsoft.com/en-us/library/jj574130(v=ws.11).aspx), this is something that should be an included functionality. Adding a "Restart the computer" option under the scripting tasks would be effective for the scripting module. Having a way to do this in a managed install would be nice, too, and Aaron is correct. There should be a better way to do a reboot in a K2000 task other than creating two or three tasks where one is all that should be needed.
This needs to be included soon. I have multi-part installations that could really use this feature.
Therese Reyes commented
I hope this gets bumped up and will be on next build. Whats the point of the Scripting if you cant do the reboot and resume? Most installation require reboot.
Gary Wekluk commented
I have other products (Symantec) that can run a script, reboot, and continue running. This is handy for installs/upgrades that require a reboot in the middle.
Kristof Vandervorst commented
I support this request.
This should be the same code logic for the K2000 post installation task which also has this same limitation.