I created an MI package that allows the users to hit 'Snooze X hours' if they desire. During testing I hit Snooze 1 Hour and Snooze 2 Hours on two different clients. Neither one showed the Install windows after their snooze duration. The next time I seen the 'Install' window was only after the client had it's inventory checked with is a 4 hour frequency.

Has anyone else see this issue or know is this is an issue? We are on the latest server and client version of KACE.

thanks,
Dave
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
What action you have selected after snooz, Install Now or Later. I think Install Now should work.
Answered 11/02/2010 by: afzal
Fourth Degree Green Belt

Please log in to comment
0
Please don't take offense when I ask, why should that matter? From my understanding, if I set the snooze timeout to 30 minutes and set snooze timeout action to 'Install Now' then after 30 minutes it will force the install. If I set the snooze timeout to 30 minutes and set snooze timeout action to 'Install Later' it gives the user an option to delay the install or popup for X hours.

Am I correct in my thinking?

Thanks for your help,
Dave
Answered 11/03/2010 by: diverdaveman1
Purple Belt

Please log in to comment
0
If you select Snooze button with Install later then it will wait till the next inventory cycle.
Answered 11/04/2010 by: afzal
Fourth Degree Green Belt

Please log in to comment
0
I agree and that is what's happening. But... If I select Allow Snooze with install Later and it will only ask during the next inventory cycle, then why would my users have the option to pick how long to Snooze?

I'm sorry... I'm just aggravated that these things don't work as expected or as they appear. KACE has a great product - probably the best IMO. I just wish they would stream line what they already have before add new cooler features.

Thanks again,
Dave
Answered 11/12/2010 by: diverdaveman1
Purple Belt

Please log in to comment
0
Picture this scenario- someone has set their agents to check in every hour; in that case a snooze for 3 hours buy me time to finish what I'm doing, then at next check in the MI does it's work. That is the intended use of this option. If you chose something longer than your check-in cycle you'd see the result you expect I think; if you're wanting to accomplish installations at specific times Scripting may be another option. Personal note- Ideally I try not to use these options (Snooze, Pre/postinstall messages) at all if they can be avoided; much better to make it not impact the user when possible. If the users forget the IT department exists that means they're doing their real jobs and we're getting ours done well.
Answered 12/09/2010 by: cblake
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity

Share