/build/static/layout/Breadcrumb_cap_w.png
03/14/2019 522 views

I have to deploy 3 of the Autodesk viewers.  They require a reboot between each of the installs or the others will not install successfully.  Can I use Task Chains to install each viewer and reboot after?
?

0 Comments   [ + ] Show comments

Comments


All Answers

0

There is no option to add a reboot into a task chain as far as I can see, however, if you think a little laterally you can now add a reboot to a script. So think about using a script that can be created with a reboot and adding that to your task chain, that may just work.

Answered 03/14/2019 by: Hobbsy
Red Belt

0

I've created a script that reboots a machine, added it to a task chain and it works really well. You could even have it in there a few times and I think it would work. My KACE system is pretty new, but there was a sample of the script already in the KACE when I received it, I just tweaked it a bit then used it in my task chain.

Answered 03/14/2019 by: psagert
Senior White Belt

  • For me, the next step after the reboot doesn't appear to wait until the machine is back up; it just runs immediately, and upon not finding a machine out there (while it's rebooting), fails.

    There doesn't seem to be a way to tell the task chain to wait for the reboot to finish before moving on to the next task.

    (And what's with these narrow field boxes that don't show the whole name of the script?!)
    • I'm also seeing this issue with the reboots, It runs the notify/reboot script but then immediately runs the next task
      • I'm having the same problem.

        What I'm currently experimenting with and having success with is adding a scripted step that waits for 120 seconds by pinging 127.0.0.1. Adding this scripted step in there seems to give a bit of buffer that prevents the next task from executing before the system reboots.

        I basically just created a script called wait 120 seconds that have a batch script with the command below that's set to continue on error and wait for completion.
        I then placed this script before the task that requires the reboot to have finished. It's kind of an ugly workaround but has worked on my limited tests so far.

        ping 127.0.0.1 -n 120 >NUL 2>&1


        I'm guessing the inconsistent behavior I've seen on this has to do with the speed of hardware and number of processes/services that need to be stopped during system shutdown as more would provide more time for the KACE agent to move to the next task.

        My TaskChain workflow looks like this.
        - Scripted software install or removal, which includes the command shutdown.exe -r -f -t 15 at the end of the script.
        - Scripted wait for 120 seconds. (system will usually reboot while this script is running but it will report as complete nonetheless)
        - Scripted software install (Configured to run on next connection if offline).
      • Update: What I mentioned above sort of worked until I began running the task chains against slower hardware, I think I resolved the issue by adding another two minute wait, after the reboot. Systems were trying to run the scripts after they had rebooted and begun downloading the dependencies, the depency download was getting interrupted and failing. I need to look into it more but I think what is happening is that the KACE agent may be briefly losing connection after the user account was automatically logged in. I'm however still doing trials and fiddling.