Skip to main content

Google Chrome Enterprise

Introduction

In this example, we will build a Google Chrome Enterprise deployment which provides the following benefits over using the standard MSI based deployment:

  • The ability to defer the installation up to 3 times
  • The ability to close any applications that could cause errors during the installation
  • Verification that the required disk space is available
  • Full removal of any previous version of Google Chrome, both consumer and enterprise versions (to prevent issues sometimes seen when doing an MSI upgrade, i.e. Missing previous installation source files)

Creating the PSAppDeployToolkit deployment

  • Start with a fresh copy of the PSAppDeployToolkit source files.

Google Chrome installation Files

  • Download and copy the Google Chrome Enterprise MSI file in to the Files folder, e.g.

Google Chrome installation Files

Script Customization

Open the Deploy-Application.ps1 script and customize with the following changes:

Initialization

Populate these variables with the application and script details:

$appVendor = 'Google'
$appName = 'Chrome Enterprise (x64)'
$appVersion = '118.0.5993.118'
$appArch = 'x64'
$appLang = 'EN'
$appRevision = '01'
$appScriptVersion = '1.0.0'
$appScriptDate = '10/31/2023'
$appScriptAuthor = 'Dan Cunningham'

Pre-Install

Copy the following into the Pre-Install section:

## Prompt the user to close the following applications if they are running and
## allow the option to defer the installation up to 3 times:
Show-InstallationWelcome -CloseApps 'chrome' -AllowDefer -DeferTimes 3

## Show Progress Message (with the default message)
Show-InstallationProgress

## Remove any previous versions of Google Chrome (consumer and enterprise)
Remove-MSIApplications -Name 'Google Chrome'

Installation

Copy the following into the Installation section:

## Install the MSI
Execute-MSI -Action Install -Path 'googlechromestandaloneenterprisex64.msi'

Post-Installation

Copy the following into the Post-Install section:

## No actions required here

Uninstallation

Copy the following into the Uninstallation section:

## Prompt the user to close the following applications if they are running:
Show-InstallationWelcome -CloseApps 'chrome'

## Show Progress Message (with a message to indicate the application is being uninstalled)
Show-InstallationProgress -StatusMessage "Uninstalling Application $installTitle. Please Wait..."

## Remove this version of Google Chrome Enterprise
Execute-MSI -Action Uninstall -Path '{3ACBC599-F9FA-344F-A90C-4BC47885D629}'

Testing the Deployment Script

  • Install the application by running the following from a Windows Powershell command prompt:
.\Deploy-Application.ps1

or

.\Deploy-Application.ps1 -DeploymentType Install
  • Uninstall the application by running:
.\Deploy-Application.ps1 -DeploymentType Uninstall

Deploying through MCM using the Application Model

Creating the Application

  • Copy the installation files to your application sources folder. This should be a network share accessible by your Microsoft Configuration Manager Primary Site.

  • Within the Configuration Manager Console, create a new Application:

MCM Create Application

  • Manually specify the application information:

MCM Select manually specify the application information

MCM Manually specify the application information

  • Specify the Software Center entry details:

MCM Specify the Software Center entry details

Creating the Deployment Type

  • Add a Deployment Type:

MCM Add a Deployment Type

  • Add a type of Script Installer:

MCM Add a type of Script Installer

MCM Specify general information for this Deployment Type

  • Specify the Content Details. Ensure the content location is set correctly and tick Persist content in the client cache.

  • Enter the following for the Installation program:

Powershell.exe -File Deploy-Application.ps1
  • Enter the following for the Uninstall program:
Powershell.exe -File Deploy-Application.ps1 -DeploymentType Uninstall

MCM Specify the content location for this Deployment Type

  • For the Deployment Type Detection Method, add a Clause. Select Windows Installer and browse for the MSI file. This should populate the product code automatically:

MCM Deployment Type Detection Method

MCM Deployment Type Detection Clause

  • For the Deployment Type User Experience, select Install for User, Installation program visibility to Normal, and select the checkbox to allow users to view and interact with the program installation.

  • Click Next on the Deployment Type Requirements page.

MCM Deployment Type Requirements

  • Click Next on the Dependencies page.

MCM Deployment Type Dependencies

  • Click Next on the Deployment Type Summary page.

MCM Deployment Type Summary

  • Click Close on the Deployment Type Completion page.

MCM Deployment Type Completion

  • Click Next on the Deployment Type page.

MCM Deployment Type

  • Click Next on the Application Summary page.

MCM Application Summary

  • Click Close on the Application Completion page.

MCM Application Completion

Deploying the Application

  • Right click on the Application and select Deploy:

MCM Deploy Application

  • Select the collection to deploy to and click Next to start the deployment.

Testing the Application

  • Within a few minutes, you should see the application available for install in Software Center:

MCM Software Center App

MCM Software Center App Details

  • Select Install to start the installation.

  • The installation will now start. When complete, the Status should change to Installed:

MCM Software Center App Complete

  • You can use the PSAppDeployToolkit automatic logging, including the Windows Installer logs by navigating to the logs folder (default is C:\Windows\Logs\Software):

MCM PSAppDeployToolkit Logs