Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Notification prior to updating and other options

Dhruvin Talati

November 17, 2017 16:43

Hey guys

Is there a way to push a package to a collection and have it notify the user of the installation? That way they get a chance to save and close before it installs. It can be a timer, not an issue. The package in question is chrome. What if they are doing some kind of a demo or training and when the package pushes, it crashes their current open browser and starts installing with the new one.

Also, is there a way we can have it install on the next reboot?

Comments

2 comments

Stephen Valdinger
November 17, 2017 16:49

Google Chrome updates don't close an open browser. The update copies a new binary, and sets a flag that the next time chrome opens, it deletes the old binary, changes the new binary name to chrome.exe, and then just uses it.

We update Chrome all the time here, and users never notice. If you do want to give warning, you could use a Message Step if you have the appropriate license level to be able to have access to that step type.

1
Dhruvin Talati
November 17, 2017 16:53

Thats great! Clear a lot of things up for me. Thanks for the prompt response Stephen!

0