Download and Install Google Chrome

What the Chrome Installer does

This Automox Worklet™ automates the download and installation of Google Chrome on macOS endpoints. The Worklet retrieves the latest universal binary installer directly from Google's distribution servers, which means you always deploy the current stable version without maintaining local installer packages.

The installation process handles the complete lifecycle: downloading the DMG file to a temporary location, mounting the disk image, copying the application bundle to the Applications folder, and cleaning up temporary files. The Worklet checks if Chrome already exists before attempting installation to avoid unnecessary downloads.

Why deploy Chrome through Automox

Standardizing browser deployment across your fleet reduces support overhead and provides a consistent user experience. When Chrome is missing from an endpoint, users may install unauthorized browsers or older versions with known vulnerabilities.

By deploying Chrome through Automox, you gain visibility into which endpoints have the browser installed and can combine this Worklet with Chrome update policies to maintain a secure browser environment. This approach also saves IT time by eliminating manual installation requests.

Google Chrome receives frequent security updates, and deploying the official installer directly from Google means new endpoints start with the latest version rather than an outdated cached installer.

How Chrome installation works

1. Evaluation phase: The Worklet immediately triggers remediation by exiting with code 1. This design allows the Worklet to reinstall Chrome if a user removes it, or you can schedule it to run once for initial deployment.

2. Remediation phase: The script checks if /Applications/Google Chrome.app exists. If Chrome is not present, it downloads the universal DMG from dl.google.com, mounts the disk image silently, copies the application bundle to /Applications, unmounts the volume, and removes the temporary DMG file. If Chrome already exists, the script skips installation.

Chrome installation requirements

• macOS Big Sur, Monterey, Ventura, or later

• Intel or Apple Silicon (M1/M2) processor

• Network access to dl.google.com

• Write access to /Applications directory

• Sufficient disk space for Chrome installation (approximately 500 MB)

Expected state after Chrome installation

After successful remediation, Google Chrome appears in the /Applications folder and is ready for users to launch. The application bundle includes the native binary for your processor architecture, so Chrome runs natively on both Intel and Apple Silicon Macs without Rosetta translation.

You can verify the installation by checking for the presence of /Applications/Google Chrome.app or by running the Worklet in evaluation-only mode. The Worklet logs indicate whether Chrome was freshly installed or already present on the endpoint.

How to validate download and install google chrome changes

1. Run this Worklet on a pilot macOS endpoint and review evaluation output for download and install google chrome.

2. Confirm Automox activity logs show successful completion and exit code 0.

3. Verify endpoint state using checks aligned to evaluation script logic, such as exit.

4. Validate remediation effects from script operations such as curl, yes, cp, then rerun evaluation for compliance.

For technical validation, compare endpoint state to the Worklet evaluation logic and remediation flow for download and install google chrome. This supports repeatable software lifecycle workflows, faster change control review, and auditable compliance evidence.

Useful script references for this Worklet include evaluation operations such as exit and remediation operations such as curl, yes, cp. Use these indicators to verify that endpoint changes match intended policy outcomes.