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

3,501

Downloads of v 5.0:

30

Last Update:

18 Feb 2023

Package Maintainer(s):

SebastianK

Software Author(s):

Rick Brewster
dotPDN

Tags:

admin editing freeware graphics image paint paint.net photo

Paint.NET (Portable)

Downloads:

3,501

Downloads of v 5.0:

Maintainer(s):

SebastianK

Software Author(s):

Rick Brewster
dotPDN

Tags:

admin editing freeware graphics image paint paint.net photo

Paint.NET (Portable)

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

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

This package was rejected on 18 Feb 2023. The reviewer Pauby has listed the following reason(s):

SebastianK (maintainer) on 12 Jan 2023 22:30:47 +00:00:

User 'SebastianK' (maintainer) submitted package.

SebastianK (maintainer) on 12 Jan 2023 22:35:27 +00:00:

User 'SebastianK' (maintainer) submitted package.

SebastianK (maintainer) on 12 Jan 2023 22:37:23 +00:00:

User 'SebastianK' (maintainer) submitted package.

chocolatey-ops (reviewer) on 12 Jan 2023 23:12:26 +00:00:

paint.net.portable has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

chocolatey-ops (reviewer) on 12 Jan 2023 23:32:28 +00:00:

paint.net.portable has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/3f7a06e4d7ef6552766c6b33eab3ec5e for details.
This is an FYI only. There is no action you need to take.

chocolatey-ops (reviewer) on 13 Jan 2023 00:16:18 +00:00:

paint.net.portable has passed automated virus scanning.

Pauby (reviewer) on 16 Feb 2023 18:56:16 +00:00:

Hi, a couple of issues / suggestions / questions:

On line 7 of your chocolateyInsxtall.ps1 you are using a Get-Item to fetch the binary from the package folder. Please use the full name for the file.
Please move the 'uninstall' functionality from your chocolateyInstall.ps1 into a chocolateyBeforeModiy.ps1 that will run upon upgrade and uninstall.
Please add $ErrorActionPreference = 'Stop' to the top of your chocolateyUIninstall.ps1.
Please add a From: <LICENSE URL> to the top of your LICENSE.txt file.
The x32 link in the VERIFICATION.txt file is not a valid link.

Thanks.

Paul

SebastianK (maintainer) on 17 Feb 2023 23:52:10 +00:00:

User 'SebastianK' (maintainer) submitted package.

SebastianK (maintainer) on 17 Feb 2023 23:55:58 +00:00:

User 'SebastianK' (maintainer) submitted package.

SebastianK (maintainer) on 17 Feb 2023 23:57:26 +00:00:

Hey Paul,

thanks for the feedback.

I've changed my update.ps1 to replace the FileFullPath always with the latest name in chocolateyInstall.ps1.
I've added a chocolateyBeforeModiy.ps1 file and put the cleanup zip tasks there.
Is also added.
The license URL is in the bottom of the VERIFICATION.txt but I've now also added it to the top of LICENSE.txt
This will be tricky to do, since the version 5.0 is not available anymore, and since my package is still in moderation process I also cannot push 5.0.1 which would have a valid download link for verification.

Thanks!

SebastianK (maintainer) on 18 Feb 2023 00:00:28 +00:00:

User 'SebastianK' (maintainer) submitted package.

chocolatey-ops (reviewer) on 18 Feb 2023 00:36:13 +00:00:

Notes

Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

chocolatey-ops (reviewer) on 18 Feb 2023 00:48:34 +00:00:

paint.net.portable has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/427c031cdae34a6b7df5f0d1bca752cb for details.
This is an FYI only. There is no action you need to take.

chocolatey-ops (reviewer) on 18 Feb 2023 01:02:23 +00:00:

paint.net.portable has been flagged as part of automated virus scanning.
Package virus scanning found that at least 1 file within, or downloaded by, the package has between 1 and 5 VirusTotal detections associated with it.
This is not enough detections to prevent the approval of this package version.

Pauby (reviewer) on 18 Feb 2023 13:36:27 +00:00:

> This will be tricky to do, since the version 5.0 is not available anymore, and since my package is still in moderation process I also cannot push 5.0.1 which would have a valid download link for verification.

I see you removed that link so the package is now x64 only?

There are two options:

We keep the package (not just this version) x64 only. It's not going to be a good user experience if we go back and forth between the package having x86 and x64 versions of the software then only x64.
We reject this version and let you push 5.0.1 which has both x64 and x86 and the links in VERIFICATION.txt will be valid?

Let me know what you want to do.

SebastianK (maintainer) on 18 Feb 2023 22:15:51 +00:00:

Hi Paul,

then please reject this one, so that I can push 5.0.1.
I'll only add the x64 variant then, since the 32-bit support was dropped by the dev.
Thanks!

Pauby (reviewer) on 18 Feb 2023 23:58:16 +00:00:

Rejected at maintainers request.
Status Change - Changed status of package from 'submitted' to 'rejected'.

Description

Paint.NET is free image and photo editing software for PCs that run Windows.
It features an intuitive and innovative user interface with support for layers,
unlimited undo, special effects, and a wide variety of useful and powerful tools.
An active and growing online community provides friendly help, tutorials, and plugins.

Features

Simple, intuitive, and innovative user interface
Performance
Support for layers
Unlimited history
Active Online Community
Automatically Updated
Special Effects
Powerful Tools

Files

tools\chocolateyBeforeModiy.ps1

$ErrorActionPreference = 'Stop'

$toolsPath = Split-Path $MyInvocation.MyCommand.Definition

Remove-Item $toolsPath\*.zip -ea 0

tools\chocolateyInstall.ps1

$ErrorActionPreference = 'Stop'

$toolsPath = Split-Path $MyInvocation.MyCommand.Definition

$packageArgs = @{
  PackageName    = 'paint.net.portable'
  FileFullPath   = "$toolsPath\paint.net.5.0.portable.x64_x64.zip"
  Destination    = $toolsPath
}

Get-ChocolateyUnzip @packageArgs

$Shortcut = Get-ChildItem $toolsPath -Recurse -Include paintdotnet.exe | Select-Object -First 1
Install-ChocolateyShortcut -shortcutFilePath "$env:ALLUSERSPROFILE\Microsoft\Windows\Start Menu\Programs\Paint.Net.lnk" $Shortcut -WorkingDirectory "$toolsPath"

tools\chocolateyUninstall.ps1

$ErrorActionPreference = 'Stop'

$icon_name = (Get-ChildItem "$env:ALLUSERSPROFILE\Microsoft\Windows\Start Menu\Programs\" -Filter "Paint.Net.lnk" -ErrorAction SilentlyContinue).FullName
Remove-Item $icon_name -ErrorAction SilentlyContinue

tools\paint.net.5.0.portable.x64_x64.zip

md5: EE9E7ABB7835B3E2C4CD7B290A43FD22 | sha1: C30F0394B2043211965BEB24996CE5D7DE7FFE00 | sha256: 3E88D0B0480921D559F10078C657B0E7E31531A57ECFAC340151D84F7D548FE7 | sha512: ED9C6B214B8AC293C6FB2283437A839188DF82327917DE270B04516D9157996464652569BF5720E9A3F58008692AA6F49D038F1F7C2625A40AFAE32D13728DEA

legal\VERIFICATION.txt

VERIFICATION

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

Package can be verified like this:

1. Go to

   x64: https://github.com/paintdotnet/release/releases/download/v5.0/paint.net.5.0.portable.x64.zip
   to download the installer.

2. You can use one of the following methods to obtain the SHA256 checksum:
   - Use powershell function 'Get-FileHash'
   - Use Chocolatey utility 'checksum.exe'

   checksum64: 3E88D0B0480921D559F10078C657B0E7E31531A57ECFAC340151D84F7D548FE7

File 'license.txt' is obtained from:
   https://www.getpaint.net/license.html

legal\LICENSE.txt

https://www.getpaint.net/license.html

Paint.NET (R)
Copyright (C) dotPDN LLC, Rick Brewster, and contributors. All Rights Reserved.
Paint.NET is a registered trademark of dotPDN LLC.

Paint.NET is free for use in any environment, including but not necessarily limited to: personal, academic, commercial, government, business, non-profit, and for-profit. "Free" in the preceding sentence means that there is no cost or charge associated with the installation and use of paint.net. Donations are always appreciated, of course! http://www.getpaint.net/donate.html

Permission is hereby granted, free of charge, to any person obtaining a copy of this software (the "Software"), to use the Software without restriction, including the rights to use, copy, publish, and distribute the Software, and to permit persons to whom the Software is furnished to do so.

You may not modify, adapt, rent, lease, loan, sell, or create derivative works based upon the Software or any part thereof. However, certain icons used in the paint.net user interface are from or adapted from those in the "Crystal" icon set, http://www.everaldo.com/crystal/, or the "Oxygen" icon set, http://www.oxygen-icons.org/. These icons are covered by the LGPL license, http://www.gnu.org/copyleft/lesser.html. These icons are stored as "loose" PNG image files in the Resources\en-US\ directory where paint.net is installed.

The above copyright notice and this permission notice shall be included in all copies of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Virus Scan Results

Microsoft.DiaSymReader.Native.amd64.dll (3aecc22ececf) - ## / 70
D3DCompiler_47_cor3.dll (ff5dddae92b3) - ## / 70
msquic.dll (2680c12fe5ee) - ## / 71
PresentationNative_cor3.dll (62505d6fede4) - ## / 67
vcruntime140.dll (76fdb83fde23) - ## / 70
vcruntime140_1.dll (e0b66601cc28) - ## / 70
msvcp140.dll (cb3c74d6fcc0) - ## / 69
paint.net.5.0.portable.x64_x64.zip (3e88d0b04809) - ## / 61
msvcp140_1.dll (8e49a6d937ee) - ## / 69
msvcp140_2.dll (25305353c51a) - ## / 69
msvcp140_atomic_wait.dll (6816a8212a20) - ## / 69
msvcp140_codecvt_ids.dll (478e7a1eec4e) - ## / 69
vcomp140.dll (cb721f775cde) - ## / 70
paint.net.portable.5.0.nupkg (4c6e6a8ed314) - ## / 62
Accessibility.dll (ebea3f1a2874) - ## / 70
clretwrc.dll (ed03220755aa) - ## / 70
clrgc.dll (6cba4d62ae51) - ## / 70
clrjit.dll (b4dc6fb897d2) - ## / 68
CommunityToolkit.HighPerformance.dll (418a0ff6893c) - ## / 68
ComputeSharp.Core.dll (514b089b8d51) - ## / 70
ComputeSharp.D2D1.dll (81ce8eb868a4) - ## / 69
coreclr.dll (c85328a6f423) - ## / 68
Crc32.NET.dll (1a707c3c3b0b) - ## / 70
createdump.exe (f33d6ad42dad) - ## / 71
DirectWriteForwarder.dll (aab760826797) - ## / 61
hostfxr.dll (cea44470b8c5) - ## / 70
hostpolicy.dll (3b64012e9430) - ## / 70
ijwhost.dll (1648452e2a51) - ## / 69
ilasm.exe (b72680e2c42d) - ## / 71
ildasm.exe (199eb6abea80) - ## / 70
Interop.WIA.dll (a768a6ef1fb3) - ## / 70
K4os.Compression.LZ4.dll (a7f1318b41dd) - ## / 69
Microsoft.CSharp.dll (e7db31d0b6b9) - ## / 70
Microsoft.VisualBasic.Core.dll (e483b2ff3aeb) - ## / 69
Microsoft.VisualBasic.dll (458d85edea93) - ## / 69
Microsoft.VisualBasic.Forms.dll (4da0dc3c4d74) - ## / 70
Microsoft.Win32.Primitives.dll (e5c8f8e39803) - ## / 70
Microsoft.Win32.Registry.AccessControl.dll (7bcfe8b7b0d1) - ## / 70
Microsoft.Win32.Registry.dll (b2588356edaa) - ## / 69
Microsoft.Win32.SystemEvents.dll (a7095a937c58) - ## / 70
Mono.Cecil.dll (540442b40ff6) - ## / 69
Mono.Cecil.Mdb.dll (c40e720d0daf) - ## / 63
Mono.Cecil.Pdb.dll (4b88a8a064a6) - ## / 68
Mono.Cecil.Rocks.dll (53c306235b1d) - ## / 70
mscordaccore.dll (014a819b0cbf) - ## / 69
mscordbi.dll (5a6783581f26) - ## / 70
mscorlib.dll (cc836713b786) - ## / 69
mscorrc.dll (a4cbb168e847) - ## / 70
nethost.dll (5ef7eca8a93c) - ## / 68
netstandard.dll (372779ca3aa6) - ## / 70
Newtonsoft.Json.dll (615a05c5ec73) - ## / 70
PaintDotNet.Base.dll (c02126a379a4) - ## / 68
PaintDotNet.Collections.dll (60954201011c) - ## / 70
PaintDotNet.ComponentModel.dll (ba64638ce607) - ## / 70
PaintDotNet.Core.dll (c29085a2a781) - ## / 60
PaintDotNet.Data.dll (765e7678b52d) - ## / 70
paintdotnet.dll (e7bb1c943e0c) - ## / 69
PaintDotNet.Effects.Core.dll (986322444c36) - ## / 68
PaintDotNet.Effects.dll (de7ef04645f9) - ## / 70
PaintDotNet.Effects.Gpu.dll (42b368127223) - ## / 67
PaintDotNet.Effects.Legacy.dll (b3b245ce0a41) - ## / 69
paintdotnet.exe (e651cd983dc6) - ## / 70
PaintDotNet.Framework.dll (1379ecba4d89) - ## / 64
PaintDotNet.Fundamentals.dll (551a7b4f4260) - ## / 60
PaintDotNet.ObjectModel.dll (0fe62317363d) - ## / 70
PaintDotNet.Plugins.Compatibility.dll (a07f16758786) - ## / 67
PaintDotNet.Primitives.dll (ebc02fcbd6b2) - ## / 69
PaintDotNet.PropertySystem.dll (9845d0949fe9) - ## / 69
PaintDotNet.Resources.dll (608d636f86ba) - ## / 70
PaintDotNet.Runtime.dll (094438c1aa9b) - ## / 65
PaintDotNet.ShellExtension.x64.dll (1e1954a867bd) - ## / 68
PaintDotNet.SystemLayer.dll (13941b7ebbd6) - ## / 69
PaintDotNet.SystemLayer.Native.x64.dll (8dfbb65b4187) - ## / 69
PaintDotNet.Systrace.dll (98f8d301d38c) - ## / 70
PaintDotNet.UI.dll (6850c1d98e34) - ## / 70
PaintDotNet.Windows.Core.dll (9ee2c9765e29) - ## / 70
PaintDotNet.Windows.dll (9386a5ac3e1b) - ## / 70
PaintDotNet.Windows.Framework.dll (6e9f22792bb9) - ## / 65
PenImc_cor3.dll (78b78f1f87fe) - ## / 68
PhotoSauce.MagicScaler.dll (b5b7fd897237) - ## / 70
PointerToolkit.dll (d4bfa778004d) - ## / 70
PointerToolkit.TerraFX.Interop.Windows.dll (cc16fdccb3f6) - ## / 69
PresentationCore.dll (36409c99688c) - ## / 69
PresentationFramework-SystemCore.dll (aa0bbd898937) - ## / 70
PresentationFramework-SystemData.dll (afa3cd5d0791) - ## / 70
PresentationFramework-SystemDrawing.dll (2f2590f9546b) - ## / 69
PresentationFramework-SystemXml.dll (29e0b4217244) - ## / 70
PresentationFramework-SystemXmlLinq.dll (2d9df2379eeb) - ## / 70
PresentationFramework.Aero.dll (ebd9198b9a02) - ## / 70
PresentationFramework.Aero2.dll (4aac17656fc5) - ## / 70
PresentationFramework.AeroLite.dll (e87b8ce1557c) - ## / 67
PresentationFramework.Classic.dll (6a73b63f138b) - ## / 68
PresentationFramework.dll (7bceefa8c121) - ## / 69
PresentationFramework.Luna.dll (d815325002ce) - ## / 62
PresentationFramework.Royale.dll (fc6908a3ee26) - ## / 67
PresentationUI.dll (9955b113fedf) - ## / 70
ReachFramework.dll (d1c822c923cf) - ## / 70
System.AppContext.dll (cbd17ecb1f99) - ## / 70
System.Buffers.dll (a82b7afd4d73) - ## / 64
System.CodeDom.dll (31a100114d09) - ## / 70
System.Collections.Concurrent.dll (e6f4a0d32b28) - ## / 70
System.Collections.dll (a56415230ca6) - ## / 70
System.Collections.Immutable.dll (20ea588b072f) - ## / 70
System.Collections.NonGeneric.dll (f32efeec4305) - ## / 69
System.Collections.Specialized.dll (10e5ed73da16) - ## / 70
System.ComponentModel.Annotations.dll (917afbb305d4) - ## / 70
System.ComponentModel.DataAnnotations.dll (473cf6114c71) - ## / 70
System.ComponentModel.dll (5f3ca0b010e1) - ## / 68
System.ComponentModel.EventBasedAsync.dll (dc7fc77b0095) - ## / 68
System.ComponentModel.Primitives.dll (45f9d05cfaa6) - ## / 69
System.ComponentModel.TypeConverter.dll (3de3ba1a7650) - ## / 69
System.Configuration.ConfigurationManager.dll (650c62c06504) - ## / 70
System.Configuration.dll (fd8e31b84266) - ## / 70
System.Console.dll (f2e576535af6) - ## / 70
System.Core.dll (d090990a5372) - ## / 70
System.Data.Common.dll (dffde53117b8) - ## / 69
System.Data.DataSetExtensions.dll (25b7c75f0271) - ## / 68
System.Data.dll (732b85cfbe39) - ## / 70
System.Design.dll (4b7b5a07beb4) - ## / 70
System.Diagnostics.Contracts.dll (7d41e0514c58) - ## / 70
System.Diagnostics.Debug.dll (b01806ddb5f8) - ## / 68
System.Diagnostics.DiagnosticSource.dll (9c295641b532) - ## / 70
System.Diagnostics.EventLog.dll (12e6fa32ce3a) - ## / 70
System.Diagnostics.EventLog.Messages.dll (c0134456a596) - ## / 70
System.Diagnostics.FileVersionInfo.dll (258f1f675a3d) - ## / 70
System.Diagnostics.PerformanceCounter.dll (fddb89e08ff0) - ## / 70
System.Diagnostics.Process.dll (6804176d2b24) - ## / 70
System.Diagnostics.StackTrace.dll (1d6807b7a3b2) - ## / 67
System.Diagnostics.TextWriterTraceListener.dll (226fc1261acb) - ## / 70
System.Diagnostics.Tools.dll (79f0cb0ebd9e) - ## / 69
System.Diagnostics.TraceSource.dll (6b305e36d61a) - ## / 70
System.Diagnostics.Tracing.dll (162a9d6e9050) - ## / 70
System.DirectoryServices.dll (71a7e0dd08b0) - ## / 65
System.dll (3de34df58307) - ## / 70
System.Drawing.Common.dll (1d2f3fd3b2d7) - ## / 70
System.Drawing.Design.dll (b3ef22cbef5b) - ## / 70
System.Drawing.dll (41ab3dbf63ff) - ## / 70
System.Drawing.Primitives.dll (16c37318764d) - ## / 54
System.Dynamic.Runtime.dll (bf85fa615566) - ## / 69
System.Formats.Asn1.dll (d0a0fd273381) - ## / 70
System.Formats.Tar.dll (8a75f63b16c3) - ## / 70
System.Globalization.Calendars.dll (18332d336067) - ## / 69
System.Globalization.dll (094ab702467f) - ## / 70
System.Globalization.Extensions.dll (5c094fd0a879) - ## / 70
System.IO.Compression.Brotli.dll (ee1061476333) - ## / 70
System.IO.Compression.dll (7cf7d320e2a4) - ## / 69
System.IO.Compression.FileSystem.dll (9430dc346f03) - ## / 67
System.IO.Compression.Native.dll (abe82363f0c0) - ## / 69
System.IO.Compression.ZipFile.dll (e5bdc36e92fe) - ## / 64
System.IO.dll (98c25ec84f2f) - ## / 70
System.IO.FileSystem.AccessControl.dll (9d348fb73566) - ## / 59
System.IO.FileSystem.dll (fa3d6b67832b) - ## / 69
System.IO.FileSystem.DriveInfo.dll (5df66ea6b35b) - ## / 70
System.IO.FileSystem.Primitives.dll (77e85d81e139) - ## / 68
System.IO.FileSystem.Watcher.dll (adf17884526d) - ## / 69
System.IO.IsolatedStorage.dll (74d715ab7300) - ## / 54
System.IO.MemoryMappedFiles.dll (a7994afef68d) - ## / 70
System.IO.Packaging.dll (53d91871b603) - ## / 69
System.IO.Pipes.AccessControl.dll (07aef69dd969) - ## / 67
System.IO.Pipes.dll (35de8e9f6c3d) - ## / 70
System.IO.UnmanagedMemoryStream.dll (c510159cbd39) - ## / 67
System.Linq.dll (f9d471d59747) - ## / 70
System.Linq.Expressions.dll (2b519a634afd) - ## / 70
System.Linq.Parallel.dll (47821ea886ab) - ## / 70
System.Linq.Queryable.dll (fa1d958a3269) - ## / 70
System.Memory.dll (4e523b02bbd8) - ## / 70
System.Net.dll (88d5e0157bc7) - ## / 70
System.Net.Http.dll (ce75a6f4b13a) - ## / 69
System.Net.Http.Json.dll (900c0f80b722) - ## / 70
System.Net.HttpListener.dll (24d9e4743e2d) - ## / 69
System.Net.Mail.dll (a02f511b7b01) - ## / 70
System.Net.NameResolution.dll (3423781d3fd8) - ## / 70
System.Net.NetworkInformation.dll (8ee8584e8869) - ## / 70
System.Net.Ping.dll (cb1f29c13f50) - ## / 70
System.Net.Primitives.dll (7397fbd39eea) - ## / 69
System.Net.Quic.dll (c737d28b4b97) - ## / 69
System.Net.Requests.dll (9f2843edcf66) - ## / 69
System.Net.Security.dll (46758a80a0ef) - ## / 70
System.Net.ServicePoint.dll (aa0a7c554b3d) - ## / 70
System.Net.Sockets.dll (45959250af43) - ## / 60
System.Net.WebClient.dll (1a2b94042d13) - ## / 42
System.Net.WebHeaderCollection.dll (aad60038200f) - ## / 70
System.Net.WebProxy.dll (45a0a265f12d) - ## / 69
System.Net.WebSockets.Client.dll (2a8301b1338b) - ## / 68
System.Net.WebSockets.dll (410c6c54b059) - ## / 67
System.Numerics.dll (725edc92b110) - ## / 70
System.Numerics.Vectors.dll (0208415c88bd) - ## / 60
System.ObjectModel.dll (65a9b2955c0b) - ## / 70
System.Printing.dll (156fe97928d1) - ## / 69
System.Private.CoreLib.dll (55b977339bb3) - ## / 68
System.Private.DataContractSerialization.dll (58c053d50409) - ## / 67
System.Private.Uri.dll (8c5ac6135d01) - ## / 65
System.Private.Xml.dll (f552e8392028) - ## / 69
System.Private.Xml.Linq.dll (dafcdf1749f0) - ## / 70
System.Reflection.DispatchProxy.dll (4fda8647eff7) - ## / 61
System.Reflection.dll (97adb7d51d9e) - ## / 70
System.Reflection.Emit.dll (aa7d8140290c) - ## / 70
System.Reflection.Emit.ILGeneration.dll (0d2a30e0ea4e) - ## / 70
System.Reflection.Emit.Lightweight.dll (96ca0df0bebc) - ## / 55
System.Reflection.Extensions.dll (31d479254355) - ## / 70
System.Reflection.Metadata.dll (a1032258fe8f) - ## / 70
System.Reflection.MetadataLoadContext.dll (5d03e479d634) - ## / 70
System.Reflection.Primitives.dll (4d8e343055ff) - ## / 70
System.Reflection.TypeExtensions.dll (f6122a8b03f4) - ## / 69
System.Resources.Extensions.dll (926ccba2eb9c) - ## / 70
System.Resources.Reader.dll (0a4fbd02d4b0) - ## / 70
System.Resources.ResourceManager.dll (9e21c5fe3b6e) - ## / 70
System.Resources.Writer.dll (d404298b1e2c) - ## / 70
System.Runtime.CompilerServices.Unsafe.dll (4cec79caf9f5) - ## / 70
System.Runtime.CompilerServices.VisualC.dll (40decca29d46) - ## / 70
System.Runtime.dll (f387004c4add) - ## / 70
System.Runtime.Extensions.dll (cf2ed303382c) - ## / 70
System.Runtime.Handles.dll (0f55fd55a561) - ## / 70
System.Runtime.InteropServices.dll (5c439e732317) - ## / 70
System.Runtime.InteropServices.JavaScript.dll (04e03e30904a) - ## / 70
System.Runtime.InteropServices.RuntimeInformation.dll (4e807808a7bd) - ## / 70
System.Runtime.Intrinsics.dll (e4d386e34c60) - ## / 70
System.Runtime.Loader.dll (4ad80480ecfa) - ## / 69
System.Runtime.Numerics.dll (172aae5578e5) - ## / 67
System.Runtime.Serialization.dll (1bd311e27a6e) - ## / 70
System.Runtime.Serialization.Formatters.dll (0c24fe8602f8) - ## / 70
System.Runtime.Serialization.Json.dll (e7262ecd0b7a) - ## / 70
System.Runtime.Serialization.Primitives.dll (1adcfbb9b8af) - ## / 66
System.Runtime.Serialization.Xml.dll (1e2bf23cc4a4) - ## / 67
System.Security.AccessControl.dll (b9207ebf266f) - ## / 70
System.Security.Claims.dll (adbb1268d135) - ## / 69
System.Security.Cryptography.Algorithms.dll (8b23c2b39419) - ## / 70
System.Security.Cryptography.Cng.dll (644904494a8b) - ## / 70
System.Security.Cryptography.Csp.dll (660504537708) - ## / 70
System.Security.Cryptography.dll (d6164589f095) - ## / 70
System.Security.Cryptography.Encoding.dll (713dab1c9bc4) - ## / 70
System.Security.Cryptography.OpenSsl.dll (f1f67091e09f) - ## / 70
System.Security.Cryptography.Pkcs.dll (e2c1d9c46c8b) - ## / 70
System.Security.Cryptography.Primitives.dll (2671b635c677) - ## / 70
System.Security.Cryptography.ProtectedData.dll (f937862afb54) - ## / 70
System.Security.Cryptography.X509Certificates.dll (8250b7427d3d) - ## / 70
System.Security.Cryptography.Xml.dll (7cd4fc77cbc3) - ## / 65
System.Security.dll (d94c5f46e77d) - ## / 70
System.Security.Permissions.dll (d9ac556034cc) - ## / 69
System.Security.Principal.dll (e776230ed731) - ## / 65
System.Security.Principal.Windows.dll (97e425355472) - ## / 70
System.Security.SecureString.dll (0fc4de21b12e) - ## / 70
System.ServiceModel.Web.dll (cbf447dacb08) - ## / 55
System.ServiceProcess.dll (baeb383b33a3) - ## / 70
System.Text.Encoding.CodePages.dll (3f932e884b37) - ## / 70
System.Text.Encoding.dll (cf1fa293e670) - ## / 70
System.Text.Encoding.Extensions.dll (0cd1a36a0134) - ## / 69
System.Text.Encodings.Web.dll (d856a82f7bd2) - ## / 62
System.Text.Json.dll (29553d5daa3e) - ## / 70
System.Text.RegularExpressions.dll (c6fd755d07ef) - ## / 67
System.Threading.AccessControl.dll (3fa11616ba26) - ## / 70
System.Threading.Channels.dll (9f8603bee6d4) - ## / 70
System.Threading.dll (b8daa1835ff5) - ## / 70
System.Threading.Overlapped.dll (c302f0310e4d) - ## / 70
System.Threading.Tasks.Dataflow.dll (f742a9f89568) - ## / 70
System.Threading.Tasks.dll (0af66e4b27be) - ## / 70
System.Threading.Tasks.Extensions.dll (c5125eec94af) - ## / 70
System.Threading.Tasks.Parallel.dll (f557ea9f0350) - ## / 70
System.Threading.Thread.dll (4de98290bacd) - ## / 70
System.Threading.ThreadPool.dll (57e8404b7be6) - ## / 70
System.Threading.Timer.dll (ab8ad76998df) - ## / 67
System.Transactions.dll (c6ed9119228d) - ## / 70
System.Transactions.Local.dll (acb1c194092b) - ## / 68
System.ValueTuple.dll (7ea9b83d52ca) - ## / 69
System.Web.dll (ec862f762731) - ## / 70
System.Web.HttpUtility.dll (65010292aace) - ## / 70
System.Windows.Controls.Ribbon.dll (1fcba609932a) - ## / 69
System.Windows.dll (2b4bc5064952) - ## / 70
System.Windows.Extensions.dll (8d2735c5c965) - ## / 70
System.Windows.Forms.Design.dll (c39c2d92982d) - ## / 69
System.Windows.Forms.Design.Editors.dll (641cef4014ff) - ## / 70
System.Windows.Forms.dll (13059f0fc388) - ## / 69
System.Windows.Forms.Legacy.dll (3958a35e5134) - ## / 70
System.Windows.Forms.Primitives.dll (0aae3218b7bd) - ## / 70
System.Windows.Input.Manipulations.dll (9ad6fbc2fc9e) - ## / 70
System.Windows.Presentation.dll (6cc3bad7068e) - ## / 69
System.Xaml.dll (3352d2fd11bb) - ## / 69
System.Xml.dll (fe86156350e4) - ## / 70
System.Xml.Linq.dll (8c5c721add7b) - ## / 70
System.Xml.ReaderWriter.dll (837291f4c4a0) - ## / 70
System.Xml.Serialization.dll (342fc561b1eb) - ## / 70
System.Xml.XDocument.dll (6d86bff5a58b) - ## / 70
System.Xml.XmlDocument.dll (05e8355f8dc0) - ## / 62
System.Xml.XmlSerializer.dll (aad3d0e6244e) - ## / 70
System.Xml.XPath.dll (6bbd476385d1) - ## / 65
System.Xml.XPath.XDocument.dll (8191d1559fad) - ## / 54
TerraFX.Interop.Windows.dll (52e696ed985a) - ## / 70
UIAutomationClient.dll (47f7a295af21) - ## / 70
UIAutomationClientSideProviders.dll (77b2d01a64dc) - ## / 70
UIAutomationProvider.dll (a89cae6aa9f9) - ## / 70
UIAutomationTypes.dll (7a88f937fb71) - ## / 66
WindowsBase.dll (3b3ae5fc58f7) - ## / 67
WindowsFormsIntegration.dll (110b575934ca) - ## / 70
wpfgfx_cor3.dll (4fdb1ec018a7) - ## / 69
AvifFileType.dll (25141ec42689) - ## / 69
AvifNative_x64.dll (914137c4eb60) - ## / 68
DdsFileTypePlus.dll (5aece4c64d77) - ## / 69
DdsFileTypePlusIO_x64.dll (7a8ca7c30c26) - ## / 69
WebPFileType.dll (625d992db1bc) - ## / 69
WebP_x64.dll (ae57af22e2bf) - ## / 69

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
Paint.NET (Portable) 5.0.13	310	Wednesday, March 6, 2024	Approved
Paint.NET (Portable) 5.0.12	364	Saturday, December 2, 2023	Approved
Paint.NET (Portable) 5.0.11	825	Thursday, October 12, 2023	Approved
Paint.NET (Portable) 5.0.10	232	Monday, October 2, 2023	Approved
Paint.NET (Portable) 5.0.9	298	Wednesday, August 9, 2023	Approved
Paint.NET (Portable) 5.0.8	225	Tuesday, August 1, 2023	Approved
Paint.NET (Portable) 5.0.7	289	Sunday, June 25, 2023	Approved
Paint.NET (Portable) 5.0.6	291	Thursday, May 25, 2023	Approved
Paint.NET (Portable) 5.0.5	184	Saturday, May 20, 2023	Approved
Paint.NET (Portable) 5.0.4	33	Saturday, May 20, 2023	Approved
Paint.NET (Portable) 5.0.3	250	Friday, March 31, 2023	Approved
Paint.NET (Portable) 5.0.2	74	Wednesday, February 22, 2023	Approved
Paint.NET (Portable) 5.0.1.20230219	57	Sunday, February 19, 2023	Approved

Release Notes

https://www.getpaint.net/roadmap.html

Dependencies

- chocolatey-core.extension (≥ 1.3.3)

Discussion for the Paint.NET (Portable) Package

Ground Rules:

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

Resources

Events

Courses

3,501

30

18 Feb 2023

Paint.NET (Portable)

Paint.NET (Portable)

Some Checks Have Failed or Are Not Yet Complete

SebastianK (maintainer) on 12 Jan 2023 22:30:47 +00:00:

SebastianK (maintainer) on 12 Jan 2023 22:35:27 +00:00:

SebastianK (maintainer) on 12 Jan 2023 22:37:23 +00:00:

chocolatey-ops (reviewer) on 12 Jan 2023 23:12:26 +00:00:

Notes

chocolatey-ops (reviewer) on 12 Jan 2023 23:32:28 +00:00:

chocolatey-ops (reviewer) on 13 Jan 2023 00:16:18 +00:00:

Pauby (reviewer) on 16 Feb 2023 18:56:16 +00:00:

SebastianK (maintainer) on 17 Feb 2023 23:52:10 +00:00:

SebastianK (maintainer) on 17 Feb 2023 23:55:58 +00:00:

SebastianK (maintainer) on 17 Feb 2023 23:57:26 +00:00:

SebastianK (maintainer) on 18 Feb 2023 00:00:28 +00:00:

chocolatey-ops (reviewer) on 18 Feb 2023 00:36:13 +00:00:

Notes

chocolatey-ops (reviewer) on 18 Feb 2023 00:48:34 +00:00:

chocolatey-ops (reviewer) on 18 Feb 2023 01:02:23 +00:00:

Pauby (reviewer) on 18 Feb 2023 13:36:27 +00:00:

SebastianK (maintainer) on 18 Feb 2023 22:15:51 +00:00:

Pauby (reviewer) on 18 Feb 2023 23:58:16 +00:00:

Features

Ground Rules: