Re: auto-updater

The IT departement is not responsible of accepting or decline an update, the users are or at least one of them. After accepting the update then the autoupdater will get a command from the IT to update when possible and most likely just after the next login.
Do not bug the user to update, if s/he has selected do not bother me with this update then do not bother him/her again.
And give me the option to shut it down AKA do not check for updates it is not all users responsibility to keep up with the updates.

Regards
Yannis.



The "users" in most organizations don't get to choose whether they want an update. This isn't a commercial app. When we deploy fixes to our in house applications, the user *has* to install the updates or they will be in deep doo doo.
.

Relevant Pages

  • Re: Garfield 8/7/06
    ... :>> If such is the case, why therefore bother to follow Christ's command to ... :>> spread the Gospel to the whole world? ...
    (rec.arts.comics.strips)
  • Re: run `tor at startup
    ... ....the command given in -c runs as toruser. ... HTH, ... "Bother," said Pooh. ...
    (comp.os.linux.misc)
  • Re: List etiquette question
    ... > well now how can anyone read an HTML line in an e-mail.. ... > COMMAND LINE why bother using the link at all? ... posting a link is giving an address. ...
    (Fedora)
  • Re: Black background printing NOT wanted
    ... > because I have this little rule that tells me not to bother running code samples if I first have ... > controls etc) from their default names. ... Then you can tell us, for example, to "pop seven command buttons and a commonm ... > DoEvents ...
    (comp.lang.basic.visual.misc)