Step 1: Review Your Packages

Step 2: Choose Your Integration Method

Step 3: Copy Your Script or Download Config

Option 1: Copy Script

Option 2: Download Config

Step 4: Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

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

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

Option 2: Internalized Package (Reliable, Scalable)

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

Step 5: Copy Your Script

See options you can pass to upgrade.

See best practices for scripting.

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

### c. Other Requirements ###

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

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

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

## 2. TOP LEVEL VARIABLES ##

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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

- name: Install and Configure Chocolatey
  hosts: all

## 2. TOP LEVEL VARIABLES ##
  vars:

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

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

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

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

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

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

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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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

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

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

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

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

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

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

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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

chocolatey_feature 'useBackgroundService' do
  action :enable
end

chocolatey_feature 'useBackgroundServiceWithNonAdministratorsOnly' do
  action :enable
end

chocolatey_feature 'allowBackgroundServiceUninstallsFromUserInstallsOnly' do
  action :enable
end

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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


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

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

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

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

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


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


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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Need Help? View our docs or file an issue.

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

Current Version	New Version

Passing
Failing
Pending
Unknown / Exempted

Downloads:

102,670

Downloads of v 8.1.1027:

394

Last Update:

21 Mar 2019

Package Maintainer(s):

Software Author(s):

Build: TuxProject.de
Developer: vim team

Tags:

vim-tux vim editor tux admin

Vim Tux

This is not the latest version of Vim Tux available.

8.1.1027 | Updated: 21 Mar 2019

Downloads:

102,670

Downloads of v 8.1.1027:

394

Maintainer(s):

Software Author(s):

Build: TuxProject.de
Developer: vim team

Tags:

vim-tux vim editor tux admin

1

2

3

Vim Tux 8.1.1027

This is not the latest version of Vim Tux available.

All Checks are Passing

3 Passing Tests

Show Checks

Validation Testing Passed

Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

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

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

To uninstall Vim Tux, 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 --internalize --version=8.1.1027 --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 -y --source="'INTERNAL REPO URL'" --version="'8.1.1027'" [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 -y --source="'INTERNAL REPO URL'" --version="'8.1.1027'" 
$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
  win_chocolatey:
    name: vim-tux
    version: '8.1.1027'
    source: INTERNAL REPO URL
    state: present

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


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

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


cChocoPackageInstaller vim-tux
{
    Name     = "vim-tux"
    Version  = "8.1.1027"
    Source   = "INTERNAL REPO URL"
}

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


package { 'vim-tux':
  ensure   => '8.1.1027',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

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

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

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

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

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

This package was approved as a trusted package on 21 Mar 2019.

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

#Install-VirtualPackage 'vim-tux.portable' 'vim-tux.install'

Virus Scan Results

vim-tux.8.1.1027.nupkg (b0f4e7275630) - ## / 58

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 8.2.3908	297	Tuesday, December 28, 2021	Approved
Vim Tux 8.2.3875	77	Thursday, December 23, 2021	Approved
Vim Tux 8.2.3858	73	Tuesday, December 21, 2021	Approved
Vim Tux 8.2.3836	66	Saturday, December 18, 2021	Approved
Vim Tux 8.2.3811	73	Thursday, December 16, 2021	Approved
Vim Tux 8.2.3794	78	Tuesday, December 14, 2021	Approved
Vim Tux 8.2.3763	99	Friday, December 10, 2021	Approved
Vim Tux 8.2.3757	70	Wednesday, December 8, 2021	Approved
Vim Tux 8.2.3718	93	Friday, December 3, 2021	Approved
Vim Tux 8.2.3717	70	Thursday, December 2, 2021	Approved
Vim Tux 8.2.3701	51	Tuesday, November 30, 2021	Approved
Vim Tux 8.2.3692	38	Monday, November 29, 2021	Approved
Vim Tux 8.2.3671	108	Friday, November 26, 2021	Approved
Vim Tux 8.2.3659	77	Thursday, November 25, 2021	Approved
Vim Tux 8.2.3651	70	Tuesday, November 23, 2021	Approved
Vim Tux 8.2.3646	57	Tuesday, November 23, 2021	Approved
Vim Tux 8.2.3623	79	Saturday, November 20, 2021	Approved
Vim Tux 8.2.3608	60	Thursday, November 18, 2021	Approved
Vim Tux 8.2.3595	86	Tuesday, November 16, 2021	Approved
Vim Tux 8.2.3579	163	Friday, November 5, 2021	Approved
Vim Tux 8.2.3565	140	Wednesday, October 27, 2021	Approved
Vim Tux 8.2.3551	114	Friday, October 22, 2021	Approved
Vim Tux 8.2.3545	71	Thursday, October 21, 2021	Approved
Vim Tux 8.2.3513	105	Saturday, October 16, 2021	Approved
Vim Tux 8.2.3505	101	Thursday, October 14, 2021	Approved
Vim Tux 8.2.3493	76	Monday, October 11, 2021	Approved
Vim Tux 8.2.3486	84	Saturday, October 9, 2021	Approved
Vim Tux 8.2.3484	78	Thursday, October 7, 2021	Approved
Vim Tux 8.2.3478	65	Wednesday, October 6, 2021	Approved
Vim Tux 8.2.3469	59	Tuesday, October 5, 2021	Approved
Vim Tux 8.2.3458	118	Tuesday, September 28, 2021	Approved
Vim Tux 8.2.3455	116	Thursday, September 23, 2021	Approved
Vim Tux 8.2.3450	93	Tuesday, September 21, 2021	Approved
Vim Tux 8.2.3416	151	Thursday, September 9, 2021	Approved
Vim Tux 8.2.3394	112	Thursday, September 2, 2021	Approved
Vim Tux 8.2.3391	54	Wednesday, September 1, 2021	Approved
Vim Tux 8.2.3376	107	Thursday, August 26, 2021	Approved
Vim Tux 8.2.3358	115	Friday, August 20, 2021	Approved
Vim Tux 8.2.3356	64	Wednesday, August 18, 2021	Approved
Vim Tux 8.2.3326	137	Wednesday, August 11, 2021	Approved
Vim Tux 8.2.3318	75	Monday, August 9, 2021	Approved
Vim Tux 8.2.3299	81	Friday, August 6, 2021	Approved
Vim Tux 8.2.3281	75	Wednesday, August 4, 2021	Approved
Vim Tux 8.2.3273	72	Monday, August 2, 2021	Approved
Vim Tux 8.2.3269	58	Monday, August 2, 2021	Approved
Vim Tux 8.2.3263	42	Sunday, August 1, 2021	Approved
Vim Tux 8.2.3253	50	Saturday, July 31, 2021	Approved
Vim Tux 8.2.3242	60	Thursday, July 29, 2021	Approved
Vim Tux 8.2.3223	88	Tuesday, July 27, 2021	Approved
Vim Tux 8.2.3204	94	Friday, July 23, 2021	Approved
Vim Tux 8.2.3187	104	Tuesday, July 20, 2021	Approved
Vim Tux 8.2.3171	107	Friday, July 16, 2021	Approved
Vim Tux 8.2.3158	79	Wednesday, July 14, 2021	Approved
Vim Tux 8.2.3154	97	Monday, July 12, 2021	Approved
Vim Tux 8.2.3131	94	Friday, July 9, 2021	Approved
Vim Tux 8.2.3120	79	Thursday, July 8, 2021	Approved
Vim Tux 8.2.3107	87	Tuesday, July 6, 2021	Approved
Vim Tux 8.2.3104	73	Monday, July 5, 2021	Approved
Vim Tux 8.2.3095	72	Sunday, July 4, 2021	Approved
Vim Tux 8.2.3080	107	Thursday, July 1, 2021	Approved
Vim Tux 8.2.3075	61	Wednesday, June 30, 2021	Approved
Vim Tux 8.2.3070	78	Tuesday, June 29, 2021	Approved
Vim Tux 8.2.3066	77	Monday, June 28, 2021	Approved
Vim Tux 8.2.3055	68	Sunday, June 27, 2021	Approved
Vim Tux 8.2.3043	97	Thursday, June 24, 2021	Approved
Vim Tux 8.2.3036	54	Wednesday, June 23, 2021	Approved
Vim Tux 8.2.3033	78	Tuesday, June 22, 2021	Approved
Vim Tux 8.2.3020	49	Sunday, June 20, 2021	Approved
Vim Tux 8.2.3017	80	Friday, June 18, 2021	Approved
Vim Tux 8.2.2840	307	Saturday, May 8, 2021	Approved
Vim Tux 8.2.2832	103	Wednesday, May 5, 2021	Approved
Vim Tux 8.2.2815	132	Wednesday, April 28, 2021	Approved
Vim Tux 8.2.2799	137	Thursday, April 22, 2021	Approved
Vim Tux 8.2.2794	60	Wednesday, April 21, 2021	Approved
Vim Tux 8.2.2763	129	Thursday, April 15, 2021	Approved
Vim Tux 8.2.2738	117	Friday, April 9, 2021	Approved
Vim Tux 8.2.2730	88	Wednesday, April 7, 2021	Approved
Vim Tux 8.2.2679	108	Wednesday, March 31, 2021	Approved
Vim Tux 8.2.2650	67	Friday, March 26, 2021	Approved
Vim Tux 8.2.2648	194	Wednesday, March 24, 2021	Approved
Vim Tux 8.2.2637	187	Tuesday, March 23, 2021	Approved
Vim Tux 8.2.2491	339	Thursday, February 11, 2021	Approved
Vim Tux 8.2.2425	217	Friday, January 29, 2021	Approved
Vim Tux 8.2.2129	428	Saturday, December 12, 2020	Approved
Vim Tux 8.2.1981	351	Saturday, November 14, 2020	Approved
Vim Tux 8.2.1955	286	Friday, November 6, 2020	Approved
Vim Tux 8.2.1923	264	Friday, October 30, 2020	Approved
Vim Tux 8.2.1905	228	Monday, October 26, 2020	Approved
Vim Tux 8.2.1883	172	Thursday, October 22, 2020	Approved
Vim Tux 8.2.1858	245	Sunday, October 18, 2020	Approved
Vim Tux 8.2.1776	333	Thursday, October 1, 2020	Approved
Vim Tux 8.2.1738	269	Friday, September 25, 2020	Approved
Vim Tux 8.2.1651	300	Thursday, September 10, 2020	Approved
Vim Tux 8.2.1058	571	Friday, June 26, 2020	Approved
Vim Tux 8.2.960	358	Friday, June 12, 2020	Approved
Vim Tux 8.2.950	185	Thursday, June 11, 2020	Approved
Vim Tux 8.2.882	364	Tuesday, June 2, 2020	Approved
Vim Tux 8.2.855	178	Sunday, May 31, 2020	Approved
Vim Tux 8.2.834	168	Friday, May 29, 2020	Approved
Vim Tux 8.2.829	237	Wednesday, May 27, 2020	Approved
Vim Tux 8.2.821	196	Tuesday, May 26, 2020	Approved
Vim Tux 8.2.806	197	Friday, May 22, 2020	Approved
Vim Tux 8.2.803	129	Thursday, May 21, 2020	Approved
Vim Tux 8.2.735	289	Tuesday, May 12, 2020	Approved
Vim Tux 8.2.713	171	Friday, May 8, 2020	Approved
Vim Tux 8.2.647	219	Monday, April 27, 2020	Approved
Vim Tux 8.2.640	89	Sunday, April 26, 2020	Approved
Vim Tux 8.2.625	221	Friday, April 24, 2020	Approved
Vim Tux 8.2.612	202	Tuesday, April 21, 2020	Approved
Vim Tux 8.2.592	193	Saturday, April 18, 2020	Approved
Vim Tux 8.2.585	170	Friday, April 17, 2020	Approved
Vim Tux 8.2.0357	506	Friday, March 6, 2020	Approved
Vim Tux 8.2.0324	265	Friday, February 28, 2020	Approved
Vim Tux 8.2.0313	150	Monday, February 24, 2020	Approved
Vim Tux 8.2.0294	191	Saturday, February 22, 2020	Approved
Vim Tux 8.2.0285	150	Friday, February 21, 2020	Approved
Vim Tux 8.2.0273	188	Tuesday, February 18, 2020	Approved
Vim Tux 8.2.0231	284	Sunday, February 9, 2020	Approved
Vim Tux 8.2.0184	286	Friday, January 31, 2020	Approved
Vim Tux 8.2.0147	247	Saturday, January 25, 2020	Approved
Vim Tux 8.2.0140	235	Wednesday, January 22, 2020	Approved
Vim Tux 8.2.0129	295	Sunday, January 19, 2020	Approved
Vim Tux 8.2.0114	309	Tuesday, January 14, 2020	Approved
Vim Tux 8.2.0109	234	Friday, January 10, 2020	Approved
Vim Tux 8.2.0092	248	Tuesday, January 7, 2020	Approved
Vim Tux 8.2.0080	266	Friday, January 3, 2020	Approved
Vim Tux 8.2.0065	135	Tuesday, December 31, 2019	Approved
Vim Tux 8.2.0055	104	Monday, December 30, 2019	Approved
Vim Tux 8.2.0052	122	Sunday, December 29, 2019	Approved
Vim Tux 8.1.2333	677	Friday, November 22, 2019	Approved
Vim Tux 8.1.2323	295	Thursday, November 21, 2019	Approved
Vim Tux 8.1.2311	379	Sunday, November 17, 2019	Approved
Vim Tux 8.1.2300	296	Thursday, November 14, 2019	Approved
Vim Tux 8.1.2204	591	Thursday, October 24, 2019	Approved
Vim Tux 8.1.2200	333	Wednesday, October 23, 2019	Approved
Vim Tux 8.1.2148	564	Monday, October 14, 2019	Approved
Vim Tux 8.1.2133	346	Friday, October 11, 2019	Approved
Vim Tux 8.1.2117	442	Sunday, October 6, 2019	Approved
Vim Tux 8.1.2108	366	Thursday, October 3, 2019	Approved
Vim Tux 8.1.2103	378	Tuesday, October 1, 2019	Approved
Vim Tux 8.1.2079	434	Friday, September 27, 2019	Approved
Vim Tux 8.1.2071	386	Wednesday, September 25, 2019	Approved
Vim Tux 8.1.2052	452	Thursday, September 19, 2019	Approved
Vim Tux 8.1.2019	540	Tuesday, September 10, 2019	Approved
Vim Tux 8.1.2004	357	Sunday, September 8, 2019	Approved
Vim Tux 8.1.1995	117	Saturday, September 7, 2019	Approved
Vim Tux 8.1.1986	363	Thursday, September 5, 2019	Approved
Vim Tux 8.1.1961	392	Monday, September 2, 2019	Approved
Vim Tux 8.1.1927	474	Monday, August 26, 2019	Approved
Vim Tux 8.1.1915	266	Saturday, August 24, 2019	Approved
Vim Tux 8.1.1906	317	Thursday, August 22, 2019	Approved
Vim Tux 8.1.1890	362	Tuesday, August 20, 2019	Approved
Vim Tux 8.1.1836	423	Sunday, August 11, 2019	Approved
Vim Tux 8.1.1744	507	Thursday, July 25, 2019	Approved
Vim Tux 8.1.1729	310	Tuesday, July 23, 2019	Approved
Vim Tux 8.1.1713	332	Friday, July 19, 2019	Approved
Vim Tux 8.1.1695	361	Tuesday, July 16, 2019	Approved
Vim Tux 8.1.1669	333	Saturday, July 13, 2019	Approved
Vim Tux 8.1.1655	382	Tuesday, July 9, 2019	Approved
Vim Tux 8.1.1631	354	Friday, July 5, 2019	Approved
Vim Tux 8.1.1601	442	Thursday, June 27, 2019	Approved
Vim Tux 8.1.1587	284	Tuesday, June 25, 2019	Approved
Vim Tux 8.1.1566	432	Tuesday, June 18, 2019	Approved
Vim Tux 8.1.1557	268	Monday, June 17, 2019	Approved
Vim Tux 8.1.1536	111	Sunday, June 16, 2019	Approved
Vim Tux 8.1.1523	118	Friday, June 14, 2019	Approved
Vim Tux 8.1.1515	101	Tuesday, June 11, 2019	Approved
Vim Tux 8.1.1511	370	Monday, June 10, 2019	Approved
Vim Tux 8.1.1455	131	Monday, June 3, 2019	Approved
Vim Tux 8.1.1432	453	Friday, May 31, 2019	Approved
Vim Tux 8.1.1413	312	Tuesday, May 28, 2019	Approved
Vim Tux 8.1.1373	383	Friday, May 24, 2019	Approved
Vim Tux 8.1.1364	171	Thursday, May 23, 2019	Approved
Vim Tux 8.1.1353	377	Monday, May 20, 2019	Approved
Vim Tux 8.1.1333	335	Thursday, May 16, 2019	Approved
Vim Tux 8.1.1328	336	Monday, May 13, 2019	Approved
Vim Tux 8.1.1312	256	Saturday, May 11, 2019	Approved
Vim Tux 8.1.1298	278	Thursday, May 9, 2019	Approved
Vim Tux 8.1.1286	310	Tuesday, May 7, 2019	Approved
Vim Tux 8.1.1229	470	Monday, April 29, 2019	Approved
Vim Tux 8.1.1204	270	Friday, April 26, 2019	Approved
Vim Tux 8.1.1197	354	Monday, April 22, 2019	Approved
Vim Tux 8.1.1183	289	Thursday, April 18, 2019	Approved
Vim Tux 8.1.1173	313	Monday, April 15, 2019	Approved
Vim Tux 8.1.1165	237	Sunday, April 14, 2019	Approved
Vim Tux 8.1.1140	396	Tuesday, April 9, 2019	Approved
Vim Tux 8.1.1136	272	Monday, April 8, 2019	Approved
Vim Tux 8.1.1124	208	Sunday, April 7, 2019	Approved
Vim Tux 8.1.1116	217	Thursday, April 4, 2019	Approved
Vim Tux 8.1.1103	226	Thursday, April 4, 2019	Approved
Vim Tux 8.1.1073	410	Saturday, March 30, 2019	Approved
Vim Tux 8.1.1057	327	Thursday, March 28, 2019	Approved
Vim Tux 8.1.1045	127	Sunday, March 24, 2019	Approved
Vim Tux 8.1.1032	142	Friday, March 22, 2019	Approved
Vim Tux 8.1.1027	394	Thursday, March 21, 2019	Approved
Vim Tux 8.1.1004	503	Monday, March 11, 2019	Approved
Vim Tux 8.1.998	335	Friday, March 8, 2019	Approved
Vim Tux 8.1.990	431	Sunday, March 3, 2019	Approved
Vim Tux 8.1.984	352	Thursday, February 28, 2019	Approved
Vim Tux 8.1.978	351	Saturday, February 23, 2019	Approved
Vim Tux 8.1.966	280	Friday, February 22, 2019	Approved
Vim Tux 8.1.947	365	Tuesday, February 19, 2019	Approved
Vim Tux 8.1.934	278	Sunday, February 17, 2019	Approved
Vim Tux 8.1.926	205	Saturday, February 16, 2019	Approved
Vim Tux 8.1.909	263	Thursday, February 14, 2019	Approved
Vim Tux 8.1.895	298	Tuesday, February 12, 2019	Approved
Vim Tux 8.1.0885	259	Sunday, February 10, 2019	Approved
Vim Tux 8.1.0877	175	Thursday, February 7, 2019	Approved
Vim Tux 8.1.0871	326	Monday, February 4, 2019	Approved
Vim Tux 8.1.0868	189	Sunday, February 3, 2019	Approved
Vim Tux 8.1.0865	249	Saturday, February 2, 2019	Approved
Vim Tux 8.1.0842	270	Thursday, January 31, 2019	Approved
Vim Tux 8.1.0837	337	Monday, January 28, 2019	Approved
Vim Tux 8.1.0814	281	Friday, January 25, 2019	Approved
Vim Tux 8.1.0796	279	Thursday, January 24, 2019	Approved
Vim Tux 8.1.0788	295	Tuesday, January 22, 2019	Approved
Vim Tux 8.1.0757	338	Thursday, January 17, 2019	Approved
Vim Tux 8.1.0749	255	Tuesday, January 15, 2019	Approved
Vim Tux 8.1.0727	270	Saturday, January 12, 2019	Approved
Vim Tux 8.1.0712	284	Thursday, January 10, 2019	Approved
Vim Tux 8.1.0700	313	Tuesday, January 8, 2019	Approved
Vim Tux 8.1.0690	313	Saturday, January 5, 2019	Approved
Vim Tux 8.1.0681	268	Thursday, January 3, 2019	Approved
Vim Tux 8.1.0674	225	Wednesday, January 2, 2019	Approved
Vim Tux 8.1.0647	292	Friday, December 28, 2018	Approved
Vim Tux 8.1.0635	232	Wednesday, December 26, 2018	Approved
Vim Tux 8.1.0630	210	Tuesday, December 25, 2018	Approved
Vim Tux 8.1.0629	225	Monday, December 24, 2018	Approved
Vim Tux 8.1.0622	201	Sunday, December 23, 2018	Approved
Vim Tux 8.1.0617	208	Saturday, December 22, 2018	Approved
Vim Tux 8.1.0594	384	Sunday, December 16, 2018	Approved
Vim Tux 8.1.0577	279	Thursday, December 13, 2018	Approved
Vim Tux 8.1.0551	527	Friday, November 30, 2018	Approved
Vim Tux 8.1.0547	369	Monday, November 26, 2018	Approved
Vim Tux 8.1.0536	387	Tuesday, November 20, 2018	Approved
Vim Tux 8.1.0524	401	Tuesday, November 13, 2018	Approved
Vim Tux 8.1.0513	317	Thursday, November 8, 2018	Approved
Vim Tux 8.1.0509	326	Sunday, November 4, 2018	Approved
Vim Tux 8.1.0498	323	Sunday, October 28, 2018	Approved
Vim Tux 8.1.0489	329	Monday, October 22, 2018	Approved
Vim Tux 8.1.0474	340	Monday, October 15, 2018	Approved
Vim Tux 8.1.0470	283	Friday, October 12, 2018	Approved
Vim Tux 8.1.0451	342	Friday, October 5, 2018	Approved
Vim Tux 8.1.0442	312	Monday, October 1, 2018	Approved
Vim Tux 8.1.0436	304	Thursday, September 27, 2018	Approved
Vim Tux 8.1.0425	329	Saturday, September 22, 2018	Approved
Vim Tux 8.1.0408	238	Thursday, September 20, 2018	Approved
Vim Tux 8.1.0401	250	Tuesday, September 18, 2018	Approved
Vim Tux 8.1.0385	279	Friday, September 14, 2018	Approved
Vim Tux 8.1.0371	243	Thursday, September 13, 2018	Approved
Vim Tux 8.1.0362	288	Tuesday, September 11, 2018	Approved
Vim Tux 8.1.0354	182	Sunday, September 9, 2018	Approved
Vim Tux 8.1.0347	305	Thursday, September 6, 2018	Approved
Vim Tux 8.1.0342	271	Sunday, September 2, 2018	Approved
Vim Tux 8.1.0332	278	Thursday, August 30, 2018	Approved
Vim Tux 8.1.0327	264	Sunday, August 26, 2018	Approved
Vim Tux 8.1.0318	227	Thursday, August 23, 2018	Approved
Vim Tux 8.1.0301	164	Tuesday, August 21, 2018	Approved
Vim Tux 8.1.0297	237	Monday, August 20, 2018	Approved
Vim Tux 8.1.0288	258	Thursday, August 16, 2018	Approved
Vim Tux 8.1.0278	267	Monday, August 13, 2018	Approved
Vim Tux 8.1.0271	225	Sunday, August 12, 2018	Approved
Vim Tux 8.1.0259	245	Friday, August 10, 2018	Approved
Vim Tux 8.1.0239	308	Sunday, August 5, 2018	Approved
Vim Tux 8.1.0229	296	Tuesday, July 31, 2018	Approved
Vim Tux 8.1.0221	257	Sunday, July 29, 2018	Approved
Vim Tux 8.1.0210	245	Thursday, July 26, 2018	Approved
Vim Tux 8.1.0207	192	Tuesday, July 24, 2018	Approved
Vim Tux 8.1.0203	335	Monday, July 23, 2018	Approved
Vim Tux 8.1.0199	252	Saturday, July 21, 2018	Approved
Vim Tux 8.1.0196	240	Friday, July 20, 2018	Approved
Vim Tux 8.1.0191	286	Tuesday, July 17, 2018	Approved
Vim Tux 8.1.0186	272	Sunday, July 15, 2018	Approved
Vim Tux 8.1.0173	317	Tuesday, July 10, 2018	Approved
Vim Tux 8.1.0153	338	Friday, July 6, 2018	Approved
Vim Tux 8.1.0138	301	Tuesday, July 3, 2018	Approved
Vim Tux 8.1.0133	245	Sunday, July 1, 2018	Approved
Vim Tux 8.1.0126	211	Friday, June 29, 2018	Approved
Vim Tux 8.1.0105	299	Sunday, June 24, 2018	Approved
Vim Tux 8.1.0054	406	Thursday, June 14, 2018	Approved
Vim Tux 8.1.0034	341	Tuesday, June 5, 2018	Approved
Vim Tux 8.1.0022	383	Friday, May 25, 2018	Approved
Vim Tux 8.1.0013	318	Tuesday, May 22, 2018	Approved
Vim Tux 8.1.0009	230	Monday, May 21, 2018	Approved
Vim Tux 8.1.0004	231	Sunday, May 20, 2018	Approved
Vim Tux 8.1.0000	248	Friday, May 18, 2018	Approved
Vim Tux 8.0.1848	302	Thursday, May 17, 2018	Approved
Vim Tux 8.0.1831	329	Monday, May 14, 2018	Approved
Vim Tux 8.0.1820	271	Sunday, May 13, 2018	Approved
Vim Tux 8.0.1806	332	Thursday, May 10, 2018	Approved
Vim Tux 8.0.1799	313	Monday, May 7, 2018	Approved
Vim Tux 8.0.1794	240	Sunday, May 6, 2018	Approved
Vim Tux 8.0.1790	274	Friday, May 4, 2018	Approved
Vim Tux 8.0.1788	254	Thursday, May 3, 2018	Approved
Vim Tux 8.0.1774	330	Monday, April 30, 2018	Approved
Vim Tux 8.0.1765	332	Thursday, April 26, 2018	Approved
Vim Tux 8.0.1748	285	Sunday, April 22, 2018	Approved
Vim Tux 8.0.1736	275	Friday, April 20, 2018	Approved
Vim Tux 8.0.1727	301	Wednesday, April 18, 2018	Approved
Vim Tux 8.0.1705	340	Saturday, April 14, 2018	Approved
Vim Tux 8.0.1679	420	Monday, April 9, 2018	Approved
Vim Tux 8.0.1664	279	Saturday, April 7, 2018	Approved
Vim Tux 8.0.1655	346	Saturday, March 31, 2018	Approved
Vim Tux 8.0.1638	435	Sunday, March 25, 2018	Approved
Vim Tux 8.0.1626	320	Thursday, March 22, 2018	Approved
Vim Tux 8.0.1612	341	Saturday, March 17, 2018	Approved
Vim Tux 8.0.1601	333	Tuesday, March 13, 2018	Approved
Vim Tux 8.0.1591	370	Friday, March 9, 2018	Approved
Vim Tux 8.0.1563	366	Sunday, March 4, 2018	Approved
Vim Tux 8.0.1553	290	Friday, March 2, 2018	Approved
Vim Tux 8.0.1532	388	Sunday, February 25, 2018	Approved
Vim Tux 8.0.1504	443	Thursday, February 15, 2018	Approved
Vim Tux 8.0.1473	406	Thursday, February 8, 2018	Approved
Vim Tux 8.0.1451	399	Saturday, February 3, 2018	Approved
Vim Tux 8.0.1438	364	Tuesday, January 30, 2018	Approved
Vim Tux 8.0.1431	387	Saturday, January 27, 2018	Approved
Vim Tux 8.0.1428	524	Thursday, January 4, 2018	Approved
Vim Tux 8.0.1422	410	Saturday, December 30, 2017	Approved
Vim Tux 8.0.1390	467	Sunday, December 17, 2017	Approved
Vim Tux 8.0.1379	342	Thursday, December 14, 2017	Approved
Vim Tux 8.0.1376	406	Thursday, December 7, 2017	Approved
Vim Tux 8.0.1358	394	Friday, December 1, 2017	Approved
Vim Tux 8.0.1330	424	Thursday, November 23, 2017	Approved
Vim Tux 8.0.1311	396	Monday, November 20, 2017	Approved
Vim Tux 8.0.1305	341	Saturday, November 18, 2017	Approved
Vim Tux 8.0.1272	401	Thursday, November 9, 2017	Approved
Vim Tux 8.0.1257	450	Sunday, November 5, 2017	Approved
Vim Tux 8.0.1203	582	Wednesday, October 18, 2017	Approved
Vim Tux 8.0.1088	671	Monday, September 11, 2017	Approved
Vim Tux 8.0.1010	550	Tuesday, August 29, 2017	Approved
Vim Tux 8.0.0987	442	Wednesday, August 23, 2017	Approved
Vim Tux 8.0.0737	612	Thursday, July 20, 2017	Approved
Vim Tux 8.0.0642	629	Sunday, June 18, 2017	Approved
Vim Tux 8.0.0584	725	Wednesday, April 26, 2017	Approved
Vim Tux 8.0.0575	392	Friday, April 21, 2017	Approved
Vim Tux 8.0.0430	776	Thursday, March 9, 2017	Approved
Vim Tux 8.0.0320	643	Friday, February 10, 2017	Approved
Vim Tux 8.0.0206	596	Friday, January 20, 2017	Approved
Vim Tux 8.0.0194	365	Tuesday, January 17, 2017	Approved
Vim Tux 8.0.0123	694	Friday, December 9, 2016	Approved
Vim Tux 8.0.0117	394	Friday, December 2, 2016	Approved
Vim Tux 8.0.0066	614	Thursday, November 10, 2016	Approved
Vim Tux 8.0.0051	552	Friday, October 28, 2016	Approved
Vim Tux 8.0.0045	487	Friday, October 21, 2016	Approved
Vim Tux 8.0.0017	577	Wednesday, September 28, 2016	Approved
Vim Tux 8.0.005	512	Friday, September 16, 2016	Approved
Vim Tux 7.4.2222	639	Thursday, August 18, 2016	Approved
Vim Tux 7.4.2180	343	Tuesday, August 9, 2016	Approved
Vim Tux 7.4.2153	373	Friday, August 5, 2016	Approved
Vim Tux 7.4.2089	606	Friday, July 22, 2016	Approved
Vim Tux 7.4.2034	362	Friday, July 15, 2016	Approved
Vim Tux 7.4.1998	366	Friday, July 8, 2016	Approved
Vim Tux 7.4.1987	334	Sunday, July 3, 2016	Approved
Vim Tux 7.4.1949	381	Thursday, June 23, 2016	Approved
Vim Tux 7.4.1913	327	Friday, June 10, 2016	Approved
Vim Tux 7.4.1905	346	Thursday, June 9, 2016	Approved
Vim Tux 7.4.1901	350	Tuesday, June 7, 2016	Approved
Vim Tux 7.4.1862	347	Thursday, June 2, 2016	Approved
Vim Tux 7.4.1856	344	Monday, May 30, 2016	Approved
Vim Tux 7.4.1848	356	Friday, May 27, 2016	Approved
Vim Tux 7.4.1842	335	Thursday, May 26, 2016	Approved
Vim Tux 7.4.1832	350	Thursday, May 19, 2016	Approved
Vim Tux 7.4.1829	381	Thursday, May 12, 2016	Approved
Vim Tux 7.4.1824	333	Monday, May 9, 2016	Approved

Release Notes

ftp://ftp.vim.org/pub/vim/patches/8.1/README

Dependencies

- vim-tux.install (≥ 8.1.1027)

Discussion for the Vim Tux Package

Ground Rules:

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

102,670

394

21 Mar 2019

Vim Tux

1 2 3 Vim Tux 8.1.1027

All Checks are Passing

Deployment Method: Individual Install, Upgrade, & Uninstall

Deployment Method:

1. Enter Your Internal Repository Url

2. Setup Your Environment

1. Ensure you are set for organizational deployment

2. Get the package into your environment

3. Copy Your Script

4. If applicable - Chocolatey configuration/installation

Package Parameters

Ground Rules:

1

2

3

Vim Tux 8.1.1027