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:

835,246

Downloads of v 34.0.2036.47:

833

Last Update:

11 Jan 2016

Package Maintainer(s):

Software Author(s):

Opera

Tags:

browser opera

Opera

This is not the latest version of Opera available.

34.0.2036.47 | Updated: 11 Jan 2016

Downloads:

835,246

Downloads of v 34.0.2036.47:

833

Maintainer(s):

Software Author(s):

Opera

Tags:

browser opera

1

2

3

Opera 34.0.2036.47

This is not the latest version of Opera available.

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 Opera, run the following command from the command line or from PowerShell:

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

To uninstall Opera, 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 opera --internalize --version=34.0.2036.47 --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 opera -y --source="'INTERNAL REPO URL'" --version="'34.0.2036.47'" [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 opera -y --source="'INTERNAL REPO URL'" --version="'34.0.2036.47'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode


- name: Install opera
  win_chocolatey:
    name: opera
    version: '34.0.2036.47'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'opera' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '34.0.2036.47'
end

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


cChocoPackageInstaller opera
{
    Name     = "opera"
    Version  = "34.0.2036.47"
    Source   = "INTERNAL REPO URL"
}

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


package { 'opera':
  ensure   => '34.0.2036.47',
  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 11 Jan 2016.

Description

The Opera web browser makes the Web fast and fun, giving you a better web browser experience on any computer.

Files

tools\chocolateyInstall.ps1

$packageName = 'Opera'
$version = '34.0.2036.47'
$fileType = 'exe'
$installArgs = '/install /silent /launchopera 0 /setdefaultbrowser 0'
$url = 'http://get.geo.opera.com/pub/opera/desktop/34.0.2036.47/win/Opera_34.0.2036.47_Setup.exe'

try {

  $regPathModifierArray = @('Wow6432Node\', '')
  $alreadyInstalled = $null

  foreach ($regPathModifier in $regPathModifierArray) {
    $regPath = "HKLM:\SOFTWARE\${regPathModifier}Microsoft\Windows\CurrentVersion\Uninstall\Opera $version"
    if (Test-Path $regPath) {
      $alreadyInstalled = $true
    }
  }

  if ($alreadyInstalled) {
    Write-Output "Opera $version is already installed. Skipping download and installation."
  } else {
    Install-ChocolateyPackage $packageName $fileType $installArgs $url
  }

} catch {
  Write-ChocolateyFailure $packageName $($_.Exception.Message)
  throw
}

Virus Scan Results

Opera.34.0.2036.47.nupkg (6c0df7c47cd0) - ## / 57
Opera_34.0.2036.47_Setup.exe (2f06d7a5c468) - ## / 56

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
Opera 83.0.4254.19	3127	Wednesday, January 19, 2022	Approved
Opera 82.0.4227.58	3360	Wednesday, January 12, 2022	Approved
Opera 82.0.4227.43	6834	Tuesday, December 21, 2021	Approved
Opera 82.0.4227.33	3523	Tuesday, December 14, 2021	Approved
Opera 82.0.4227.23	4850	Thursday, December 2, 2021	Approved
Opera 81.0.4196.60	3781	Tuesday, November 23, 2021	Approved
Opera 81.0.4196.54	3040	Wednesday, November 17, 2021	Approved
Opera 81.0.4196.37	3980	Tuesday, November 9, 2021	Approved
Opera 81.0.4196.31	3283	Thursday, November 4, 2021	Approved
Opera 80.0.4170.72	3947	Wednesday, October 27, 2021	Approved
Opera 80.0.4170.63	3863	Wednesday, October 20, 2021	Approved
Opera 80.0.4170.40	3891	Thursday, October 14, 2021	Approved
Opera 80.0.4170.16	4856	Tuesday, October 5, 2021	Approved
Opera 79.0.4143.72	4187	Tuesday, September 28, 2021	Approved
Opera 79.0.4143.66	2561	Friday, September 24, 2021	Approved
Opera 79.0.4143.56	1443	Thursday, September 23, 2021	Approved
Opera 79.0.4143.50	1620	Tuesday, September 21, 2021	Approved
Opera 79.0.4143.22	4028	Tuesday, September 14, 2021	Approved
Opera 78.0.4093.184	6838	Wednesday, August 25, 2021	Approved
Opera 78.0.4093.147	5151	Thursday, August 12, 2021	Approved
Opera 78.0.4093.112	3416	Tuesday, August 3, 2021	Approved
Opera 77.0.4054.277	4626	Wednesday, July 21, 2021	Approved
Opera 77.0.4054.254	3000	Wednesday, July 14, 2021	Approved
Opera 77.0.4054.203	2940	Wednesday, July 7, 2021	Approved
Opera 77.0.4054.146	4254	Thursday, June 24, 2021	Approved
Opera 77.0.4054.90	11922	Thursday, June 17, 2021	Approved
Opera 77.0.4054.80	2215	Tuesday, June 15, 2021	Approved
Opera 77.0.4054.64	2625	Thursday, June 10, 2021	Approved
Opera 77.0.4054.60	1464	Wednesday, June 9, 2021	Approved
Opera 76.0.4017.177	3208	Wednesday, June 2, 2021	Approved
Opera 76.0.4017.175	1302	Tuesday, June 1, 2021	Approved
Opera 76.0.4017.154	2869	Wednesday, May 26, 2021	Approved
Opera 76.0.4017.123	5753	Wednesday, May 12, 2021	Approved
Opera 76.0.4017.107	3159	Thursday, May 6, 2021	Approved
Opera 76.0.4017.94	3584	Wednesday, April 28, 2021	Approved
Opera 75.0.3969.243	1994	Monday, April 26, 2021	Approved
Opera 75.0.3969.218	3910	Tuesday, April 20, 2021	Approved
Opera 75.0.3969.171	3038	Tuesday, April 13, 2021	Approved
Opera 75.0.3969.149	4292	Friday, April 2, 2021	Approved
Opera 74.0.3911.232	6174	Thursday, March 18, 2021	Approved
Opera 74.0.3911.218	3531	Thursday, March 11, 2021	Approved
Opera 74.0.3911.203	3683	Thursday, March 4, 2021	Approved
Opera 74.0.3911.160	4562	Monday, February 22, 2021	Approved
Opera 74.0.3911.154	31	Friday, February 19, 2021	Approved
Opera 74.0.3911.144	2273	Thursday, February 18, 2021	Approved
Opera 74.0.3911.139	1295	Wednesday, February 17, 2021	Approved
Opera 74.0.3911.107	3465	Tuesday, February 9, 2021	Approved
Opera 74.0.3911.75	3415	Wednesday, February 3, 2021	Approved
Opera 73.0.3856.344	6147	Thursday, January 14, 2021	Approved
Opera 73.0.3856.329	3999	Tuesday, January 5, 2021	Approved
Opera 73.0.3856.284	5402	Wednesday, December 16, 2020	Approved
Opera 73.0.3856.257	3375	Wednesday, December 9, 2020	Approved
Opera 72.0.3815.400	4663	Wednesday, November 25, 2020	Approved
Opera 72.0.3815.378	2539	Wednesday, November 18, 2020	Approved
Opera 72.0.3815.371	523	Wednesday, November 18, 2020	Approved
Opera 72.0.3815.320	4086	Tuesday, November 10, 2020	Approved
Opera 72.0.3815.211	1246	Monday, November 9, 2020	Approved
Opera 72.0.3815.207	2258	Thursday, November 5, 2020	Approved
Opera 72.0.3815.200	896	Wednesday, November 4, 2020	Approved
Opera 72.0.3815.186	2938	Thursday, October 29, 2020	Approved
Opera 72.0.3815.148	3590	Wednesday, October 21, 2020	Approved
Opera 71.0.3770.284	1187	Tuesday, October 20, 2020	Approved
Opera 71.0.3770.271	2122	Wednesday, October 14, 2020	Approved
Opera 71.0.3770.228	3997	Tuesday, October 6, 2020	Approved
Opera 71.0.3770.198	3468	Tuesday, September 29, 2020	Approved
Opera 71.0.3770.171	2721	Wednesday, September 23, 2020	Approved
Opera 71.0.3770.148	3445	Wednesday, September 16, 2020	Approved
Opera 70.0.3728.189	817	Tuesday, September 15, 2020	Approved
Opera 70.0.3728.178	3451	Wednesday, September 9, 2020	Approved
Opera 70.0.3728.154	6143	Wednesday, September 2, 2020	Approved
Opera 70.0.3728.144	2076	Monday, August 31, 2020	Approved
Opera 70.0.3728.133	3141	Tuesday, August 25, 2020	Approved
Opera 70.0.3728.119	3686	Tuesday, August 18, 2020	Approved
Opera 70.0.3728.106	3407	Tuesday, August 11, 2020	Approved
Opera 70.0.3728.95	1923	Saturday, August 8, 2020	Approved
Opera 70.0.3728.71	3984	Tuesday, July 28, 2020	Approved
Opera 69.0.3686.95	1402	Monday, July 27, 2020	Approved
Opera 69.0.3686.77	4400	Wednesday, July 15, 2020	Approved
Opera 69.0.3686.57	3168	Wednesday, July 8, 2020	Approved
Opera 69.0.3686.49	2844	Thursday, July 2, 2020	Approved
Opera 69.0.3686.36	3595	Wednesday, June 24, 2020	Approved
Opera 68.0.3618.173	2667	Thursday, June 18, 2020	Approved
Opera 68.0.3618.165	3375	Wednesday, June 10, 2020	Approved
Opera 68.0.3618.125	5828	Tuesday, May 19, 2020	Approved
Opera 68.0.3618.104	3485	Wednesday, May 13, 2020	Approved
Opera 68.0.3618.63	4482	Wednesday, April 29, 2020	Approved
Opera 68.0.3618.56	2659	Friday, April 24, 2020	Approved
Opera 68.0.3618.46	2166	Wednesday, April 22, 2020	Approved
Opera 67.0.3575.137	4748	Wednesday, April 8, 2020	Approved
Opera 67.0.3575.115	4034	Friday, March 27, 2020	Approved
Opera 67.0.3575.97	3832	Thursday, March 19, 2020	Approved
Opera 67.0.3575.79	1777	Thursday, March 12, 2020	Approved
Opera 67.0.3575.53	91	Tuesday, March 3, 2020	Approved
Opera 67.0.3575.31	6631	Tuesday, February 25, 2020	Approved
Opera 66.0.3515.115	1388	Monday, February 24, 2020	Approved
Opera 66.0.3515.103	6333	Tuesday, February 18, 2020	Approved
Opera 66.0.3515.95	3028	Thursday, February 13, 2020	Approved
Opera 66.0.3515.60	5013	Thursday, January 30, 2020	Approved
Opera 66.0.3515.44	3620	Wednesday, January 22, 2020	Approved
Opera 66.0.3515.36	4047	Thursday, January 16, 2020	Approved
Opera 66.0.3515.27	4375	Wednesday, January 8, 2020	Approved
Opera 65.0.3467.78	4934	Thursday, December 19, 2019	Approved
Opera 65.0.3467.72	3632	Thursday, December 12, 2019	Approved
Opera 65.0.3467.69	2056	Tuesday, December 10, 2019	Approved
Opera 65.0.3467.62	120	Wednesday, December 4, 2019	Approved
Opera 65.0.3467.48	6422	Wednesday, November 20, 2019	Approved
Opera 65.0.3467.42	2937	Friday, November 15, 2019	Approved
Opera 65.0.3467.38	1530	Thursday, November 14, 2019	Approved
Opera 64.0.3417.92	3835	Tuesday, November 5, 2019	Approved
Opera 64.0.3417.83	3049	Wednesday, October 30, 2019	Approved
Opera 64.0.3417.73	3198	Wednesday, October 23, 2019	Approved
Opera 64.0.3417.61	3295	Wednesday, October 16, 2019	Approved
Opera 64.0.3417.54	3347	Wednesday, October 9, 2019	Approved
Opera 64.0.3417.47	1509	Tuesday, October 8, 2019	Approved
Opera 63.0.3368.71	7205	Tuesday, September 3, 2019	Approved
Opera 63.0.3368.66	1199	Monday, September 2, 2019	Approved
Opera 63.0.3368.53	3318	Tuesday, August 27, 2019	Approved
Opera 63.0.3368.43	2706	Thursday, August 22, 2019	Approved
Opera 63.0.3368.35	1773	Tuesday, August 20, 2019	Approved
Opera 62.0.3331.99	6208	Wednesday, July 24, 2019	Approved
Opera 62.0.3331.72	2969	Friday, July 12, 2019	Approved
Opera 62.0.3331.66	2595	Wednesday, July 10, 2019	Approved
Opera 62.0.3331.43	2951	Wednesday, July 3, 2019	Approved
Opera 62.0.3331.18	3004	Thursday, June 27, 2019	Approved
Opera 60.0.3255.151	6452	Wednesday, June 5, 2019	Approved
Opera 60.0.3255.109	4358	Friday, May 24, 2019	Approved
Opera 60.0.3255.95	2675	Saturday, May 18, 2019	Approved
Opera 60.0.3255.84	2978	Friday, May 10, 2019	Approved
Opera 60.0.3255.70	4488	Friday, April 26, 2019	Approved
Opera 60.0.3255.59	2810	Sunday, April 21, 2019	Approved
Opera 60.0.3255.56	2294	Thursday, April 18, 2019	Approved
Opera 60.0.3255.27	3498	Tuesday, April 9, 2019	Approved
Opera 58.0.3135.127	4175	Thursday, March 28, 2019	Approved
Opera 58.0.3135.118	2869	Friday, March 22, 2019	Approved
Opera 58.0.3135.117	1518	Thursday, March 21, 2019	Approved
Opera 58.0.3135.107	3403	Thursday, March 14, 2019	Approved
Opera 58.0.3135.90	3303	Thursday, March 7, 2019	Approved
Opera 58.0.3135.79	3647	Tuesday, February 26, 2019	Approved
Opera 58.0.3135.68	3218	Wednesday, February 20, 2019	Approved
Opera 58.0.3135.65	3630	Tuesday, February 12, 2019	Approved
Opera 58.0.3135.53	4265	Wednesday, January 30, 2019	Approved
Opera 58.0.3135.47	3200	Wednesday, January 23, 2019	Approved
Opera 57.0.3098.116	4317	Wednesday, January 9, 2019	Approved
Opera 57.0.3098.110	2640	Thursday, January 3, 2019	Approved
Opera 57.0.3098.106	3324	Wednesday, December 19, 2018	Approved
Opera 57.0.3098.102	2643	Thursday, December 13, 2018	Approved
Opera 57.0.3098.91	2638	Thursday, December 6, 2018	Approved
Opera 57.0.3098.76	3180	Wednesday, November 28, 2018	Approved
Opera 56.0.3051.116	1663	Monday, November 26, 2018	Approved
Opera 56.0.3051.104	3824	Wednesday, November 14, 2018	Approved
Opera 56.0.3051.99	3326	Tuesday, November 6, 2018	Approved
Opera 56.0.3051.88	4228	Monday, October 29, 2018	Approved
Opera 56.0.3051.52	4105	Wednesday, October 17, 2018	Approved
Opera 56.0.3051.36	5189	Tuesday, October 2, 2018	Approved
Opera 56.0.3051.31	3201	Tuesday, September 25, 2018	Approved
Opera 55.0.2994.61	3932	Thursday, September 13, 2018	Approved
Opera 55.0.2994.59	1373	Wednesday, September 12, 2018	Approved
Opera 55.0.2994.56	2457	Thursday, September 6, 2018	Approved
Opera 55.0.2994.44	3359	Thursday, August 23, 2018	Approved
Opera 55.0.2994.37	2774	Thursday, August 16, 2018	Approved
Opera 54.0.2952.71	3015	Tuesday, August 7, 2018	Approved
Opera 54.0.2952.64	3038	Wednesday, July 25, 2018	Approved
Opera 54.0.2952.60	2496	Thursday, July 19, 2018	Approved
Opera 54.0.2952.54	3862	Wednesday, July 11, 2018	Approved
Opera 54.0.2952.51	3068	Friday, July 6, 2018	Approved
Opera 54.0.2952.46	1890	Thursday, July 5, 2018	Approved
Opera 54.0.2952.41	3176	Thursday, June 28, 2018	Approved
Opera 53.0.2907.110	1041	Tuesday, June 26, 2018	Approved
Opera 53.0.2907.106	2180	Thursday, June 21, 2018	Approved
Opera 53.0.2907.99	2811	Tuesday, June 12, 2018	Approved
Opera 53.0.2907.88	12910	Tuesday, June 5, 2018	Approved
Opera 53.0.2907.68	3746	Wednesday, May 23, 2018	Approved
Opera 53.0.2907.57	3135	Wednesday, May 16, 2018	Approved
Opera 53.0.2907.37	2682	Thursday, May 10, 2018	Approved
Opera 52.0.2871.99	3231	Thursday, April 26, 2018	Approved
Opera 52.0.2871.97	1711	Wednesday, April 25, 2018	Approved
Opera 52.0.2871.64	3288	Wednesday, April 11, 2018	Approved
Opera 52.0.2871.40	2731	Thursday, March 29, 2018	Approved
Opera 52.0.2871.37	820	Monday, March 26, 2018	Approved
Opera 52.0.2871.30	2300	Thursday, March 22, 2018	Approved
Opera 51.0.2830.55	2796	Thursday, March 8, 2018	Approved
Opera 51.0.2830.40	3783	Thursday, February 22, 2018	Approved
Opera 51.0.2830.34	5306	Thursday, February 15, 2018	Approved
Opera 51.0.2830.26	5106	Wednesday, February 7, 2018	Approved
Opera 50.0.2762.67	6017	Monday, January 22, 2018	Approved
Opera 50.0.2762.58	4248	Thursday, January 11, 2018	Approved
Opera 50.0.2762.45	3608	Wednesday, January 3, 2018	Approved
Opera 49.0.2725.64	5070	Tuesday, December 19, 2017	Approved
Opera 49.0.2725.56	3224	Monday, December 11, 2017	Approved
Opera 49.0.2725.47	5878	Thursday, November 23, 2017	Approved
Opera 49.0.2725.39	4127	Thursday, November 16, 2017	Approved
Opera 49.0.2725.34	4605	Tuesday, November 7, 2017	Approved
Opera 48.0.2685.52	7083	Tuesday, October 24, 2017	Approved
Opera 48.0.2685.50	2698	Thursday, October 19, 2017	Approved
Opera 48.0.2685.39	4838	Tuesday, October 10, 2017	Approved
Opera 48.0.2685.35	3517	Monday, October 2, 2017	Approved
Opera 48.0.2685.32	2407	Tuesday, September 26, 2017	Approved
Opera 47.0.2631.80	6459	Wednesday, September 6, 2017	Approved
Opera 47.0.2631.71	3258	Friday, August 25, 2017	Approved
Opera 47.0.2631.55	2749	Monday, August 14, 2017	Approved
Opera 47.0.2631.48	1452	Thursday, August 10, 2017	Approved
Opera 47.0.2631.39	1219	Wednesday, August 9, 2017	Approved
Opera 46.0.2597.61	1197	Monday, August 7, 2017	Approved
Opera 46.0.2597.57	3853	Wednesday, July 19, 2017	Approved
Opera 46.0.2597.46	2232	Tuesday, July 11, 2017	Approved
Opera 46.0.2597.39	5850	Tuesday, July 4, 2017	Approved
Opera 46.0.2597.32	1788	Tuesday, June 27, 2017	Approved
Opera 46.0.2597.26	1723	Wednesday, June 21, 2017	Approved
Opera 45.0.2552.898	2556	Tuesday, June 13, 2017	Approved
Opera 45.0.2552.888	2190	Wednesday, May 31, 2017	Approved
Opera 45.0.2552.881	3950	Thursday, May 25, 2017	Approved
Opera 45.0.2552.812	1986	Monday, May 15, 2017	Approved
Opera 45.0.2552.635	1697	Tuesday, May 9, 2017	Approved
Opera 44.0.2510.1457	1809	Friday, April 28, 2017	Approved
Opera 44.0.2510.1449	1196	Tuesday, April 25, 2017	Approved
Opera 44.0.2510.1218	533	Tuesday, April 25, 2017	Approved
Opera 44.0.2510.857	3061	Wednesday, March 22, 2017	Approved
Opera 43.0.2442.991	2717	Tuesday, February 21, 2017	Approved
Opera 43.0.2442.806	3178	Monday, February 6, 2017	Approved
Opera 42.0.2393.94	4007	Monday, December 19, 2016	Approved
Opera 42.0.2393.85	1287	Monday, December 12, 2016	Approved
Opera 41.0.2353.69	2135	Tuesday, November 22, 2016	Approved
Opera 41.0.2353.56	1713	Tuesday, November 8, 2016	Approved
Opera 41.0.2353.46	1771	Monday, October 24, 2016	Approved
Opera 40.0.2308.90	1254	Tuesday, October 18, 2016	Approved
Opera 40.0.2308.81	1658	Monday, October 3, 2016	Approved
Opera 39.0.2256.48	17461	Wednesday, August 3, 2016	Approved
Opera 39.0.2256.43	814	Monday, August 1, 2016	Approved
Opera 38.0.2220.41	926	Sunday, July 10, 2016	Approved
Opera 38.0.2220.31	361	Monday, June 13, 2016	Approved
Opera 38.0.2220.29	350	Tuesday, June 7, 2016	Approved
Opera 37.0.2178.54	359	Monday, May 30, 2016	Approved
Opera 37.0.2178.43	355	Monday, May 9, 2016	Approved
Opera 37.0.2178.32	366	Wednesday, May 4, 2016	Approved
Opera 36.0.2130.65	1457	Monday, April 11, 2016	Approved
Opera 36.0.2130.46	1138	Tuesday, March 29, 2016	Approved
Opera 36.0.2130.32	1317	Monday, March 14, 2016	Approved
Opera 35.0.2066.92	1229	Tuesday, March 1, 2016	Approved
Opera 35.0.2066.82	830	Monday, February 22, 2016	Approved
Opera 35.0.2066.68	777	Tuesday, February 16, 2016	Approved
Opera 35.0.2066.37	1056	Monday, February 1, 2016	Approved
Opera 34.0.2036.50	1062	Tuesday, January 19, 2016	Approved
Opera 34.0.2036.47	833	Monday, January 11, 2016	Approved
Opera 34.0.2036.25	1459	Monday, December 7, 2015	Approved
Opera 33.0.1990.58	1486	Monday, November 2, 2015	Approved
Opera 33.0.1990.43	1076	Monday, October 26, 2015	Approved
Opera 32.0.1948.69	1366	Monday, September 28, 2015	Approved
Opera 32.0.1948.25	1016	Monday, September 14, 2015	Approved
Opera 31.0.1889.99	2306	Monday, August 3, 2015	Approved
Opera 30.0.1835.88	1726	Tuesday, June 23, 2015	Approved
Opera 30.0.1835.59	967	Wednesday, June 10, 2015	Approved
Opera 30.0.1835.52	472	Monday, June 8, 2015	Approved
Opera 29.0.1795.60	1155	Tuesday, May 19, 2015	Approved
Opera 29.0.1795.47	1123	Monday, April 27, 2015	Approved
Opera 28.0.1750.51	1079	Wednesday, April 8, 2015	Approved
Opera 28.0.1750.48	1515	Tuesday, March 17, 2015	Approved
Opera 28.0.1750.40	1100	Monday, March 9, 2015	Approved
Opera 27.0.1689.76	1358	Monday, February 23, 2015	Approved
Opera 27.0.1689.69	1306	Tuesday, February 10, 2015	Approved
Opera 27.0.1689.66	1200	Monday, February 2, 2015	Approved
Opera 27.0.1689.54	1122	Monday, January 26, 2015	Approved
Opera 26.0.1656.60	1612	Wednesday, December 17, 2014	Approved
Opera 26.0.1656.32	834	Monday, December 1, 2014	Approved
Opera 26.0.1656.24	722	Thursday, November 20, 2014	Approved
Opera 25.0.1614.71	563	Monday, November 17, 2014	Approved
Opera 25.0.1614.68	885	Thursday, October 30, 2014	Approved
Opera 25.0.1614.63	629	Monday, October 27, 2014	Approved
Opera 25.0.1614.50	722	Wednesday, October 15, 2014	Approved
Opera 24.0.1558.64	969	Friday, September 26, 2014	Approved
Opera 24.0.1558.61	807	Tuesday, September 16, 2014	Approved
Opera 24.0.1558.53	869	Monday, September 1, 2014	Approved
Opera 23.0.1522.77	715	Monday, August 18, 2014	Approved
Opera 23.0.1522.75	608	Monday, August 11, 2014	Approved
Opera 23.0.1522.72	591	Tuesday, August 5, 2014	Approved
Opera 23.0.1522.60	653	Tuesday, July 22, 2014	Approved
Opera 22.0.1471.70	840	Wednesday, June 18, 2014	Approved
Opera 22.0.1471.50	584	Monday, June 2, 2014	Approved
Opera 21.0.1432.68	436	Wednesday, May 28, 2014	Approved
Opera 21.0.1432.67	591	Tuesday, May 13, 2014	Approved
Opera 21.0.1432.57	528	Monday, May 5, 2014	Approved
Opera 20.0.1387.91	804	Wednesday, April 2, 2014	Approved
Opera 20.0.1387.82	602	Thursday, March 20, 2014	Approved
Opera 20.0.1387.77	577	Wednesday, March 12, 2014	Approved
Opera 20.0.1387.64	546	Tuesday, March 4, 2014	Approved
Opera 19.0.1326.63	561	Wednesday, February 12, 2014	Approved
Opera 19.0.1326.59	585	Monday, February 3, 2014	Approved
Opera 19.0.1326.56	490	Wednesday, January 29, 2014	Approved
Opera 19.0.1326.47	467	Monday, January 27, 2014	Approved
Opera 18.0.1284.68	692	Monday, December 16, 2013	Approved
Opera 18.0.1284.63	465	Friday, December 6, 2013	Approved
Opera 18.0.1284.49	517	Tuesday, November 19, 2013	Approved
Opera 17.0.1241.53	589	Wednesday, October 23, 2013	Approved
Opera 17.0.1241.45	479	Tuesday, October 8, 2013	Approved
Opera 16.0.1196.80	393	Wednesday, September 25, 2013	Approved
Opera 16.0.1196.73	507	Thursday, September 5, 2013	Approved
Opera 15.0.1147.141	666	Thursday, July 18, 2013	Approved
Opera 12.15	1552	Friday, June 28, 2013	Approved
Opera 12.02	1050	Wednesday, September 12, 2012	Approved

Dependencies

This package has no dependencies.

Discussion for the Opera Package

Ground Rules:

This discussion is only about Opera and the Opera 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 Opera, 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.

835,246

833

11 Jan 2016

Opera

1 2 3 Opera 34.0.2036.47

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

Opera 34.0.2036.47