Hi all, i have tried to find info on this but come up blank so far. also on phone to kace support so if they give me a solution i will post. Basically i have a terrible installer that gives me no options other than install (i can install silently which is fortunate) anyway, if after you install the software you run the installer again in silent it auto uninstalls. I dont know if there is a way around this if there is let me know. Anyway the major issue is that i am installing this via a managed installations which means if the user reboots before they check in it will uninstall. i dont know how to get around this so any help would be very useful thank you!

ps got placed on hold by dell kace support guy 10 mins ago, still on hold, i hadnt even asked him my question!!! lol

Answer Summary:
0 Comments   [ - ] Hide Comments


Please log in to comment

Community Chosen Answer



ahhh i may be barking up the wrong tree.....forget the managed install....maybe a script would be best? i didnt realise that scripts have an update sched....here is my suggestion, does anybody know if its the right way to do things? i have only ever used scripts to run now:

1. create a smart label to identify all systems without the software installed using the "software title" and "does not contain" option

2. Create a script that is limited to deploy to the above created label

3. Set the schedule to "do not run on a schedule" and tick the "also run at machine boot-up"

4. add a new dependency which will be the exe for install

5. Under policy or job rules task 1 will have the following settings:

1. "verify a file exists" set this to the location of the exe when the software is installed

2. "on success" blank (so that when it is installed and the above file exists the script doesnt run)

3. "remediation"  will be "launch a program":

directory = download location of the dependancy

file = name of the exe

parameters = silent install parameters


does anybody have any suggestions on the above whether i am totally wrong?


Answered 01/08/2013 by: bushki
Yellow Belt

  • That sounds like it would work. I would stick with an online script. It will not give you the option of running at machine boot up, but you can schedule to run every 30 minutes or so (depending on how many machines). Offline scripts can eat up your Kbox if used for things like installs. Those should be used more for reg settings, and things that do not need to download items (dependencies) from the Kbox.

    You do not need to create a label since you are using the verify file exists. Although verifying the exe exists will work I've gotten in the habit of copying down a blank .txt file to use as a flag file. If the copy is set to the last part of your script then the next verify should see the flag file and not install again. Also make sure "allow run while logged off" is checked.
    • can i just confirm i am correct in the way i interpret the way the scripting schedule works? if i use offline script and do not get it to run on schedule but set it to run at bootup (with the also allow run while logged off option as you suggested) then should it download the script at the next script check and then run as per my scheduled options or am i totally wrong?

      i also basically shot myself in the foot and informed the company it will run at bootup so im sticking with offline scripts. it is only a small installer and we currently only have around 5 connections a min so shouldnt be too much of an issue....

      i also need a label as it will be deployed to laptops only so need to be able to identify them which smart labels seem to be perfect for.

      i agree with the user of a txt file but i only tend to use those for file syncs so i can tell which machines have received the files.
      • That should work. Again I don't really use the offline scripts so I can't speak much for them. I would try not to get too much in the habit of using them if they have dependencies. The Kbox uses what's called Konductor tasks. The easiest way to describe it this.

        Online scripts are managed by the Konductor tasks. They get the job based on the schedule, and then download the dependencies then run the tasks. Based on the task throughput that you set.

        Offline scripts are not managed by the Konductor tasks. If say 50 machines boot at the same time they'll all try and download the dependencies at the same time. This has been known to bring down some Kboxs.

        I have about 20,000 machines so I really have to be careful with this. With a two hour check in time I'm assuming you don't have too many, and should be ok.

        The label thing can be solved with a report. Again since we have so many machines I try and stay away from creating a label for everything since it can get messy.

        WHERE (S.DISPLAY_NAME not like '%Software Name%')
  • thanks dugullet..... i have tested it and the dependancy downloaded prior to reboot. I believe that offline tasks were specifcally designed so that the jobs would run regardless of network access (hence offline task) so shouldnt put any load on the kbox. the only load will come when the agent does the script update (ours is set to every hour) but the script installed fine and several reboots are not causing a reinstall (the particular system i am using has been added directly to the script deployment by name so will run every boot)

    i do like the idea of the report rather than the label though as you say it gets very messy! i will look into that, thanks for the assistance
Please log in to comment
Answer this question or Comment on this question for clarity




can you pass a parameter to the installer to avoid the reboot?

This can be a solution and can give the time to the K1000 to realize that the software is installed.



Answered 01/08/2013 by: StockTrader
Red Belt

  • thanks for the response. the installer doesnt prompt the restart it will be a user initiated thing. Unfortunately its a laptop only install and our users are pretty mobile so often turn their laptops off, which could be 30 mins after they log in so thus will have the install run twice.....

    i suppose another question would be how often does the agent check in....we have it set to every 2 hours but what is 2 hours? is it 2 hours after login? or startup? or is it every 2 hours after it was originally installed??
Please log in to comment