An organization I support just informed us that they have enabled automatic updates on Chrome and Firefox across the enterprise. Why would they have not had that enabled from the start?

Share This Discussion

2 Comments

  • wowneatlookatthat

    October 21, 2021

    One example would be to reduce support costs when new features are added. Controlling the version installed allows admins to test and make sure it works with any legacy software or sites users might be using. Prevents a flurry of “help chrome broke my <insert app here>” tickets. This is becoming less of a problem though.

    From a security perspective, you may not always want the latest and greatest as that can introduce new vulnerabilities. There’s been times where a chrome release included a new vulnerability and was immediately patched right after.

    Reply
  • pyker42

    October 21, 2021

    Historically, updates tend to break things, so a lot of admins went with the “if it ain’t broke don’t fix it” attitude. This is course makes it more likely something will break when updates are finally applied.

    It’s better now, but overcoming organizational inertia can be really challenging.

    Reply

Leave a Comment

Note: By filling this form and submitting your commen, you acknowledge, agree and comply with our terms of service. In addition you acknowledge that you are willingly sharing your email address with AiOWikis and you might receive notification emails from AiOWikis for comment notifications. AiOWiksi guarantees that your email address WILL NOT be used for advertisement or email marketting purposes.

This site uses Akismet to reduce spam. Learn how your comment data is processed.