Set up Chrome for Work
Chrome for Work allows you to deploy and manage the Chrome browser for your users in a variety of ways. Chrome is supported on Linux, Mac, and Windows. For details, see Chrome system requirements.
- To install and manage Chrome on your corporate devices (Windows, Mac, and Linux), see the MSI installation instructions and Set up device-based policies below.
- To set Chrome policies for users on their personal computers and when they sign in to Chrome with their Google Apps account when they're away from work, see Set up user-based policies below.
- To set Chrome policies for your managed Chromebook and Chromebox users, see Manage Chrome devices.
- To set Chrome as the default browser on devices running Microsoft® Windows 10® and above, see Make Chrome default browser on Windows 10
The instructions are for how to install the Chrome for Work MSI in a Windows environment. To set up Chrome for an organization:
For Windows environments, download the Google Chrome Microsoft installer (MSI), which installs Chrome without an internet connection. For Mac and Linux environments, download the consumer version.Chrome installs at the system level, giving all users on the machine access to the same instance of Chrome.
Configure Chrome preferences and policies.
Preferences are user settings that configure an individual instance of Chrome, while policies are administrator settings that configure multiple Chrome instances and override any conflicting user preferences.
Pre-install Chrome extensions.
Extensions enhance the functionality of Chrome. (See Pre-install Chrome extensions.)
- Push Chrome to your users' computers.
In Windows environments, you can use Systems Management Server (SMS) or a similar set of tools to push out the MSI, or run the MSI on the target machines directly, and silently, with this command:
Msiexec /q /I GoogleChrome.msi
Test your installation.
On a target machine, launch Google Chrome and verify that your configurations appear.If the policies do not appear, run Microsoft's Group Policy Update Utility (gpupdate) to refresh policy settings.
After you install Chrome for Work on your users’ computers, there are three ways you can manage your users’ instance of Chrome on your corporate-managed devices:
- Group Policies to push Chrome to users, install applications, manage auto-updates, and enforce policies.
- Windows Registry to install apps and extensions on users’ instances of Chrome.
- Master Preferences to set up Chrome defaults, which users can later configure.
Deployment tip: Many Windows administrators install Chrome using the MSI, and manage their users’ Chrome instance through Windows Group Policies (see below). Quick start guides with technical details on how to configure management policies for Chrome on Windows, Mac, and Linux are on the Chrome developer site.
In addition to device-based policies, you can optionally provide users with the convenience of having their work tabs sync, and pre-install Chrome apps, extensions, and themes when they sign in to Chrome from a non-work computer. These cloud policies are set in the Admin console and include most of the same 100+ policies that are available via Group Policies. They apply to a user no matter which device they use, when they sign in to Chrome with their Google Apps account.
Have your users download Chrome on their personal computers.
Sign in to your Admin console.
Create the organizational units that you want to set policies for, if you haven’t already. For example, full-time employees and contractors, or teachers and students.
Go to Device management > Chrome management > User settings and set the policies you want to configure for your organization. Note that many admins choose to leave the default settings in Chrome, and only configure settings such as startup pages, new tab pages, apps, and extensions.
When you’re done, click Save, and these policies will be enforced when your users sign in to Chrome with their Google Apps accounts, no matter what computer they’re signing in with.
- Unlike corporate-managed devices, these settings will only apply to a user’s personal computer when the user signs in to Chrome with their Google Apps account. Common settings admins configure are startup pages, new tab pages, apps, extensions, and themes.
- Group Policy settings (device-based settings) take precedence if there’s a conflict between Group Policy settings and cloud-managed policies on corporate-managed devices.
For user policies to work on users' Windows, Mac, or Linux computer, Chrome Management needs to be turned on for those users in the Admin console. An exception is if you purchase Chrome device management licenses. In that case, policies apply to users who sign in to a managed Chrome device, whether or not Chrome Management is turned on. For details, see Turn Chrome Management on or off.
If your organization wants to take advantage of the Chrome browser, but your users still need to access older website and apps that require Internet Explorer, you can use the Chrome Legacy Browser Support extension to switch automatically between Chrome and another browser. When your users click links that require a legacy browser to open, the URL will automatically be opened in the legacy browser from Chrome.
Learn more how to set up Legacy Browser Support for Chrome and Internet Explorer.
For detailed instructions on how to deploy Chrome for your business, see the Chrome for Work Deployment Guide.