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.1.1.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.1.1.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.1.1.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.1.1.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'],
  }
}

Need Help? View our docs or file an issue.

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

Current Version	New Version

Passing
Failing
Pending
Unknown / Exempted

Downloads:

32,882

Downloads of v 3.1.1929.28-snapshot:

61

Last Update:

10 Jun 2020

Package Maintainer(s):

Pauby

Software Author(s):

Vivaldi

Tags:

vivaldi chromium browser googlechrome chrome

Vivaldi (install)

This is a prerelease version of Vivaldi (install).

3.1.1929.28-snapshot | Updated: 10 Jun 2020

Downloads:

32,882

Downloads of v 3.1.1929.28-snapshot:

Maintainer(s):

Pauby

Software Author(s):

Vivaldi

Tags:

vivaldi chromium browser googlechrome chrome

1

2

3

Vivaldi (install) 3.1.1929.28-snapshot

This is a prerelease version of Vivaldi (install).

All Checks are Passing

3 Passing Tests

Show Checks

Validation Testing Passed

Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Vivaldi (install), run the following command from the command line or from PowerShell:

To upgrade Vivaldi (install), run the following command from the command line or from PowerShell:

To uninstall Vivaldi (install), 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 vivaldi.install --internalize --version=3.1.1929.28-snapshot --pre --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 vivaldi.install -y --source="'INTERNAL REPO URL'" --version="'3.1.1929.28-snapshot'" --prerelease [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 vivaldi.install -y --source="'INTERNAL REPO URL'" --version="'3.1.1929.28-snapshot'" --prerelease
$exitCode = $LASTEXITCODE

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

Exit $exitCode


- name: Install vivaldi.install
  win_chocolatey:
    name: vivaldi.install
    version: '3.1.1929.28-snapshot'
    source: INTERNAL REPO URL
    state: present
    allow_prerelease: yes

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


chocolatey_package 'vivaldi.install' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '3.1.1929.28-snapshot'
  options  '--prerelease'
end

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


cChocoPackageInstaller vivaldi.install
{
    Name        = "vivaldi.install"
    Version     = "3.1.1929.28-snapshot"
    Source      = "INTERNAL REPO URL"
    chocoParams = "--prerelease"
}

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


package { 'vivaldi.install':
  ensure          => '3.1.1929.28-snapshot',
  install_options => ['--prerelease'],
  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.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

This package was approved as a trusted package on 11 Jun 2020.

Description

Web browser based on Chromium with added features inspired by Opera.

Files

tools\chocolateyinstall.ps1

$ErrorActionPreference = 'Stop';

$packageName= 'vivaldi'

$packageArgs = @{
    packageName    = $packageName
    fileType       = 'exe'

    url            = 'https://downloads.vivaldi.com/snapshot-auto/Vivaldi.3.1.1929.28.exe'
    silentArgs     = '--vivaldi-silent --do-not-launch-chrome --vivaldi-update --system-level'
    
    checksum       = '75897DB58575D7452FBE1177F93824F032DB731F038841D96197A6415B4E00C3'
    checksumType   = 'sha256'
    url64bit       = 'https://downloads.vivaldi.com/snapshot-auto/Vivaldi.3.1.1929.28.x64.exe'
    checksum64     = 'E791331142D766F748A319EEF9AA7884E6331735BE9F02AD2AC413C518F1186A'
    checksumType64 = 'sha256'
}

Install-ChocolateyPackage @packageArgs

tools\chocolateyuninstall.ps1

$ErrorActionPreference = 'Stop';

$packageName = 'vivaldi'
 
$regKey = Get-ItemProperty -Path 'HKCU:\Software\Vivaldi'

if (!$regKey) {
    Write-Warning "Vivaldi looks to already be uninstalled"
} else {
    $packageArgs = @{
        packageName    = $packageName
        file           = "$($regKey.UninstallString)"
                              # Workaround to get around issue with incorrect positive from package validator
        silentArgs     = "$($($regKey.('Uninstall'+'Arguments')).Replace('--vivaldi','')) --force-uninstall --vivaldi-silent --do-not-launch-chrome"
        validExitCodes = @(0,19)
    }

    Uninstall-ChocolateyPackage @packageArgs
}

Virus Scan Results

vivaldi.install.3.1.1929.28-snapshot.nupkg (fdd73379af60) - ## / 62
Vivaldi.3.1.1929.28.x64.exe (e791331142d7) - ## / 68
Vivaldi.3.1.1929.28.exe (75897db58575) - ## / 61

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
Vivaldi (Install) 5.2.2623.48	539	Wednesday, May 18, 2022	Approved
Vivaldi (Install) 5.2.2623.46	447	Wednesday, May 11, 2022	Approved
Vivaldi (Install) 5.2.2623.41	639	Thursday, April 28, 2022	Approved
Vivaldi (Install) 5.2.2623.39	570	Saturday, April 16, 2022	Approved
Vivaldi (Install) 5.2.2623.36	143	Friday, April 15, 2022	Approved
Vivaldi (Install) 5.2.2623.34	80	Thursday, April 14, 2022	Approved
Vivaldi (Install) 5.2.2623.33	15	Tuesday, April 12, 2022	Approved
Vivaldi (Install) 5.2.2623.26	418	Friday, April 8, 2022	Approved
Vivaldi (Install) 5.2.2623.24	236	Wednesday, April 6, 2022	Approved
Vivaldi (install) 5.2.2581.4-snapshot	29	Monday, February 14, 2022	Exempted
Vivaldi (Install) 5.1.2567.73	927	Saturday, March 26, 2022	Approved
Vivaldi (Install) 5.1.2567.66	928	Thursday, March 17, 2022	Approved
Vivaldi (Install) 5.1.2567.57	984	Thursday, March 3, 2022	Approved
Vivaldi (Install) 5.1.2567.49	221	Tuesday, March 1, 2022	Approved
Vivaldi (install) 5.1.2567.38-snapshot	20	Tuesday, February 8, 2022	Exempted
Vivaldi (install) 5.1.2567.31-snapshot	18	Monday, February 7, 2022	Exempted
Vivaldi (install) 5.1.2567.24-snapshot	19	Friday, February 4, 2022	Exempted
Vivaldi (install) 5.1.2567.22-snapshot	17	Thursday, February 3, 2022	Exempted
Vivaldi (install) 5.1.2567.18-snapshot	21	Wednesday, February 2, 2022	Exempted
Vivaldi (install) 5.1.2567.3-snapshot	16	Tuesday, February 1, 2022	Exempted
Vivaldi (install) 5.1.2566.3-snapshot	18	Monday, January 31, 2022	Exempted
Vivaldi (install) 5.1.2562.3-snapshot	15	Thursday, January 27, 2022	Exempted
Vivaldi (install) 5.1.2553.3-snapshot	28	Tuesday, January 18, 2022	Exempted
Vivaldi (install) 5.1.2549.3-snapshot	20	Friday, January 14, 2022	Exempted
Vivaldi (install) 5.1.2533.3-snapshot	16	Thursday, January 13, 2022	Exempted
Vivaldi (install) 5.1.2526.3-snapshot	34	Wednesday, December 22, 2021	Exempted
Vivaldi (install) 5.1.2519.3-snapshot	19	Wednesday, December 15, 2021	Exempted
Vivaldi (install) 5.1.2514.11-snapshot	30	Friday, December 10, 2021	Exempted
Vivaldi (install) 5.1.2512.3-snapshot	22	Wednesday, December 8, 2021	Exempted
Vivaldi (install) 5.0.2497.25-snapshot	24	Wednesday, December 1, 2021	Exempted
Vivaldi (install) 5.0.2497.18-snapshot	26	Wednesday, December 1, 2021	Exempted
Vivaldi (install) 5.0.2497.14-snapshot	20	Tuesday, November 30, 2021	Exempted
Vivaldi (install) 5.0.2497.10-snapshot	32	Sunday, November 28, 2021	Exempted
Vivaldi (install) 4.4.2493.3-snapshot	33	Monday, November 22, 2021	Exempted
Vivaldi (install) 4.4.2490.3-snapshot	29	Friday, November 19, 2021	Exempted
Vivaldi (install) 4.4.2488.3-snapshot	23	Wednesday, November 17, 2021	Exempted
Vivaldi (install) 4.4.2482.13-snapshot	29	Friday, November 12, 2021	Approved
Vivaldi (install) 4.4.2473.3-snapshot	63	Tuesday, November 2, 2021	Exempted
Vivaldi (install) 4.4.2465.3-snapshot	33	Wednesday, October 27, 2021	Exempted
Vivaldi (install) 4.4.2457.3-snapshot	27	Tuesday, October 19, 2021	Exempted
Vivaldi (install) 4.3.2439.41-snapshot	37	Thursday, October 7, 2021	Exempted
Vivaldi (install) 4.3.2439.37-snapshot	29	Wednesday, October 6, 2021	Exempted
Vivaldi (install) 4.3.2439.29-snapshot	23	Tuesday, October 5, 2021	Exempted
Vivaldi (install) 4.3.2439.19-snapshot	29	Monday, October 4, 2021	Exempted
Vivaldi (install) 4.3.2439.3-snapshot	32	Friday, October 1, 2021	Exempted
Vivaldi (install) 4.3.2431.3-snapshot	43	Thursday, September 23, 2021	Exempted
Vivaldi (install) 4.2.2406.40-snapshot	29	Tuesday, September 14, 2021	Approved
Vivaldi (install) 4.2.2406.30-snapshot	31	Monday, September 13, 2021	Exempted
Vivaldi (install) 4.2.2406.25-snapshot	29	Friday, September 10, 2021	Exempted
Vivaldi (install) 4.2.2406.23-snapshot	20	Friday, September 10, 2021	Exempted
Vivaldi (install) 4.2.2406.21-snapshot	28	Thursday, September 9, 2021	Exempted
Vivaldi (install) 4.2.2406.4-snapshot	35	Monday, August 30, 2021	Exempted
Vivaldi (install) 4.2.2392.3-snapshot	31	Thursday, August 19, 2021	Exempted
Vivaldi (install) 4.1.2369.10-snapshot	33	Tuesday, July 27, 2021	Exempted
Vivaldi (install) 4.1.2367.3-snapshot	35	Sunday, July 25, 2021	Exempted
Vivaldi (install) 4.1.2358.15-snapshot	48	Thursday, July 15, 2021	Exempted
Vivaldi (install) 4.1.2355.3-snapshot	39	Monday, July 12, 2021	Exempted
Vivaldi (install) 4.1.2352.3-snapshot	39	Friday, July 9, 2021	Exempted
Vivaldi (install) 4.1.2350.3-snapshot	34	Thursday, July 8, 2021	Exempted
Vivaldi (install) 4.1.2345.3-snapshot	36	Thursday, July 1, 2021	Exempted
Vivaldi (install) 4.1.2339.3-snapshot	30	Friday, June 25, 2021	Exempted
Vivaldi (install) 4.1.2328.3-snapshot	47	Tuesday, June 15, 2021	Exempted
Vivaldi (install) 4.0.2312.21-snapshot	41	Tuesday, June 8, 2021	Exempted
Vivaldi (install) 4.0.2312.17-snapshot	51	Sunday, June 6, 2021	Exempted
Vivaldi (install) 4.0.2312.13-snapshot	47	Saturday, June 5, 2021	Exempted
Vivaldi (install) 4.0.2312.11-snapshot	45	Friday, June 4, 2021	Exempted
Vivaldi (install) 4.0.2312.7-snapshot	48	Thursday, June 3, 2021	Exempted
Vivaldi (install) 4.0.2312.3-snapshot	39	Wednesday, June 2, 2021	Exempted
Vivaldi (install) 3.9.2305.3-snapshot	45	Thursday, May 27, 2021	Exempted
Vivaldi (install) 3.9.2289.3-snapshot	62	Tuesday, May 11, 2021	Exempted
Vivaldi (install) 3.8.2259.32-snapshot	39	Monday, May 10, 2021	Exempted
Vivaldi (install) 3.8.2238.3-snapshot	138	Wednesday, March 24, 2021	Approved
Vivaldi (install) 3.7.2218.42-snapshot	91	Tuesday, March 16, 2021	Exempted
Vivaldi (install) 3.7.2218.37-snapshot	62	Tuesday, March 16, 2021	Exempted
Vivaldi (install) 3.7.2218.32-snapshot	60	Monday, March 15, 2021	Exempted
Vivaldi (install) 3.7.2218.29-snapshot	58	Friday, March 12, 2021	Exempted
Vivaldi (install) 3.7.2218.25-snapshot	64	Thursday, March 11, 2021	Approved
Vivaldi (install) 3.7.2218.21-snapshot	48	Wednesday, March 10, 2021	Exempted
Vivaldi (install) 3.7.2218.3-snapshot	71	Friday, March 5, 2021	Exempted
Vivaldi (install) 3.7.2209.3-snapshot	61	Wednesday, February 24, 2021	Approved
Vivaldi (install) 3.7.2202.3-snapshot	59	Wednesday, February 17, 2021	Approved
Vivaldi (install) 3.6.2165.40	5824	Friday, February 19, 2021	Approved
Vivaldi (install) 3.6.2165.36	50	Friday, February 5, 2021	Approved
Vivaldi (install) 3.6.2165.34	841	Thursday, January 28, 2021	Approved
Vivaldi (install) 3.6.2165.32-snapshot	64	Wednesday, January 27, 2021	Approved
Vivaldi (install) 3.6.2165.26-snapshot	48	Tuesday, January 26, 2021	Approved
Vivaldi (install) 3.6.2165.22-snapshot	75	Friday, January 22, 2021	Approved
Vivaldi (install) 3.6.2165.3-snapshot	62	Thursday, January 14, 2021	Approved
Vivaldi (install) 3.6.2160.3-snapshot	58	Thursday, January 7, 2021	Approved
Vivaldi (install) 3.6.2137.3-snapshot	63	Tuesday, December 15, 2020	Approved
Vivaldi (install) 3.5.2131.8-snapshot	59	Thursday, December 10, 2020	Approved
Vivaldi (install) 3.5.2130.3-snapshot	49	Wednesday, December 9, 2020	Approved
Vivaldi (install) 3.5.2115.87	617	Thursday, January 7, 2021	Approved
Vivaldi (install) 3.5.2115.81	653	Friday, December 11, 2020	Approved
Vivaldi (install) 3.5.2115.73	258	Tuesday, December 8, 2020	Approved
Vivaldi (install) 3.5.2115.71-snapshot	64	Monday, December 7, 2020	Approved
Vivaldi (install) 3.5.2115.67-snapshot	55	Friday, December 4, 2020	Approved
Vivaldi (install) 3.5.2115.63-snapshot	54	Thursday, December 3, 2020	Approved
Vivaldi (install) 3.5.2115.54-snapshot	46	Wednesday, December 2, 2020	Approved
Vivaldi (install) 3.5.2115.31-snapshot	52	Friday, November 27, 2020	Approved
Vivaldi (install) 3.5.2115.21-snapshot	57	Thursday, November 26, 2020	Approved
Vivaldi (install) 3.5.2115.4-snapshot	56	Tuesday, November 24, 2020	Approved
Vivaldi (install) 3.5.2110.3-snapshot	56	Thursday, November 19, 2020	Approved
Vivaldi (install) 3.5.2088.7-snapshot	63	Thursday, October 29, 2020	Approved
Vivaldi (install) 3.5.2080.3-snapshot	81	Tuesday, October 20, 2020	Approved
Vivaldi (install) 3.4.2066.106	516	Thursday, November 12, 2020	Approved
Vivaldi (install) 3.4.2066.99	290	Tuesday, November 10, 2020	Approved
Vivaldi (install) 3.4.2066.94	310	Tuesday, November 3, 2020	Approved
Vivaldi (install) 3.4.2066.90	240	Friday, October 30, 2020	Approved
Vivaldi (install) 3.4.2066.88	58	Friday, October 30, 2020	Approved
Vivaldi (install) 3.4.2066.86	353	Thursday, October 22, 2020	Approved
Vivaldi (install) 3.4.2066.76	215	Thursday, October 15, 2020	Approved
Vivaldi (install) 3.4.2066.70-snapshot	59	Wednesday, October 14, 2020	Approved
Vivaldi (install) 3.4.2066.64-snapshot	55	Wednesday, October 14, 2020	Approved
Vivaldi (install) 3.4.2066.37-snapshot	61	Friday, October 9, 2020	Exempted
Vivaldi (install) 3.4.2066.7-snapshot	64	Wednesday, October 7, 2020	Exempted
Vivaldi (install) 3.4.2064.6-snapshot	69	Monday, October 5, 2020	Approved
Vivaldi (install) 3.4.2059.2-snapshot	75	Thursday, October 1, 2020	Approved
Vivaldi (install) 3.4.2056.19-snapshot	70	Monday, September 28, 2020	Approved
Vivaldi (install) 3.4.2049.2-snapshot	73	Tuesday, September 22, 2020	Approved
Vivaldi (install) 3.4.2038.4-snapshot	82	Friday, September 11, 2020	Approved
Vivaldi (install) 3.4.2036.3-snapshot	80	Wednesday, September 9, 2020	Approved
Vivaldi (install) 3.4.2035.3-snapshot	82	Tuesday, September 8, 2020	Approved
Vivaldi (install) 3.3.2022.47	388	Tuesday, September 22, 2020	Approved
Vivaldi (install) 3.3.2022.45	268	Thursday, September 10, 2020	Approved
Vivaldi (install) 3.3.2022.39	177	Tuesday, September 8, 2020	Approved
Vivaldi (install) 3.3.2022.36	124	Monday, September 7, 2020	Approved
Vivaldi (install) 3.3.2022.35-snapshot	76	Friday, September 4, 2020	Approved
Vivaldi (install) 3.3.2022.27-snapshot	76	Friday, September 4, 2020	Approved
Vivaldi (install) 3.3.2022.23-snapshot	57	Wednesday, September 2, 2020	Approved
Vivaldi (install) 3.3.2022.6-snapshot	85	Thursday, August 27, 2020	Exempted
Vivaldi (install) 3.3.2020.3-snapshot	91	Tuesday, August 25, 2020	Approved
Vivaldi (install) 3.3.2009.3-snapshot	88	Friday, August 14, 2020	Approved
Vivaldi (install) 3.3.2001.3-snapshot	90	Sunday, August 9, 2020	Approved
Vivaldi (install) 3.2.1967.47	295	Wednesday, August 19, 2020	Approved
Vivaldi (install) 3.2.1967.45	98	Tuesday, August 18, 2020	Approved
Vivaldi (install) 3.2.1967.43-snapshot	77	Wednesday, August 5, 2020	Approved
Vivaldi (install) 3.2.1967.41	290	Wednesday, August 5, 2020	Approved
Vivaldi (install) 3.2.1967.38-snapshot	87	Wednesday, July 29, 2020	Approved
Vivaldi (install) 3.2.1967.30-snapshot	77	Friday, July 24, 2020	Exempted
Vivaldi (install) 3.2.1964.3-snapshot	72	Tuesday, June 30, 2020	Approved
Vivaldi (install) 3.2.1959.3-snapshot	95	Thursday, June 25, 2020	Approved
Vivaldi (install) 3.2.1957.9-snapshot	71	Tuesday, June 23, 2020	Approved
Vivaldi (install) 3.2.1952.3-snapshot	77	Thursday, June 18, 2020	Approved
Vivaldi (install) 3.2.1950.3-snapshot	73	Tuesday, June 16, 2020	Approved
Vivaldi (install) 3.1.1929.48	224	Wednesday, July 29, 2020	Approved
Vivaldi (install) 3.1.1929.45	360	Wednesday, June 24, 2020	Approved
Vivaldi (install) 3.1.1929.40	191	Friday, June 19, 2020	Approved
Vivaldi (install) 3.1.1929.34	192	Friday, June 12, 2020	Approved
Vivaldi (install) 3.1.1929.29	93	Thursday, June 11, 2020	Approved
Vivaldi (install) 3.1.1929.28-snapshot	61	Wednesday, June 10, 2020	Approved
Vivaldi (install) 3.1.1929.23-snapshot	85	Tuesday, June 9, 2020	Approved
Vivaldi (install) 3.1.1929.21-snapshot	95	Monday, June 8, 2020	Approved
Vivaldi (install) 3.1.1929.19-snapshot	83	Friday, June 5, 2020	Approved
Vivaldi (install) 3.1.1929.13-snapshot	81	Wednesday, June 3, 2020	Approved
Vivaldi (install) 3.1.1929.3-snapshot	96	Thursday, May 28, 2020	Approved
Vivaldi (install) 3.1.1906.3-snapshot	91	Friday, May 8, 2020	Approved
Vivaldi (install) 3.0.1874.38	396	Friday, May 8, 2020	Approved
Vivaldi (install) 3.0.1874.33	193	Wednesday, April 29, 2020	Approved
Vivaldi (install) 3.0.1874.32	192	Friday, April 24, 2020	Approved
Vivaldi (install) 3.0.1874.27-snapshot	112	Thursday, April 23, 2020	Approved
Vivaldi (install) 3.0.1874.23	147	Wednesday, April 22, 2020	Approved
Vivaldi (install) 3.0.1874.22-snapshot	97	Monday, April 20, 2020	Approved
Vivaldi (install) 3.0.1874.15-snapshot	90	Sunday, April 19, 2020	Approved
Vivaldi (install) 3.0.1874.11-snapshot	93	Saturday, April 18, 2020	Approved
Vivaldi (install) 3.0.1874.7-snapshot	83	Friday, April 17, 2020	Approved
Vivaldi (install) 3.0.1874.5-snapshot	88	Thursday, April 16, 2020	Approved
Vivaldi (install) 3.0.1874.3-snapshot	88	Wednesday, April 15, 2020	Approved
Vivaldi (install) 2.12.1874.30-snapshot	88	Tuesday, April 14, 2020	Approved
Vivaldi (install) 2.12.1873.3-snapshot	77	Monday, April 6, 2020	Exempted
Vivaldi (install) 2.12.1867.3-snapshot	106	Monday, March 30, 2020	Exempted
Vivaldi (install) 2.12.1862.3-snapshot	89	Wednesday, March 25, 2020	Approved
Vivaldi (install) 2.12.1856.3-snapshot	102	Thursday, March 19, 2020	Approved
Vivaldi (install) 2.12.1854.5-snapshot	85	Tuesday, March 17, 2020	Approved
Vivaldi (install) 2.12.1849.7-snapshot	98	Thursday, March 12, 2020	Approved
Vivaldi (install) 2.12.1848.4-snapshot	79	Wednesday, March 11, 2020	Approved
Vivaldi (install) 2.12.1843.5-snapshot	108	Friday, March 6, 2020	Approved
Vivaldi (install) 2.12.1838.3-snapshot	75	Monday, March 2, 2020	Approved
Vivaldi (install) 2.11.1811.52	209	Friday, April 3, 2020	Approved
Vivaldi (install) 2.11.1811.51	191	Thursday, April 2, 2020	Approved
Vivaldi (install) 2.11.1811.49	240	Friday, March 20, 2020	Approved
Vivaldi (install) 2.11.1811.47	286	Thursday, March 5, 2020	Approved
Vivaldi (install) 2.11.1811.44	184	Wednesday, February 26, 2020	Approved
Vivaldi (install) 2.11.1811.41	113	Monday, February 24, 2020	Approved
Vivaldi (install) 2.11.1811.38	78	Tuesday, February 18, 2020	Approved
Vivaldi (install) 2.11.1811.33	94	Wednesday, February 12, 2020	Approved
Vivaldi (install) 2.11.1811.28-snapshot	121	Tuesday, February 11, 2020	Exempted
Vivaldi (install) 2.11.1811.23-snapshot	87	Monday, February 10, 2020	Exempted
Vivaldi (install) 2.11.1811.3-snapshot	103	Tuesday, February 4, 2020	Exempted
Vivaldi (install) 2.11.1805.3-snapshot	90	Wednesday, January 29, 2020	Exempted
Vivaldi (install) 2.11.1800.5-snapshot	112	Friday, January 24, 2020	Exempted
Vivaldi (install) 2.11.1789.3-snapshot	115	Monday, January 13, 2020	Exempted
Vivaldi (install) 2.11.1784.3-snapshot	82	Thursday, January 9, 2020	Exempted
Vivaldi (install) 2.10.1745.27	265	Friday, January 17, 2020	Exempted
Vivaldi (install) 2.10.1745.26	107	Friday, January 10, 2020	Exempted
Vivaldi (install) 2.10.1745.23	207	Tuesday, January 7, 2020	Exempted
Vivaldi (install) 2.10.1745.21	111	Tuesday, January 7, 2020	Exempted
Vivaldi (install) 2.10.1745.18-snapshot	95	Wednesday, December 18, 2019	Exempted
Vivaldi (install) 2.10.1745.7-snapshot	100	Tuesday, December 17, 2019	Exempted
Vivaldi (install) 2.10.1745.3-snapshot	84	Monday, December 16, 2019	Exempted
Vivaldi (install) 2.10.1745.1-snapshot	73	Tuesday, December 10, 2019	Exempted
Vivaldi (install) 2.9.1745.22-snapshot	114	Friday, December 6, 2019	Exempted
Vivaldi (install) 2.9.1745.9-snapshot	96	Tuesday, December 3, 2019	Exempted
Vivaldi (install) 2.9.1735.3-snapshot	61	Friday, November 22, 2019	Exempted
Vivaldi (install) 2.9.1732.13-snapshot	83	Wednesday, November 20, 2019	Exempted
Vivaldi 2.9.1719.3-snapshot	78	Monday, November 11, 2019	Exempted
Vivaldi 2.9.1705.41	213	Monday, November 11, 2019	Approved
Vivaldi 2.9.1705.38	85	Monday, November 11, 2019	Approved
Vivaldi 2.9.1705.34	91	Monday, November 11, 2019	Approved
Vivaldi 2.9.1705.31	78	Thursday, October 31, 2019	Approved
Vivaldi 2.9.1705.30-snapshot	111	Wednesday, October 30, 2019	Exempted
Vivaldi 2.9.1705.27-snapshot	107	Monday, October 28, 2019	Exempted
Vivaldi 2.9.1705.4-snapshot	83	Friday, October 25, 2019	Exempted

Vivaldi Technologies

Release Notes

https://vivaldi.com/blog/snapshots

Dependencies

This package has no dependencies.

Discussion for the Vivaldi (install) Package

Ground Rules:

This discussion is only about Vivaldi (install) and the Vivaldi (install) 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 Vivaldi (install), 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.

32,882

61

10 Jun 2020

Vivaldi (install)

1 2 3 Vivaldi (install) 3.1.1929.28-snapshot

All Checks are Passing

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

Vivaldi (install) 3.1.1929.28-snapshot