Scripting Question

KACE K1000 scripting task resume after reboot

06/23/2015 3105 views

I am task to uninstall office 2010 and install office 2013. I created a script with task 1 to uninstall office 2010, I know it's good practice to reboot the computer after the uninstall. However after the reboot, task 2 does not continue. Does anyone know how to continue the task after a reboot?


0 Comments   [ + ] Show comments


All Answers

How about an offline kscript with the option "Also run once at next device checkin" enabled? You could run it overnight for example. It fires off, reboots, then runs again at checkin. Just a thought.
Answered 06/24/2015 by: jegolf
Red Belt

This content is currently hidden from public view.
Reason: Removed by member request For more information, visit our FAQ's.
This content is currently hidden from public view.
Reason: Removed by member request For more information, visit our FAQ's.
Really? I mean...REALLY? You're completely incapable of using a search engine? Try "K1000 resume after reboot"!!!
Answered 06/24/2015 by: VBScab
Red Belt

  • Really, for how long we have to tolerate your inappropriate comments!!
    • I guess that'll be for however long it is that people are too bone idle to perform basic research.
      • Hi VBScab,
        I know it can be frustrating at times, and instead of banging your head against the table you'd like to bang someone else's against a wall, but sometimes "Contenance bewahren" is the best thing. Your google links are way funnier....
  • "K1000 resume after reboot" is both specific (will "k1000 continue after reboot" get the same results?), and fairly useless, as this Google search doesn't come up with a great deal of solution. What is there tends to be old.

    As far as I can tell, there's still no good solution to this problem.

    It's perfectly reasonable for someone to post on this forum looking for possible solutions. It's not perfectly reasonable (nor mature) to denigrate someone for asking for help. Perhaps you were just having a bad day, VBScab.

    gplee, one way to accomplish this would be to break your task into two scripts. The first script would uninstall Office 2010, and then set some sort of condition, like setting some dummy registry key, that would trigger a SmartLabel to be applied to the computer, then reboot, and then your second script would install Office 2013 to the machines that have that new SmartLabel.

    That's ugly. But it's what Quest has left us with.

    Another possibility would be to write your script so that it takes parameters at the command line. The first half of your script would uninstall Office 2010, copy a batch file to the StartUp folder (varies, depending on version of Windows), and reboots. This batch file would then run your script again, this time from the hard drive rather than from the K1 (assuming it's still on the hard drive; if not, you'd have to program the first half of your script to preserve it on the hard drive in some way). When it runs this second time, your batch file would add a parameter that tells the script it's running for the second time. Your script then would see it's being run for the second time, and instead of uninstalling Office 2010, it would then install Office 2013.

    Again, ugly. But it's what Quest has left us with.

    There may be other methods as well. I suggest you go add your vote to https://kace.uservoice.com/forums/82699-sma-k1000/suggestions/2077521-resume-an-already-started-script-at-reboot so that maybe Quest will do something about this need after six+ years of people asking for it.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

View more:


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