When does a Managed Install install??
I have a managed install for IE8 that i've tested and found the best way to install it with my managed install with a lot of trial and error. Kudo's to those that have posted on my prior posts! I have a smart label that the machines join after they check in to my k1000. After the managed install runs and installes ie8 they drop out of that group and are no longer prone to getting the managed install action.
So my question is, when the heck will the managed installs install themselves? I have 85 machines sitting with a "to be installed" action for my managed install for 3 days. 1 machine has installed it and that's because I manaually hit the "force inventory update" button on it. In terms of settings on my MI, I have it set to "execute anytime" and I have no snooze option for it. several machines have checked in more than once, but the install isn't happening on it's own.
why not?
Answers (5)
Reduce the check in time for inventory updates.
7 days. Yes, Long time. I've asked about shortening this. We went to this because we have over 10,000 pc's and I think we had issues with bandwith with them all checking in so often.
If, as i was suspecting, the answer is they will wait 7 days to do their inventory update and then they will also run the m.i., then i'm definatly pushing for reducing this.
Also, due to this, I looked at the default script, Force Check-In, and I duplicated it, and modified it for my group of machines, and applied it. It's schedule is set to Also run at next client check in, and allow run while logged off. But i'm guessing without a schedule of some sort those two checks don't do anything for me.
but I was hoping a scheduled script would force a check in more frequently
Comments:
-
Why not change that check in script to run every couple of hours? If it is running on next client check in that sort of defeats the purpose. Since the machines drop out of the label after IE8 is installed it shouldn't affect your bandwith all that much. - dugullett 11 years ago
-
Dugullett is right, Simply saying running at next checkin is not going to catch it after its done its install. - RandomITPro 11 years ago
Managed Installs install them selves on a pull basis. A machine needs to check-in then it will see "Oh , hey I need this now" and queue it up. Now depending on your execute times on that particular install, It will then wait for that moment in time.
Heres the anoying part, you dont know if it works UNTIL it checks in again. So for the whole thing to be over and done with it takes 2 checkins. I cringe at your 7 day wait.
There is a built in script for force checking in. Assign a label to it then assign those labels to your comps and execute script. Dont do too many at a time.
Comments:
-
Also another way you can do it is add to your script, execute the kagent after install. Why it doesn't do this automatically is beyond me but w/e. - RandomITPro 11 years ago
If certain systems are prioity you can do a force inventory update to kick it off.
by force inventory update, you mean to go to the individual machine and click that button. that works awesome, but i'm trying to get a few hundred machines updated as fast as possible without clicking on that individually. and in about 2 weeks, my pc count will reach around 25000 connected to kace, hince our long 7day inventory checkin. the powers that be are being cautious about bandwith.
Comments:
-
With a large check in interval I'm not sure how you could get them to deploy faster. Maybe with some labels or different organizations. I would check with Kace for the best way to handle this. - ckubaska 11 years ago