chrome browser
deployment guide
set up and deploy chrome browser in your organization
enterprise & education
table of contents
about this guide
introduction
configure chrome browser options
best practices summary
legacy browser support
chrome browser cloud management
policies and templates
cloud policies master preferences privacy
chrome browser deployment
methodology
prepare your installation package
installation process
summary: best practices for installation and updates
configuration options
installation procedure for chrome browser
create a distribution point
configure chrome policies
change the configuration settings for the target group of users
install extensions automatically (optional) assign gpo to a set of users
assign a package
make chrome browser the default browser (optional) manage google updates (optional)
test your installation
example customer configurations
healthcare organization in a regulated environment
public organization with 15,000 users
global enterprise of more than 35,000 users global enterprise of more than 25,000 users commercial organization with 1,000 users
additional resources
this guide focuses on the two critical steps required for a successful chrome browser deployment:
● configuration—the considerations and decisions to build an installation package to deliver to each user.
● deployment—the timing and testing requirements for an installation package to deploy chrome
browser.
this guide focuses on the windows installer (msi) version of chrome browser for enterprise, which is available for microsoft windows 7 and later. it’s possible to install a managed version of chrome browser for linux-based systems and to configure device-based policies on a mac, but these configurations will not be covered in this guide.
this guide covers cloud-based policies and legacy browser support. for more in-depth documentation, refer to the chrome enterprise help center.
the recommendations in this guide on deploying chrome browser in an enterprise setting were gathered through our work with a variety of clients and environments in the field. we thank our customers and partners for sharing their experiences and insights.
what’s covered
instructions, recommendations, and critical considerations for deploying
chrome browser in an enterprise environment
primary audience
microsoft windows administrators
it environment
microsoft windows 7 and above
deployment phases
core it, early adopter
takeaways
best practices checklist for the critical considerations and decisions of a
chrome deployment
last updated: may, 2019.
location of the document: https://support.google.com/chrome/a/answer/3115278
third-party products: this document describes how google products work with the microsoft windows operating systems and the configurations that google recommends. google does not provide technical support for configuring third-party products. google accepts no responsibility for third-party products. please consult the product's web site for the latest configuration and support information. you may also contact google solutions providers for consulting services.
©2019 google llc all rights reserved. google and the google logo are registered trademarks of google llc. all other company and product names may be trademarks of the respective companies with which they are associated. [chrome-en-2.0]
chrome enterprise lets you deploy and manage chrome browser for your organization. it consists of chrome browser and a set of admin tools, resources, and installer packages which allow an it administrator to deploy and manage chrome browser in an enterprise environment. the admin tools allow
administrators to configure, package, and deploy chrome browser at the system level, and manage policies on an ongoing basis.
chrome browser offers the user many configuration options and settings to personalize and enhance their web browsing experience. when deploying chrome browser, the administrator can control chrome browser default settings and policies using the following methods:
● policies: can be used to enforce and maintain settings on client computers. for example, you can enable auto-updates, and set the update interval, the default search engine, and the default browser.
● preferences: can be used to set the default value for particular setting, while still allowing the user
flexibility to change the setting. for example, you can set the user’s default homepage to the company intranet, set the home button to display in their toolbar, or allow the bookmarks bar to display in the toolbar.
for information about how to deploy master preferences on users’ computers, see use master preferences
for chrome browser in the chrome enterprise help center.
configure chrome browser options
● use group policy objects (gpos) and cloud policy over preferences when possible. unlike policies, preferences do not apply to previous installations of chrome browser and are only applied to a single profile. policies also override any preferences settings for a feature. also note that the master_preference file can be changed and not enforced like group policies can.
remember that gpo is a machine policy. for example, gpo applies to any user that uses the computer, whereas cloud policy is tied to the user, and it only applies if the user is signed in to chrome browser on their computer.
● we strongly recommend enabling chrome browser auto-updates (this is the default policy setting)
to ensure that users have the latest features and security fixes.
legacy browser support
if your organization wants to take advantage of the chrome browser, but your users still need to access legacy websites and web apps that require microsoft internet explorer, you can use legacy browser support to easily switch between browsers. when users click a link in chrome browser that requires a legacy browser to open (such as a website with an embedded activex control), the url will automatically open in the legacy browser.
administrators can specify which urls to launch into a legacy browser and deploy this chrome policy for the organization. for information, see legacy browser support for windows.
chrome browser cloud management
you can use the google admin console to manage chrome browser on windows, mac, and linux devices running chrome browser version 73 or later.
with chrome browser cloud management, you can:
● enforce 100+ chrome policies for all users who open chrome browser on a managed device. users don't have to sign in or have google accounts to receive policies.
● block suspicious extensions across your organization and do other common it tasks.
● view reports on chrome browsers deployed across your organization, including each browser's current version, installed apps and extensions, and enforced policies.
for instructions on how to enroll devices and manage chrome browser, see set up chrome browser cloud
management.
chrome policies are applied differently depending on the client operating system.
after selecting the right template for the target environment, the administrator needs to define which
chrome policies will be enforced in the enterprise environment. the chromium.org site lists the supported
policies for chrome browser and can be applied via policy templates. for information about how to install and configure policy templates, see set chrome browser policies on managed pcs.
windows
use adm or admx templates to manage chrome browser using group policy. for windows vista and later, use admx templates. consult your windows support provider if you need help to decide which templates you should use in your organization.
adm and admx templates do not automatically update. you need to download and install the latest administrative templates.
there are three types of chrome policy templates released: stable, beta, and dev. with beta and dev templates, you get access to policies that are scheduled for future releases. this lets you test policies that are not yet available in the stable template. whichever template channel you use, the policies that you configure apply to all chrome browser releases—stable, beta, dev, and canary.
there are separate templates for chrome browser, google update, and lbs policies. you might need to use them all to manage your chrome browser deployment. the specific template being discussed in this guide will be called out as we discuss each one.
macos x
use a .plist (property list) file to set chrome policies. use your preferred systems management tool to push the file to client macs. for instructions on how to manage chrome browser on mac computers, see the
mac quick start guide.
linux
use a javascript object notation (json) configuration file to set chrome policies. use your preferred systems management tool to push the file to client pcs. for instructions on how to manage chrome browser on linux computers, see the linux quick start guide.
cloud policies
in addition to machine-based policies, you can optionally provide users with the convenience of having their open tabs, bookmarks, and theme synced with any pc where chrome browser is installed.
additionally, administrators can define pre-installation of chrome apps, extensions, and themes when users sign in to chrome browser.
these cloud policies are defined by administrators in the google admin console and include many of the policies that are available via the chrome policy template deployed by gpo. these policies apply to users on any pc where the user signs in to chrome browser with their google account.
if you’re a g suite customer or have chrome licenses, you can use cloud policies to manage chrome
browser for your users.
administrators with access to the admin console can synchronize users and their passwords with their
ldap server to manage user policy. more information can be found below:
● google cloud directory sync (gcds) –automatically add, modify, and delete users, groups, and non employee contacts to synchronize the data in your g suite domain with your ldap server.
● g suite password sync (gsps)–automatically keep your user’s google account password in sync
with their microsoft active directory passwords.
cloud policies are deployed and updated anytime the client has internet connectivity. unlike the typical gpo policy push scenario which requires the pc to have lan or vpn connectivity to the active directory controller, cloud policies can be pushed when the client pc has a connection to the public internet. for information about how to manage policies from the cloud see cloud-managed chrome browser.
note: machine policies (gpo) take precedence over cloud policies when there’s a conflict. for details, see
set chrome browser policies on managed pcs.
master preferences
administrators can use master preferences to deploy default preferences to chrome browser users on managed computers.
when users launch chrome for the first time, the user’s preference file is copied from the master_preferences file. we recommend you validate the master_preferences file with a json validator and formatter prior to deploying. after the master_preferences file has been verified, package it with the chrome installation for deployment.
for details, see use master preferences for chrome browser .
privacy
the google chrome privacy notice describes how we treat personal information when you use chrome browser and associated services such as safe browsing. you can review the latest version here, which outlines the data collected based on the feature being used.
note that in many cases, specific features can be disabled by the user or via policy to minimize the information sent to google. these include but are not limited to:
● chrome sync with syncdisabled
● omnibox search suggestions with searchsuggestenabled
● translate feature with translateenabled
● spellcheck feature with spellcheckserviceenabled
● autofill feature with autofillenabled
● anonymous usage statistics and crash reports to google with metricsreportingenabled
chrome browser deployment
enterprise software deployments require a phased roll-out to capture and resolve any issues before deploying the software company-wide. we recommend you deploy chrome browser in a structured approach with the following phases: development, partial deployment, and full deployment. this
multi-step approach allows you to evaluate the deployment at each stage and make necessary changes. below are some of the tasks that should be performed in each chrome browser deployment phase:
chrome browser uses a standard msi installer package and can be deployed via standard windows deployment tools. software deployment tools can bundle the msi, preferences, bookmarks, and extensions. some of the most common distribution methods are:
● active directory group policy management
● hp client automation
● microsoft system center configuration manager
use software delivery mechanisms to package, deliver, and maintain distributions of chrome browser.
chrome browser installations from an msi package are installed at the system level and are available to all users. as a result, any user-level installation of chrome browser, (i.e. a user’s own chrome browser installation), will be overridden. here’s where chrome browser is installed and linked for the two types of chrome browser installers:
● user level: “%user data%\google\chrome\application\”
● system level: “program files\google\chrome\application\”
note: chrome browser will not allow an older version to be installed over a newer version. any msi of chrome browser needs to be newer than the version already deployed (for example, chrome 68 cannot overwrite chrome 69).
test your installation process
some users might have downloaded and installed chrome browser prior to your enterprise installation, and there will be a previous “user level” installation. in this case, chrome browser will install for all users and leave the user data (preferences, cache, etc.) untouched, unless you choose to have your distribution software uninstall any previous installations. it will also attempt to repoint all of the default shortcuts to point to the new system level installation.
important: test your chrome browser installation process to make sure it works correctly on your organization’s windows image and method of software distribution.
application globally unique identifiers
when chrome browser is installed, it is entered into the windows registry with an application globally unique identifier (guid). there will also be a parent guid for the chrome binaries. any registry changes you wish to make should be made to the parent guid, especially as it relates to automatic updating.
in windows you can find these in the registry in these locations:
● chrome binaries
{hklm|hkcu}\software\google\update\clientstate{4dc8b4ca-1bda-483e-b5fa-d3c12e1
5b62d}
● chrome
{hklm|hkcu}\software\google\update\clientstate{8a69d345-d564-463c-aff1-a69d9e5
30f96}
important: the chrome binaries guid will become the default for all installations. however, previous settings for an individual guid will be maintained.
summary: best practices for installation and updates
chrome options
● leave auto-update enabled for chrome browser.
○ auto update will provide the latest security updates.
● use a phased approach to test and deploy chrome browser.
○ to ensure that there is no regression or loss of functionality for your users, have your it
group test the beta and dev channel of chrome browser.
■ the beta channel gives a 4-6 week feature complete preview of the next stable
chrome release.
■ the dev channel gives a 9-12 weeks preview of what’s coming next - keep in mind that the dev release may not be 100% stable.
installation
● customize the branding of the application with its shortcut text and icon through your software distribution mechanism.
logging
● increase logging for windows installation to troubleshoot problems.
● increase logging of your distribution software to log successful and failed installations.
● use the logs created by the chrome browser installation to troubleshoot errors.
chrome browser updates and bandwidth
● account for the increased network traffic for automatic updates to chrome browser.
● stagger your client installations so they don’t all update at once.
● delta updates between releases are typically only a few megabytes as opposed to a full update which is ~20 mb.
● there is currently no built-in facility for rate-limiting auto-updates or forcing them across several
days. multiple group policy objects (gpos) can be set for segregated organizational units to customize the autoupdatecheckperiodminutes parameter to a different value for each organization to ensure scattering of auto-update checks.
you can make microsoft windows-related changes to your deployment through the software management system you have chosen.
a common option might be changing the icon image, text, and placement of a chrome icon on the desktop. these options and others are done through your software management as they don’t specifically apply to the configuration of chrome browser itself.
there are two key points where logging data can be beneficial in any troubleshooting process. each point is dependent on the amount of information you would like regarding the distribution and subsequent updates of chrome browser.
software distribution
the software distribution packages mentioned above all have varying levels of logging capabilities. depending on your need for this information, it is important to configure it to a point where you can confirm the success or failure of the installation, and any status codes or errors returned by the msi. for details,
see command-line options.
chrome msi
the msi itself can also be configured to increase its logging verbosity to provide more clarity on the success or any failure. it’s important to understand why a particular installation of the msi failed.
separately, the logs created by the chrome browser installation are defaulted to the highest verbosity level and located here:
● %temp%\chrome_installer.log
important: %temp% should be the system temp directory and not the user-level system variable.
chrome browser updates
there are two important aspects to updating chrome browser: google update (based on omaha ) and
network usage.
we highly recommended you allow chrome browser to auto-update. for two primary reasons:
access to the latest security patches and bug fixes
support is only provided on the latest release of chrome browser
for more information on auto-updates, see manage chrome updates (windows).
track chrome updates
follow the chrome release blog to stay up-to-date on the latest changes to chrome browser.
google update
chrome uses an update engine called google update. while you can configure the update frequency, it’s important to understand what logging options are available when troubleshooting updates to chrome browser.
if you encounter issues updating chrome browser, do the following:
enable verbose logging in google update
invoke ‘googleupdate.exe /update’
a. e.g., on windows 7 it is located at “program files > google > update”
b. additional switches to googleupdate.exe are located here
recover the update log
a. e.g., on windows 7 it is located at “program data > google > update > log” there will also be a folder for each version installed here:
● c:\program files (x86)\google\chrome\application
google update policies
note that there’s a separate set of policies (and templates) for google update outside of chrome browser. for more information on managing updates to chrome browser, see manage chrome updates (windows).
network bandwidth
be mindful of network bandwidth requirements for updating chrome browser. you can expect a new chrome release every six weeks. caching can be enabled via policy if your network infrastructure supports caching of update files.
the initial chrome browser installation is approximately 50 mb. subsequent updates from one version to the next are approximately 10–15 mb. patch updates are typically 3–5 mb. updates from a major version to a later non-consecutive major version usually require a new complete installation.
installation procedure for chrome browser
this procedure covers the general installation of chrome browser for enterprise and updating group policies in a windows environment with domain-joined computers. screenshots and detailed setup steps are for windows server 2012 r2 standard and are for illustration purposes only.
you can download the standalone chrome msi or the chrome enterprise bundle. the bundle contains
chrome msi and administrative policy templates. for more information, see download chrome enterprise
bundle .
the scenario assumes two machines: (server) and (client), both on the chromeforwork.com active
directory domain.
create a distribution point
to publish or assign a computer program, you must create a distribution point on the publishing server:
log on to the server computer as administrator.
download the latest chrome browser msi package from
https://cloud.google.com/chrome-enterprise/browser/download/
create a shared network folder where you will put the microsoft windows installer package (.msi file) that you want to distribute.
note: this share must be accessible by your client machine. the client machine will request the
file from this location. verify the share is working correctly.
set permissions on the share to allow access to the distribution package.
note: the instructions are for manually adding a gpo template if you are not using centralized gpo
storage. if you are using centralized gpo storage, please unpack and save adm/admx policy templates for chrome browser to where your local administrative gpo templates are stored (e.g. c:\windows\policydefinitions). if you do so, you can skip step 5 below.
to add chrome policies to the deployment:
download the latest adm/admx policy templates for chrome browser from
https://dl.google.com/dl/edgedl/chrome/policy/policy_templates.zip.
load the group policy management tool.
go to server manager > tools > group policy management.
navigate to your domain to create a gpo object.
a. find group policy management > forest:chromeforwork.com > domains >
chromeforwork.com.
b. right-click chromeforwork.com and select create a gpo in this domain…
c. create a new gpo policy called chrome browser for work.
.. chrome enterprise
navigate to the ewly created gpo object
chromeforwork.com > chrome browser for work.
b. right-click chrome browser for work and select edit to load the group policy
ma agement editor
e group policy management
file action view window help
2 x
group po.licy managemen chrome browser for work
.d forest: omef orwork.com scope i details isetti i delegalion i
.d g domains
a om mefeof orworkιωk.
| chrome browser for w
lirb
dis links in this localion ichromefopo\'ork .com
default domain p olicy edit." ins and ous are linked to this gpo
test default enforced
1> gj domain controllers
e rced
1> [! group policy 0ts
1> [ wmi filters
fj} group policy modeling
enabled no
save rep 0 rt".
'
delete can only apply to the following groups u
group p olicy results a
rename
rεfresh (chromeforwork\domain compute
help
d d remove
1 1 propertie
wnirit
this gpo is linked to the following w mi mer
open the gpo editor
chrome browser deployment guide i may 2019 16
add the chrome adm/admx policy template for chrome browser to the gpo object in group
policy management editor.
note: this step can be skipped if you are using centralized gpo storage and have already saved
chrome adm/admx policy templates to centralized storage, as described in step 1 above. a. find computer configuration > policies > administrative templates...
b. right-click administrative templates, and select add/remove templates.
c. add the chrome.adm template via the dialog.
d. once completed, a google / chrome folder will appear under administrative templates if it's not there already.
enforce the gpo object.
chromeforwork.com > chrome browser for work.
b. right-click chrome browser for work and select enforced.
there are many policies you may want to control. for the purposes of this guide, we will walk through the steps of setting up homepage and disabling anonymous usage metric collection. these are two policies administrators commonly set up. a full list of supported policies is at
http://www.chromium.org/administrators/policy-list-3.
navigate to the newly created gpo object in the chrome management policy editor. a. find group policy management > forest:chromeforwork.com > domains >
b. update the policies defined in the chrome template as needed:
set the home page.
this is the url that users see when they first open the browser or click the “home” button.
a. find the home page folder under google > google chrome and change the two policies:
■ enable a new homepage url and provide a url.
■ make sure use new tab page as homepage is enabled.
b. find the show home button on toolbar policy under google > google chrome:
■ enable the policy.
disable anonymous usage statistics and crash information.
administrators can turn off sending any crash information or anonymous statistics to google.
a. find the enable reporting of usage and crash-related data policy under google > google
chrome:
■ disable the policy
note: in both examples above, you can apply these policies at the device or user level by changing the policy under computer configuration or user configuration.
install extensions automatically (optional)
another policy to try is to force install an extension automatically on chrome. let’s try setting up
keepawake via the extensioninstallforcelist policy in the extension set of policies.
the id for the chrome web store version is: bijihlabcfdnabacffofojgmehjdielb
the auto-update link needed is: http://clients2.google.com/service/update2/crx
bijihlabcfdnabacffofojgmehjdielb ;http://clients2.google.com/service/update2/crx
for privately hosted apps (i.e., not in the chrome web store), use a string such as: pckdojakecnhhplcgfflhndiffaohfah;https://sites.google.com/site/pushcrx/privatew ebstore/extension_info.xml
… where the url is specified to the internal app’s update.xml rather than the public-facing clients2.google.com url.
the policies can then be applied to the target users and/or machines. depending on the network’s configuration, this may require time for the policy to propagate. policies may be propagated manually by running gpupdate on the client workstation.
now let’s define which devices and users will be managed by the gpo policies we defined.
navigate to the chrome browser for work gpo object in the chrome policy management tool
a. find group policy management > forest:chromeforwork.com > domains >
chromeforwork.com > chrome browser for work and select it.
assign the gpo object to all devices in the domain.
a. in the security filtering pane, click add.
b. in the select user, computer, or group window, type the name of the object you want to add, click check names (to verify the name you entered), and then click ok.
c. you can type domain computers to add all workstations and servers joined to this domain
(as shown in the example below) or you can specify a different group of computers.
to install chrome browser on computers or users that belong to the domain:
navigate to the newly created gpo object in the chrome management policy editor.
under computer configuration, expand software settings.
right-click software installation, point to new, and then click package.
in the open dialog box, type the full universal naming convention (unc) path of the shared installer package that you want. for example,
\server\packages\googlechromestandaloneenterprise.msi.
a. important: if you use the browse button to access the location, make sure that you use the unc path to the shared installer package. remember that the client machine will look for the file at this specified location.
click open.
click assigned, and then click ok. the package is listed in the right pane of the group policy window.
close the group policy snap-in, click ok, and then quit the active directory users and computers
snap-in.
note: at this point, you have created a policy to deploy and install chrome on the endpoint and are ready to test the installation.
make chrome browser the default browser (optional)
you can choose to set chrome browser as the default browser. please take a look at the following instructions for making chrome browser the default browser for different versions of windows:
● windows 8, 10 - detailed instructions can be found here.
○ create a default application association xml file.
○ create a gpo policy (separate of chrome browser for work policy).
○ set a default associations configuration file.
● previous versions of windows
○ enable the “defaultbrowsersettingenabled” policy.
force users to sign in to chrome browser (optional)
you can force users to sign in to their chrome profiles before they use chrome browser on a managed computer. this ensures that the cloud policies that you set in the google admin console are applied on users’ computers. you can force everyone in your organization to sign in or just specific users. you can control who can save and synchronize chrome browser settings and data to their managed google account.
for details, see force users to sign in to chrome browser.
manage google updates (optional)
you can manage how chrome browser handles auto updates with google update. there are two policies that control google update’s general behavior.
● auto-update check period override—use this policy to set the period of auto update checks.
● downloadpreference—when enabled this policy can be used to cache updates to reduce external network bandwidth. use of this policy will result in the server responding with a payload that could be cached by downstream proxies or similar types of content caching solutions. this is a best effort policy and should be verified and tested.
for more details on these two policies, see install and update google applications.
download the latest adm/admx policy templates for google update from
http://dl.google.com/update2/enterprise/googleupdate.adm or
http://dl.google.com/update2/enterprise/googleupdateadmx.zip
load the group policy management tool:
a. server manager > tools > group policy management
navigate to your domain to create a gpo object:
c. create a new gpo policy called google update for work.
navigate to the newly created gpo object:
chromeforwork.com > google update for work.
b. right-click google update for work and select edit to load the group policy management
editor.
add the adm/admx policy template for google update to the gpo object in group policy
management editor:
a. find computer configuration > policies > administrative templates...
b. right-click administrative templates, and select add/remove templates. c. add the googleupdate.adm template via the dialog.
d. once complete, a google / google update folder will appear under administrative
templates if it's not there already.
enforce the gpo object:
b. right-click google update for work and select enforce.
assign the google update gpo to the same set of users as the chrome browser gpo:
a. navigate to the google update for work gpo object in the chrome policy management tool.
i. find group policy management > forest:chromeforwork.com > domains >
chromeforwork.com > google update for work and select it. b. assign the gpo object to all devices in the domain.
i. in the security filtering pane, click add.
ii. in the select user, computer, or group window, type the name of the object you want to add, click check names (to verify the name you entered), and click ok.
iii. you can type domain computers to add all workstations and servers joined to this domain (as in the example below) or you can specify a different group of computers.
test if chrome browser is automatically installed on the target machine:
start the assigned client machine.
when the client computer restarts, the managed software package is automatically installed.
if it does not install, open the command prompt and run the following command:
gpupdate /force
restart the computer.
on client machine, launch chrome browser. the settings you applied in step 3 should be noticeable on the test machine. congratulations!
to further verify the policies being applied to chrome browser and the user signed-in, go to the
address: chrome://policy to see all policies being applied.
if the policies have not propagated to the test machine / user, you may be able to run “gpupdate” to refresh policy settings.
on the client machine, use regedit to view the registry settings:
● the client workstation settings are held at
hkey_local_machine\software\policies\google\chrome
example customer configurations
healthcare organization in a regulated1 environment
chrome browser configuration
the following were set through gpo policies unless otherwise noted:
regulation focused
● disabled the sending of crash information and anonymous usage statistics to google
● disabled autofill
● disabled translate
● disable chrome sync
● disable searchsuggest
● blocked installation of data saver extension
general configuration
● configure lbs on machines, due to a few legacy web applications, to launch ie when needed to based on a known list of incompatible apps
● show home button on the toolbar
● set the homepage to internal intranet portal
● new tab defaults to the homepage
software management configuration
● pushed package via existing software distribution mechanism for windows
● it maintained a set of test machines on beta channel to ensure all core web applications used by the business function correctly before the next stable release
● turned on auto update with google update but have a policy template ready (and tested) to stop
updates if an issue occurs
deployment decisions
● deployed the package on initial pilot machines without any pii information
● adjusted group policies based on testing and feedback from users while reviewing any policy changes for impact to hipaa compliance
● partial deployment to early adopter machines to test deployment with revised policies, including
machines collecting pii information
● deployed to the entire user base after three months of testing by early adopters, location by location over the next 6 months
this example configuration is for informational purposes only. google does not intend the information or recommendations in this guide to constitute legal advice. each customer should independently evaluate its own particular use of chrome browser with enforced policies as appropriate to support its legal compliance obligations.
● disabled extensions and the default browser check
● internet explorer favorites and history were not imported
● changed the default search engine to google
● altered the group policy object (gpo) to allow chrome browser to self-update on a scheduled basis once the latest version was released and internally tested and approved
● changed the registry to use chrome browser for all mailto: links in any browser so mail links users
clicked on will load in gmail
● created a desktop shortcut pointing to “email.domain.com” with custom text
● created shortcuts to additional services in the windows start bar: calendar, contacts, documents, groups, mail, sites, and video
background: during the deployment process, a new version of chrome browser was released.
● performed two partial deployments with previous version of chrome browser
○ first to approximately 8% of their client machines and then incorporated feedback
○ second to 25% of their client machines
● performed a full deployment of the current version of chrome browser over the course of two weeks prior to their g suite go-live
● allowed the client machines on the previous version of chrome browser upgrade to the latest
version by enabling the auto-update gpo
● once all machines were on the latest version of chrome browser, the gpo to disable auto-updates was enabled
● used a master_preferences file to disable the default browser check
● changed the registry to allow chrome browser to self-update at a 14 day interval
● with their distribution software they created a shortcut on the desktop to open the url “email.domain.com” with chrome browser
● deployed the package on a few initial pilot machines and all their base images
● made changes to the package based on feedback from the testing deployment
● partial deployment to 400 of their client machines to test the deployment of the package
● full deployment to the entire user base over a 48 hour period
global enterprise of more than 25,000 users
● due to legacy web application requirements, customer chose to disable default browser check via master preference file
● configured to update once a week
● enabled and set the default search provider to google
● set the homepage to www.google.com
● disable the password manager
● three tabs opened on the browser launch to (mail, sites, help site)
● configure auto-update to check once per week
● push package via software distribution or batch file along with google talk plugin
● package distribution handled through landesk via an autoit script
● disabled placing an icon on the desktop via software distribution
● development of the package on 20 initial beta users
● made changes to the distribution script based on feedback from the pilot group. customer decided to use distribution script rather than alter the package (landesk)
● current iterations remove previous chrome browser packages as a safeguard
● the chrome browser package was pushed to a pilot of 200 users to ratify installation and settings
● further deployment was based on the g suite rollout schedule. general practice was to push
chrome browser to users two weeks before they were migrated to gmail
commercial organization with 1,000 users
the following were set through policies unless otherwise noted
● used a master_preferences file to set default homepage to company sites page to help users know where to start
● use vbscript to set default mail handler to chrome browser so when users click on mail links in an
application or browser it opens gmail
● during testing an hourly check-in for updates was configured, after testing a 7 day interval was chosen
● created a test organizational unit and added a few pilot machines
● adjust group policies based on testing and feedback
● full deployment to the entire user base before the g suite go-live
additional resources
google chrome enterprise help center
a collection of help articles covering deployment and frequently asked questions.
download chrome enterprise bundle
information about the single package that contains all the tools and components you need to deploy
chrome in your enterprise.
chrome enterprise release notes
details about improvements and other changes in stable chrome browser releases.
legacy browser support
learn how to switch between chrome and legacy sites that require internet explorer.
chrome browser cloud management
information about how to securely manage chrome browser from the admin console.
managing extensions in your enterprise
best practices for managing chrome browser extensions in your organization.
chromium documentation for administrators
a source of detailed documentation and common problems.
chrome version
the current version per platform and release.
remotely install software (microsoft kb)
use group policy to remotely install software in windows server 2008 and windows server 2003.
get support
details about what we support with chrome for business.
windows quick start guide
answers to many common questions for it administrators when rolling out chrome browser.
