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.2.4.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.2.4.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.2.4.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.2.4.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

Downloads:

26,537

Downloads of v 1.2.17.0-current:

169

Last Update:

24 Apr 2020

Published Date:

24 Apr 2020

Package Maintainer(s):

Vaquero

Software Author(s):

https://github.com/jamovi/jamovi/graphs/contributors

Tags:

data analysis analytics statistics r data-mining

jamovi (portable)

(Pending automated review)

This is a prerelease version of jamovi (portable).

1.2.17.0-current | Updated: 24 Apr 2020

Downloads:

26,537

Downloads of v 1.2.17.0-current:

169

Published:

24 Apr 2020

Maintainer(s):

Vaquero

Software Author(s):

https://github.com/jamovi/jamovi/graphs/contributors

Tags:

data analysis analytics statistics r data-mining

jamovi (portable) 1.2.17.0-current

(Pending automated review)

This is a prerelease version of jamovi (portable).

Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by https://github.com/jamovi/jamovi/graphs/contributors. The inclusion of https://github.com/jamovi/jamovi/graphs/contributors trademark(s), if any, upon this webpage is solely to identify https://github.com/jamovi/jamovi/graphs/contributors goods or services and not for commercial purposes.

This Package Contains an Exempted Check

Not All Tests Have Passed

Hide Checks

Validation Testing Passed

Verification Testing Passed

Details

Scan Testing Exemption for this package version only:

Details

NOTE

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.

IMPORTANT

This version is in moderation and has not yet been approved. This means it doesn't show up under normal search.

Until approved, you should consider this package version unsafe - it could do very bad things to your system (it probably doesn't but you have been warned, that's why we have moderation).
This package version can change wildly over the course of moderation until it is approved. If you install it and it later has changes to this version, you will be out of sync with any changes that have been made to the package. Until approved, you should consider that this package version doesn't even exist.
You cannot install this package under normal scenarios. See How to install package version under moderation for more information.
There are also no guarantees that it will be approved.

WARNING

There are versions of this package awaiting moderation (possibly just this one). See the Version History section below.

Vaquero (maintainer) on 24 Apr 2020 21:31:37 +00:00:

User 'Vaquero' (maintainer) submitted package.

chocolatey-ops (reviewer) on 24 Apr 2020 22:03:32 +00:00:

jamovi.portable has passed automated validation. It may have or may still fail other checks like testing (verification).
Congratulations! This package passed automatic validation review without flagging on any issues the validator currently checks. A human review could still turn up issues a computer may not easily find.

chocolatey-ops (reviewer) on 24 Apr 2020 23:05:16 +00:00:

jamovi.portable has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/ea7748d4860e4185c1fefd5433b9beaa for details.
This is an FYI only. There is no action you need to take. This package is a prerelease, which means it automatically is approved (even if it fails).

Description

STATS MADE SIMPLE

jamovi is a new "3rd generation" statistical spreadsheet. designed from the ground up to be easy to use, jamovi is a compelling alternative to costly statistical products such as SPSS and SAS.

R INTEGRATION:

jamovi is built on top of the R statistical language, giving you access to the best the statistics community has to offer. would you like the R code for your analyses? jamovi can provide that too.

FREE AND OPEN:

jamovi will always be free and open - that's one of our core values - because jamovi is made by the scientific community, for the scientific community.

SOLID vs CURRENT

jamovi offers 2 streams: a solid version recommended for most users, and a current version which has the latest features, but might not be stable.
The current versions are offered as pre-release packages on chocolatey. Get it by using choco install jamovi.portable --pre

Files

tools\chocolateyInstall.ps1

$ErrorActionPreference = 'Stop'

$packageArgs = @{
  packageName    = 'jamovi.portable'
  UnzipLocation  = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
  url64bit       = 'https://www.jamovi.org/downloads/jamovi-1.2.17.0-win64.zip'
  checksum64     = 'ddcd5593656c7da30bcc9e4e858fe1314bad8b7fdcd62d65cb995575ccd60df1'
  checksumType64 = 'sha256'
}

Install-ChocolateyZipPackage @packageArgs

$installDir = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
$files = get-childitem $installDir -include *.exe -recurse

foreach ($file in $files) {
  if (!($file.Name.Contains("jamovi.exe"))) {
    #generate an ignore file
    New-Item "$file.ignore" -type file -force | Out-Null
  }
  else{
    New-Item "$file.gui" -type file -force | Out-Null
  }
}

Virus Scan Results

node1.exe (74abfa53909b) - ## / 61
msvcp140.dll (517cd3aac217) - ## / 66
sample.xml.gz (fc0a69d302a9) - ## / 58
nanomsg.dll (1c4d55153092) - ## / 67
dtd.zip (4dae42863eb0) - ## / 59
eurofxref-hist.xml.gz (bcf3368a39f7) - ## / 42
xyz.svg.gz (0b872fcea541) - ## / 46
tcl86.dll (f01d84354fcc) - ## / 69
tclsh86.exe (8d85e33fd8c3) - ## / 71
tk86.dll (d257b3d742ec) - ## / 70
wish86.exe (26dbdd5b677e) - ## / 70
zlib1.dll (e81068997681) - ## / 71
tcldde14.dll (b7e43c620e8a) - ## / 69
itcl403.dll (ca3650fa8a13) - ## / 69
tclreg13.dll (cb6c899df52b) - ## / 70
sqlite3883.dll (96f24fdc02b8) - ## / 69
tdbc103.dll (f3eb20e4c7ee) - ## / 69
tdbcmysql103.dll (e2ac8759545e) - ## / 69
tdbcodbc103.dll (b424d3f3da9a) - ## / 68
tdbcpostgres103.dll (1f1cffba906f) - ## / 70
thread272.dll (b17c8d8007aa) - ## / 70
Tktable211.dll (69432a78acee) - ## / 67
ucrtbase.dll (d804ea40eacf) - ## / 63
mtcars.csv.zip (384e3398cfed) - ## / 56
libcrypto-1_1-x64.dll (2a57183839c3) - ## / 67
libssl-1_1-x64.dll (9d35d8dd9854) - ## / 70
vcruntime140.dll (6cadb4fef773) - ## / 71
d3dcompiler_47.dll (dca0cd7272a5) - ## / 72
allchar.csv.gz (24b573930bdf) - ## / 56
ddaspkcomments.txt.gz (69d270103b5b) - ## / 46
grr.csv.gz (285335e62e46) - ## / 58
issue_2157_sampling_overlap.txt.gz (8c94661f3ac9) - ## / 57
libansari.R6EA3HQP5KZ6TAXU4Y4ZVTRPT7UVA53Z.gfortran-win_amd64.dll (d798cb032816) - ## / 68
libbanded5x.YUREFBE7I7SVCEADSLRKXT6OOZGRBSI4.gfortran-win_amd64.dll (c8865a97a5c8) - ## / 68
libbispeu.5N2XSD7URZS4WTOSLTOG4DDMA4HGB46U.gfortran-win_amd64.dll (84bbc24393d9) - ## / 69
libblkdta00.5GIEOPPZ5HSTP5DAMUKWIW364O4QBFMY.gfortran-win_amd64.dll (231e4d41177f) - ## / 69
libchkder.6HLXPVTQJEGRZGLI5DFRMNW3SS76BHP6.gfortran-win_amd64.dll (aca4cdf16390) - ## / 69
libcobyla2.JEGTSUUFJ7DFXWZN5PAYZTTLBDATC4WD.gfortran-win_amd64.dll (97d979475bb3) - ## / 71
libdcosqb.K4J3XBR4PEETMRHZICUWW4LXG5UONZ34.gfortran-win_amd64.dll (16ef4772db31) - ## / 69
libdcosqb.QRGA36MB6CFHWLQN6ETWARR4M4E6P3C2.gfortran-win_amd64.dll (b43955952e69) - ## / 70
libdcsrch.I2AOPDCXAPDRFNPWY55H5UE7XZSU5CVN.gfortran-win_amd64.dll (06b822021aae) - ## / 69
libdet.NGI4SZSHQBJM5NEVUSJQND4WM2GMQE54.gfortran-win_amd64.dll (7eea674feaf2) - ## / 69
libdfft_sub.H6SHLMT5W26CD2XUAFVQ3LOOJUC4U4T4.gfortran-win_amd64.dll (93ec92e68cc0) - ## / 70
libdfitpack.PJU6IBGOYZCWITNVROHYOQAYNGAXO3HT.gfortran-win_amd64.dll (c4869a0f5d37) - ## / 68
libdgamln.KTXSQTWP7LWG4EZMWBS4LH477BS6ZGYC.gfortran-win_amd64.dll (b897cbb13c0f) - ## / 70
libdop853.6TJTQZW3I3Q3QIDQHEOBEZKJ3NYRXI4B.gfortran-win_amd64.dll (7bfc28bee3b6) - ## / 69
libdqag.VX5QPGEJYMIC5JGWBYFC5BHJCBBVPPDV.gfortran-win_amd64.dll (48ca2f7e3fd8) - ## / 70
libd_odr.KVFHIZPGUGII2ECJE7R2OHXK5HXMWUBQ.gfortran-win_amd64.dll (7c700cbf52d0) - ## / 71
libgetbreak.A6HULTPFZ6I2MFB4CVJ5HQKTG6FYIBPY.gfortran-win_amd64.dll (ba539c698fb5) - ## / 70
liblbfgsb.B2GDIH5ZLORB7V6SRZRPDJE26PPONKZC.gfortran-win_amd64.dll (e688bf81fe55) - ## / 69
libmvndst.RBJKFH65GH3A3NKEATRJ523P6WF4AZAG.gfortran-win_amd64.dll (86f5ccf78df4) - ## / 69
libnnls.IXEEHJUCGHJL42YZEM6UIEMROJWXHMLJ.gfortran-win_amd64.dll (0edf5345d0a5) - ## / 70
libopenblas.BNVRK7633HSX7YVO2TADGR4A5KEKXJAW.gfortran-win_amd64.dll (f7cd3b4281e0) - ## / 70
libopenblas.CSRRD7HKRKC3T3YXA7VY7TAZGLSWDKW6.gfortran-win_amd64.dll (48bfafb126cc) - ## / 69
libslsqp_op.NNY57ZXZ43A4RH3YWFA7BKHP5PC2K3I5.gfortran-win_amd64.dll (020a64d9f5cf) - ## / 69
libspecfun.BHLTWMBI4EYWDACZN4DQUESSDJRJNGEL.gfortran-win_amd64.dll (a1bd112f977c) - ## / 69
libvode.4H2RO3B5HKRH6QPBU4GYYKK3YPWS7OUR.gfortran-win_amd64.dll (76a346c3fcd4) - ## / 70
libwrap_dum.43IN5WJ7HGVGKYPFVJK5YQ34OMH3IKLA.gfortran-win_amd64.dll (70612a54c094) - ## / 68
libwrap_dum.V5FHT5OP45YBBACXAHY3NF5CISQJNFFQ.gfortran-win_amd64.dll (eda13f54a91c) - ## / 68
lib_arpack-.3EACCC44R6URYOMHQMYVCKQCOM2QIBWU.gfortran-win_amd64.dll (adc5958412bc) - ## / 71
lib_blas_su.QEQE75KHNLMPCS22K3WRCEACXGLTB6HX.gfortran-win_amd64.dll (be26e799fab1) - ## / 69
lib_test_fo.JF5HTWMUPBXWGAYEBVEJU3OZAHTSVKCT.gfortran-win_amd64.dll (b923866b2b90) - ## / 70
logo.svg.gz (1958f9a60c33) - ## / 57
opkdmain.f.gz (88d1829de4ce) - ## / 47
opkdmaincomments.txt.gz (6f80f95c8534) - ## / 46
tli.txt.gz (705694e23388) - ## / 54
vodecomments.txt.gz (0e12f92be30e) - ## / 46
libcrypto-1_1.dll (95e3e9a86da6) - ## / 72
libssl-1_1.dll (0c9573ee9605) - ## / 69
python3.dll (6ab5afb9b0af) - ## / 71
python37.dll (8eb835d88e72) - ## / 71
python.exe (c8ab37abfa5e) - ## / 73
python37.zip (6661f13e0df5) - ## / 60
pythonw.exe (e095899451ef) - ## / 72
sqlite3.dll (45ad9162c374) - ## / 72
a010013l.afm.gz (ab1d54dffda0) - ## / 60
a010015l.afm.gz (61605acf3f09) - ## / 57
a010033l.afm.gz (a068f011252a) - ## / 60
a010035l.afm.gz (ddacbd12decb) - ## / 59
acepack.dll (bb17701b15d9) - ## / 63
agdo____.afm.gz (b36d6e071d75) - ## / 58
agd_____.afm.gz (719c23aeb3e8) - ## / 59
agwo____.afm.gz (4c257e8b1a68) - ## / 59
agw_____.afm.gz (a6268e29be24) - ## / 58
alluniquechar.csv.gz (99702619a0f4) - ## / 60
ArialMT-Bold.afm.gz (887eab594ae8) - ## / 57
ArialMT-BoldItalic.afm.gz (9b2d2f2cf416) - ## / 58
ArialMT-Italic.afm.gz (25ec795e0215) - ## / 60
ArialMT.afm.gz (d3007e1330fb) - ## / 60
b018012l.afm.gz (6de0158a9366) - ## / 59
b018015l.afm.gz (ae466ac74c54) - ## / 60
b018032l.afm.gz (5abd428a9372) - ## / 59
b018035l.afm.gz (88ea86043f87) - ## / 59
backports.dll (386897f1fcc9) - ## / 71
base64enc.dll (1243832efff3) - ## / 67
BayesFactor.dll (8fc04a3c271e) - ## / 71
BDgraph.dll (491ccb888f14) - ## / 70
bitops.dll (2525b188c692) - ## / 69
bkdi____.afm.gz (011d9c1bc488) - ## / 59
bkd_____.afm.gz (32013b9cdaf3) - ## / 60
bkli____.afm.gz (c87d848dd643) - ## / 59
bkl_____.afm.gz (da7fc7796e38) - ## / 58
c059013l.afm.gz (e8ef4e83c421) - ## / 59
c059016l.afm.gz (21005d5a64c3) - ## / 60
c059033l.afm.gz (b6cc9982a40b) - ## / 58
c059036l.afm.gz (f05469a3d713) - ## / 60
caTools.dll (0602ad97725a) - ## / 71
checkmate.dll (70a67ed0d0bd) - ## / 72
class.dll (c04402f81d7a) - ## / 71
client.dll (0ac58f851f78) - ## / 70
cluster.dll (dba6858b2e1d) - ## / 69
cmbxti10.afm.gz (8b3fe891756e) - ## / 60
cmdunzip.exe (fad502aacb80) - ## / 73
cmdzip.exe (caaaef760f4a) - ## / 73
cmti10.afm.gz (5e6447438ff6) - ## / 59
CM_boldx_10.afm.gz (33100277fe99) - ## / 60
CM_boldx_italic_10.afm.gz (def1f30a6b8d) - ## / 58
CM_italic_10.afm.gz (7593d55cc2ca) - ## / 60
CM_regular_10.afm.gz (3ec4c59b1b8b) - ## / 59
CM_symbol_10.afm.gz (099bc08c8621) - ## / 60
cobo____.afm.gz (904148500571) - ## / 59
cob_____.afm.gz (4eab587f05c1) - ## / 60
colorspace.dll (2dfec8a9a5f6) - ## / 72
com_____.afm.gz (4ffe6daa38af) - ## / 60
contfrac.dll (43aba977806a) - ## / 71
coo_____.afm.gz (f321b5a4fbbf) - ## / 60
Courier-Bold.afm.gz (df77c04eda3a) - ## / 59
Courier-BoldOblique.afm.gz (090f07850206) - ## / 60
Courier-Oblique.afm.gz (5881a3fae0dd) - ## / 60
Courier.afm.gz (f35e6f2f8dbe) - ## / 60
curl.dll (c22578bb2b38) - ## / 72
datatable.dll (034475cd5230) - ## / 72
deSolve.dll (3c1f030209c5) - ## / 71
digest.dll (f2fe10bf11e0) - ## / 71
dplyr.dll (dbff1f5e66fd) - ## / 71
ellipsis.dll (a5f8b0a01acd) - ## / 72
example.zip (1f38b3c2da3b) - ## / 58
fansi.dll (f6985465d8da) - ## / 72
farver.dll (6810502e4106) - ## / 71
fdrtool.dll (367d47975607) - ## / 70
foreign.dll (3bb7684c1faa) - ## / 69
ggforce.dll (6c0481ead636) - ## / 68
ggraph.dll (19c323c15446) - ## / 72
ggrepel.dll (01be912f94ee) - ## / 72
glasso.dll (0d8d02e597fd) - ## / 71
glue.dll (6b22b8e50edc) - ## / 72
gnm.dll (c0fb478d8ee3) - ## / 72
graphics.dll (815e8cb54afb) - ## / 69
graphlayouts.dll (4ae4b7c57fb2) - ## / 70
grDevices.dll (60758db369ce) - ## / 70
grid.dll (c851a830b5f2) - ## / 68
gtools.dll (2cc68ee93428) - ## / 69
haven.dll (7445239afa70) - ## / 68
Helvetica-Bold.afm.gz (a6efefddf287) - ## / 60
Helvetica-BoldOblique.afm.gz (33a7ebb04ccc) - ## / 59
Helvetica-Oblique.afm.gz (1d37f0e76c13) - ## / 60
Helvetica.afm.gz (88ba9ced907b) - ## / 59
Hmisc.dll (eeaaf91f6ffc) - ## / 70
htmltools.dll (84a03d639f00) - ## / 72
huge.dll (ce583e1bdb44) - ## / 71
hvbo____.afm.gz (ced054321186) - ## / 59
hvb_____.afm.gz (a0117c92ce23) - ## / 59
hvnbo___.afm.gz (378d2a59c6fd) - ## / 60
hvnb____.afm.gz (7144b1337264) - ## / 59
hvno____.afm.gz (a815d81b984e) - ## / 59
hvn_____.afm.gz (3b1b8023daa6) - ## / 60
hvo_____.afm.gz (5a2b7279f657) - ## / 59
hv______.afm.gz (d9b93feded7a) - ## / 59
igraph.dll (668105cd2923) - ## / 72
internet.dll (66b169ad5de3) - ## / 70
interrupt.exe (b7c322c8a8a4) - ## / 73
issue_1116_fread_few_lines.txt.gz (2ae9f547e997) - ## / 59
issue_1116_fread_few_lines_2.txt.gz (e2aa81cb65d7) - ## / 59
issue_1462_fread_quotes.txt.gz (7d14eb4a817d) - ## / 59
issue_2051.csv.gz (35bb7281318f) - ## / 59
issue_785_fread.txt.gz (f30e6c6bff23) - ## / 57
jpeg.dll (5ae7eb43d35e) - ## / 70
jsonlite.dll (5fe386c94c08) - ## / 71
KernSmooth.dll (e5d6fc8c827b) - ## / 69
lapack.dll (0787b4864240) - ## / 71
lattice.dll (a9b1c08b4d49) - ## / 68
lazyeval.dll (d936909462f3) - ## / 72
libRInside.dll (5ddd18efad9d) - ## / 72
lme4.dll (b3d3bd0a1363) - ## / 72
lmtest.dll (0df3be28edff) - ## / 72
maptools.dll (2d6aeb159873) - ## / 72
markdown.dll (8b7a6b182e6f) - ## / 72
MASS.dll (5ec2ab3cd963) - ## / 70
Matrix.dll (c2e80481ce7b) - ## / 69
melt-warning-1752.tsv.gz (0cc817182187) - ## / 60
melt_1754.R.gz (c5e04053bca8) - ## / 60
methods.dll (1fe627b022c8) - ## / 69
mgcv.dll (7dfc9142954e) - ## / 68
mime.dll (ab557ac4d753) - ## / 68
minqa.dll (13ae882a3cdf) - ## / 71
mnormt.dll (dbbfc42d22be) - ## / 69
mvtnorm.dll (e6a9fb534bea) - ## / 69
n019003l.afm.gz (28b5f8ebb333) - ## / 60
n019004l.afm.gz (80071005afda) - ## / 60
n019023l.afm.gz (2e7317073f77) - ## / 60
n019024l.afm.gz (6c502a155ce6) - ## / 59
n019043l.afm.gz (32f737b28684) - ## / 57
n019044l.afm.gz (3af870dda707) - ## / 60
n019063l.afm.gz (4045ec4641bb) - ## / 58
n019064l.afm.gz (b666fa52f2ba) - ## / 59
n021003l.afm.gz (20b3e06d83f8) - ## / 59
n021004l.afm.gz (3f0df0a9956a) - ## / 59
n021023l.afm.gz (248953867b08) - ## / 60
n021024l.afm.gz (54e5514a9cc9) - ## / 59
n022003l.afm.gz (d6c7f802d600) - ## / 59
n022004l.afm.gz (0ac15426b493) - ## / 60
n022023l.afm.gz (5be8abcc1ab8) - ## / 59
n022024l.afm.gz (c3ba10174473) - ## / 60
ncbi____.afm.gz (b816f8e422a2) - ## / 59
ncb_____.afm.gz (8c48094e9023) - ## / 59
nci_____.afm.gz (ddcf2d17f8e9) - ## / 59
ncr_____.afm.gz (b685dae8d990) - ## / 60
nlme.dll (2e80b6620974) - ## / 69
nloptr.dll (92f29a32ef79) - ## / 71
nnet.dll (1b5b2e783f9d) - ## / 69
noquote.csv.gz (88a0b3e72a69) - ## / 60
open.exe (ec4e130ae45a) - ## / 70
OpenMx.dll (6f0a4c8b702e) - ## / 70
openxlsx.dll (74eeefde7f6d) - ## / 71
p052003l.afm.gz (c36df0c10161) - ## / 59
p052004l.afm.gz (16791604ef7c) - ## / 60
p052023l.afm.gz (a47f9d312a65) - ## / 59
p052024l.afm.gz (ac1ebc4436c4) - ## / 60
parallel.dll (c152f0dcb7be) - ## / 70
pbivnorm.dll (23d8e0aed00c) - ## / 70
pkgload.dll (bcfb3cc71aa0) - ## / 69
plyr.dll (369960845c10) - ## / 71
png.dll (707aa6646473) - ## / 69
pobi____.afm.gz (e9d00da1192c) - ## / 60
pob_____.afm.gz (d585f2513c1e) - ## / 59
poi_____.afm.gz (c620e400492f) - ## / 60
polyclip.dll (6897c5c36216) - ## / 70
por_____.afm.gz (54ccc57c4419) - ## / 60
processx.dll (378c813676f6) - ## / 68
ps.dll (5eff1204d03e) - ## / 72
purrr.dll (5376569e4a8d) - ## / 72
px.exe (71dae6d18ae4) - ## / 73
qgraph.dll (1847118a9a7e) - ## / 71
quantreg.dll (4470bd622a54) - ## / 72
R.dll (b7ed9565618f) - ## / 70
R.exe (06aa21f3e49d) - ## / 69
Rblas.dll (b5b9a3cc2523) - ## / 69
Rcmd.exe (3b5c7bd25fe5) - ## / 72
Rcpp.dll (77cc477601c0) - ## / 72
RcppArmadillo.dll (7213f1ddc07c) - ## / 71
RcppEigen.dll (adf64b2652cb) - ## / 71
RCurl.dll (8b9d170c8d74) - ## / 69
readr.dll (4c63fafdc0ac) - ## / 72
readxl.dll (aae8d4d9cbb2) - ## / 71
regsem.dll (4f82dffd2e21) - ## / 72
reshape2.dll (d2ef00c040be) - ## / 71
Rfe.exe (6e91c6c0cf3b) - ## / 69
Rgraphapp.dll (ec9b1db99e77) - ## / 70
Rgui.exe (aaa174ca229b) - ## / 72
Riconv.dll (6f916c47753a) - ## / 68
RInside.dll (208bc875394c) - ## / 72
rjson.dll (1fd0c26aec60) - ## / 70
rlang.dll (01bbd4f8cef8) - ## / 69
Rlapack.dll (1b3f7871e300) - ## / 69
rpart.dll (b92737bd0c01) - ## / 70
rpf.dll (b29281703645) - ## / 71
RProtoBuf.dll (98eb4bdaacf4) - ## / 72
Rscript.exe (471e51645bcb) - ## / 73
RSetReg.exe (52d743de77f7) - ## / 71
Rterm.exe (02c823c22aa0) - ## / 73
s050000l.afm.gz (898e3b3adc5f) - ## / 59
SA2-by-DJZ.csv.gz (ea8d3f9d5d89) - ## / 60
sem.dll (d132c140a6e1) - ## / 72
sp.dll (a394a1145dd5) - ## / 72
SparseM.dll (b4a2e29ab010) - ## / 72
spatial.dll (2d9a6bce1b57) - ## / 71
splines.dll (f4aed02f4676) - ## / 68
StanHeaders.dll (777f30eaba25) - ## / 72
stats.dll (04b9ab9296c9) - ## / 69
stringi.dll (affad45d962b) - ## / 70
supervisor.exe (716423d9858b) - ## / 72
survival.dll (bf085b5e2035) - ## / 70
Symbol.afm.gz (38ac2bcabe1a) - ## / 59
sy______.afm.gz (45f843a34f0e) - ## / 60
tcltk.dll (655590daaa3c) - ## / 69
tibble.dll (67474b78c6bd) - ## / 72
tibi____.afm.gz (7bd163f20e4c) - ## / 60
tib_____.afm.gz (e030c2996a50) - ## / 60
tidygraph.dll (444e96d75843) - ## / 72
tidyr.dll (943528ef2dca) - ## / 72
tidyselect.dll (be75c2d98f6a) - ## / 72
tii_____.afm.gz (c82c565406cc) - ## / 59
Times-Bold.afm.gz (9e72588497a4) - ## / 59
Times-BoldItalic.afm.gz (484fa9bad017) - ## / 59
Times-Italic.afm.gz (2a4568814b97) - ## / 59
Times-Roman.afm.gz (1bfba3c3bea7) - ## / 59
tir_____.afm.gz (4a45785135b4) - ## / 59
tools.dll (78bef98839ce) - ## / 70
truncnorm.dll (cff8ebf63ffd) - ## / 72
tweenr.dll (afe2ddce6486) - ## / 72
unins000.exe (6ee11932317d) - ## / 70
utf8.dll (1283b7d5ac16) - ## / 72
utils.dll (1d70bb0ca6d1) - ## / 69
vctrs.dll (d532bef3549f) - ## / 71
winCairo.dll (edecc52c346e) - ## / 69
XML.dll (83cef8f5f425) - ## / 68
yaml.dll (04152b986e8d) - ## / 69
ZapfDingbats.afm.gz (f4f870c40bf5) - ## / 60
zip.dll (971668bcb9f2) - ## / 72
zoo.dll (8df25fb849c1) - ## / 72
ffmpeg.dll (a6c69e80e201) - ## / 72
jamovi.exe (c81344937e51) - ## / 72
libEGL.dll (ecbe73c2ce44) - ## / 72
libGLESv2.dll (54bce1915169) - ## / 72
isoband.dll (057a3b26702d) - ## / 72
testthat.dll (7e6ad86d11e7) - ## / 71
jamovi.portable.1.2.17.0-current.nupkg (0dcc578ac23c) - ## / 63
jamovi-engine.exe (c95f99b2ad38) - ## / 73

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
jamovi (portable) 2.5.2.0-current	52	Wednesday, April 10, 2024	Exempted
jamovi (portable) 2.4.14.0-current	43	Saturday, February 10, 2024	Exempted
jamovi (portable) 2.4.11.0-current	71	Monday, October 23, 2023	Exempted
jamovi (portable) 2.4.8.0-current	71	Thursday, August 24, 2023	Exempted
jamovi (portable) 2.4.6.0-current	66	Monday, August 14, 2023	Approved
jamovi (portable) 2.4.5.0-current	40	Sunday, August 6, 2023	Exempted
jamovi (portable) 2.4.4.0-current	59	Thursday, August 3, 2023	Exempted
jamovi (portable) 2.4.2.0-current	51	Friday, July 28, 2023	Exempted
jamovi (portable) 2.4.1.0-current	50	Friday, July 14, 2023	Exempted
jamovi (portable) 2.4.0.0-current	53	Monday, July 10, 2023	Exempted
jamovi (portable) 2.3.28.0	82	Monday, July 10, 2023	Approved
jamovi (portable) 2.3.28.0-current	73	Thursday, May 25, 2023	Approved
jamovi (portable) 2.3.26.0	56	Thursday, May 25, 2023	Approved
jamovi (portable) 2.3.26.0-current	53	Tuesday, April 11, 2023	Approved
jamovi (portable) 2.3.24.0-current	62	Wednesday, February 15, 2023	Exempted
jamovi (portable) 2.3.23.0-current	60	Saturday, February 11, 2023	Approved
jamovi (portable) 2.3.21.0	69	Wednesday, December 7, 2022	Approved
jamovi (portable) 2.3.21.0-current	58	Wednesday, December 7, 2022	Approved
jamovi (portable) 2.3.19.0	67	Saturday, December 3, 2022	Approved
jamovi (portable) 2.3.19.0-current	44	Saturday, December 3, 2022	Approved
jamovi (portable) 2.3.18.0-current	67	Monday, October 10, 2022	Approved
jamovi (portable) 2.3.17.0	77	Wednesday, October 5, 2022	Approved
jamovi (portable) 2.3.17.0-current	65	Friday, September 30, 2022	Exempted
jamovi (portable) 2.3.16.0-current	76	Friday, August 19, 2022	Exempted
jamovi (portable) 2.3.15.0-current	72	Wednesday, August 10, 2022	Exempted
jamovi (portable) 2.3.13.0-current	81	Wednesday, June 22, 2022	Exempted
jamovi (portable) 2.3.12.0-current	69	Wednesday, June 1, 2022	Exempted
jamovi (portable) 2.3.11.0-current	68	Monday, May 30, 2022	Exempted
jamovi (portable) 2.3.9.0-current	72	Sunday, May 8, 2022	Exempted
jamovi (portable) 2.3.7.0-current	67	Thursday, May 5, 2022	Exempted
jamovi (portable) 2.3.6.0-current	64	Monday, April 25, 2022	Exempted
jamovi (portable) 2.3.5.0-current	66	Wednesday, April 20, 2022	Exempted
jamovi (portable) 2.3.2.0-current	91	Sunday, March 13, 2022	Exempted
jamovi (portable) 2.3.0.0-current	79	Wednesday, February 9, 2022	Exempted
jamovi (portable) 2.2.5.0	130	Thursday, December 30, 2021	Exempted
jamovi (portable) 2.2.5.0-current	79	Tuesday, December 14, 2021	Exempted
jamovi (portable) 2.2.3.0-current	108	Tuesday, November 23, 2021	Exempted
jamovi (portable) 2.2.2.0-current	108	Monday, October 18, 2021	Exempted
jamovi (portable) 2.2.1.0-current	79	Monday, October 11, 2021	Exempted
jamovi (portable) 2.0.0.0-current	107	Monday, July 12, 2021	Exempted
jamovi (portable) 1.8.4.0-current	117	Thursday, June 10, 2021	Exempted
jamovi (portable) 1.8.2.0-current	94	Monday, May 24, 2021	Exempted
jamovi (portable) 1.8.1.0-current	117	Monday, April 19, 2021	Approved
jamovi (portable) 1.8.0.0-current	112	Friday, April 9, 2021	Approved
jamovi (portable) 1.6.23.0	129	Saturday, April 17, 2021	Approved
jamovi (portable) 1.6.22.0-current	106	Tuesday, April 6, 2021	Approved
jamovi (portable) 1.6.21.0-current	118	Tuesday, March 23, 2021	Exempted
jamovi (portable) 1.6.16.0-current	169	Wednesday, February 17, 2021	Approved
jamovi (portable) 1.6.15.0	102	Wednesday, February 17, 2021	Approved
jamovi (portable) 1.6.14.0-current	123	Tuesday, February 9, 2021	Exempted
jamovi (portable) 1.6.13.0-current	134	Saturday, January 23, 2021	Approved
jamovi (portable) 1.6.12.0-current	120	Sunday, January 17, 2021	Exempted
jamovi (portable) 1.6.11.0-current	149	Wednesday, January 13, 2021	Approved
jamovi (portable) 1.6.10.0-current	142	Monday, January 11, 2021	Exempted
jamovi (portable) 1.6.9.0-current	146	Saturday, December 19, 2020	Approved
jamovi (portable) 1.6.8.0-current	139	Wednesday, December 2, 2020	Approved
jamovi (portable) 1.6.7.0-current	132	Friday, November 20, 2020	Exempted
jamovi (portable) 1.6.6.0-current	123	Wednesday, November 4, 2020	Exempted
jamovi (portable) 1.6.5.0-current	139	Friday, October 30, 2020	Exempted
jamovi (portable) 1.6.4.0-current	144	Sunday, October 25, 2020	Exempted
jamovi (portable) 1.6.3.0-current	141	Wednesday, September 9, 2020	Approved
jamovi (portable) 1.6.1.0-current	161	Tuesday, September 1, 2020	Approved
jamovi (portable) 1.6.0.0-current	168	Monday, August 31, 2020	Approved
jamovi (portable) 1.2.27.0	175	Monday, August 31, 2020	Approved
jamovi (portable) 1.2.26.0-current	143	Friday, August 21, 2020	Exempted
jamovi (portable) 1.2.25.0-current	158	Thursday, July 30, 2020	Approved
jamovi (portable) 1.2.24.0-current	147	Monday, July 27, 2020	Approved
jamovi (portable) 1.2.22.20200530-current	183	Saturday, May 30, 2020	Approved
jamovi (portable) 1.2.22.0-current	146	Thursday, May 28, 2020	Exempted
jamovi (portable) 1.2.21.0-current	143	Saturday, May 23, 2020	Approved
jamovi (portable) 1.2.19.0-current	152	Tuesday, May 19, 2020	Approved
jamovi (portable) 1.2.18.0-current	142	Sunday, May 17, 2020	Approved
jamovi (portable) 1.2.17.0-current	169	Friday, April 24, 2020	Pending Automated Review
jamovi (portable) 1.2.16.0-current	193	Friday, April 3, 2020	Approved
jamovi (portable) 1.2.12.0-current	156	Wednesday, March 25, 2020	Approved
jamovi (portable) 1.2.11.0-current	178	Monday, March 23, 2020	Approved
jamovi (portable) 1.2.9.0-current	187	Thursday, March 12, 2020	Approved
jamovi (portable) 1.2.8.0-current	181	Tuesday, March 10, 2020	Approved
jamovi (portable) 1.2.7.0-current	185	Saturday, March 7, 2020	Approved
jamovi (portable) 1.2.6.0-current	191	Friday, March 6, 2020	Pending Automated Review
jamovi (portable) 1.2.2.0-current	195	Friday, January 17, 2020	Approved
jamovi (portable) 1.2.1.0-current	191	Thursday, January 16, 2020	Approved
jamovi (portable) 1.2.0.0-current	213	Saturday, January 4, 2020	Approved
jamovi (portable) 1.1.9.0	313	Saturday, January 4, 2020	Approved
jamovi (portable) 1.1.9.0-current	194	Friday, December 13, 2019	Approved
jamovi (portable) 1.1.8.0-current	175	Thursday, November 28, 2019	Approved
jamovi (portable) 1.1.7.000-current	213	Friday, November 8, 2019	Approved
jamovi (portable) 1.0.7.000	240	Saturday, August 24, 2019	Approved
jamovi (portable) 1.0.5.000	153	Thursday, July 25, 2019	Approved
jamovi (portable) 1.0.4.000	197	Tuesday, July 9, 2019	Approved
jamovi (portable) 1.0.3.000	186	Monday, July 8, 2019	Approved
jamovi (portable) 1.0.1.000	187	Friday, June 14, 2019	Approved
jamovi (portable) 1.0.0.000	202	Friday, May 24, 2019	Approved
jamovi (portable) 0.9.6.900	222	Tuesday, April 16, 2019	Approved
jamovi (portable) 0.9.6.700	184	Wednesday, April 10, 2019	Approved
jamovi (portable) 0.9.5.1200	223	Saturday, January 19, 2019	Approved
jamovi (portable) 0.9.2.800	264	Monday, October 8, 2018	Approved
jamovi (portable) 0.9.1.1100	260	Monday, August 6, 2018	Approved
jamovi (portable) 0.9.1.1000	262	Thursday, July 26, 2018	Approved
jamovi (portable) 0.9.1.900	247	Wednesday, July 25, 2018	Approved
jamovi (portable) 0.9.1.700	264	Friday, July 13, 2018	Approved
jamovi (portable) 0.9.1.600	260	Friday, July 6, 2018	Approved
jamovi (portable) 0.9.1.400	269	Thursday, June 21, 2018	Approved
jamovi (portable) 0.9.1.300	299	Friday, June 15, 2018	Approved
jamovi (portable) 0.9.1.100	264	Wednesday, June 13, 2018	Approved
jamovi (portable) 0.9.1.000	311	Friday, June 8, 2018	Approved
jamovi (portable) 0.9.0.500	285	Tuesday, May 15, 2018	Approved
jamovi (portable) 0.9.0.300	287	Sunday, April 29, 2018	Approved
jamovi (portable) 0.9.0.100	295	Thursday, April 26, 2018	Approved
jamovi (portable) 0.8.6.000	345	Friday, March 30, 2018	Approved
jamovi (portable) 0.8.5.000	317	Tuesday, March 20, 2018	Approved
jamovi (portable) 0.8.4.000	309	Monday, March 19, 2018	Approved
jamovi (portable) 0.8.3.000	326	Friday, March 2, 2018	Approved
jamovi (portable) 0.8.2.200	300	Tuesday, February 20, 2018	Approved
jamovi (portable) 0.8.2.000	320	Wednesday, February 14, 2018	Approved
jamovi (portable) 0.8.1.2000	266	Saturday, February 10, 2018	Approved
jamovi (portable) 0.8.1.1900	290	Friday, February 9, 2018	Approved
jamovi (portable) 0.8.1.1700	319	Sunday, February 4, 2018	Approved
jamovi (portable) 0.8.1.1400	336	Saturday, January 20, 2018	Approved
jamovi (portable) 0.8.1.1300	344	Monday, January 8, 2018	Approved
jamovi (portable) 0.8.1.1200	355	Monday, December 18, 2017	Approved
jamovi (portable) 0.8.1.1000	362	Monday, November 27, 2017	Approved
jamovi (portable) 0.8.1.800	368	Wednesday, November 22, 2017	Approved
jamovi (portable) 0.8.1.700	389	Saturday, November 18, 2017	Approved
jamovi (portable) 0.8.1.600	348	Tuesday, November 14, 2017	Approved
jamovi (portable) 0.8.1.500	324	Saturday, November 11, 2017	Approved
jamovi (portable) 0.8.1.000	323	Monday, October 30, 2017	Approved
jamovi (portable) 0.8.0.900	364	Sunday, October 8, 2017	Approved
jamovi (portable) 0.8.0.200	389	Thursday, September 7, 2017	Approved
jamovi (portable) 0.7.5.700	388	Wednesday, August 16, 2017	Approved
jamovi (portable) 0.7.5.600	344	Monday, August 7, 2017	Approved
jamovi (portable) 0.7.5.400	357	Wednesday, July 26, 2017	Approved
jamovi (portable) 0.7.5.200	355	Thursday, July 6, 2017	Approved
jamovi (portable) 0.7.5.100	334	Wednesday, June 28, 2017	Approved
jamovi (portable) 0.7.3.500	390	Wednesday, June 7, 2017	Approved
jamovi (portable) 0.7.3.300	337	Wednesday, May 31, 2017	Approved
jamovi (portable) 0.7.3.200	346	Wednesday, May 17, 2017	Approved
jamovi (portable) 0.7.3.100	330	Wednesday, May 10, 2017	Approved
jamovi (portable) 0.7.3.000	330	Wednesday, May 3, 2017	Approved
jamovi (portable) 0.7.2.700	355	Tuesday, April 4, 2017	Approved
jamovi (portable) 0.7.2.6	350	Tuesday, March 28, 2017	Approved

Release Notes

https://www.jamovi.org/release-notes.html

Dependencies

This package has no dependencies.

Discussion for the jamovi (portable) Package

Ground Rules:

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

Resources

Events

Courses

26,537

169

24 Apr 2020

24 Apr 2020

jamovi (portable)

jamovi (portable) 1.2.17.0-current

(Pending automated review)

This Package Contains an Exempted Check

Vaquero (maintainer) on 24 Apr 2020 21:31:37 +00:00:

chocolatey-ops (reviewer) on 24 Apr 2020 22:03:32 +00:00:

chocolatey-ops (reviewer) on 24 Apr 2020 23:05:16 +00:00:

STATS MADE SIMPLE

R INTEGRATION:

FREE AND OPEN:

SOLID vs CURRENT

Ground Rules: