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.3.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.3.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.3.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.3.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:

151,619

Downloads of v 8.2.3717:

135

Last Update:

02 Dec 2021

Package Maintainer(s):

Pauby

Software Author(s):

Build: TuxProject.de
Developer: vim team

Tags:

vim-tux vim editor tux admin

Vim Tux (Install)

This is not the latest version of Vim Tux (Install) available.

8.2.3717 | Updated: 02 Dec 2021

Downloads:

151,619

Downloads of v 8.2.3717:

135

Maintainer(s):

Pauby

Software Author(s):

Build: TuxProject.de
Developer: vim team

Tags:

vim-tux vim editor tux admin

Vim Tux (Install) 8.2.3717

This is not the latest version of Vim Tux (Install) available.

Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Build: TuxProject.de, Developer: vim team. The inclusion of Build: TuxProject.de, Developer: vim team trademark(s), if any, upon this webpage is solely to identify Build: TuxProject.de, Developer: vim team goods or services and not for commercial purposes.

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Hide Checks

Validation Testing Passed

Verification Testing Passed

Details

Scan Testing Resulted in Flagged as a Note:

At least one file within this package has greater than 0 detections, but less than 5

Details

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Vim Tux (Install), run the following command from the command line or from PowerShell:

To upgrade Vim Tux (Install), run the following command from the command line or from PowerShell:

To uninstall Vim Tux (Install), run the following command from the command line or from PowerShell:

NOTE

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

1. Enter Your Internal Repository Url

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

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

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

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

Option 2: Internalized Package (Reliable, Scalable)

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

Package Internalizer (C4B)

Run: (additional options)

choco download vim-tux.install --internalize --version=8.2.3717 --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 vim-tux.install -y --source="'INTERNAL REPO URL'" --version="'8.2.3717'" [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 vim-tux.install -y --source="'INTERNAL REPO URL'" --version="'8.2.3717'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode


- name: Install vim-tux.install
  win_chocolatey:
    name: vim-tux.install
    version: '8.2.3717'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'vim-tux.install' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '8.2.3717'
end

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


cChocoPackageInstaller vim-tux.install
{
    Name     = "vim-tux.install"
    Version  = "8.2.3717"
    Source   = "INTERNAL REPO URL"
}

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


package { 'vim-tux.install':
  ensure   => '8.2.3717',
  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.

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.

WARNING

There are versions of this package awaiting moderation . See the Version History section below.

Package Approved

This package was approved as a trusted package on 02 Dec 2021.

Description

Package Parameters

The following package parameters can be set:

/InstallPopUp - Install into the context menu "Edit with gVim", powered by GVimExt.dll.
/RestartExplorer - Kill explorer.exe before each update to free up the in-use GVimExt.dll.
/NoCreateBatFiles - Do not create batch files in C:\Windows (vim.bat, vimdiff.bat, etc).

Please visit the official site at https://tuxproject.de/projects/vim/ for more information.
Build provided by TuxProject.de - consider donating to help support their server costs.

Files

tools\chocolateyinstall.ps1

$ErrorActionPreference = 'Stop'
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$destDir = Join-Path $ENV:ProgramFiles 'Vim\vim82'
if ($Env:ChocolateyPackageParameters -match '/InstallDir:\s*(.+)') {
	$destDir = $Matches[1]
	$destDir = $destDir -replace '^[''"]|[''"]$' # Strip quotations. Necessary?
	$destDir = $destDir -replace '[\/]$' # Remove any slashes from end of line
	if (-not ($destDir.EndsWith('vim82'))) { $destDir = Join-Path $destDir 'vim82' } # installer will not run if it is not within folder vim82
}

$pp = Get-PackageParameters

# Optionally restart explorer before install
if ($pp['RestartExplorer'] -eq 'true') {
	Write-Debug "Restarting Explorer"
	Get-Process explorer | Stop-Process -Force
}

# Create batch files in C:\Windows by default
$createBatFiles = '-create-batfiles vim gvim evim view gview vimdiff gvimdiff'
if ($pp['NoCreateBatFiles'] -eq 'true') {
	Write-Debug 'Not installing batch files'
	$createBatFiles = $null
}

# Do not install context menu entry by default
$installPopUp = $null
if ($pp['InstallPopUp'] -eq 'true') {
	Write-Debug 'Installing context menu entry'
	$installPopUp = '-install-popup'
}

$baseArgs = "-install-openwith -add-start-menu"
$installArgs = $installPopUp, $createBatFiles, $baseArgs -ne $null -join ' '

$packageArgs = @{
        packageName  = 'vim-tux.install'
        filetype     = 'exe'
        file         = gi $toolsDir\*_x32.exe
        file64       = gi $toolsDir\*_x64.exe
        silentArgs   = "-o`"$destDir`" -y"
        softwareName = 'vim*'
}

Install-ChocolateyPackage @packageArgs
Move-Item "$toolsDir\patch.exe.manifest" $destDir -Force -ea 0 # Supplied manifest fixes useless UAC request
(Get-Item $destdir\patch.exe).LastWriteTime = (Get-Date) # exe must be newer than manifest
# Run vim's installer
Move-Item "$toolsDir\install" "$destDir\install.exe" -Force -ea 0 # vim-tux removed the installer, just in time for Defender to stop flagging it
Move-Item "$toolsDir\uninstal" "$destDir\uninstal.exe" -Force -ea 0 # vim-tux removed the uninstaller, just in time for Defender to stop flagging it
Start-ChocolateyProcessAsAdmin "$installArgs" "$destDir\install.exe" -validExitCodes '0'
Remove-Item -Force -ea 0 "$toolsDir\*_x32.exe","$toolsDir\*_x64.exe"
Write-Host 'Build provided by TuxProject.de - consider donating to help support their server costs.'

tools\chocolateyuninstall.ps1

$packageName = 'vim-tux.install'
$destDir = Join-Path $ENV:ProgramFiles "Vim"

# Apparently doesn't have a non-interactive mode. Send 'y' to its input
Set-Content -Path "$env:TEMP\vimuninstallinput" -Value 'y'
Start-Process -FilePath "$destDir\vim82\uninstal.exe" -ArgumentList '-nsis' -RedirectStandardInput "$env:TEMP\vimuninstallinput" -Wait
Remove-Item "$env:TEMP\vimuninstallinput"
Remove-Item $destDir -Force -Recurse

tools\complete-x64_x64.exe

md5: 3A1EB0160E1EFC06CC7893D3DE56C98D | sha1: EEE5FF7EC0554A4BF7FE8A3A224EA4D07BA119C3 | sha256: 3061323D2F961C08CA4BAB3185A49DC0DC683CEAA8ABD1A5C891A4CE895366BF | sha512: 7DD23A0941B6BC857280207906537E71C007592F5C5BDB2B3CF609D2F6A48FCB74C4C342EA2364AE9C97BA8A539E609827B3E95A72F910C9713488B13647BBC6

tools\complete-x86_x32.exe

md5: EF96C0BC4DD2F23BECC6D95CAF00C23C | sha1: 6AA8F875116C0FB2EF7B18C3387D1D5ADEA6F27C | sha256: 75B2AE16FAEA2D4CF4891E459807ACC305A925F7591C574674694F9EF1D7244F | sha512: A1E66EA31B8635ACAF110BA855D806C1B54AD2E6BD8C8E81FDF16FE21D55B6A74928B180BA14388B6BB9CCA127336BC66A3E38D11063D3A18374BFF1833778F8

tools\install

tools\LICENSE.txt

*uganda.txt*    For Vim version 8.1.  Last change: 2018 May 17


		  VIM REFERENCE MANUAL    by Bram Moolenaar


			*uganda* *Uganda* *copying* *copyright* *license*
SUMMARY
								*iccf* *ICCF*
Vim is Charityware.  You can use and copy it as much as you like, but you are
encouraged to make a donation for needy children in Uganda.  Please see |kcc|
below or visit the ICCF web site, available at these URLs:

	http://iccf-holland.org/
	http://www.vim.org/iccf/
	http://www.iccf.nl/

You can also sponsor the development of Vim.  Vim sponsors can vote for
features.  See |sponsor|.  The money goes to Uganda anyway.

The Open Publication License applies to the Vim documentation, see
|manual-copyright|.

=== begin of license ===

VIM LICENSE

I)  There are no restrictions on distributing unmodified copies of Vim except
    that they must include this license text.  You can also distribute
    unmodified parts of Vim, likewise unrestricted except that they must
    include this license text.  You are also allowed to include executables
    that you made from the unmodified Vim sources, plus your own usage
    examples and Vim scripts.

II) It is allowed to distribute a modified (or extended) version of Vim,
    including executables and/or source code, when the following four
    conditions are met:
    1) This license text must be included unmodified.
    2) The modified Vim must be distributed in one of the following five ways:
       a) If you make changes to Vim yourself, you must clearly describe in
	  the distribution how to contact you.  When the maintainer asks you
	  (in any way) for a copy of the modified Vim you distributed, you
	  must make your changes, including source code, available to the
	  maintainer without fee.  The maintainer reserves the right to
	  include your changes in the official version of Vim.  What the
	  maintainer will do with your changes and under what license they
	  will be distributed is negotiable.  If there has been no negotiation
	  then this license, or a later version, also applies to your changes.
	  The current maintainer is Bram Moolenaar <[email protected]>.  If this
	  changes it will be announced in appropriate places (most likely
	  vim.sf.net, www.vim.org and/or comp.editors).  When it is completely
	  impossible to contact the maintainer, the obligation to send him
	  your changes ceases.  Once the maintainer has confirmed that he has
	  received your changes they will not have to be sent again.
       b) If you have received a modified Vim that was distributed as
	  mentioned under a) you are allowed to further distribute it
	  unmodified, as mentioned at I).  If you make additional changes the
	  text under a) applies to those changes.
       c) Provide all the changes, including source code, with every copy of
	  the modified Vim you distribute.  This may be done in the form of a
	  context diff.  You can choose what license to use for new code you
	  add.  The changes and their license must not restrict others from
	  making their own changes to the official version of Vim.
       d) When you have a modified Vim which includes changes as mentioned
	  under c), you can distribute it without the source code for the
	  changes if the following three conditions are met:
	  - The license that applies to the changes permits you to distribute
	    the changes to the Vim maintainer without fee or restriction, and
	    permits the Vim maintainer to include the changes in the official
	    version of Vim without fee or restriction.
	  - You keep the changes for at least three years after last
	    distributing the corresponding modified Vim.  When the maintainer
	    or someone who you distributed the modified Vim to asks you (in
	    any way) for the changes within this period, you must make them
	    available to him.
	  - You clearly describe in the distribution how to contact you.  This
	    contact information must remain valid for at least three years
	    after last distributing the corresponding modified Vim, or as long
	    as possible.
       e) When the GNU General Public License (GPL) applies to the changes,
	  you can distribute the modified Vim under the GNU GPL version 2 or
	  any later version.
    3) A message must be added, at least in the output of the ":version"
       command and in the intro screen, such that the user of the modified Vim
       is able to see that it was modified.  When distributing as mentioned
       under 2)e) adding the message is only required for as far as this does
       not conflict with the license used for the changes.
    4) The contact information as required under 2)a) and 2)d) must not be
       removed or changed, except that the person himself can make
       corrections.

III) If you distribute a modified version of Vim, you are encouraged to use
     the Vim license for your changes and make them available to the
     maintainer, including the source code.  The preferred way to do this is
     by e-mail or by uploading the files to a server and e-mailing the URL.
     If the number of changes is small (e.g., a modified Makefile) e-mailing a
     context diff will do.  The e-mail address to be used is
     <[email protected]>

IV)  It is not allowed to remove this license from the distribution of the Vim
     sources, parts of it or from a modified version.  You may use this
     license for previous Vim releases instead of the license that they came
     with, at your option.

=== end of license ===

Note:

- If you are happy with Vim, please express that by reading the rest of this
  file and consider helping needy children in Uganda.

- If you want to support further Vim development consider becoming a
  |sponsor|.  The money goes to Uganda anyway.

- According to Richard Stallman the Vim license is GNU GPL compatible.
  A few minor changes have been made since he checked it, but that should not
  make a difference.

- If you link Vim with a library that goes under the GNU GPL, this limits
  further distribution to the GNU GPL.  Also when you didn't actually change
  anything in Vim.

- Once a change is included that goes under the GNU GPL, this forces all
  further changes to also be made under the GNU GPL or a compatible license.

- If you distribute a modified version of Vim, you can include your name and
  contact information with the "--with-modified-by" configure argument or the
  MODIFIED_BY define.

==============================================================================
Kibaale Children's Centre		*kcc* *Kibaale*  *charity*

Kibaale Children's Centre (KCC) is located in Kibaale, a small town in the
south of Uganda, near Tanzania, in East Africa.  The area is known as Rakai
District.  The population is mostly farmers.  Although people are poor, there
is enough food.  But this district is suffering from AIDS more than any other
part of the world.  Some say that it started there.  Estimations are that 10
to 30% of the Ugandans are infected with HIV.  Because parents die, there are
many orphans.  In this district about 60,000 children have lost one or both
parents, out of a population of 350,000.  And this is still continuing.

The children need a lot of help.  The KCC is working hard to provide the needy
with food, medical care and education.  Food and medical care to keep them
healthy now, and education so that they can take care of themselves in the
future.  KCC works on a Christian base, but help is given to children of any
religion.

The key to solving the problems in this area is education.  This has been
neglected in the past years with president Idi Amin and the following civil
wars.  Now that the government is stable again, the children and parents have
to learn how to take care of themselves and how to avoid infections.  There is
also help for people who are ill and hungry, but the primary goal is to
prevent people from getting ill and to teach them how to grow healthy food.

Most of the orphans are living in an extended family.  An uncle or older
sister is taking care of them.  Because these families are big and the income
(if any) is low, a child is lucky if it gets healthy food.  Clothes, medical
care and schooling is beyond its reach.  To help these needy children, a
sponsorship program was put into place.  A child can be financially adopted.
For a few dollars a month KCC sees to it that the child gets indispensable
items, is healthy, goes to school and KCC takes care of anything else that
needs to be done for the child and the family that supports it.

Besides helping the child directly, the environment where the child grows up
needs to be improved.  KCC helps schools to improve their teaching methods.
There is a demonstration school at the centre and teacher trainings are given.
Health workers are being trained, hygiene education is carried out and
households are stimulated to build a proper latrine.  I helped setting up a
production site for cement slabs.  These are used to build a good latrine.
They are sold below cost price.

There is a small clinic at the project, which provides children and their
family with medical help.  When needed, transport to a hospital is offered.
Immunization programs are carried out and help is provided when an epidemic is
breaking out (measles and cholera have been a problem).
							*donate*
Summer 1994 to summer 1995 I spent a whole year at the centre, working as a
volunteer.  I have helped to expand the centre and worked in the area of water
and sanitation.  I learned that the help that the KCC provides really helps.
When I came back to Holland, I wanted to continue supporting KCC.  To do this
I'm raising funds and organizing the sponsorship program.  Please consider one
of these possibilities:

1.  Sponsor a child in primary school: 17 euro a month (or more).
2.  Sponsor a child in secondary school: 25 euro a month (or more).
3.  Sponsor the clinic: Any amount a month or quarter
4.  A one-time donation

Compared with other organizations that do child sponsorship the amounts are
very low.  This is because the money goes directly to the centre.  Less than
5% is used for administration.  This is possible because this is a small
organization that works with volunteers.  If you would like to sponsor a
child, you should have the intention to do this for at least one year.

How do you know that the money will be spent right?  First of all you have my
personal guarantee as the author of Vim.  I trust the people that are working
at the centre, I know them personally.  Furthermore, the centre has been
co-sponsored and inspected by World Vision, Save the Children Fund and is now
under the supervision of Pacific Academy Outreach Society.  The centre is
visited about once a year to check the progress (at our own cost).  I have
visited the centre myself many times, starting in 1993.  The visit reports are
on the ICCF web site.

If you have any further questions, send me e-mail: <[email protected]>.

The address of the centre is:
			Kibaale Children's Centre
			p.o. box 1658
			Masaka, Uganda, East Africa

Sending money:						*iccf-donations*

Check the ICCF web site for the latest information!  See |iccf| for the URL.


USA:		The methods mentioned below can be used.
		Sending a check to the Nehemiah Group Outreach Society (NGOS)
		is no longer possible, unfortunately. We are looking for
		another way to get you an IRS tax receipt. 
		For sponsoring a child contact KCF in Canada (see below). US
		checks can be sent to them to lower banking costs.

Canada:		Contact Kibaale Children's Fund (KCF) in Surrey, Canada.  They
		take care of the Canadian sponsors for the children in
		Kibaale.  KCF forwards 100% of the money to the project in
		Uganda.  You can send them a one time donation directly.
		Please send me a note so that I know what has been donated
		because of Vim.  Ask KCF for information about sponsorship.
			Kibaale Children's Fund c/o Pacific Academy
			10238-168 Street
			Surrey, B.C. V4N 1Z4
			Canada
			Phone: 604-581-5353
		If you make a donation to Kibaale Children's Fund (KCF) you
		will receive a tax receipt which can be submitted with your
		tax return.

Holland:	Transfer to the account of "Stichting ICCF Holland" in Lisse.
		This will allow for tax deduction if you live in Holland.
			Postbank, nr. 4548774
			IBAN: NL95 INGB 0004 5487 74

Germany:	It is possible to make donations that allow for a tax return.
		Check the ICCF web site for the latest information:
			http://iccf-holland.org/germany.html

World:		Use a postal money order.  That should be possible from any
		country, mostly from the post office.  Use this name (which is
		in my passport): "Abraham Moolenaar".  Use Euro for the
		currency if possible.

Europe:		Use a bank transfer if possible.  Your bank should have a form
		that you can use for this.  See "Others" below for the swift
		code and IBAN number.
		Any other method should work.  Ask for information about
		sponsorship.

Credit Card:	You can use PayPal to send money with a Credit card.  This is
		the most widely used Internet based payment system.  It's
		really simple to use.  Use this link to find more info:
		    https://www.paypal.com/en_US/mrb/pal=XAC62PML3GF8Q
		The e-mail address for sending the money to is:
		    [email protected]
		For amounts above 400 Euro ($500) sending a check is
		preferred.

Others:		Transfer to one of these accounts if possible:
		    Postbank, account 4548774
				Swift code: INGB NL 2A
				IBAN: NL95 INGB 0004 5487 74
			under the name "stichting ICCF Holland", Lisse
		    If that doesn't work:
		    Rabobank Lisse, account 3765.05.117
				Swift code: RABO NL 2U
			under the name "Bram Moolenaar", Lisse
		Otherwise, send a check in euro or US dollars to the address
		below.  Minimal amount: $70 (my bank does not accept smaller
		amounts for foreign check, sorry)

Address to send checks to:
			Bram Moolenaar
			Finsterruetihof 1
			8134 Adliswil
			Switzerland

This address is expected to be valid for a long time.

 vim:tw=78:ts=8:ft=help:norl:

tools\patch.exe.manifest

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
  <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
    <security>
      <requestedPrivileges>
        <!-- Make sure that UAC believes
        that it does not require administrative privilege -->
        <requestedExecutionLevel level="asInvoker" uiAccess="false"/>
      </requestedPrivileges>
    </security>
  </trustInfo>
</assembly>

tools\uninstal

tools\VERIFICATION.txt

VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

The embedded software have been downloaded from the listed download
location on <https://tuxproject.de/projects/vim/>
and can be verified by doing the following:

1. Download the following installers:
  32-Bit: <http://tuxproject.de/projects/vim/complete-x86.7z>
  64-Bit: <http://tuxproject.de/projects/vim/complete-x64.7z>
2. Get the checksum using one of the following methods:
  - Using powershell function 'Get-FileHash'
  - Use chocolatey utility 'checksum.exe'
3. The checksums should match the following:

  checksumType: sha256
  checksum32: 75B2AE16FAEA2D4CF4891E459807ACC305A925F7591C574674694F9EF1D7244F
  checksum64: 3061323D2F961C08CA4BAB3185A49DC0DC683CEAA8ABD1A5C891A4CE895366BF

4. The install.exe and the uninstal.exe have been pulled from the last build of vim-tux to include them: 8.2.0357. Preserved here:
  <https://chocolatey.org/api/v2/package/vim-tux.install/8.2.0357>
  
  checksumType: sha256
  install: cb927a1e6e8e5a4069e7f5fd9bfa0ecee3f36b56d85bc0f06c661c94f6584dbd
  uninstal: 709001aa1903546a6fb013a4c003f5319e15750046f7da443f16c1cfb7aff556

The file 'LICENSE.txt' has been obtained from <https://github.com/vim/vim/blob/master/runtime/doc/uganda.txt>

Virus Scan Results

vim-tux.install.8.2.3717.nupkg (6f3782a7c897) - ## / 55
vim-tux.portableInstall.exe (3061323d2f96) - ## / 58
vim-tux.portableInstall.exe (75b2ae16faea) - ## / 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
Vim Tux (Install) 9.1.758	4	Saturday, October 5, 2024	Ready
Vim Tux (Install) 9.1.757	5	Friday, October 4, 2024	Ready
Vim Tux (Install) 9.1.740	74	Tuesday, September 24, 2024	Exempted
Vim Tux (Install) 9.1.736	7	Wednesday, September 18, 2024	Waiting for Maintainer
Vim Tux (Install) 9.1.733	55	Monday, September 16, 2024	Approved
Vim Tux (Install) 9.1.730	33	Saturday, September 14, 2024	Approved
Vim Tux (Install) 9.1.727	4	Thursday, September 12, 2024	Waiting for Maintainer
Vim Tux (Install) 9.1.724	31	Wednesday, September 11, 2024	Approved
Vim Tux (Install) 9.1.722	27	Tuesday, September 10, 2024	Approved
Vim Tux (Install) 9.1.718	29	Friday, September 6, 2024	Approved
Vim Tux (Install) 9.1.714	24	Thursday, September 5, 2024	Approved
Vim Tux (Install) 9.1.708	59	Monday, September 2, 2024	Approved
Vim Tux (Install) 9.1.702	44	Thursday, August 29, 2024	Approved
Vim Tux (Install) 9.1.697	43	Monday, August 26, 2024	Approved
Vim Tux (Install) 9.1.689	30	Friday, August 23, 2024	Approved
Vim Tux (Install) 9.1.682	51	Tuesday, August 20, 2024	Approved
Vim Tux (Install) 9.1.679	36	Sunday, August 18, 2024	Approved
Vim Tux (Install) 9.1.674	46	Thursday, August 15, 2024	Approved
Vim Tux (Install) 9.1.672	34	Monday, August 12, 2024	Approved
Vim Tux (Install) 9.1.668	30	Saturday, August 10, 2024	Approved
Vim Tux (Install) 9.1.661	48	Tuesday, August 6, 2024	Approved
Vim Tux (Install) 9.1.618	82	Saturday, July 27, 2024	Approved
Vim Tux (Install) 9.1.611	41	Wednesday, July 24, 2024	Approved
Vim Tux (Install) 9.1.602	39	Friday, July 19, 2024	Approved
Vim Tux (Install) 9.1.598	29	Friday, July 19, 2024	Approved
Vim Tux (Install) 9.1.589	37	Tuesday, July 16, 2024	Approved
Vim Tux (Install) 9.1.586	24	Tuesday, July 16, 2024	Approved
Vim Tux (Install) 9.1.554	51	Thursday, July 11, 2024	Approved
Vim Tux (Install) 9.1.546	30	Tuesday, July 9, 2024	Approved
Vim Tux (Install) 9.1.544	34	Tuesday, July 9, 2024	Approved
Vim Tux (Install) 9.1.531	38	Saturday, July 6, 2024	Approved
Vim Tux (Install) 9.1.519	34	Thursday, July 4, 2024	Approved
Vim Tux (Install) 9.1.516	66	Monday, June 24, 2024	Approved
Vim Tux (Install) 9.1.514	39	Sunday, June 23, 2024	Approved
Vim Tux (Install) 9.1.512	25	Saturday, June 22, 2024	Approved
Vim Tux (Install) 9.1.505	33	Thursday, June 20, 2024	Approved
Vim Tux (Install) 9.1.500	41	Wednesday, June 19, 2024	Approved
Vim Tux (Install) 9.1.487	53	Saturday, June 15, 2024	Approved
Vim Tux (Install) 9.1.474	52	Tuesday, June 11, 2024	Approved
Vim Tux (Install) 9.1.472	26	Monday, June 10, 2024	Approved
Vim Tux (Install) 9.1.470	65	Thursday, June 6, 2024	Approved
Vim Tux (Install) 9.1.466	33	Thursday, June 6, 2024	Approved
Vim Tux (Install) 9.1.465	43	Wednesday, June 5, 2024	Approved
Vim Tux (Install) 9.1.461	27	Tuesday, June 4, 2024	Approved
Vim Tux (Install) 9.1.454	44	Saturday, June 1, 2024	Approved
Vim Tux (Install) 9.1.448	59	Thursday, May 30, 2024	Approved
Vim Tux (Install) 9.1.447	44	Tuesday, May 28, 2024	Approved
Vim Tux (Install) 9.1.442	60	Saturday, May 25, 2024	Approved
Vim Tux (Install) 9.1.433	33	Friday, May 24, 2024	Approved
Vim Tux (Install) 9.1.432	35	Thursday, May 23, 2024	Approved
Vim Tux (Install) 9.1.426	38	Wednesday, May 22, 2024	Approved
Vim Tux (Install) 9.1.412	40	Tuesday, May 21, 2024	Approved
Vim Tux (Install) 9.1.411	78	Monday, May 13, 2024	Approved
Vim Tux (Install) 9.1.407	53	Sunday, May 12, 2024	Approved
Vim Tux (Install) 9.1.393	59	Wednesday, May 8, 2024	Approved
Vim Tux (Install) 9.1.386	73	Thursday, May 2, 2024	Approved
Vim Tux (Install) 9.1.380	25	Tuesday, April 30, 2024	Approved
Vim Tux (Install) 9.1.373	24	Saturday, April 27, 2024	Approved
Vim Tux (Install) 9.1.368	73	Thursday, April 25, 2024	Approved
Vim Tux (Install) 9.1.366	28	Wednesday, April 24, 2024	Approved
Vim Tux (Install) 9.1.354	56	Saturday, April 20, 2024	Approved
Vim Tux (Install) 9.1.336	53	Tuesday, April 16, 2024	Approved
Vim Tux (Install) 9.1.330	45	Monday, April 15, 2024	Approved
Vim Tux (Install) 9.1.296	62	Thursday, April 11, 2024	Approved
Vim Tux (Install) 9.1.193	116	Friday, March 22, 2024	Approved
Vim Tux (Install) 9.1.186	51	Tuesday, March 19, 2024	Approved
Vim Tux (Install) 9.1.181	51	Friday, March 15, 2024	Approved
Vim Tux (Install) 9.1.113	181	Friday, February 16, 2024	Approved
Vim Tux (Install) 9.1.67	134	Friday, February 2, 2024	Approved
Vim Tux (Install) 9.0.2181	197	Thursday, December 21, 2023	Approved
Vim Tux (Install) 9.0.2167	71	Friday, December 15, 2023	Approved
Vim Tux (Install) 9.0.2155	95	Saturday, December 9, 2023	Approved
Vim Tux (Install) 9.0.2146	81	Tuesday, December 5, 2023	Approved
Vim Tux (Install) 9.0.2134	76	Wednesday, November 29, 2023	Approved
Vim Tux (Install) 9.0.2122	83	Friday, November 24, 2023	Approved
Vim Tux (Install) 9.0.2120	64	Wednesday, November 22, 2023	Approved
Vim Tux (Install) 9.0.2103	106	Tuesday, November 14, 2023	Approved
Vim Tux (Install) 9.0.2095	90	Friday, November 10, 2023	Approved
Vim Tux (Install) 9.0.2092	78	Tuesday, November 7, 2023	Approved
Vim Tux (Install) 9.0.2081	81	Wednesday, November 1, 2023	Approved
Vim Tux (Install) 9.0.2077	73	Saturday, October 28, 2023	Approved
Vim Tux (Install) 9.0.2067	86	Friday, October 27, 2023	Approved
Vim Tux (Install) 9.0.2063	91	Tuesday, October 24, 2023	Approved
Vim Tux (Install) 9.0.2053	107	Friday, October 20, 2023	Approved
Vim Tux (Install) 9.0.2050	50	Thursday, October 19, 2023	Approved
Vim Tux (Install) 9.0.2048	64	Thursday, October 19, 2023	Approved
Vim Tux (Install) 9.0.2043	61	Wednesday, October 18, 2023	Approved
Vim Tux (Install) 9.0.2034	83	Tuesday, October 17, 2023	Approved
Vim Tux (Install) 9.0.2009	98	Tuesday, October 10, 2023	Approved
Vim Tux (Install) 9.0.1976	70	Wednesday, October 4, 2023	Approved
Vim Tux (Install) 9.0.1943	523	Wednesday, September 27, 2023	Approved
Vim Tux (Install) 9.0.1927	615	Friday, September 22, 2023	Approved
Vim Tux (Install) 9.0.1907	82	Tuesday, September 19, 2023	Approved
Vim Tux (Install) 9.0.1901	191	Saturday, September 16, 2023	Approved
Vim Tux (Install) 9.0.1897	121	Wednesday, September 13, 2023	Approved
Vim Tux (Install) 9.0.1877	56	Thursday, September 7, 2023	Approved
Vim Tux (Install) 9.0.1872	78	Wednesday, September 6, 2023	Exempted
Vim Tux (Install) 9.0.0814	127	Saturday, October 22, 2022	Approved
Vim Tux (Install) 9.0.0806	68	Friday, October 21, 2022	Approved
Vim Tux (Install) 9.0.0797	82	Thursday, October 20, 2022	Approved
Vim Tux (Install) 9.0.0780	98	Tuesday, October 18, 2022	Approved
Vim Tux (Install) 9.0.0733	113	Thursday, October 13, 2022	Approved
Vim Tux (Install) 9.0.0715	87	Tuesday, October 11, 2022	Approved
Vim Tux (Install) 9.0.0682	140	Saturday, October 8, 2022	Approved
Vim Tux (Install) 9.0.656.20221005	89	Thursday, October 6, 2022	Approved
Vim Tux (Install) 9.0.0656	91	Wednesday, October 5, 2022	Approved
Vim Tux (Install) 8.2.3875	534	Thursday, December 23, 2021	Approved
Vim Tux (Install) 8.2.3836	157	Saturday, December 18, 2021	Approved
Vim Tux (Install) 8.2.3811	152	Wednesday, December 15, 2021	Approved
Vim Tux (Install) 8.2.3794	140	Tuesday, December 14, 2021	Approved
Vim Tux (Install) 8.2.3757	150	Wednesday, December 8, 2021	Approved
Vim Tux (Install) 8.2.3752	119	Tuesday, December 7, 2021	Approved
Vim Tux (Install) 8.2.3718	169	Friday, December 3, 2021	Approved
Vim Tux (Install) 8.2.3717	135	Thursday, December 2, 2021	Approved
Vim Tux (Install) 8.2.3701	103	Wednesday, December 1, 2021	Approved
Vim Tux (Install) 8.2.3692	101	Monday, November 29, 2021	Approved
Vim Tux (Install) 8.2.3671	186	Friday, November 26, 2021	Approved
Vim Tux (Install) 8.2.3659	158	Thursday, November 25, 2021	Approved
Vim Tux (Install) 8.2.3651	126	Tuesday, November 23, 2021	Approved
Vim Tux (Install) 8.2.3646	138	Tuesday, November 23, 2021	Approved
Vim Tux (Install) 8.2.3623	166	Saturday, November 20, 2021	Approved
Vim Tux (Install) 8.2.3608	136	Thursday, November 18, 2021	Approved
Vim Tux (Install) 8.2.3595	161	Tuesday, November 16, 2021	Approved
Vim Tux (Install) 8.2.3579	269	Friday, November 5, 2021	Approved
Vim Tux (Install) 8.2.3565	231	Wednesday, October 27, 2021	Approved
Vim Tux (Install) 8.2.3551	185	Friday, October 22, 2021	Approved
Vim Tux (Install) 8.2.3545	149	Thursday, October 21, 2021	Approved
Vim Tux (Install) 8.2.3532	134	Tuesday, October 19, 2021	Approved
Vim Tux (Install) 8.2.3513	185	Saturday, October 16, 2021	Approved
Vim Tux (Install) 8.2.3505	175	Thursday, October 14, 2021	Approved
Vim Tux (Install) 8.2.3493	164	Monday, October 11, 2021	Approved
Vim Tux (Install) 8.2.3486	154	Saturday, October 9, 2021	Approved
Vim Tux (Install) 8.2.3484	149	Thursday, October 7, 2021	Approved
Vim Tux (Install) 8.2.3478	115	Wednesday, October 6, 2021	Approved
Vim Tux (Install) 8.2.3469	120	Tuesday, October 5, 2021	Approved
Vim Tux (Install) 8.2.3458	249	Tuesday, September 28, 2021	Approved
Vim Tux (Install) 8.2.3455	183	Thursday, September 23, 2021	Approved
Vim Tux (Install) 8.2.3450	149	Tuesday, September 21, 2021	Approved
Vim Tux (Install) 8.2.3448	130	Sunday, September 19, 2021	Approved
Vim Tux (Install) 8.2.3434	162	Tuesday, September 14, 2021	Approved
Vim Tux (Install) 8.2.3416	231	Thursday, September 9, 2021	Approved
Vim Tux (Install) 8.2.3394	228	Thursday, September 2, 2021	Approved
Vim Tux (Install) 8.2.3391	124	Wednesday, September 1, 2021	Approved
Vim Tux (Install) 8.2.3376	207	Thursday, August 26, 2021	Approved
Vim Tux (Install) 8.2.3358	215	Friday, August 20, 2021	Approved
Vim Tux (Install) 8.2.3356	137	Wednesday, August 18, 2021	Approved
Vim Tux (Install) 8.2.3326	215	Wednesday, August 11, 2021	Approved
Vim Tux (Install) 8.2.3318	141	Monday, August 9, 2021	Approved
Vim Tux (Install) 8.2.3299	178	Friday, August 6, 2021	Approved
Vim Tux (Install) 8.2.3290	96	Thursday, August 5, 2021	Approved
Vim Tux (Install) 8.2.3281	160	Wednesday, August 4, 2021	Approved
Vim Tux (Install) 8.2.3273	133	Monday, August 2, 2021	Approved
Vim Tux (Install) 8.2.3269	125	Monday, August 2, 2021	Approved
Vim Tux (Install) 8.2.3263	86	Sunday, August 1, 2021	Approved
Vim Tux (Install) 8.2.3253	125	Saturday, July 31, 2021	Approved
Vim Tux (Install) 8.2.3242	139	Thursday, July 29, 2021	Approved
Vim Tux (Install) 8.2.3204	178	Friday, July 23, 2021	Approved
Vim Tux (Install) 8.2.3187	190	Tuesday, July 20, 2021	Approved
Vim Tux (Install) 8.2.3171	203	Friday, July 16, 2021	Approved
Vim Tux (Install) 8.2.3158	222	Wednesday, July 14, 2021	Approved
Vim Tux (Install) 8.2.3154	188	Monday, July 12, 2021	Approved
Vim Tux (Install) 8.2.3131	173	Friday, July 9, 2021	Approved
Vim Tux (Install) 8.2.3120	152	Thursday, July 8, 2021	Approved
Vim Tux (Install) 8.2.3113	118	Wednesday, July 7, 2021	Approved
Vim Tux (Install) 8.2.3107	177	Monday, July 5, 2021	Approved
Vim Tux (Install) 8.2.3095	142	Sunday, July 4, 2021	Approved
Vim Tux (Install) 8.2.3080	201	Thursday, July 1, 2021	Approved
Vim Tux (Install) 8.2.3075	127	Wednesday, June 30, 2021	Approved
Vim Tux (Install) 8.2.3066	160	Monday, June 28, 2021	Approved
Vim Tux (Install) 8.2.3055	142	Sunday, June 27, 2021	Approved
Vim Tux (Install) 8.2.3043	159	Thursday, June 24, 2021	Exempted
Vim Tux (Install) 8.2.3033	202	Tuesday, June 22, 2021	Approved
Vim Tux (Install) 8.2.3017	158	Friday, June 18, 2021	Exempted
Vim Tux (Install) 8.2.2832	217	Wednesday, May 5, 2021	Exempted
Vim Tux (Install) 8.2.2799	282	Thursday, April 22, 2021	Approved
Vim Tux (Install) 8.2.2794	133	Wednesday, April 21, 2021	Approved
Vim Tux (Install) 8.2.2763	239	Thursday, April 15, 2021	Approved
Vim Tux (Install) 8.2.2738	213	Friday, April 9, 2021	Approved
Vim Tux (Install) 8.2.2730	163	Wednesday, April 7, 2021	Approved
Vim Tux (Install) 8.2.2679	194	Wednesday, March 31, 2021	Approved
Vim Tux (Install) 8.2.2650	130	Friday, March 26, 2021	Approved
Vim Tux (Install) 8.2.2648	285	Wednesday, March 24, 2021	Approved
Vim Tux (Install) 8.2.2417	313	Thursday, January 28, 2021	Approved
Vim Tux (Install) 8.2.2129	604	Saturday, December 12, 2020	Approved
Vim Tux (Install) 8.2.1981	517	Saturday, November 14, 2020	Approved
Vim Tux (Install) 8.2.1955	414	Friday, November 6, 2020	Approved
Vim Tux (Install) 8.2.1905	365	Monday, October 26, 2020	Approved
Vim Tux (Install) 8.2.1883	316	Thursday, October 22, 2020	Approved
Vim Tux (Install) 8.2.1858	331	Sunday, October 18, 2020	Approved
Vim Tux (Install) 8.2.1801	380	Monday, October 5, 2020	Approved
Vim Tux (Install) 8.2.1651	519	Thursday, September 10, 2020	Approved
Vim Tux (Install) 8.2.1139	840	Monday, July 6, 2020	Approved
Vim Tux (Install) 8.2.1058	527	Friday, June 26, 2020	Approved
Vim Tux (Install) 8.2.960	452	Friday, June 12, 2020	Approved
Vim Tux (Install) 8.2.950	287	Thursday, June 11, 2020	Approved
Vim Tux (Install) 8.2.916	304	Sunday, June 7, 2020	Approved
Vim Tux (Install) 8.2.882	439	Tuesday, June 2, 2020	Approved
Vim Tux (Install) 8.2.855	215	Sunday, May 31, 2020	Approved
Vim Tux (Install) 8.2.834	239	Friday, May 29, 2020	Approved
Vim Tux (Install) 8.2.829	337	Wednesday, May 27, 2020	Approved
Vim Tux (Install) 8.2.821	301	Tuesday, May 26, 2020	Approved
Vim Tux (Install) 8.2.806	293	Friday, May 22, 2020	Approved
Vim Tux (Install) 8.2.803	198	Thursday, May 21, 2020	Approved
Vim Tux (Install) 8.2.750	357	Thursday, May 14, 2020	Approved
Vim Tux (Install) 8.2.647	441	Monday, April 27, 2020	Approved
Vim Tux (Install) 8.2.640	272	Sunday, April 26, 2020	Approved
Vim Tux (Install) 8.2.625	318	Friday, April 24, 2020	Approved
Vim Tux (Install) 8.2.612	296	Tuesday, April 21, 2020	Approved
Vim Tux (Install) 8.2.592	237	Saturday, April 18, 2020	Approved
Vim Tux (Install) 8.2.585	252	Friday, April 17, 2020	Approved
Vim Tux (Install) 8.2.577	266	Wednesday, April 15, 2020	Approved
Vim Tux (Install) 8.2.0357	693	Friday, March 6, 2020	Approved
Vim Tux (Install) 8.2.0324	387	Friday, February 28, 2020	Approved
Vim Tux (Install) 8.2.0313	312	Monday, February 24, 2020	Approved
Vim Tux (Install) 8.2.0294	254	Saturday, February 22, 2020	Approved
Vim Tux (Install) 8.2.0285	225	Friday, February 21, 2020	Approved
Vim Tux (Install) 8.2.0273	294	Tuesday, February 18, 2020	Approved
Vim Tux (Install) 8.2.0231	393	Sunday, February 9, 2020	Approved
Vim Tux (Install) 8.2.0184	384	Friday, January 31, 2020	Approved
Vim Tux (Install) 8.2.0164	291	Wednesday, January 29, 2020	Approved
Vim Tux (Install) 8.2.0140	327	Wednesday, January 22, 2020	Approved
Vim Tux (Install) 8.2.0129	346	Sunday, January 19, 2020	Approved
Vim Tux (Install) 8.2.0114	473	Tuesday, January 14, 2020	Approved
Vim Tux (Install) 8.2.0109	308	Friday, January 10, 2020	Approved
Vim Tux (Install) 8.2.0092	383	Tuesday, January 7, 2020	Approved
Vim Tux (Install) 8.2.0080	517	Friday, January 3, 2020	Approved
Vim Tux (Install) 8.1.2333	854	Friday, November 22, 2019	Approved
Vim Tux (Install) 8.1.2323	437	Thursday, November 21, 2019	Approved
Vim Tux (Install) 8.1.2311	523	Sunday, November 17, 2019	Approved
Vim Tux (Install) 8.1.2300	424	Thursday, November 14, 2019	Approved
Vim Tux (Install) 8.1.2237	631	Friday, November 1, 2019	Approved
Vim Tux (Install) 8.1.2204	659	Thursday, October 24, 2019	Approved
Vim Tux (Install) 8.1.2200	420	Wednesday, October 23, 2019	Approved
Vim Tux (Install) 8.1.2148	753	Monday, October 14, 2019	Approved
Vim Tux (Install) 8.1.2133	489	Friday, October 11, 2019	Approved
Vim Tux (Install) 8.1.2117	590	Sunday, October 6, 2019	Approved
Vim Tux (Install) 8.1.2108	456	Thursday, October 3, 2019	Approved
Vim Tux (Install) 8.1.2103	464	Tuesday, October 1, 2019	Approved
Vim Tux (Install) 8.1.2079	520	Friday, September 27, 2019	Approved
Vim Tux (Install) 8.1.2071	494	Wednesday, September 25, 2019	Approved
Vim Tux (Install) 8.1.2052	609	Thursday, September 19, 2019	Approved
Vim Tux (Install) 8.1.2019	675	Tuesday, September 10, 2019	Approved
Vim Tux (Install) 8.1.2004	486	Sunday, September 8, 2019	Approved
Vim Tux (Install) 8.1.1995	343	Saturday, September 7, 2019	Approved
Vim Tux (Install) 8.1.1986	450	Thursday, September 5, 2019	Approved
Vim Tux (Install) 8.1.1961	475	Monday, September 2, 2019	Approved
Vim Tux (Install) 8.1.1927	612	Monday, August 26, 2019	Approved
Vim Tux (Install) 8.1.1915	338	Saturday, August 24, 2019	Approved
Vim Tux (Install) 8.1.1906	386	Thursday, August 22, 2019	Approved
Vim Tux (Install) 8.1.1890	426	Tuesday, August 20, 2019	Approved
Vim Tux (Install) 8.1.1836	544	Sunday, August 11, 2019	Approved
Vim Tux (Install) 8.1.1744	734	Thursday, July 25, 2019	Approved
Vim Tux (Install) 8.1.1729	425	Tuesday, July 23, 2019	Approved
Vim Tux (Install) 8.1.1713	442	Friday, July 19, 2019	Approved
Vim Tux (Install) 8.1.1695	449	Tuesday, July 16, 2019	Approved
Vim Tux (Install) 8.1.1669	459	Saturday, July 13, 2019	Approved
Vim Tux (Install) 8.1.1655	548	Tuesday, July 9, 2019	Approved
Vim Tux (Install) 8.1.1631	447	Friday, July 5, 2019	Approved
Vim Tux (Install) 8.1.1601	571	Thursday, June 27, 2019	Approved
Vim Tux (Install) 8.1.1587	400	Tuesday, June 25, 2019	Approved
Vim Tux (Install) 8.1.1573	451	Thursday, June 20, 2019	Approved
Vim Tux (Install) 8.1.1566	516	Tuesday, June 18, 2019	Approved
Vim Tux (Install) 8.1.1557	331	Monday, June 17, 2019	Approved
Vim Tux (Install) 8.1.1536	336	Sunday, June 16, 2019	Approved
Vim Tux (Install) 8.1.1523	321	Friday, June 14, 2019	Approved
Vim Tux (Install) 8.1.1515	369	Tuesday, June 11, 2019	Approved
Vim Tux (Install) 8.1.1511	438	Monday, June 10, 2019	Approved
Vim Tux (Install) 8.1.1455	519	Monday, June 3, 2019	Approved
Vim Tux (Install) 8.1.1432	356	Friday, May 31, 2019	Approved
Vim Tux (Install) 8.1.1413	392	Tuesday, May 28, 2019	Approved
Vim Tux (Install) 8.1.1373	497	Friday, May 24, 2019	Approved
Vim Tux (Install) 8.1.1364	342	Thursday, May 23, 2019	Approved
Vim Tux (Install) 8.1.1353	507	Monday, May 20, 2019	Approved
Vim Tux (Install) 8.1.1333	469	Thursday, May 16, 2019	Approved
Vim Tux (Install) 8.1.1328	434	Monday, May 13, 2019	Approved
Vim Tux (Install) 8.1.1312	321	Saturday, May 11, 2019	Approved
Vim Tux (Install) 8.1.1298	391	Thursday, May 9, 2019	Approved
Vim Tux (Install) 8.1.1286	407	Tuesday, May 7, 2019	Approved
Vim Tux (Install) 8.1.1229	549	Monday, April 29, 2019	Approved
Vim Tux (Install) 8.1.1183	426	Thursday, April 18, 2019	Approved
Vim Tux (Install) 8.1.1173	427	Monday, April 15, 2019	Approved
Vim Tux (Install) 8.1.1165	315	Sunday, April 14, 2019	Approved
Vim Tux (Install) 8.1.1140	490	Tuesday, April 9, 2019	Approved
Vim Tux (Install) 8.1.1136	384	Monday, April 8, 2019	Approved
Vim Tux (Install) 8.1.1124	322	Sunday, April 7, 2019	Approved
Vim Tux (Install) 8.1.1116	367	Thursday, April 4, 2019	Approved
Vim Tux (Install) 8.1.1103	351	Thursday, April 4, 2019	Approved
Vim Tux (Install) 8.1.1097	311	Monday, April 1, 2019	Approved
Vim Tux (Install) 8.1.1073	463	Saturday, March 30, 2019	Approved
Vim Tux (Install) 8.1.1057	417	Thursday, March 28, 2019	Approved
Vim Tux (Install) 8.1.1045	204	Sunday, March 24, 2019	Approved
Vim Tux (Install) 8.1.1032	179	Friday, March 22, 2019	Approved
Vim Tux (Install) 8.1.1027	525	Thursday, March 21, 2019	Approved
Vim Tux (Install) 8.1.1017	357	Tuesday, March 19, 2019	Approved
Vim Tux (Install) 8.1.1004	617	Monday, March 11, 2019	Approved
Vim Tux (Install) 8.1.998	416	Friday, March 8, 2019	Approved
Vim Tux (Install) 8.1.990	554	Sunday, March 3, 2019	Approved
Vim Tux (Install) 8.1.984	437	Thursday, February 28, 2019	Approved
Vim Tux (Install) 8.1.978	462	Saturday, February 23, 2019	Approved
Vim Tux (Install) 8.1.966	368	Friday, February 22, 2019	Approved
Vim Tux (Install) 8.1.947	454	Tuesday, February 19, 2019	Approved
Vim Tux (Install) 8.1.934	328	Sunday, February 17, 2019	Approved
Vim Tux (Install) 8.1.926	342	Saturday, February 16, 2019	Approved
Vim Tux (Install) 8.1.909	352	Thursday, February 14, 2019	Approved
Vim Tux (Install) 8.1.895	382	Tuesday, February 12, 2019	Approved
Vim Tux (Install) 8.1.0885	358	Sunday, February 10, 2019	Approved
Vim Tux (Install) 8.1.0877	220	Thursday, February 7, 2019	Approved
Vim Tux (Install) 8.1.0871	439	Monday, February 4, 2019	Approved
Vim Tux (Install) 8.1.0868	308	Sunday, February 3, 2019	Approved
Vim Tux (Install) 8.1.0865	316	Saturday, February 2, 2019	Approved
Vim Tux (Install) 8.1.0842	313	Thursday, January 31, 2019	Approved
Vim Tux (Install) 8.1.0837	397	Monday, January 28, 2019	Approved
Vim Tux (Install) 8.1.0814	374	Friday, January 25, 2019	Approved
Vim Tux (Install) 8.1.0796	325	Thursday, January 24, 2019	Approved
Vim Tux (Install) 8.1.0788	360	Tuesday, January 22, 2019	Approved
Vim Tux (Install) 8.1.0712	503	Thursday, January 10, 2019	Approved
Vim Tux (Install) 8.1.0700	376	Tuesday, January 8, 2019	Approved
Vim Tux (Install) 8.1.0690	445	Saturday, January 5, 2019	Approved
Vim Tux (Install) 8.1.0681	321	Thursday, January 3, 2019	Approved
Vim Tux (Install) 8.1.0674	323	Wednesday, January 2, 2019	Approved
Vim Tux (Install) 8.1.0647	374	Friday, December 28, 2018	Approved
Vim Tux (Install) 8.1.0635	338	Wednesday, December 26, 2018	Approved
Vim Tux (Install) 8.1.0630	272	Tuesday, December 25, 2018	Approved
Vim Tux (Install) 8.1.0629	288	Monday, December 24, 2018	Approved
Vim Tux (Install) 8.1.0622	248	Sunday, December 23, 2018	Approved
Vim Tux (Install) 8.1.0617	366	Saturday, December 22, 2018	Approved
Vim Tux (Install) 8.1.0594	504	Sunday, December 16, 2018	Approved
Vim Tux (Install) 8.1.0577	366	Thursday, December 13, 2018	Approved
Vim Tux (Install) 8.1.0551	610	Friday, November 30, 2018	Approved
Vim Tux (Install) 8.1.0547	463	Monday, November 26, 2018	Approved
Vim Tux (Install) 8.1.0536	449	Tuesday, November 20, 2018	Approved
Vim Tux (Install) 8.1.0524	476	Tuesday, November 13, 2018	Approved
Vim Tux (Install) 8.1.0513	378	Thursday, November 8, 2018	Approved
Vim Tux (Install) 8.1.0509	402	Sunday, November 4, 2018	Approved
Vim Tux (Install) 8.1.0498	474	Sunday, October 28, 2018	Approved
Vim Tux (Install) 8.1.0489	414	Monday, October 22, 2018	Approved
Vim Tux (Install) 8.1.0474	498	Monday, October 15, 2018	Approved
Vim Tux (Install) 8.1.0470	393	Friday, October 12, 2018	Approved
Vim Tux (Install) 8.1.0451	474	Friday, October 5, 2018	Approved
Vim Tux (Install) 8.1.0442	451	Monday, October 1, 2018	Approved
Vim Tux (Install) 8.1.0436	430	Thursday, September 27, 2018	Approved
Vim Tux (Install) 8.1.0425	473	Saturday, September 22, 2018	Approved
Vim Tux (Install) 8.1.0408	327	Thursday, September 20, 2018	Approved
Vim Tux (Install) 8.1.0401	316	Tuesday, September 18, 2018	Approved
Vim Tux (Install) 8.1.0385	465	Friday, September 14, 2018	Approved
Vim Tux (Install) 8.1.0371	342	Thursday, September 13, 2018	Approved
Vim Tux (Install) 8.1.0362	391	Tuesday, September 11, 2018	Approved
Vim Tux (Install) 8.1.0354	361	Sunday, September 9, 2018	Approved
Vim Tux (Install) 8.1.0347	376	Thursday, September 6, 2018	Approved
Vim Tux (Install) 8.1.0342	370	Sunday, September 2, 2018	Approved
Vim Tux (Install) 8.1.0332	397	Thursday, August 30, 2018	Approved
Vim Tux (Install) 8.1.0327	407	Sunday, August 26, 2018	Approved
Vim Tux (Install) 8.1.0318	339	Thursday, August 23, 2018	Approved
Vim Tux (Install) 8.1.0301	245	Tuesday, August 21, 2018	Approved
Vim Tux (Install) 8.1.0297	381	Monday, August 20, 2018	Approved
Vim Tux (Install) 8.1.0288	382	Thursday, August 16, 2018	Approved
Vim Tux (Install) 8.1.0278	387	Monday, August 13, 2018	Approved
Vim Tux (Install) 8.1.0271	307	Sunday, August 12, 2018	Approved
Vim Tux (Install) 8.1.0259	398	Friday, August 10, 2018	Approved
Vim Tux (Install) 8.1.0239	440	Sunday, August 5, 2018	Approved
Vim Tux (Install) 8.1.0229	408	Tuesday, July 31, 2018	Approved
Vim Tux (Install) 8.1.0221	348	Sunday, July 29, 2018	Approved
Vim Tux (Install) 8.1.0210	369	Thursday, July 26, 2018	Approved
Vim Tux (Install) 8.1.0207	342	Tuesday, July 24, 2018	Approved
Vim Tux (Install) 8.1.0203	379	Monday, July 23, 2018	Approved
Vim Tux (Install) 8.1.0199	378	Saturday, July 21, 2018	Approved
Vim Tux (Install) 8.1.0196	334	Friday, July 20, 2018	Approved
Vim Tux (Install) 8.1.0191	393	Tuesday, July 17, 2018	Approved
Vim Tux (Install) 8.1.0186	348	Sunday, July 15, 2018	Approved
Vim Tux (Install) 8.1.0173	449	Tuesday, July 10, 2018	Approved
Vim Tux (Install) 8.1.0153	439	Friday, July 6, 2018	Approved
Vim Tux (Install) 8.1.0138	386	Tuesday, July 3, 2018	Approved
Vim Tux (Install) 8.1.0133	506	Sunday, July 1, 2018	Approved
Vim Tux (Install) 8.1.0126	390	Friday, June 29, 2018	Approved
Vim Tux (Install) 8.1.0105	418	Sunday, June 24, 2018	Approved
Vim Tux (Install) 8.1.0054	616	Thursday, June 14, 2018	Approved
Vim Tux (Install) 8.1.0034	663	Tuesday, June 5, 2018	Approved
Vim Tux (Install) 8.1.0022	520	Friday, May 25, 2018	Approved
Vim Tux (Install) 8.1.0013	445	Tuesday, May 22, 2018	Approved
Vim Tux (Install) 8.1.0009	348	Monday, May 21, 2018	Approved
Vim Tux (Install) 8.1.0004	307	Sunday, May 20, 2018	Approved
Vim Tux (Install) 8.1.0000	364	Saturday, May 19, 2018	Approved
Vim Tux (Install) 8.0.1848	365	Thursday, May 17, 2018	Approved
Vim Tux (Install) 8.0.1831	423	Monday, May 14, 2018	Approved
Vim Tux (Install) 8.0.1820	374	Sunday, May 13, 2018	Approved
Vim Tux (Install) 8.0.1806	435	Thursday, May 10, 2018	Approved
Vim Tux (Install) 8.0.1799	433	Monday, May 7, 2018	Approved
Vim Tux (Install) 8.0.1794	309	Sunday, May 6, 2018	Approved
Vim Tux (Install) 8.0.1790	349	Friday, May 4, 2018	Approved
Vim Tux (Install) 8.0.1788	406	Thursday, May 3, 2018	Approved
Vim Tux (Install) 8.0.1774	441	Monday, April 30, 2018	Approved
Vim Tux (Install) 8.0.1765	472	Thursday, April 26, 2018	Approved
Vim Tux (Install) 8.0.1748	395	Sunday, April 22, 2018	Approved
Vim Tux (Install) 8.0.1736	356	Friday, April 20, 2018	Approved
Vim Tux (Install) 8.0.1727	375	Wednesday, April 18, 2018	Approved
Vim Tux (Install) 8.0.1705	427	Saturday, April 14, 2018	Approved
Vim Tux (Install) 8.0.1679	478	Monday, April 9, 2018	Approved
Vim Tux (Install) 8.0.1664	382	Saturday, April 7, 2018	Approved
Vim Tux (Install) 8.0.1655	465	Saturday, March 31, 2018	Approved
Vim Tux (Install) 8.0.1638	576	Sunday, March 25, 2018	Approved
Vim Tux (Install) 8.0.1626	480	Thursday, March 22, 2018	Approved
Vim Tux (Install) 8.0.1612	472	Saturday, March 17, 2018	Approved
Vim Tux (Install) 8.0.1601	491	Tuesday, March 13, 2018	Approved
Vim Tux (Install) 8.0.1591	458	Friday, March 9, 2018	Approved
Vim Tux (Install) 8.0.1563	486	Sunday, March 4, 2018	Approved
Vim Tux (Install) 8.0.1553	350	Friday, March 2, 2018	Approved
Vim Tux (Install) 8.0.1532	544	Sunday, February 25, 2018	Approved
Vim Tux (Install) 8.0.1504	658	Thursday, February 15, 2018	Approved
Vim Tux (Install) 8.0.1473	513	Thursday, February 8, 2018	Approved
Vim Tux (Install) 8.0.1451	492	Saturday, February 3, 2018	Approved
Vim Tux (Install) 8.0.1438	450	Tuesday, January 30, 2018	Approved
Vim Tux (Install) 8.0.1431	492	Saturday, January 27, 2018	Approved
Vim Tux (Install) 8.0.1428	701	Thursday, January 4, 2018	Approved
Vim Tux (Install) 8.0.1422	473	Saturday, December 30, 2017	Approved
Vim Tux (Install) 8.0.1390	578	Sunday, December 17, 2017	Approved
Vim Tux (Install) 8.0.1379	434	Thursday, December 14, 2017	Approved
Vim Tux (Install) 8.0.1376	494	Thursday, December 7, 2017	Approved
Vim Tux (Install) 8.0.1358	570	Friday, December 1, 2017	Approved
Vim Tux (Install) 8.0.1330	562	Thursday, November 23, 2017	Approved
Vim Tux (Install) 8.0.1311	469	Monday, November 20, 2017	Approved
Vim Tux (Install) 8.0.1305	465	Saturday, November 18, 2017	Approved
Vim Tux (Install) 8.0.1272	587	Thursday, November 9, 2017	Approved
Vim Tux (Install) 8.0.1257	505	Sunday, November 5, 2017	Approved
Vim Tux (Install) 8.0.1203	649	Wednesday, October 18, 2017	Approved
Vim Tux (Install) 8.0.1157	677	Friday, September 29, 2017	Approved
Vim Tux (Install) 8.0.1088	684	Monday, September 11, 2017	Approved
Vim Tux (Install) 8.0.1010	605	Tuesday, August 29, 2017	Approved
Vim Tux (Install) 8.0.0737	769	Thursday, July 20, 2017	Approved
Vim Tux (Install) 8.0.0642	735	Sunday, June 18, 2017	Approved
Vim Tux (Install) 8.0.0584	915	Wednesday, April 26, 2017	Approved
Vim Tux (Install) 8.0.0575	555	Friday, April 21, 2017	Approved
Vim Tux (Install) 8.0.0430	915	Thursday, March 9, 2017	Approved
Vim Tux (Install) 8.0.0320	802	Friday, February 10, 2017	Approved
Vim Tux (Install) 8.0.0206	759	Friday, January 20, 2017	Approved
Vim Tux (Install) 8.0.0194	461	Tuesday, January 17, 2017	Approved
Vim Tux (Install) 8.0.0123	855	Friday, December 9, 2016	Approved
Vim Tux (Install) 8.0.0117	508	Friday, December 2, 2016	Approved
Vim Tux (Install) 8.0.0066	701	Thursday, November 10, 2016	Approved
Vim Tux (Install) 8.0.0051	648	Friday, October 28, 2016	Approved
Vim Tux (Install) 8.0.0045	529	Friday, October 21, 2016	Approved
Vim Tux (Install) 8.0.0017	602	Wednesday, September 28, 2016	Approved
Vim Tux (Install) 8.0.005	672	Friday, September 16, 2016	Approved
Vim Tux (Install) 7.4.2222	741	Thursday, August 18, 2016	Approved
Vim Tux (Install) 7.4.2180	370	Tuesday, August 9, 2016	Approved
Vim Tux (Install) 7.4.2153	398	Friday, August 5, 2016	Approved
Vim Tux (Install) 7.4.2089	601	Friday, July 22, 2016	Approved
Vim Tux (Install) 7.4.2034	362	Friday, July 15, 2016	Approved
Vim Tux (Install) 7.4.1998	374	Friday, July 8, 2016	Approved
Vim Tux (Install) 7.4.1987	409	Sunday, July 3, 2016	Approved
Vim Tux (Install) 7.4.1949	399	Thursday, June 23, 2016	Approved
Vim Tux (Install) 7.4.1913	413	Friday, June 10, 2016	Approved
Vim Tux (Install) 7.4.1905	460	Thursday, June 9, 2016	Approved
Vim Tux (Install) 7.4.1901	418	Tuesday, June 7, 2016	Approved
Vim Tux (Install) 7.4.1862	388	Thursday, June 2, 2016	Approved
Vim Tux (Install) 7.4.1856	375	Monday, May 30, 2016	Approved
Vim Tux (Install) 7.4.1848	376	Friday, May 27, 2016	Approved
Vim Tux (Install) 7.4.1842	363	Thursday, May 26, 2016	Approved
Vim Tux (Install) 7.4.1832	371	Thursday, May 19, 2016	Approved
Vim Tux (Install) 7.4.1829	368	Thursday, May 12, 2016	Approved
Vim Tux (Install) 7.4.1824	390	Monday, May 9, 2016	Approved

Release Notes

http://ftp.vim.org/pub/vim/patches/8.2/README

Dependencies

- vcredist2015
- chocolatey-core.extension (≥ 1.1.0)

Discussion for the Vim Tux (Install) Package

Ground Rules:

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

Resources

Events

Courses

151,619

135

02 Dec 2021

Vim Tux (Install)

Vim Tux (Install) 8.2.3717

Some Checks Have Failed or Are Not Yet Complete

Deployment Method: Individual Install, Upgrade, & Uninstall

Deployment Method:

1. Enter Your Internal Repository Url

2. Setup Your Environment

1. Ensure you are set for organizational deployment

2. Get the package into your environment

3. Copy Your Script

4. If applicable - Chocolatey configuration/installation

Package Parameters

Ground Rules: