Chrome Browser quick start (Windows)
4. Deploy and test
Installing Chrome Browser from an MSI will override any version of Chrome Browser installed by a user. Here’s where Chrome is installed and linked for the 2 types of installers:
- User Level: "%USER DATA%\Google\Chrome\Application\"
- System Level: "Program Files\Google\Chrome\Application\"
Note: Chrome won’t allow an older version to be installed over a newer version. Any MSI of Chrome needs to be newer than the version already deployed (for example, Chrome 62 can’t overwrite Chrome 63).
Step 1: Push the MSI package
There are several ways .msi files can be distributed to managed Windows computers, including:
- Active Directory Group Policy Management
- HP Client Automation
- Microsoft System Center Configuration Manager
If you’re using SMS or other tools to deploy software, you should push the Chrome Browser MSI package just like you would for any other .msi installation. Otherwise, you can run the file on the target machines directly and silently with the msiexec /q /l GoogleChrome.msi command.
Step 2: Test your installation
For each scenario or type of policy setup you want to deploy:
- On each computer in the test group, go to chrome://policy.
- Verify that the correct policies are in effect. For details, see View a device’s current Chrome policies.
- If you don’t see the correct policies or settings, open a command line and enter gpupdate /force to force Group Policy Management Editor to update.