Linux - Software - Install Google Chrome

What the Chrome Linux installer does

This Automox Worklet™ deploys Google Chrome to Linux endpoints by automating the distribution-specific installation process. The Worklet identifies your system's package manager by reading the OS-Release file, then downloads and installs the latest stable Chrome package directly from Google's official repository.

Supported Linux distributions include Ubuntu 18.04+, Debian 10+, openSUSE 15.2+, and Fedora 32+. The Worklet uses dnf or apt depending on your system, verifying compatibility across rpm-based and apt-based package managers.

Why deploy Chrome through Automox

Web browsers serve as a critical interface for accessing cloud services, SaaS applications, and internal IT tools. Outdated browser versions expose your organization to security vulnerabilities, since older Chrome releases lack the latest security patches and exploit mitigations.

By using this Worklet, you automate Chrome deployment rather than relying on users to install it manually. This maintains all endpoints have the same browser version, eliminating compatibility issues with web-based applications and reducing support tickets from users with missing or outdated installations.

Security vulnerabilities in Chrome are patched frequently. Using Automox to deploy Chrome maintains you can schedule regular update policies, keeping all Linux endpoints protected against emerging threats.

How Chrome installation works

1. Evaluation phase: Reads /etc/os-release to identify the Linux distribution and its package manager. Checks if google-chrome-stable is already installed using rpm -qa (for yum-based systems) or apt list --installed (for apt-based systems). If Chrome is detected, the Worklet exits with status 0, skipping remediation. If Chrome is not found, it schedules remediation.

2. Remediation phase: Downloads the appropriate Chrome package directly from https://dl.google.com/linux/direct/ (RPM for Fedora/openSUSE or DEB for Ubuntu/Debian). Installs the package using dnf localinstall (RPM-based) or dpkg (DEB-based). Runs a final verification check to confirm the google-chrome-stable package is installed and exits with status 0 on success.

Chrome deployment requirements

• 64-bit Linux systems only (Ubuntu 18.04 or later, Debian 10 or later, openSUSE 15.2 or later, or Fedora 32 or later)

• Root or sudo access required to install packages

• wget utility available for downloading packages from Google's repository

• Active internet connectivity to reach dl.google.com

• FixNow compatible for immediate single-endpoint deployment

Expected Chrome installation state

After remediation completes successfully, the endpoint will have the latest stable version of Google Chrome installed and ready to use. The google-chrome-stable package will be registered in your system's package manager (rpm database or dpkg status), verifying it integrates with standard package update workflows.

Users can launch Chrome from their application menu or command line (google-chrome). Subsequent patch policies will automatically keep Chrome updated to the latest stable version. If you run the Worklet again on an endpoint where Chrome is already installed, it will detect the existing installation and skip the remediation phase, preventing unnecessary re-downloads.