If someone is on the computer and presses install or ignores the prompt the install runs fine. If no one is logged in, after about 1/2 a day to 1 day the computer hits the 3 of 3 attempts and is marked as Failed.

I thought that if there was no one logged on the snooze would just time out and run. This does not appear to be the case. How do I get this to run with or without the user logged on?

Comments

Answers

0

Quoted from the Managed Install page help on the right hand side of the page:

Selecting Snooze will cause the client UI to be displayed to the user. Do not create a snoozeable package that is to be deployed at a time that the user will not be logged in. Snooze-able packages will not be executed if the Windows Desktop is not available.

That being said, it's something I would love for them to change. It doesn't make sense to have two different copies of a managed install, one with a prompt and one without, since a lot of times we won't know at the time of deployment if someone is logged in.

Yes, I believe it is, since the client UI is still involved. At least, I believe that's been my experience in the past. I've just stopped using pre-install/snooze on packages that MIGHT be pushed when a user isn't logged in and have had to resort to notifying the user via email/IM of any impending restarts, etc. I went ahead and posted this to the UserVoice as I could not find anyone else having suggested it. Feel free to vote it up: http://kace.uservoice.com/forums/82699-k1000/suggestions/5208288-bypass-snooze-if-no-one-is-logged-on-to-pc

Thanks. Maybe I could use the option to do it before logon after the machine boots. Can you tell me if the application installs download at some point "before" the next reboot. The reason I ask is because we have some remote user that do not have a file server where we could have a replication share and I don't want the computer to:

--boot up
--decide it needs a 500MB download
--Sit there while it downloads for 30 min
--Sit there while it installs for another 15 min
--Finally allow logon.

Is there a setting where the app downloads locally, sits there, then waits for the user to reboot?