Step 1: Review Your Packages

Step 2: Choose Your Integration Method

Step 3: Copy Your Script or Download Config

Option 1: Copy Script

Option 2: Download Config

Step 4: Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)

Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the packages and push them to a repository
  Download Packages

Option 2: Internalized Package (Reliable, Scalable)

Open Source
- Download the packages:
  Download Packages
- Follow manual internalization instructions
Package Internalizer (C4B)
- Run: (additional options)
- For package and dependencies run:
- Automate package internalization

Step 5: Copy Your Script

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

If Applicable - Chocolatey Configuration/Installation


## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###

#### We initialize a few things that are needed by this script - there are no other requirements.
$ErrorActionPreference = "Stop"

#### Set TLS 1.2 (3072) as that is the minimum required by various up-to-date repositories.
#### Use integers because the enumeration value for TLS 1.2 won't exist
#### in .NET 4.0, even though they are addressable if .NET 4.5+ is
#### installed (.NET 4.5 is an in-place upgrade).
[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072

#### We use this variable for future REST calls.
$RequestArguments = @{
    UseBasicParsing = $true
}

## 2. TOP LEVEL VARIABLES ##

### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
$NugetRepositoryUrl = "INTERNAL REPO URL"

### b. Internal Repository Credential ###
#### If required, add the repository access credential here
# $NugetRepositoryCredential = [PSCredential]::new(
#     "username",
#     ("password" | ConvertTo-SecureString -AsPlainText -Force)
# )
# $RequestArguments.Credential = $NugetRepositoryCredential

### c. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it
$ChocolateyDownloadUrl = "$($NugetRepositoryUrl.TrimEnd('/'))/package/chocolatey.0.12.0.nupkg"

### d. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# $ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService"

#### ii. If using a Client Salt, add it here
# $ChocolateyCentralManagementClientSalt = "clientsalt"

#### iii. If using a Service Salt, add it here
# $ChocolateyCentralManagementServiceSalt = "servicesalt"

## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository

#### Download the Nupkg, appending .zip to the filename to handle archive cmdlet limitations
if (-not (Get-Command choco.exe -ErrorAction SilentlyContinue)) {
    $TempDirectory = Join-Path $env:Temp "chocolateyInstall"
    if (-not (Test-Path $TempDirectory -PathType Container)) {
        $null = New-Item -Path $TempDirectory -ItemType Directory
    }
    $DownloadedNupkg = Join-Path $TempDirectory "$(Split-Path $ChocolateyDownloadUrl -Leaf).zip"
    Invoke-WebRequest -Uri $ChocolateyDownloadUrl -OutFile $DownloadedNupkg @RequestArguments

    #### Extract the Nupkg, and run the chocolateyInstall script
    if (Get-Command Microsoft.PowerShell.Archive\Expand-Archive -ErrorAction SilentlyContinue) {
        Microsoft.PowerShell.Archive\Expand-Archive -Path $DownloadedNupkg -DestinationPath $TempDirectory -Force
    } else {
        # PowerShell versions <4.0 do not have this function available
        try {
            $shellApplication = New-Object -ComObject Shell.Application
            $zipPackage = $shellApplication.NameSpace($DownloadedNupkg)
            $destinationFolder = $shellApplication.NameSpace($TempDirectory)
            $destinationFolder.CopyHere($zipPackage.Items(), 0x10)
        } catch {
            Write-Warning "Unable to unzip package using built-in compression."
            throw $_
        }
    }

    & $(Join-Path $TempDirectory "tools\chocolateyInstall.ps1")
}

if (-not (Get-Command choco.exe -ErrorAction SilentlyContinue)) {
    refreshenv
}

## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# choco feature enable -n useFipsCompliantChecksums

### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
choco config set --name cacheLocation --value C:\ProgramData\chocolatey\cache

#### Increase timeout to at least 4 hours
choco config set --name commandExecutionTimeoutSeconds --value 14400

#### Turn off download progress when running choco through integrations
choco feature disable --name showDownloadProgress

### c. Sources ###
#### Remove the default community package repository source
choco source list --limitoutput | ConvertFrom-Csv -Header 'Name', 'Location' -Delimiter '|' | ForEach-Object {
    if ($_.Location -eq 'https://community.chocolatey.org/api/v2/') {
        choco source remove -n $_.Name
    }
}

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here

#### NOTE: This EXAMPLE may require changes
if ($NugetRepositoryCredential) {
    choco source add --name ChocolateyInternal --source $NugetRepositoryUrl --user $NugetRepositoryCredential.UserName --password $NugetRepositoryCredential.GetNetworkCredential().Password --priority 1
} else {
    choco source add --name ChocolateyInternal --source $NugetRepositoryUrl --priority 1
}

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/
choco upgrade chocolatey --confirm

## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.

### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
choco install chocolatey-license --source $NugetRepositoryUrl --confirm

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
if ("chocolatey-license" -in (choco list --localonly --limitoutput | ConvertFrom-Csv -Header "Name" -Delimiter "|").Name) {
    choco source disable --name chocolatey.licensed
} else {
    Write-Warning "Not disabling 'chocolatey.licensed' feed, as Chocolatey-License has not been installed."
}

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
if ("chocolatey-license" -in (choco list --localonly --limitoutput | ConvertFrom-Csv -Header "Name" -Delimiter "|").Name) {
    choco install chocolatey.extension --source $NugetRepositoryUrl --confirm
} else {
    Write-Warning "Not installing 'chocolatey.extension', as Chocolatey-License has not been installed."
}

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
choco feature disable --name showNonElevatedWarnings
choco feature enable --name useBackgroundService
choco feature enable --name useBackgroundServiceWithNonAdministratorsOnly
choco feature enable --name allowBackgroundServiceUninstallsFromUserInstallsOnly
choco config set --name allowedBackgroundServiceCommands --value "install,upgrade,uninstall"

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
if ($ChocolateyCentralManagementUrl) {
    choco install chocolatey-agent --source $NugetRepositoryUrl --confirm
    choco config set --name CentralManagementServiceUrl --value $ChocolateyCentralManagementUrl
    if ($ChocolateyCentralManagementClientSalt) {
        choco config set --name centralManagementClientCommunicationSaltAdditivePassword --value $ChocolateyCentralManagementClientSalt
    }
    if ($ChocolateyCentralManagementServiceSalt) {
        choco config set --name centralManagementServiceCommunicationSaltAdditivePassword --value $ChocolateyCentralManagementServiceSalt
    }
    choco feature enable --name useChocolateyCentralManagement
    choco feature enable --name useChocolateyCentralManagementDeployments
}

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

If Applicable - Chocolatey Configuration/Installation


## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###
#### i. chocolatey.chocolatey
##### You will require the chocolatey.chocolatey collection to be installed
##### on all machines using this playbook.
##### Please see https://github.com/chocolatey/chocolatey-ansible/#installing-the-collection-from-ansible-galaxy

- name: Install and Configure Chocolatey
  hosts: all

## 2. TOP LEVEL VARIABLES ##
  vars:

### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
    nuget_repository_url: INTERNAL REPO URL

### b. Internal Repository Credential ###
#### If required, add the repository access credential here and
#### uncomment lines with source_username and source_password below
#    nuget_repository_username: username
#    nuget_repository_password: password

### c. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
#    chocolatey_central_management_url: https://chocolatey-central-management:24020/ChocolateyManagementService

#### ii. If using a Client Salt, add it here
#    chocolatey_central_management_client_salt: clientsalt

#### iii. If using a Service Salt, add it here
#    chocolatey_central_management_service_salt: servicesalt

## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository

  tasks:
  - name: Install chocolatey
    win_chocolatey:
      name: chocolatey
      source: {{ nuget_repository_url }}
      # source_username: {{ nuget_repository_username }}
      # source_password: {{ nuget_repository_password }}

## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
#   - name: Enable FIPS compliance
#     win_chocolatey_feature:
#       name: useFipsCompliantChecksums
#       state: enabled

### b. Apply Recommended Configuration ###

#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
  - name: Set the cache location
    win_chocolatey_config:
      name: cacheLocation
      state: present
      value: C:\ProgramData\chocolatey\cache

#### Increase timeout to at least 4 hours
  - name: Set the command execution timeout
    win_chocolatey_config:
      name: commandExecutionTimeoutSeconds
      state: present
      value: 14400

#### Turn off download progress when running choco through integrations
  - name: Disable showing download progress
    win_chocolatey_feature:
      name: showDownloadProgress
      state: disabled

### c. Sources ###
#### Remove the default community package repository source
  - name: Remove Chocolatey Community Repository
    win_chocolatey_source:
      name: chocolatey
      state: absent

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here
#### NOTE: This EXAMPLE may require changes
  - name: Add Internal Repository
    win_chocolatey_source:
      name: ChocolateyInternal
      state: present
      source: {{ nuget_repository_url }}
      # source_username: {{ nuget_repository_username }}
      # source_password: {{ nuget_repository_password }}
      priority: 1

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/
  - name: Upgrade Chocolatey
    win_chocolatey:
      name: chocolatey
      state: latest

## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
  - name: Install Chocolatey License
    win_chocolatey:
      name: chocolatey-license
      source: ChocolateyInternal
      state: latest

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
  - name: Disable Chocolatey Community Repository
    win_chocolatey_source:
      name: chocolatey.licensed
      state: disabled

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
  - name: Install Chocolatey Extension
    win_chocolatey:
      name: chocolatey.extension
      source: ChocolateyInternal
      state: latest

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
  - name: Hide not-elevated warnings
    win_chocolatey_feature:
      name: showNonElevatedWarnings
      state: disabled

  - name: Use background mode for self-service
    win_chocolatey_feature:
      name: useBackgroundService
      state: enabled

  - name: Use background service for non-admins
    win_chocolatey_feature:
      name: useBackgroundServiceWithNonAdministratorsOnly
      state: enabled

  - name: Allow background uninstallation for user installs
    win_chocolatey_feature:
      name: allowBackgroundServiceUninstallsFromUserInstallsOnly
      state: enabled

  - name: Set allowed background service commands
    win_chocolatey_config:
      name: backgroundServiceAllowedCommands
      state: present
      value: install,upgrade,uninstall

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
  - name: Install Chocolatey Agent
    when: chocolatey_central_management_url is defined
    win_chocolatey:
      name: chocolatey-agent
      source: ChocolateyInternal
      state: latest

  - name: Set the Central Management Service URL
    when: chocolatey_central_management_url is defined
    win_chocolatey_config:
      name: CentralManagementServiceUrl
      state: present
      value: {{ chocolatey_central_management_url }}

  - name: Set the Central Management Client Salt
    when: chocolatey_central_management_client_salt is defined
    win_chocolatey_config:
      name: centralManagementClientCommunicationSaltAdditivePassword
      state: present
      value: {{ chocolatey_central_management_client_salt }}

  - name: Set the Central Management Service Salt
    when: chocolatey_central_management_service_salt is defined
    win_chocolatey_config:
      name: centralManagementServiceCommunicationSaltAdditivePassword
      state: present
      value: {{ chocolatey_central_management_service_salt }}

  - name: Use Central Management
    when: chocolatey_central_management_url is defined
    win_chocolatey_feature:
      name: useChocolateyCentralManagement
      state: enabled

  - name: Use Central Management Deployments
    when: chocolatey_central_management_url is defined
    win_chocolatey_feature:
      name: useChocolateyCentralManagementDeployments
      state: enabled

See docs at https://docs.chef.io/resource_chocolatey_package.html.

If Applicable - Chocolatey Configuration/Installation


## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###
#### The Chocolatey resources are available with any recent version of Chef.
#### We utilise the Chocolatey recipe to install the Chocolatey binaries.
include_recipe "chocolatey"

## 2. TOP LEVEL VARIABLES ##
### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
NugetRepositoryUrl = "INTERNAL REPO URL"

### b. Internal Repository Credential ###
#### If required, add the repository access credential here
# NugetRepositoryUsername = "username"
# NugetRepositoryPassword = "password"

### c. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
ChocolateyNupkgUrl = "INTERNAL REPO URL/package/chocolatey.0.12.0.nupkg",

### d. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService"

#### ii. If using a Client Salt, add it here
# ChocolateyCentralManagementClientSalt = "clientsalt"

#### iii. If using a Service Salt, add it here
# ChocolateyCentralManagementServiceSalt = "servicesalt"

## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
node['chocolatey']['install vars'] = {
  'chocolateyDownloadUrl' => "#{ChocolateyNupkgUrl}",
}

## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# chocolatey_feature 'useFipsCompliantChecksums' do
#   action :enable
# end

### b. Apply Recommended Configuration ###

#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
chocolatey_config 'cacheLocation' do
  value 'C:\ProgramData\chocolatey\cache'
end

#### Increase timeout to at least 4 hours
chocolatey_config 'commandExecutionTimeoutSeconds' do
  value '14400'
end

#### Turn off download progress when running choco through integrations
chocolatey_feature 'showDownloadProgress' do
  action :disable
end

### c. Sources ###
#### Remove the default community package repository source
chocolatey_source 'chocolatey' do
  action :remove
end

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here

#### NOTE: This EXAMPLE may require changes
chocolatey_source 'ChocolateyInternal' do
  source "#{NugetRepositoryUrl}"
  priority 1
  action   :add
end

execute 'ChocolateyInternal' do
  command "choco source add --name ChocolateyInternal -s #{NugetRepositoryUrl} -u=#{NugetRepositoryUsername} -p=#{NugetRepositoryPassword} --priority=1"
  only_if { NugetRepositoryUsername != nil || NugetRepositoryPassword != nil }
end

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/
chocolatey_package 'chocolatey' do
  action :upgrade
  source "#{NugetRepositoryUrl}"
end

## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.

### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
chocolatey_package 'chocolatey-license' do
  action :install
  source "#{NugetRepositoryUrl}"
end

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
chocolatey_source 'chocolatey.licensed' do
  action            :disable
end

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
chocolatey_package 'chocolatey.extention' do
  action     install
  source     "#{NugetRepositoryUrl}"
end

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
chocolatey_feature 'showNonElevatedWarnings' do
  action :disable
end

chocolatey_feature 'useBackgroundService' do
  action :enable
end

chocolatey_feature 'useBackgroundServiceWithNonAdministratorsOnly' do
  action :enable
end

chocolatey_feature 'allowBackgroundServiceUninstallsFromUserInstallsOnly' do
  action :enable
end

chocolatey_config 'backgroundServiceAllowedCommands' do
  value 'install,upgrade,uninstall'
end

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
chocolatey_package 'chocolatey-agent' do
  action     install
  source     "#{NugetRepositoryUrl}"
  # user       "#{NugetRepositoryUsername}"
  # password   "#{NugetRepositoryPassword}"
  only_if { ChocolateyCentralManagementUrl != nil }
end

chocolatey_config 'CentralManagementServiceUrl' do
  value  "#{ChocolateyCentralManagementUrl}"
  only_if { ChocolateyCentralManagementUrl != nil }
end

chocolatey_config 'centralManagementClientCommunicationSaltAdditivePassword' do
  value   "#{ChocolateyCentralManagementClientSalt}"
  only_if { ChocolateyCentralManagementClientSalt != nil }
end

chocolatey_config 'centralManagementServiceCommunicationSaltAdditivePassword' do
  value   "#{ChocolateyCentralManagementServiceSalt}"
  only_if { ChocolateyCentralManagementServiceSalt != nil }
end

chocolatey_feature 'useChocolateyCentralManagement' do
  action :enable
  only_if { ChocolateyCentralManagementUrl != nil }
end

chocolatey_feature 'useChocolateyCentralManagementDeployments' do
  action :enable
  only_if { ChocolateyCentralManagementUrl != nil }
end

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.

If Applicable - Chocolatey Configuration/Installation


#requires -Modules cChoco
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###
#### i. Requires chocolatey\cChoco DSC module to be installed on the machine compiling the DSC manifest
#### NOTE: This will need to be installed before running the DSC portion of this script
if (-not (Get-Module cChoco -ListAvailable)) {
    $null = Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force
    if (($PSGallery = Get-PSRepository -Name PSGallery).InstallationPolicy -ne "Trusted") {
        Set-PSRepository -Name PSGallery -InstallationPolicy Trusted
    }
    Install-Module -Name cChoco
    if ($PSGallery.InstallationPolicy -ne "Trusted") {
        Set-PSRepository -Name PSGallery -InstallationPolicy $PSGallery.InstallationPolicy
    }
}

#### ii. Requires a hosted copy of the install.ps1 script
##### This should be available to download without authentication.
##### The original script can be found here: https://community.chocolatey.org/install.ps1

Configuration ChocolateyConfig {
## 2. TOP LEVEL VARIABLES ##
    param(
### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
        $NugetRepositoryUrl      = "INTERNAL REPO URL",

### b. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
        $ChocolateyNupkgUrl      = "INTERNAL REPO URL/package/chocolatey.0.12.0.nupkg",

### c. Internal Repository Credential ###
#### If required, add the repository access credential here
#        $NugetRepositoryCredential = [PSCredential]::new(
#            "username",
#            ("password" | ConvertTo-SecureString -AsPlainText -Force)
#        ),

### d. Install.ps1 URL
#### The path to the hosted install script:
        $ChocolateyInstallPs1Url = "https://community.chocolatey.org/install.ps1"

### e. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
#        $ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService",

#### ii. If using a Client Salt, add it here
#        $ChocolateyCentralManagementClientSalt = "clientsalt",

#### iii. If using a Service Salt, add it here
#        $ChocolateyCentralManagementServiceSalt = "servicesalt"
    )
    Import-DscResource -ModuleName PSDesiredStateConfiguration
    Import-DscResource -ModuleName cChoco

    Node 'localhost' {
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
        Environment chocoDownloadUrl {
            Name  = "chocolateyDownloadUrl"
            Value = $ChocolateyNupkgUrl
        }

        cChocoInstaller installChocolatey {
            DependsOn = "[Environment]chocoDownloadUrl"
            InstallDir = Join-Path $env:ProgramData "chocolatey"
            ChocoInstallScriptUrl = $ChocolateyInstallPs1Url
        }

## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
#        cChocoFeature featureFipsCompliance {
#            FeatureName = "useFipsCompliantChecksums"
#        }

### b. Apply Recommended Configuration ###

#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
        cChocoConfig cacheLocation {
            DependsOn  = "[cChocoInstaller]installChocolatey"
            ConfigName = "cacheLocation"
            Value      = "C:\ProgramData\chocolatey\cache"
        }

#### Increase timeout to at least 4 hours
        cChocoConfig commandExecutionTimeoutSeconds {
            DependsOn  = "[cChocoInstaller]installChocolatey"
            ConfigName = "commandExecutionTimeoutSeconds"
            Value      = 14400
        }

#### Turn off download progress when running choco through integrations
        cChocoFeature showDownloadProgress {
            DependsOn   = "[cChocoInstaller]installChocolatey"
            FeatureName = "showDownloadProgress"
            Ensure      = "Absent"
        }

### c. Sources ###
#### Remove the default community package repository source
        cChocoSource removeCommunityRepository {
            DependsOn  = "[cChocoInstaller]installChocolatey"
            Name       = "chocolatey"
            Ensure     = "Absent"
        }

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here.
#### NOTE: This EXAMPLE may require changes
        cChocoSource addInternalSource {
            DependsOn  = "[cChocoInstaller]installChocolatey"
            Name        = "ChocolateyInternal"
            Source      = $NugetRepositoryUrl
            Credentials = $NugetRepositoryCredential
            Priority    = 1
        }

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/
        cChocoPackageInstaller updateChocolatey {
            DependsOn   = "[cChocoSource]addInternalSource", "[cChocoSource]removeCommunityRepository"
            Name        = "chocolatey"
            AutoUpgrade = $true
        }

## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.

### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
        cChocoPackageInstaller chocolateyLicense {
            DependsOn = "[cChocoPackageInstaller]updateChocolatey"
            Name      = "chocolatey-license"
        }

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
        Script disableLicensedSource {
            DependsOn  = "[cChocoPackageInstaller]chocolateyLicense"
            GetScript  = {
                $Source = choco source list --limitoutput | `
                    ConvertFrom-Csv -Delimiter '|' -Header Name, Source, Disabled | `
                    Where-Object Name -eq "chocolatey.licensed"

                return @{
                    Result = if ($Source) {
                        [bool]::Parse($Source.Disabled)
                    } else {
                        Write-Warning "Source 'chocolatey.licensed' was not present."
                        $true  # Source does not need disabling
                    }
                }
            }
            SetScript  = {
                $null = choco source disable --name "chocolatey.licensed"
            }
            TestScript = {
                $State = [ScriptBlock]::Create($GetScript).Invoke()
                return $State.Result
            }
        }

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
        cChocoPackageInstaller chocolateyLicensedExtension {
            DependsOn = "[Script]disableLicensedSource"
            Name      = "chocolatey.extension"
        }

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
        cChocoFeature hideElevatedWarnings {
            DependsOn   = "[cChocoPackageInstaller]chocolateyLicensedExtension"
            FeatureName = "showNonElevatedWarnings"
            Ensure      = "Absent"
        }

        cChocoFeature useBackgroundService {
            DependsOn   = "[cChocoPackageInstaller]chocolateyLicensedExtension"
            FeatureName = "useBackgroundService"
            Ensure      = "Present"
        }

        cChocoFeature useBackgroundServiceWithNonAdmins {
            DependsOn   = "[cChocoPackageInstaller]chocolateyLicensedExtension"
            FeatureName = "useBackgroundServiceWithNonAdministratorsOnly"
            Ensure      = "Present"
        }

        cChocoFeature useBackgroundServiceUninstallsForUserInstalls {
            DependsOn   = "[cChocoPackageInstaller]chocolateyLicensedExtension"
            FeatureName = "allowBackgroundServiceUninstallsFromUserInstallsOnly"
            Ensure      = "Present"
        }

        cChocoConfig allowedBackgroundServiceCommands {
            DependsOn   = "[cChocoFeature]useBackgroundService"
            ConfigName = "backgroundServiceAllowedCommands"
            Value       = "install,upgrade,uninstall"
        }

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
        if ($ChocolateyCentralManagementUrl) {
            cChocoPackageInstaller chocolateyAgent {
                DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
                Name      = "chocolatey-agent"
            }

            cChocoConfig centralManagementServiceUrl {
                DependsOn   = "[cChocoPackageInstaller]chocolateyAgent"
                ConfigName = "CentralManagementServiceUrl"
                Value       = $ChocolateyCentralManagementUrl
            }

            if ($ChocolateyCentralManagementClientSalt) {
                cChocoConfig centralManagementClientSalt {
                    DependsOn  = "[cChocoPackageInstaller]chocolateyAgent"
                    ConfigName = "centralManagementClientCommunicationSaltAdditivePassword"
                    Value      = $ChocolateyCentralManagementClientSalt
                }
            }

            if ($ChocolateyCentralManagementServiceSalt) {
                cChocoConfig centralManagementServiceSalt {
                    DependsOn  = "[cChocoPackageInstaller]chocolateyAgent"
                    ConfigName = "centralManagementServiceCommunicationSaltAdditivePassword"
                    Value      = $ChocolateyCentralManagementServiceSalt
                }
            }

            cChocoFeature useCentralManagement {
                DependsOn   = "[cChocoPackageInstaller]chocolateyAgent"
                FeatureName = "useChocolateyCentralManagement"
                Ensure      = "Present"
            }

            cChocoFeature useCentralManagementDeployments {
                DependsOn   = "[cChocoPackageInstaller]chocolateyAgent"
                FeatureName = "useChocolateyCentralManagementDeployments"
                Ensure      = "Present"
            }
        }
    }
}

# If working this into an existing configuration with a good method for 
$ConfigData = @{
    AllNodes = @(
        @{
            NodeName                    = "localhost"
            PSDscAllowPlainTextPassword = $true
        }
    )
}

try {
    Push-Location $env:Temp
    $Config = ChocolateyConfig -ConfigurationData $ConfigData
    Start-DscConfiguration -Path $Config.PSParentPath -Wait -Verbose -Force
} finally {
    Pop-Location
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.

If Applicable - Chocolatey Configuration/Installation


## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###
#### i. Requires puppetlabs/chocolatey module
####  See https://forge.puppet.com/puppetlabs/chocolatey


## 2. TOP LEVEL VARIABLES ##
### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
$_repository_url = 'INTERNAL REPO URL'

### b. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
$_choco_download_url = 'INTERNAL REPO URL/package/chocolatey.0.12.0.nupkg'

### c. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# $_chocolatey_central_management_url = 'https://chocolatey-central-management:24020/ChocolateyManagementService'

#### ii. If using a Client Salt, add it here
# $_chocolatey_central_management_client_salt = "clientsalt"

#### iii. If using a Service Salt, add it here
# $_chocolatey_central_management_service_salt = 'servicesalt'


## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
### Note: `chocolatey_download_url is completely different than normal
###  source locations. This is directly to the bare download url for the
###  chocolatey.nupkg, similar to what you see when you browse to
###  https://community.chocolatey.org/api/v2/package/chocolatey
class {'chocolatey':
  chocolatey_download_url => $_choco_download_url,
  use_7zip                => false,
}


## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations

#chocolateyfeature {'useFipsCompliantChecksums':
#  ensure => enabled,
#}

### b. Apply Recommended Configuration ###

#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
chocolateyconfig {'cacheLocation':
  value => 'C:\ProgramData\chocolatey\cache',
}

#### Increase timeout to at least 4 hours
chocolateyconfig {'commandExecutionTimeoutSeconds':
  value => '14400',
}

#### Turn off download progress when running choco through integrations
chocolateyfeature {'showDownloadProgress':
  ensure => disabled,
}

### c. Sources ###
#### Remove the default community package repository source
chocolateysource {'chocolatey':
  ensure   => absent,
  location => 'https://community.chocolatey.org/api/v2/',
}

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here

#### NOTE: This EXAMPLE requires changes
chocolateysource {'internal_chocolatey':
  ensure             => present,
  location           => $_repository_url,
  priority           => 1,
  username           => 'optional',
  password           => 'optional,not ensured',
  bypass_proxy       => true,
  admin_only         => false,
  allow_self_service => false,
}

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/

package {'chocolatey':
  ensure   => latest,
  provider => chocolatey,
  source   => $_repository_url,
}


## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.

### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/guides/organizations/organizational-deployment-guide#exercise-4-create-a-package-for-the-license

# TODO: Add resource for installing/ensuring the chocolatey-license package
package {'chocolatey-license':
  ensure   => latest,
  provider => chocolatey,
  source   => $_repository_url,
}

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
## Disabled sources still need all other attributes until
## https://tickets.puppetlabs.com/browse/MODULES-4449 is resolved.
## Password is necessary with user, but not ensurable, so it should not
## matter what it is set to here. If you ever do get into trouble here,
## the password is your license GUID.
chocolateysource {'chocolatey.licensed':
  ensure   => disabled,
  priority => '10',
  user     => 'customer',
  password => '1234',
  require  => Package['chocolatey-license'],
}

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
package {'chocolatey.extension':
  ensure   => latest,
  provider => chocolatey,
  source   => $_repository_url,
  require  => Package['chocolatey-license'],
}

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
chocolateyfeature {'showNonElevatedWarnings':
  ensure => disabled,
}

chocolateyfeature {'useBackgroundService':
  ensure => enabled,
}

chocolateyfeature {'useBackgroundServiceWithNonAdministratorsOnly':
  ensure => enabled,
}

chocolateyfeature {'allowBackgroundServiceUninstallsFromUserInstallsOnly':
  ensure => enabled,
}

chocolateyconfig {'backgroundServiceAllowedCommands':
  value => 'install,upgrade,uninstall',
}

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
if $_chocolatey_central_management_url {
  package {'chocolatey-agent':
    ensure   => latest,
    provider => chocolatey,
    source   => $_repository_url,
    require  => Package['chocolatey-license'],
  }

  chocolateyconfig {'CentralManagementServiceUrl':
    value   => $_chocolatey_central_management_url,
  }

  if $_chocolatey_central_management_client_salt {
    chocolateyconfig {'centralManagementClientCommunicationSaltAdditivePassword':
      value => $_chocolatey_central_management_client_salt,
    }
  }

  if $_chocolatey_central_management_service_salt {
    chocolateyconfig {'centralManagementClientCommunicationSaltAdditivePassword':
      value => $_chocolatey_central_management_client_salt,
    }
  }

  chocolateyfeature {'useChocolateyCentralManagement':
    ensure  => enabled,
    require => Package['chocolatey-agent'],
  }

  chocolateyfeature {'useChocolateyCentralManagementDeployments':
    ensure  => enabled,
    require => Package['chocolatey-agent'],
  }
}

There is already a version of this package in your Script Builder

Current Version	New Version

Passing
Failing
Pending
Unknown / Exempted

Downloads:

62,937,895

Downloads of v 32.0.1700.76:

2,319

Last Update:

15 Jan 2014

Package Maintainer(s):

Software Author(s):

Google.com

Google Chrome

This is not the latest version of Google Chrome available.

32.0.1700.76 | Updated: 15 Jan 2014

Downloads:

62,937,895

Downloads of v 32.0.1700.76:

2,319

Maintainer(s):

Software Author(s):

Google.com

1

2

3

Google Chrome 32.0.1700.76

This is not the latest version of Google Chrome available.

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Hide Checks

Validation Testing Unknown

Verification Testing Unknown

Scan Testing Resulted in Flagged:

This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.

We recommend clicking the "Details" link to make your own decision on installing this package.

Details

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Google Chrome, run the following command from the command line or from PowerShell:

To upgrade Google Chrome, run the following command from the command line or from PowerShell:

To uninstall Google Chrome, run the following command from the command line or from PowerShell:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)

Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download

Option 2: Internalized Package (Reliable, Scalable)

Open Source
- Download the package:
  Download
- Follow manual internalization instructions

Package Internalizer (C4B)

Run: (additional options)

choco download googlechrome --internalize --version=32.0.1700.76 --source=https://community.chocolatey.org/api/v2/

For package and dependencies run:

choco push --source="'INTERNAL REPO URL'"

Automate package internalization

3. Copy Your Script

choco upgrade googlechrome -y --source="'INTERNAL REPO URL'" --version="'32.0.1700.76'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade googlechrome -y --source="'INTERNAL REPO URL'" --version="'32.0.1700.76'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode


- name: Install googlechrome
  win_chocolatey:
    name: googlechrome
    version: '32.0.1700.76'
    source: INTERNAL REPO URL
    state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'googlechrome' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '32.0.1700.76'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


cChocoPackageInstaller googlechrome
{
    Name     = "googlechrome"
    Version  = "32.0.1700.76"
    Source   = "INTERNAL REPO URL"
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'googlechrome':
  ensure   => '32.0.1700.76',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 27 Nov 2014.

Description

Chrome Browser
A modern web browser with an MSI and admin tools designed for organizations that need standardized, easy and secure deployment and management.

Files

Virus Scan Results

GoogleChromeStandaloneEnterprise.msi (1e6cd93cfaa1) - ## / 56
GoogleChrome.32.0.1700.76.nupkg (12e22be6f2af) - ## / 57

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version History

Version	Downloads	Last Updated	Status
Google Chrome 97.0.4692.99	762815	Thursday, January 20, 2022	Approved
Google Chrome 97.0.4692.71	1041119	Wednesday, January 5, 2022	Approved
Google Chrome 96.0.4664.110	1068705	Tuesday, December 14, 2021	Approved
Google Chrome 96.0.4664.93	717878	Tuesday, December 7, 2021	Approved
Google Chrome 96.0.4664.45	1104005	Monday, November 15, 2021	Approved
Google Chrome 95.0.4638.69	1015266	Friday, October 29, 2021	Approved
Google Chrome 95.0.4638.54	839786	Wednesday, October 20, 2021	Approved
Google Chrome 94.0.4606.81	921211	Thursday, October 7, 2021	Approved
Google Chrome 94.0.4606.71	759342	Friday, October 1, 2021	Approved
Google Chrome 94.0.4606.61	701846	Friday, September 24, 2021	Approved
Google Chrome 94.0.4606.54	497233	Tuesday, September 21, 2021	Approved
Google Chrome 93.0.4577.82	670397	Tuesday, September 14, 2021	Approved
Google Chrome 93.0.4577.63	792815	Wednesday, September 1, 2021	Approved
Google Chrome 92.0.4515.159	804351	Tuesday, August 17, 2021	Approved
Google Chrome 92.0.4515.131	725300	Tuesday, August 3, 2021	Approved
Google Chrome 92.0.4515.107	687715	Wednesday, July 21, 2021	Approved
Google Chrome 91.0.4472.164	469604	Friday, July 16, 2021	Approved
Google Chrome 91.0.4472.124	841423	Friday, June 25, 2021	Approved
Google Chrome 91.0.4472.114	530058	Friday, June 18, 2021	Approved
Google Chrome 91.0.4472.106	482394	Tuesday, June 15, 2021	Approved
Google Chrome 91.0.4472.101	433134	Thursday, June 10, 2021	Approved
Google Chrome 91.0.4472.77	744373	Wednesday, May 26, 2021	Approved
Google Chrome 90.0.4430.212	701681	Monday, May 10, 2021	Approved
Google Chrome 90.0.4430.93	610506	Tuesday, April 27, 2021	Approved
Google Chrome 90.0.4430.72	885578	Thursday, April 15, 2021	Approved
Google Chrome 89.0.4389.128	232077	Wednesday, April 14, 2021	Approved
Google Chrome 89.0.4389.114	528284	Wednesday, March 31, 2021	Approved
Google Chrome 89.0.4389.90	729714	Saturday, March 13, 2021	Approved
Google Chrome 89.0.4389.82	562447	Saturday, March 6, 2021	Approved
Google Chrome 89.0.4389.72	366261	Wednesday, March 3, 2021	Approved
Google Chrome 88.0.4324.190	560489	Tuesday, February 23, 2021	Approved
Google Chrome 88.0.4324.182	436730	Wednesday, February 17, 2021	Approved
Google Chrome 88.0.4324.150	572747	Friday, February 5, 2021	Approved
Google Chrome 88.0.4324.146	296570	Wednesday, February 3, 2021	Approved
Google Chrome 88.0.4324.104	566339	Friday, January 22, 2021	Approved
Google Chrome 87.0.4280.141	623336	Thursday, January 7, 2021	Approved
Google Chrome 87.0.4280.88	765809	Thursday, December 3, 2020	Approved
Google Chrome 87.0.4280.66	535966	Wednesday, November 18, 2020	Approved
Google Chrome 86.0.4240.198	408093	Thursday, November 12, 2020	Approved
Google Chrome 86.0.4240.193	356488	Tuesday, November 10, 2020	Approved
Google Chrome 86.0.4240.183	402709	Tuesday, November 3, 2020	Approved
Google Chrome 86.0.4240.111	498281	Wednesday, October 21, 2020	Approved
Google Chrome 86.0.4240.75	541042	Wednesday, October 7, 2020	Approved
Google Chrome 85.0.4183.121	1885897	Tuesday, September 22, 2020	Approved
Google Chrome 85.0.4183.102	509470	Tuesday, September 8, 2020	Approved
Google Chrome 85.0.4183.83	472094	Wednesday, August 26, 2020	Approved
Google Chrome 84.0.4147.135	362100	Wednesday, August 19, 2020	Approved
Google Chrome 84.0.4147.125	367183	Tuesday, August 11, 2020	Approved
Google Chrome 84.0.4147.105	404069	Tuesday, July 28, 2020	Approved
Google Chrome 84.0.4147.89	405619	Tuesday, July 14, 2020	Approved
Google Chrome 83.0.4103.116	547637	Monday, June 22, 2020	Approved
Google Chrome 83.0.4103.106	317708	Monday, June 15, 2020	Approved
Google Chrome 83.0.4103.97	377474	Wednesday, June 3, 2020	Approved
Google Chrome 83.0.4103.61	424638	Tuesday, May 19, 2020	Approved
Google Chrome 81.0.4044.138	449953	Wednesday, May 6, 2020	Approved
Google Chrome 81.0.4044.129	321743	Tuesday, April 28, 2020	Approved
Google Chrome 81.0.4044.122	282483	Wednesday, April 22, 2020	Approved
Google Chrome 81.0.4044.113	301659	Thursday, April 16, 2020	Approved
Google Chrome 81.0.4044.92	337165	Wednesday, April 8, 2020	Approved
Google Chrome 80.0.3987.163	281254	Friday, April 3, 2020	Approved
Google Chrome 80.0.3987.162	194064	Wednesday, April 1, 2020	Approved
Google Chrome 80.0.3987.149	440596	Wednesday, March 18, 2020	Approved
Google Chrome 80.0.3987.132	456148	Wednesday, March 4, 2020	Approved
Google Chrome 80.0.3987.122	355284	Tuesday, February 25, 2020	Approved
Google Chrome 80.0.3987.116	358192	Tuesday, February 18, 2020	Approved
Google Chrome 80.0.3987.106	159924	Friday, February 14, 2020	Approved
Google Chrome 80.0.3987.100	508015	Wednesday, February 12, 2020	Approved
Google Chrome 80.0.3987.87	392017	Wednesday, February 5, 2020	Approved
Google Chrome 79.0.3945.130	605865	Friday, January 17, 2020	Approved
Google Chrome 79.0.3945.117	384538	Wednesday, January 8, 2020	Approved
Google Chrome 79.0.3945.88	497238	Wednesday, December 18, 2019	Approved
Google Chrome 79.0.3945.79	361374	Wednesday, December 11, 2019	Approved
Google Chrome 78.0.3904.108	582039	Tuesday, November 19, 2019	Approved
Google Chrome 78.0.3904.97	416268	Thursday, November 7, 2019	Approved
Google Chrome 78.0.3904.87	293992	Friday, November 1, 2019	Approved
Google Chrome 78.0.3904.70	366044	Tuesday, October 22, 2019	Approved
Google Chrome 77.0.3865.120	380516	Thursday, October 10, 2019	Approved
Google Chrome 77.0.3865.90	531025	Wednesday, September 18, 2019	Approved
Google Chrome 77.0.3865.75	318863	Wednesday, September 11, 2019	Approved
Google Chrome 76.0.3809.132	490727	Tuesday, August 27, 2019	Approved
Google Chrome 76.0.3809.100	483575	Wednesday, August 7, 2019	Approved
Google Chrome 76.0.3809.87	289296	Wednesday, July 31, 2019	Approved
Google Chrome 75.0.3770.142	404538	Tuesday, July 16, 2019	Approved
Google Chrome 75.0.3770.100	492530	Tuesday, June 18, 2019	Approved
Google Chrome 75.0.3770.90	203895	Thursday, June 13, 2019	Approved
Google Chrome 75.0.3770.80	288208	Tuesday, June 4, 2019	Approved
Google Chrome 74.0.3729.169	300939	Wednesday, May 22, 2019	Approved
Google Chrome 74.0.3729.157	232311	Tuesday, May 14, 2019	Approved
Google Chrome 74.0.3729.131	298655	Wednesday, May 1, 2019	Approved
Google Chrome 74.0.3729.108	224479	Wednesday, April 24, 2019	Approved
Google Chrome 73.0.3683.103	362674	Friday, April 5, 2019	Approved
Google Chrome 73.0.3683.86	299778	Thursday, March 21, 2019	Approved
Google Chrome 73.0.3683.75	203701	Wednesday, March 13, 2019	Approved
Google Chrome 72.0.3626.121	301579	Saturday, March 2, 2019	Approved
Google Chrome 72.0.3626.119	180216	Friday, February 22, 2019	Approved
Google Chrome 72.0.3626.109	183831	Thursday, February 14, 2019	Approved
Google Chrome 72.0.3626.96	172505	Thursday, February 7, 2019	Approved
Google Chrome 72.0.3626.81	197733	Wednesday, January 30, 2019	Approved
Google Chrome 71.0.3578.98	435666	Thursday, December 13, 2018	Approved
Google Chrome 71.0.3578.80	179930	Wednesday, December 5, 2018	Approved
Google Chrome 70.0.3538.11000	252975	Monday, November 19, 2018	Approved
Google Chrome 70.0.3538.10200	200792	Saturday, November 10, 2018	Approved
Google Chrome 70.0.3538.7700	299315	Thursday, October 25, 2018	Approved
Google Chrome 70.0.3538.6700	202728	Wednesday, October 17, 2018	Approved
Google Chrome 69.0.3497.10000	401282	Tuesday, September 18, 2018	Approved
Google Chrome 69.0.3497.9200	131132	Wednesday, September 12, 2018	Approved
Google Chrome 69.0.3497.8100	217080	Wednesday, September 5, 2018	Approved
Google Chrome 68.0.3440.10600	383834	Thursday, August 9, 2018	Approved
Google Chrome 68.0.3440.8400	174054	Wednesday, August 1, 2018	Approved
Google Chrome 68.0.3440.7500	158572	Wednesday, July 25, 2018	Approved
Google Chrome 67.0.3396.9900	326105	Monday, June 25, 2018	Approved
Google Chrome 67.0.3396.8700	234880	Tuesday, June 12, 2018	Approved
Google Chrome 67.0.3396.7900	129877	Wednesday, June 6, 2018	Approved
Google Chrome 67.0.3396.6200	150368	Wednesday, May 30, 2018	Approved
Google Chrome 66.0.3359.18100	177930	Tuesday, May 15, 2018	Approved
Google Chrome 66.0.3359.17000	103416	Friday, May 11, 2018	Approved
Google Chrome 66.0.3359.13900	193511	Friday, April 27, 2018	Approved
Google Chrome 66.0.3359.11700	141070	Wednesday, April 18, 2018	Approved
Google Chrome 65.0.3325.18100	311957	Wednesday, March 21, 2018	Approved
Google Chrome 65.0.3325.16200	118704	Wednesday, March 14, 2018	Approved
Google Chrome 65.0.3325.14600	151471	Wednesday, March 7, 2018	Approved
Google Chrome 64.0.3282.18600	178348	Friday, February 23, 2018	Approved
Google Chrome 64.0.3282.16800	340758	Wednesday, February 14, 2018	Approved
Google Chrome 64.0.3282.16700	17830	Wednesday, February 14, 2018	Approved
Google Chrome 64.0.3282.14000	296583	Friday, February 2, 2018	Approved
Google Chrome 64.0.3282.11900	161073	Wednesday, January 24, 2018	Approved
Google Chrome 63.0.3239.132	284041	Friday, January 5, 2018	Approved
Google Chrome 63.0.3239.108	279601	Friday, December 15, 2017	Approved
Google Chrome 63.0.3239.84	144300	Thursday, December 7, 2017	Approved
Google Chrome 62.0.3202.94	327202	Tuesday, November 14, 2017	Approved
Google Chrome 62.0.3202.89	121055	Monday, November 6, 2017	Approved
Google Chrome 62.0.3202.75	156761	Friday, October 27, 2017	Approved
Google Chrome 62.0.3202.62	139968	Wednesday, October 18, 2017	Approved
Google Chrome 61.0.3163.100	573613	Friday, September 22, 2017	Approved
Google Chrome 61.0.3163.91	96969	Friday, September 15, 2017	Approved
Google Chrome 61.0.3163.79	138005	Wednesday, September 6, 2017	Approved
Google Chrome 60.0.3112.113	153424	Thursday, August 24, 2017	Approved
Google Chrome 60.0.3112.101	134640	Monday, August 14, 2017	Approved
Google Chrome 60.0.3112.90	128798	Thursday, August 3, 2017	Approved
Google Chrome 60.0.3112.78	107571	Wednesday, July 26, 2017	Approved
Google Chrome 59.0.3071.115	256604	Monday, June 26, 2017	Approved
Google Chrome 59.0.3071.109	91234	Wednesday, June 21, 2017	Approved
Google Chrome 59.0.3071.104	61384	Friday, June 16, 2017	Approved
Google Chrome 59.0.3071.86	101978	Tuesday, June 6, 2017	Approved
Google Chrome 58.0.3029.110	247480	Tuesday, May 9, 2017	Approved
Google Chrome 58.0.3029.96	76694	Wednesday, May 3, 2017	Approved
Google Chrome 58.0.3029.81	115967	Wednesday, April 19, 2017	Approved
Google Chrome 57.0.2987.13301	61523	Friday, April 14, 2017	Approved
Google Chrome 57.0.2987.133	142900	Thursday, March 30, 2017	Approved
Google Chrome 57.0.2987.110	130180	Friday, March 17, 2017	Approved
Google Chrome 57.0.2987.98	79869	Friday, March 10, 2017	Approved
Google Chrome 56.0.2924.87001	123185	Wednesday, March 1, 2017	Approved
Google Chrome 56.0.2924.87	567866	Thursday, February 2, 2017	Approved
Google Chrome 56.0.2924.76	99167	Thursday, January 26, 2017	Approved
Google Chrome 55.0.2883.87	555825	Friday, December 9, 2016	Approved
Google Chrome 55.0.2883.75	127244	Friday, December 2, 2016	Approved
Google Chrome 54.0.2840.99	360067	Thursday, November 10, 2016	Approved
Google Chrome 54.0.2840.87	171436	Wednesday, November 2, 2016	Approved
Google Chrome 54.0.2840.71	91310	Thursday, October 20, 2016	Approved
Google Chrome 54.0.2840.59	121107	Wednesday, October 12, 2016	Approved
Google Chrome 53.0.2785.143	92782	Thursday, September 29, 2016	Approved
Google Chrome 53.0.2785.116	87374	Wednesday, September 14, 2016	Approved
Google Chrome 53.0.2785.113	17421	Tuesday, September 13, 2016	Approved
Google Chrome 53.0.2785.101	52714	Wednesday, September 7, 2016	Approved
Google Chrome 53.0.2785.89	79751	Wednesday, August 31, 2016	Approved
Google Chrome 52.0.2743.116	218373	Wednesday, August 3, 2016	Approved
Google Chrome 52.0.2743.82	84141	Wednesday, July 20, 2016	Approved
Google Chrome 51.0.2704.106	3259	Friday, June 24, 2016	Approved
Google Chrome 51.0.2704.103	714	Thursday, June 16, 2016	Approved
Google Chrome 51.0.2704.84	571	Monday, June 6, 2016	Approved
Google Chrome 51.0.2704.79	719	Wednesday, June 1, 2016	Approved
Google Chrome 51.0.2704.63	1496	Wednesday, May 25, 2016	Approved
Google Chrome 50.0.2661.102	1068	Wednesday, May 11, 2016	Approved
Google Chrome 50.0.2661.94	14946	Thursday, April 28, 2016	Approved
Google Chrome 50.0.2661.87	19661	Thursday, April 21, 2016	Approved
Google Chrome 50.0.2661.75	22117	Wednesday, April 13, 2016	Approved
Google Chrome 49.0.2623.112	17127	Thursday, April 7, 2016	Approved
Google Chrome 49.0.2623.110	22097	Monday, March 28, 2016	Approved
Google Chrome 49.0.2623.108	10721	Thursday, March 24, 2016	Approved
Google Chrome 49.0.2623.87	27692	Wednesday, March 9, 2016	Approved
Google Chrome 49.0.2623.75	15529	Wednesday, March 2, 2016	Approved
Google Chrome 48.0.2564.116	23035	Thursday, February 18, 2016	Approved
Google Chrome 48.0.2564.109	19051	Tuesday, February 9, 2016	Approved
Google Chrome 48.0.2564.103	13949	Wednesday, February 3, 2016	Approved
Google Chrome 48.0.2564.97	16931	Wednesday, January 27, 2016	Approved
Google Chrome 48.0.2564.82	14089	Wednesday, January 20, 2016	Approved
Google Chrome 47.0.2526.111	15385	Wednesday, January 13, 2016	Approved
Google Chrome 47.0.2526.106	27567	Wednesday, December 16, 2015	Approved
Google Chrome 47.0.2526.82	10074	Saturday, December 12, 2015	Approved
Google Chrome (32-bit) 47.0.2526.81	708	Saturday, December 12, 2015	Approved
Google Chrome (32-bit) 47.0.2526.80	7456	Tuesday, December 8, 2015	Approved
Google Chrome (32-bit) 47.0.2526.73	9087	Tuesday, December 1, 2015	Approved
Google Chrome (32-bit) 46.0.2490.86	22158	Tuesday, November 10, 2015	Approved
Google Chrome (32-bit) 46.0.2490.71	28743	Thursday, October 15, 2015	Approved
Google Chrome (32-bit) 45.0.2454.101	28105	Thursday, September 24, 2015	Approved
Google Chrome (32-bit) 45.0.2454.99	10242	Monday, September 21, 2015	Approved
Google Chrome (32-bit) 45.0.2454.93	12145	Tuesday, September 15, 2015	Approved
Google Chrome (32-bit) 45.0.2454.85	18287	Tuesday, September 1, 2015	Approved
Google Chrome (32-bit) 44.0.2403.157	18067	Thursday, August 20, 2015	Approved
Google Chrome (32-bit) 44.0.2403.155	14377	Tuesday, August 11, 2015	Approved
Google Chrome (32-bit) 44.0.2403.130	10055	Tuesday, August 4, 2015	Approved
Google Chrome (32-bit) 44.0.2403.125	9667	Tuesday, July 28, 2015	Approved
Google Chrome (32-bit) 44.0.2403.107	5571	Friday, July 24, 2015	Approved
Google Chrome (32-bit) 44.0.2403.89	6231	Tuesday, July 21, 2015	Approved
Google Chrome (32-bit) 43.0.2357.134	10752	Tuesday, July 14, 2015	Approved
Google Chrome (32-bit) 43.0.2357.132	7124	Tuesday, July 7, 2015	Approved
Google Chrome (32-bit) 43.0.2357.124	18467	Tuesday, June 9, 2015	Approved
Google Chrome (32-bit) 43.0.2357.81	10110	Monday, May 25, 2015	Approved
Google Chrome (32-bit) 43.0.2357.65	6317	Tuesday, May 19, 2015	Approved
Google Chrome (32-bit) 42.0.2311.152	6664	Tuesday, May 12, 2015	Approved
Google Chrome (32-bit) 42.0.2311.135	8960	Tuesday, April 28, 2015	Approved
Google Chrome (32-bit) 42.0.2311.90	9844	Tuesday, April 14, 2015	Approved
Google Chrome (32-bit) 41.0.2272.118	11484	Wednesday, April 1, 2015	Approved
Google Chrome (32-bit) 41.0.2272.101	11864	Friday, March 20, 2015	Approved
Google Chrome (32-bit) 41.0.2272.89	9666	Tuesday, March 10, 2015	Approved
Google Chrome (32-bit) 41.0.2272.76	5534	Friday, March 6, 2015	Approved
Google Chrome (32-bit) 40.0.2214.115	12432	Thursday, February 19, 2015	Approved
Google Chrome (32-bit) 40.0.2214.111	10743	Thursday, February 5, 2015	Approved
Google Chrome (32-bit) 40.0.2214.94	7928	Thursday, January 29, 2015	Approved
Google Chrome (32-bit) 40.0.2214.93	3951	Tuesday, January 27, 2015	Approved
Google Chrome (32-bit) 40.0.2214.91	4519	Thursday, January 22, 2015	Approved
Google Chrome (32-bit) 39.0.2171.99	7273	Tuesday, January 13, 2015	Approved
Google Chrome (32-bit) 39.0.2171.95	11744	Tuesday, December 9, 2014	Approved
Google Chrome (32-bit) 39.0.2171.71	5452	Tuesday, November 25, 2014	Approved
Google Chrome (32-bit) 39.0.2171.65	4835	Tuesday, November 18, 2014	Approved
Google Chrome (32-bit) 38.0.2125.122	2519	Wednesday, November 12, 2014	Approved
Google Chrome (32-bit) 38.0.2125.111	11484	Monday, October 27, 2014	Approved
Google Chrome (32-bit) 38.0.2125.104	5774	Tuesday, October 14, 2014	Approved
Google Chrome (32-bit) 38.0.2125.101	4040	Tuesday, October 7, 2014	Approved
Google Chrome (32-bit) 37.0.2062.124	5836	Wednesday, September 24, 2014	Approved
Google Chrome (32-bit) 37.0.2062.120	6181	Tuesday, September 9, 2014	Approved
Google Chrome (32-bit) 37.0.2062.103	4306	Tuesday, September 2, 2014	Approved
Google Chrome (32-bit) 37.0.2062.102	2197	Friday, August 29, 2014	Approved
Google Chrome (32-bit) 37.0.2062.95	1089	Thursday, August 28, 2014	Approved
Google Chrome 37.0.2062.94	1847	Tuesday, August 26, 2014	Approved
Google Chrome 36.0.1985.143	4762	Tuesday, August 12, 2014	Approved
Google Chrome 36.0.1985.122	5778	Wednesday, July 16, 2014	Approved
Google Chrome 35.0.1916.153	831	Wednesday, July 16, 2014	Approved
Google Chrome 35.0.1916.114	9779	Tuesday, May 20, 2014	Approved
Google Chrome 34.0.1847.11601	5767	Tuesday, April 22, 2014	Approved
Google Chrome 34.0.1847.131	792	Thursday, April 24, 2014	Approved
Google Chrome 34.0.1847.116	3252	Wednesday, April 9, 2014	Approved
Google Chrome 33.0.1750.154	4539	Saturday, March 15, 2014	Approved
Google Chrome 33.0.1750.149	2010	Tuesday, March 11, 2014	Approved
Google Chrome 33.0.1750.146	2358	Tuesday, March 4, 2014	Approved
Google Chrome 33.0.1750.117	2387	Thursday, February 20, 2014	Approved
Google Chrome 32.0.1700.107	3057	Monday, February 3, 2014	Approved
Google Chrome 32.0.1700.102	1862	Monday, January 27, 2014	Approved
Google Chrome 32.0.1700.76	2319	Wednesday, January 15, 2014	Approved
Google Chrome 31.0.1650.63	3934	Thursday, December 5, 2013	Approved
Google Chrome 31.0.1650.57	1892	Sunday, November 17, 2013	Approved
Google Chrome 31.0.1650.48	1009	Wednesday, November 13, 2013	Approved
Google Chrome 30.0.1599.101	2359	Wednesday, October 16, 2013	Approved
Google Chrome 30.0.1599.69	1298	Friday, October 4, 2013	Approved
Google Chrome 30.0.1599.66	789	Thursday, October 3, 2013	Approved
Google Chrome 29.0.1547.76	1290	Thursday, September 19, 2013	Approved
Google Chrome 29.0.1547.66	1877	Thursday, September 5, 2013	Approved
Google Chrome 29.0.1547.62	1461	Wednesday, August 28, 2013	Approved
Google Chrome 29.0.1547.57	1437	Wednesday, August 21, 2013	Approved
Google Chrome 28.0.1500.95	1864	Wednesday, July 31, 2013	Approved
Google Chrome 28.0.1500.72	1514	Sunday, July 21, 2013	Approved
Google Chrome 28.0.1500.71	1289	Wednesday, July 10, 2013	Approved
Google Chrome 27.0.1453.116	1643	Wednesday, June 19, 2013	Approved
Google Chrome 27.0.1453.110	827	Monday, June 17, 2013	Approved
Google Chrome 26.0.1410.64	1954	Friday, May 10, 2013	Approved
Google Chrome 10.0.0	5413	Saturday, March 3, 2012	Approved

Release Notes

Now uses the administrative installer that installs for all users.

Dependencies

This package has no dependencies.

Discussion for the Google Chrome Package

Ground Rules:

This discussion is only about Google Chrome and the Google Chrome package. If you have feedback for Chocolatey, please contact the Google Group.
This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
Tell us what you love about the package or Google Chrome, or tell us what needs improvement.
Share your experiences with the package, or extra configuration or gotchas that you've found.
If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.

62,937,895

2,319

15 Jan 2014

Google Chrome

1 2 3 Google Chrome 32.0.1700.76

Some Checks Have Failed or Are Not Yet Complete

Deployment Method: Individual Install, Upgrade, & Uninstall

Deployment Method:

1. Enter Your Internal Repository Url

2. Setup Your Environment

1. Ensure you are set for organizational deployment

2. Get the package into your environment

3. Copy Your Script

4. If applicable - Chocolatey configuration/installation

Ground Rules:

1

2

3

Google Chrome 32.0.1700.76