How to get Managed Installs to deploy in order?
I'm trying to get two pieces of software to deploy in a specific order.
Software 1 - A hotfix that requires a reboot. Set to deploy without a user logged in. Order set to 9.
Software 2 - The actual software I'm trying to install. Set to deploy any time. Order set to 10.
So, if you can read this graphic, it looks like this:
When I view the machine in inventory, it shows both of them as Waiting Managed Installs. Since I have the order set as "9" and "10", I would expect the "9" would have to deploy before it would do "10", and if "9" hasn't installed, then it would not move on to "10" because... well... That's the order. Except... It's not doing this.
"10" will install regardless if "9" has installed. Why is this? I need "9" to install first because it's a prereq. I thought about using a script instead of an MI, but I love how the MIs work... They are just easier to deal with long term.
Any ideas? Am I doing something wrong that's really simple? Thanks for any ideas...
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
rockhead44
8 years ago
Let's try this again. I typed a reply but it didn't post when I clicked Submit.....
As for the order, the Managed Installs deploy in order starting with number 1 and continuing in order until your highest number is reached. So, in your case, 9 would deploy before 10.
Does the hotfix not deploy if someone is logged in? Could that be a reason why it would not deploy, whereas your software deploys no matter?
Comments:
-
Correct, the hotfix does not deploy when someone is logged in. The reason for this is that it must reboot. I tried using the noreboot flags, and that prevents the reboot, but my hotfix isn't fully configured at that point, so it appears Windows actually needs the reboot.
I emailed support on this question earlier today. They replied and said
"... the priorities are not directly for MIs among them but for Kace to understand a priority level based on the among of taks targeting a specific device."
So basically, the order won't work if I have two different deploy times ("not logged in" and "anytime"). Kind of counter-intuitive because I would assume the order is the order... And lets say the first one fails, why would I want it to move on to the next one? (That's a rhetorical question... As I wouldn't want it to move on... But, it appears that it will.)
Support suggested I do a smart label, targeting the machines that already have the Hotfix. So I set this up, and have been testing this afternoon. It does work... It's just a little clunkier than I feel like it should be. - sundermannc@wdmcs.org 8 years ago-
The smart label idea was also in my original post. I left that out of my re-post as I tried to remember everything. I don't see any way around it. As for the order, that's just the order it tries to deploy. If #9 fails due to some restriction being met (in your case, someone being logged in) it ends, as it is supposed to do. Then it moves to the next applicable MI (#10, for you) and tries to run that - rockhead44 8 years ago
-
Yea... It just seems odd for my brain for it to work that way. I mean, I get it now, but it's just a different way to think.
Alas, the smart label seems to be the solution, so at least I have something. Many thanks for your time. - sundermannc@wdmcs.org 8 years ago
