Step 1: Review Your Packages

Step 2: Choose Your Integration Method

Step 3: Copy Your Script or Download Config

Option 1: Copy Script

Option 2: Download Config

Step 4: Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

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

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

Option 2: Internalized Package (Reliable, Scalable)

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

Step 5: Copy Your Script

See options you can pass to upgrade.

See best practices for scripting.

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

### c. Other Requirements ###

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

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

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

## 2. TOP LEVEL VARIABLES ##

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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

- name: Install and Configure Chocolatey
  hosts: all

## 2. TOP LEVEL VARIABLES ##
  vars:

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

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

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

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

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

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

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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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

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

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

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

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

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

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

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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

chocolatey_feature 'useBackgroundService' do
  action :enable
end

chocolatey_feature 'useBackgroundServiceWithNonAdministratorsOnly' do
  action :enable
end

chocolatey_feature 'allowBackgroundServiceUninstallsFromUserInstallsOnly' do
  action :enable
end

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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


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

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

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

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

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


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


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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Need Help? View our docs or file an issue.

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

Current Version	New Version

Downloads:

98,521

Downloads of v 3.0.1.374-phantom:

205

Last Update:

21 Feb 2019

Package Maintainer(s):

mkevenaar

Software Author(s):

Mark McDowall
Keivan Beigi

Tags:

pvr p2p filesharing torrent nntp admin

Sonarr

This is a prerelease version of Sonarr.

3.0.1.374-phantom | Updated: 21 Feb 2019

Downloads:

98,521

Downloads of v 3.0.1.374-phantom:

205

Maintainer(s):

mkevenaar

Software Author(s):

Mark McDowall
Keivan Beigi

Tags:

pvr p2p filesharing torrent nntp admin

Sonarr 3.0.1.374-phantom

This is a prerelease version of Sonarr.

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

Some Checks Are Exempted or Have Failed

Not All Tests Have Passed

Hide Checks

Validation Testing Passed

Verification Testing Exemption:

Failing due to the fact that V3 requires .net 4.6.1 now.

Details

Scan Testing Resulted in Flagged:

This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.

We recommend clicking the "Details" link to make your own decision on installing this package.

Details

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

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

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

To uninstall Sonarr, 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 sonarr --internalize --version=3.0.1.374-phantom --pre --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 sonarr -y --source="'INTERNAL REPO URL'" --version="'3.0.1.374-phantom'" --prerelease [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 sonarr -y --source="'INTERNAL REPO URL'" --version="'3.0.1.374-phantom'" --prerelease
$exitCode = $LASTEXITCODE

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

Exit $exitCode


- name: Install sonarr
  win_chocolatey:
    name: sonarr
    version: '3.0.1.374-phantom'
    source: INTERNAL REPO URL
    state: present
    allow_prerelease: yes

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


chocolatey_package 'sonarr' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '3.0.1.374-phantom'
  options  '--prerelease'
end

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


cChocoPackageInstaller sonarr
{
    Name        = "sonarr"
    Version     = "3.0.1.374-phantom"
    Source      = "INTERNAL REPO URL"
    chocoParams = "--prerelease"
}

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


package { 'sonarr':
  ensure          => '3.0.1.374-phantom',
  install_options => ['--prerelease'],
  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.

Package Approved

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

Description

Sonarr (formerly NzbDrone) is a PVR for Usenet and BitTorrent users. It can monitor multiple RSS feeds for new episodes of your favorite shows and will grab, sorts and renames them. It can also be configured to automatically upgrade the quality of files already downloaded when a better quality format becomes available.

Features

Support for major platforms: Windows, Linux, macOS, Raspberry Pi, etc.
Automatically detects new episodes
Can scan your existing library and download any missing episodes
Can watch for better quality of the episodes you already have and do an automatic upgrade. eg. from DVD to Blu-Ray
Automatic failed download handling will try another release if one fails
Manual search so you can pick any release or to see why a release was not downloaded automatically
Fully configurable episode renaming
Full integration with SABnzbd and NZBGet
Full integration with Kodi, Plex (notification, library update, metadata)
Full support for specials and multi-episode releases
And a beautiful UI

Community

Notes

This is the pre-release versions of Sonarr V3 otherwise known as Phantom.

Sonarr v2 migration
- Sonarr v3 will automatically convert the existing Sonarr v2 installation. Sonarr v2 stored it's database in C:\ProgramData\NzbDrone, which will be automatically converted to C:\ProgramData\Sonarr. It's advisable to make a backup of the v2 data first.

Installs as a service, to get to Sonarr open browser and go here or go to http://<your-ip>:8989/

Files

legal\LICENSE.txt

### GNU GENERAL PUBLIC LICENSE

Version 3, 29 June 2007

Copyright (C) 2007 Free Software Foundation, Inc.
<http://fsf.org/>

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

### Preamble

The GNU General Public License is a free, copyleft license for
software and other kinds of works.

The licenses for most software and other practical works are designed
to take away your freedom to share and change the works. By contrast,
the GNU General Public License is intended to guarantee your freedom
to share and change all versions of a program--to make sure it remains
free software for all its users. We, the Free Software Foundation, use
the GNU General Public License for most of our software; it applies
also to any other work released this way by its authors. You can apply
it to your programs, too.

When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
them if you wish), that you receive source code or can get it if you
want it, that you can change the software or use pieces of it in new
free programs, and that you know you can do these things.

To protect your rights, we need to prevent others from denying you
these rights or asking you to surrender the rights. Therefore, you
have certain responsibilities if you distribute copies of the
software, or if you modify it: responsibilities to respect the freedom
of others.

For example, if you distribute copies of such a program, whether
gratis or for a fee, you must pass on to the recipients the same
freedoms that you received. You must make sure that they, too, receive
or can get the source code. And you must show them these terms so they
know their rights.

Developers that use the GNU GPL protect your rights with two steps:
(1) assert copyright on the software, and (2) offer you this License
giving you legal permission to copy, distribute and/or modify it.

For the developers' and authors' protection, the GPL clearly explains
that there is no warranty for this free software. For both users' and
authors' sake, the GPL requires that modified versions be marked as
changed, so that their problems will not be attributed erroneously to
authors of previous versions.

Some devices are designed to deny users access to install or run
modified versions of the software inside them, although the
manufacturer can do so. This is fundamentally incompatible with the
aim of protecting users' freedom to change the software. The
systematic pattern of such abuse occurs in the area of products for
individuals to use, which is precisely where it is most unacceptable.
Therefore, we have designed this version of the GPL to prohibit the
practice for those products. If such problems arise substantially in
other domains, we stand ready to extend this provision to those
domains in future versions of the GPL, as needed to protect the
freedom of users.

Finally, every program is threatened constantly by software patents.
States should not allow patents to restrict development and use of
software on general-purpose computers, but in those that do, we wish
to avoid the special danger that patents applied to a free program
could make it effectively proprietary. To prevent this, the GPL
assures that patents cannot be used to render the program non-free.

The precise terms and conditions for copying, distribution and
modification follow.

### TERMS AND CONDITIONS

#### 0. Definitions.

"This License" refers to version 3 of the GNU General Public License.

"Copyright" also means copyright-like laws that apply to other kinds
of works, such as semiconductor masks.

"The Program" refers to any copyrightable work licensed under this
License. Each licensee is addressed as "you". "Licensees" and
"recipients" may be individuals or organizations.

To "modify" a work means to copy from or adapt all or part of the work
in a fashion requiring copyright permission, other than the making of
an exact copy. The resulting work is called a "modified version" of
the earlier work or a work "based on" the earlier work.

A "covered work" means either the unmodified Program or a work based
on the Program.

To "propagate" a work means to do anything with it that, without
permission, would make you directly or secondarily liable for
infringement under applicable copyright law, except executing it on a
computer or modifying a private copy. Propagation includes copying,
distribution (with or without modification), making available to the
public, and in some countries other activities as well.

To "convey" a work means any kind of propagation that enables other
parties to make or receive copies. Mere interaction with a user
through a computer network, with no transfer of a copy, is not
conveying.

An interactive user interface displays "Appropriate Legal Notices" to
the extent that it includes a convenient and prominently visible
feature that (1) displays an appropriate copyright notice, and (2)
tells the user that there is no warranty for the work (except to the
extent that warranties are provided), that licensees may convey the
work under this License, and how to view a copy of this License. If
the interface presents a list of user commands or options, such as a
menu, a prominent item in the list meets this criterion.

#### 1. Source Code.

The "source code" for a work means the preferred form of the work for
making modifications to it. "Object code" means any non-source form of
a work.

A "Standard Interface" means an interface that either is an official
standard defined by a recognized standards body, or, in the case of
interfaces specified for a particular programming language, one that
is widely used among developers working in that language.

The "System Libraries" of an executable work include anything, other
than the work as a whole, that (a) is included in the normal form of
packaging a Major Component, but which is not part of that Major
Component, and (b) serves only to enable use of the work with that
Major Component, or to implement a Standard Interface for which an
implementation is available to the public in source code form. A
"Major Component", in this context, means a major essential component
(kernel, window system, and so on) of the specific operating system
(if any) on which the executable work runs, or a compiler used to
produce the work, or an object code interpreter used to run it.

The "Corresponding Source" for a work in object code form means all
the source code needed to generate, install, and (for an executable
work) run the object code and to modify the work, including scripts to
control those activities. However, it does not include the work's
System Libraries, or general-purpose tools or generally available free
programs which are used unmodified in performing those activities but
which are not part of the work. For example, Corresponding Source
includes interface definition files associated with source files for
the work, and the source code for shared libraries and dynamically
linked subprograms that the work is specifically designed to require,
such as by intimate data communication or control flow between those
subprograms and other parts of the work.

The Corresponding Source need not include anything that users can
regenerate automatically from other parts of the Corresponding Source.

The Corresponding Source for a work in source code form is that same
work.

#### 2. Basic Permissions.

All rights granted under this License are granted for the term of
copyright on the Program, and are irrevocable provided the stated
conditions are met. This License explicitly affirms your unlimited
permission to run the unmodified Program. The output from running a
covered work is covered by this License only if the output, given its
content, constitutes a covered work. This License acknowledges your
rights of fair use or other equivalent, as provided by copyright law.

You may make, run and propagate covered works that you do not convey,
without conditions so long as your license otherwise remains in force.
You may convey covered works to others for the sole purpose of having
them make modifications exclusively for you, or provide you with
facilities for running those works, provided that you comply with the
terms of this License in conveying all material for which you do not
control copyright. Those thus making or running the covered works for
you must do so exclusively on your behalf, under your direction and
control, on terms that prohibit them from making any copies of your
copyrighted material outside their relationship with you.

Conveying under any other circumstances is permitted solely under the
conditions stated below. Sublicensing is not allowed; section 10 makes
it unnecessary.

#### 3. Protecting Users' Legal Rights From Anti-Circumvention Law.

No covered work shall be deemed part of an effective technological
measure under any applicable law fulfilling obligations under article
11 of the WIPO copyright treaty adopted on 20 December 1996, or
similar laws prohibiting or restricting circumvention of such
measures.

When you convey a covered work, you waive any legal power to forbid
circumvention of technological measures to the extent such
circumvention is effected by exercising rights under this License with
respect to the covered work, and you disclaim any intention to limit
operation or modification of the work as a means of enforcing, against
the work's users, your or third parties' legal rights to forbid
circumvention of technological measures.

#### 4. Conveying Verbatim Copies.

You may convey verbatim copies of the Program's source code as you
receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice;
keep intact all notices stating that this License and any
non-permissive terms added in accord with section 7 apply to the code;
keep intact all notices of the absence of any warranty; and give all
recipients a copy of this License along with the Program.

You may charge any price or no price for each copy that you convey,
and you may offer support or warranty protection for a fee.

#### 5. Conveying Modified Source Versions.

You may convey a work based on the Program, or the modifications to
produce it from the Program, in the form of source code under the
terms of section 4, provided that you also meet all of these
conditions:

-   a) The work must carry prominent notices stating that you modified
    it, and giving a relevant date.
-   b) The work must carry prominent notices stating that it is
    released under this License and any conditions added under
    section 7. This requirement modifies the requirement in section 4
    to "keep intact all notices".
-   c) You must license the entire work, as a whole, under this
    License to anyone who comes into possession of a copy. This
    License will therefore apply, along with any applicable section 7
    additional terms, to the whole of the work, and all its parts,
    regardless of how they are packaged. This License gives no
    permission to license the work in any other way, but it does not
    invalidate such permission if you have separately received it.
-   d) If the work has interactive user interfaces, each must display
    Appropriate Legal Notices; however, if the Program has interactive
    interfaces that do not display Appropriate Legal Notices, your
    work need not make them do so.

A compilation of a covered work with other separate and independent
works, which are not by their nature extensions of the covered work,
and which are not combined with it such as to form a larger program,
in or on a volume of a storage or distribution medium, is called an
"aggregate" if the compilation and its resulting copyright are not
used to limit the access or legal rights of the compilation's users
beyond what the individual works permit. Inclusion of a covered work
in an aggregate does not cause this License to apply to the other
parts of the aggregate.

#### 6. Conveying Non-Source Forms.

You may convey a covered work in object code form under the terms of
sections 4 and 5, provided that you also convey the machine-readable
Corresponding Source under the terms of this License, in one of these
ways:

-   a) Convey the object code in, or embodied in, a physical product
    (including a physical distribution medium), accompanied by the
    Corresponding Source fixed on a durable physical medium
    customarily used for software interchange.
-   b) Convey the object code in, or embodied in, a physical product
    (including a physical distribution medium), accompanied by a
    written offer, valid for at least three years and valid for as
    long as you offer spare parts or customer support for that product
    model, to give anyone who possesses the object code either (1) a
    copy of the Corresponding Source for all the software in the
    product that is covered by this License, on a durable physical
    medium customarily used for software interchange, for a price no
    more than your reasonable cost of physically performing this
    conveying of source, or (2) access to copy the Corresponding
    Source from a network server at no charge.
-   c) Convey individual copies of the object code with a copy of the
    written offer to provide the Corresponding Source. This
    alternative is allowed only occasionally and noncommercially, and
    only if you received the object code with such an offer, in accord
    with subsection 6b.
-   d) Convey the object code by offering access from a designated
    place (gratis or for a charge), and offer equivalent access to the
    Corresponding Source in the same way through the same place at no
    further charge. You need not require recipients to copy the
    Corresponding Source along with the object code. If the place to
    copy the object code is a network server, the Corresponding Source
    may be on a different server (operated by you or a third party)
    that supports equivalent copying facilities, provided you maintain
    clear directions next to the object code saying where to find the
    Corresponding Source. Regardless of what server hosts the
    Corresponding Source, you remain obligated to ensure that it is
    available for as long as needed to satisfy these requirements.
-   e) Convey the object code using peer-to-peer transmission,
    provided you inform other peers where the object code and
    Corresponding Source of the work are being offered to the general
    public at no charge under subsection 6d.

A separable portion of the object code, whose source code is excluded
from the Corresponding Source as a System Library, need not be
included in conveying the object code work.

A "User Product" is either (1) a "consumer product", which means any
tangible personal property which is normally used for personal,
family, or household purposes, or (2) anything designed or sold for
incorporation into a dwelling. In determining whether a product is a
consumer product, doubtful cases shall be resolved in favor of
coverage. For a particular product received by a particular user,
"normally used" refers to a typical or common use of that class of
product, regardless of the status of the particular user or of the way
in which the particular user actually uses, or expects or is expected
to use, the product. A product is a consumer product regardless of
whether the product has substantial commercial, industrial or
non-consumer uses, unless such uses represent the only significant
mode of use of the product.

"Installation Information" for a User Product means any methods,
procedures, authorization keys, or other information required to
install and execute modified versions of a covered work in that User
Product from a modified version of its Corresponding Source. The
information must suffice to ensure that the continued functioning of
the modified object code is in no case prevented or interfered with
solely because modification has been made.

If you convey an object code work under this section in, or with, or
specifically for use in, a User Product, and the conveying occurs as
part of a transaction in which the right of possession and use of the
User Product is transferred to the recipient in perpetuity or for a
fixed term (regardless of how the transaction is characterized), the
Corresponding Source conveyed under this section must be accompanied
by the Installation Information. But this requirement does not apply
if neither you nor any third party retains the ability to install
modified object code on the User Product (for example, the work has
been installed in ROM).

The requirement to provide Installation Information does not include a
requirement to continue to provide support service, warranty, or
updates for a work that has been modified or installed by the
recipient, or for the User Product in which it has been modified or
installed. Access to a network may be denied when the modification
itself materially and adversely affects the operation of the network
or violates the rules and protocols for communication across the
network.

Corresponding Source conveyed, and Installation Information provided,
in accord with this section must be in a format that is publicly
documented (and with an implementation available to the public in
source code form), and must require no special password or key for
unpacking, reading or copying.

#### 7. Additional Terms.

"Additional permissions" are terms that supplement the terms of this
License by making exceptions from one or more of its conditions.
Additional permissions that are applicable to the entire Program shall
be treated as though they were included in this License, to the extent
that they are valid under applicable law. If additional permissions
apply only to part of the Program, that part may be used separately
under those permissions, but the entire Program remains governed by
this License without regard to the additional permissions.

When you convey a copy of a covered work, you may at your option
remove any additional permissions from that copy, or from any part of
it. (Additional permissions may be written to require their own
removal in certain cases when you modify the work.) You may place
additional permissions on material, added by you to a covered work,
for which you have or can give appropriate copyright permission.

Notwithstanding any other provision of this License, for material you
add to a covered work, you may (if authorized by the copyright holders
of that material) supplement the terms of this License with terms:

-   a) Disclaiming warranty or limiting liability differently from the
    terms of sections 15 and 16 of this License; or
-   b) Requiring preservation of specified reasonable legal notices or
    author attributions in that material or in the Appropriate Legal
    Notices displayed by works containing it; or
-   c) Prohibiting misrepresentation of the origin of that material,
    or requiring that modified versions of such material be marked in
    reasonable ways as different from the original version; or
-   d) Limiting the use for publicity purposes of names of licensors
    or authors of the material; or
-   e) Declining to grant rights under trademark law for use of some
    trade names, trademarks, or service marks; or
-   f) Requiring indemnification of licensors and authors of that
    material by anyone who conveys the material (or modified versions
    of it) with contractual assumptions of liability to the recipient,
    for any liability that these contractual assumptions directly
    impose on those licensors and authors.

All other non-permissive additional terms are considered "further
restrictions" within the meaning of section 10. If the Program as you
received it, or any part of it, contains a notice stating that it is
governed by this License along with a term that is a further
restriction, you may remove that term. If a license document contains
a further restriction but permits relicensing or conveying under this
License, you may add to a covered work material governed by the terms
of that license document, provided that the further restriction does
not survive such relicensing or conveying.

If you add terms to a covered work in accord with this section, you
must place, in the relevant source files, a statement of the
additional terms that apply to those files, or a notice indicating
where to find the applicable terms.

Additional terms, permissive or non-permissive, may be stated in the
form of a separately written license, or stated as exceptions; the
above requirements apply either way.

#### 8. Termination.

You may not propagate or modify a covered work except as expressly
provided under this License. Any attempt otherwise to propagate or
modify it is void, and will automatically terminate your rights under
this License (including any patent licenses granted under the third
paragraph of section 11).

However, if you cease all violation of this License, then your license
from a particular copyright holder is reinstated (a) provisionally,
unless and until the copyright holder explicitly and finally
terminates your license, and (b) permanently, if the copyright holder
fails to notify you of the violation by some reasonable means prior to
60 days after the cessation.

Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.

Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License. If your rights have been terminated and not permanently
reinstated, you do not qualify to receive new licenses for the same
material under section 10.

#### 9. Acceptance Not Required for Having Copies.

You are not required to accept this License in order to receive or run
a copy of the Program. Ancillary propagation of a covered work
occurring solely as a consequence of using peer-to-peer transmission
to receive a copy likewise does not require acceptance. However,
nothing other than this License grants you permission to propagate or
modify any covered work. These actions infringe copyright if you do
not accept this License. Therefore, by modifying or propagating a
covered work, you indicate your acceptance of this License to do so.

#### 10. Automatic Licensing of Downstream Recipients.

Each time you convey a covered work, the recipient automatically
receives a license from the original licensors, to run, modify and
propagate that work, subject to this License. You are not responsible
for enforcing compliance by third parties with this License.

An "entity transaction" is a transaction transferring control of an
organization, or substantially all assets of one, or subdividing an
organization, or merging organizations. If propagation of a covered
work results from an entity transaction, each party to that
transaction who receives a copy of the work also receives whatever
licenses to the work the party's predecessor in interest had or could
give under the previous paragraph, plus a right to possession of the
Corresponding Source of the work from the predecessor in interest, if
the predecessor has it or can get it with reasonable efforts.

You may not impose any further restrictions on the exercise of the
rights granted or affirmed under this License. For example, you may
not impose a license fee, royalty, or other charge for exercise of
rights granted under this License, and you may not initiate litigation
(including a cross-claim or counterclaim in a lawsuit) alleging that
any patent claim is infringed by making, using, selling, offering for
sale, or importing the Program or any portion of it.

#### 11. Patents.

A "contributor" is a copyright holder who authorizes use under this
License of the Program or a work on which the Program is based. The
work thus licensed is called the contributor's "contributor version".

A contributor's "essential patent claims" are all patent claims owned
or controlled by the contributor, whether already acquired or
hereafter acquired, that would be infringed by some manner, permitted
by this License, of making, using, or selling its contributor version,
but do not include claims that would be infringed only as a
consequence of further modification of the contributor version. For
purposes of this definition, "control" includes the right to grant
patent sublicenses in a manner consistent with the requirements of
this License.

Each contributor grants you a non-exclusive, worldwide, royalty-free
patent license under the contributor's essential patent claims, to
make, use, sell, offer for sale, import and otherwise run, modify and
propagate the contents of its contributor version.

In the following three paragraphs, a "patent license" is any express
agreement or commitment, however denominated, not to enforce a patent
(such as an express permission to practice a patent or covenant not to
sue for patent infringement). To "grant" such a patent license to a
party means to make such an agreement or commitment not to enforce a
patent against the party.

If you convey a covered work, knowingly relying on a patent license,
and the Corresponding Source of the work is not available for anyone
to copy, free of charge and under the terms of this License, through a
publicly available network server or other readily accessible means,
then you must either (1) cause the Corresponding Source to be so
available, or (2) arrange to deprive yourself of the benefit of the
patent license for this particular work, or (3) arrange, in a manner
consistent with the requirements of this License, to extend the patent
license to downstream recipients. "Knowingly relying" means you have
actual knowledge that, but for the patent license, your conveying the
covered work in a country, or your recipient's use of the covered work
in a country, would infringe one or more identifiable patents in that
country that you have reason to believe are valid.

If, pursuant to or in connection with a single transaction or
arrangement, you convey, or propagate by procuring conveyance of, a
covered work, and grant a patent license to some of the parties
receiving the covered work authorizing them to use, propagate, modify
or convey a specific copy of the covered work, then the patent license
you grant is automatically extended to all recipients of the covered
work and works based on it.

A patent license is "discriminatory" if it does not include within the
scope of its coverage, prohibits the exercise of, or is conditioned on
the non-exercise of one or more of the rights that are specifically
granted under this License. You may not convey a covered work if you
are a party to an arrangement with a third party that is in the
business of distributing software, under which you make payment to the
third party based on the extent of your activity of conveying the
work, and under which the third party grants, to any of the parties
who would receive the covered work from you, a discriminatory patent
license (a) in connection with copies of the covered work conveyed by
you (or copies made from those copies), or (b) primarily for and in
connection with specific products or compilations that contain the
covered work, unless you entered into that arrangement, or that patent
license was granted, prior to 28 March 2007.

Nothing in this License shall be construed as excluding or limiting
any implied license or other defenses to infringement that may
otherwise be available to you under applicable patent law.

#### 12. No Surrender of Others' Freedom.

If conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot convey a
covered work so as to satisfy simultaneously your obligations under
this License and any other pertinent obligations, then as a
consequence you may not convey it at all. For example, if you agree to
terms that obligate you to collect a royalty for further conveying
from those to whom you convey the Program, the only way you could
satisfy both those terms and this License would be to refrain entirely
from conveying the Program.

#### 13. Use with the GNU Affero General Public License.

Notwithstanding any other provision of this License, you have
permission to link or combine any covered work with a work licensed
under version 3 of the GNU Affero General Public License into a single
combined work, and to convey the resulting work. The terms of this
License will continue to apply to the part which is the covered work,
but the special requirements of the GNU Affero General Public License,
section 13, concerning interaction through a network will apply to the
combination as such.

#### 14. Revised Versions of this License.

The Free Software Foundation may publish revised and/or new versions
of the GNU General Public License from time to time. Such new versions
will be similar in spirit to the present version, but may differ in
detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Program
specifies that a certain numbered version of the GNU General Public
License "or any later version" applies to it, you have the option of
following the terms and conditions either of that numbered version or
of any later version published by the Free Software Foundation. If the
Program does not specify a version number of the GNU General Public
License, you may choose any version ever published by the Free
Software Foundation.

If the Program specifies that a proxy can decide which future versions
of the GNU General Public License can be used, that proxy's public
statement of acceptance of a version permanently authorizes you to
choose that version for the Program.

Later license versions may give you additional or different
permissions. However, no additional obligations are imposed on any
author or copyright holder as a result of your choosing to follow a
later version.

#### 15. Disclaimer of Warranty.

THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT
WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND
PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE
DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR
CORRECTION.

#### 16. Limitation of Liability.

IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR
CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES
ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT
NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR
LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM
TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER
PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

#### 17. Interpretation of Sections 15 and 16.

If the disclaimer of warranty and limitation of liability provided
above cannot be given local legal effect according to their terms,
reviewing courts shall apply local law that most closely approximates
an absolute waiver of all civil liability in connection with the
Program, unless a warranty or assumption of liability accompanies a
copy of the Program in return for a fee.

END OF TERMS AND CONDITIONS

### How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.

To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively state
the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.

        <one line to give the program's name and a brief idea of what it does.>
        Copyright (C) <year>  <name of author>

        This program is free software: you can redistribute it and/or modify
        it under the terms of the GNU General Public License as published by
        the Free Software Foundation, either version 3 of the License, or
        (at your option) any later version.

        This program is distributed in the hope that it will be useful,
        but WITHOUT ANY WARRANTY; without even the implied warranty of
        MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
        GNU General Public License for more details.

        You should have received a copy of the GNU General Public License
        along with this program.  If not, see <http://www.gnu.org/licenses/>.

Also add information on how to contact you by electronic and paper
mail.

If the program does terminal interaction, make it output a short
notice like this when it starts in an interactive mode:

        <program>  Copyright (C) <year>  <name of author>
        This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
        This is free software, and you are welcome to redistribute it
        under certain conditions; type `show c' for details.

The hypothetical commands \`show w' and \`show c' should show the
appropriate parts of the General Public License. Of course, your
program's commands might be different; for a GUI interface, you would
use an "about box".

You should also get your employer (if you work as a programmer) or
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. For more information on this, and how to apply and follow
the GNU GPL, see <http://www.gnu.org/licenses/>.

The GNU General Public License does not permit incorporating your
program into proprietary programs. If your program is a subroutine
library, you may consider it more useful to permit linking proprietary
applications with the library. If this is what you want to do, use the
GNU Lesser General Public License instead of this License. But first,
please read <http://www.gnu.org/philosophy/why-not-lgpl.html>.

legal\VERIFICATION.txt

VERIFICATION

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

The embedded software has been downloaded from the listed download
location on <https://sonarr.tv/>
and can be verified by doing the following:

1. Download the following:

  url: <http://download.sonarr.tv/v3/phantom-develop/3.0.1.374/Sonarr.phantom-develop.3.0.1.374.windows.exe>

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

  checksum type: sha256
  checksum: 838454C60528DBBA633D0682356C002D2ADC6BA863ED8D65A4BB36A07AE6BCDE

Using AU:

  Get-RemoteChecksum

The file 'license.txt' is obtained from:
  <https://github.com/Sonarr/Sonarr/blob/develop/LICENSE.md>

tools\chocolateyBeforeModify.ps1

# Stop Sonarr service before upgrade/uninstall if running
$service = 'Sonarr'
if (Get-Service "$service" -ErrorAction SilentlyContinue) {
  $running = Get-Service $service
  if ($running.Status -eq "Running") {
    Stop-Service $service
  }
}

tools\chocolateyInstall.ps1

$ErrorActionPreference = 'Stop'

$packageName = 'sonarr'

$toolsDir = Split-Path $MyInvocation.MyCommand.Definition
$fileLocation = Get-Item "$toolsDir\*.exe"

$packageArgs = @{
  packageName    = $packageName
  fileType       = 'exe'
  file           = $fileLocation
  silentArgs     = "/VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP- /LOG=`"$($env:TEMP)\$($env:chocolateyPackageName).$($env:chocolateyPackageVersion).InnoInstall.log`""
  validExitCodes = @(0)
}

Install-ChocolateyInstallPackage @packageArgs

# Remove the installers as there is no more need for it
Remove-Item $toolsDir\*.exe -ea 0 -Force

# Start service if it's not running
$service = 'Sonarr'
if (Get-Service "$service" -ErrorAction SilentlyContinue) {
  $running = Get-Service $service
  if ($running.Status -eq "Running") {
    Write-Host 'Service is already running'
  } elseif ($running.Status -eq "Stopped") {
    Start-Service $service
  }
}

tools\chocolateyUninstall.ps1

$ErrorActionPreference = 'Stop'

$packageName = 'sonarr'
$programUninstallEntryName = 'Sonarr*'

$registry = Get-UninstallRegistryKey -SoftwareName $programUninstallEntryName
$file = $registry.UninstallString

$packageArgs = @{
  packageName    = $packageName
  fileType       = 'exe'
  silentArgs     = '/VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-'
  validExitCodes = @(0)
  file           = $file
}

Uninstall-ChocolateyPackage @packageArgs

tools\Sonarr.phantom-develop.3.0.1.374.windows.exe

md5: FE2B1A7A81AE07C31B6228C50411DBFF | sha1: 869577B20D4079CEE45951D4AD704D84E8C503A8 | sha256: 838454C60528DBBA633D0682356C002D2ADC6BA863ED8D65A4BB36A07AE6BCDE | sha512: F3252FFAA11D2B607691E6BDB6ED881E51CF73B445E047904765EB21C2A2D9DF9B8C46880EE27ABC5FA9E4FA711CBCBA210A2CCF9A2746C8F467B5F52750F2E0

Virus Scan Results

sonarr.3.0.1.374-phantom.nupkg (e50aba7456a8) - ## / 58
Sonarr.phantom-develop.3.0.1.374.windows.exe (838454c60528) - ## / 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
Sonarr 4.0.10.2656	129	Friday, November 15, 2024	Approved
Sonarr 4.0.10.2624	186	Monday, November 4, 2024	Approved
Sonarr 4.0.10.2544	165	Saturday, October 26, 2024	Approved
Sonarr 4.0.9.2513	243	Tuesday, October 8, 2024	Approved
Sonarr 4.0.9.2457	231	Saturday, September 28, 2024	Approved
Sonarr 4.0.9.2421	218	Saturday, September 21, 2024	Approved
Sonarr 4.0.9.2386	202	Sunday, September 15, 2024	Approved
Sonarr 4.0.9.2342	161	Wednesday, September 4, 2024	Approved
Sonarr 4.0.9.2332	50	Monday, September 2, 2024	Approved
Sonarr 4.0.9.2300	89	Saturday, August 31, 2024	Approved
Sonarr 4.0.9.2278	114	Tuesday, August 27, 2024	Approved
Sonarr 4.0.9.2257	59	Monday, August 26, 2024	Approved
Sonarr 4.0.9.2244	18	Monday, August 26, 2024	Approved
Sonarr 4.0.8.2223	110	Wednesday, August 21, 2024	Approved
Sonarr 4.0.8.2208	62	Monday, August 19, 2024	Approved
Sonarr 4.0.8.2158	108	Thursday, August 15, 2024	Approved
Sonarr 4.0.8.2093	97	Sunday, August 11, 2024	Approved
Sonarr 4.0.8.2008	139	Thursday, August 1, 2024	Approved
Sonarr 4.0.8.1988	65	Wednesday, July 31, 2024	Approved
Sonarr 4.0.8.1967	73	Monday, July 29, 2024	Approved
Sonarr 4.0.8.1929	114	Thursday, July 25, 2024	Approved
Sonarr 4.0.8.1902	123	Thursday, July 18, 2024	Approved
Sonarr 4.0.8.1893	58	Wednesday, July 17, 2024	Approved
Sonarr 4.0.8.1874	57	Tuesday, July 16, 2024	Approved
Sonarr 4.0.7.1868	24	Monday, July 15, 2024	Approved
Sonarr 4.0.7.1863	68	Monday, July 15, 2024	Approved
Sonarr 4.0.6.1847	112	Wednesday, July 10, 2024	Approved
Sonarr 4.0.6.1820	138	Saturday, July 6, 2024	Approved
Sonarr 4.0.6.1805	128	Monday, July 1, 2024	Approved
Sonarr 4.0.5.1801	22	Sunday, June 30, 2024	Approved
Sonarr 4.0.5.1791	90	Friday, June 28, 2024	Approved
Sonarr 4.0.5.1782	92	Wednesday, June 26, 2024	Approved
Sonarr 4.0.5.1778	52	Wednesday, June 26, 2024	Approved
Sonarr 4.0.5.1760	164	Tuesday, June 18, 2024	Approved
Sonarr 4.0.5.1740	143	Tuesday, June 11, 2024	Approved
Sonarr 4.0.5.1719	200	Saturday, June 1, 2024	Approved
Sonarr 4.0.5.1710	132	Thursday, May 30, 2024	Approved
Sonarr 4.0.4.1699	158	Friday, May 24, 2024	Approved
Sonarr 4.0.4.1695	63	Thursday, May 23, 2024	Approved
Sonarr 4.0.4.1692	74	Wednesday, May 22, 2024	Approved
Sonarr 4.0.4.1668	225	Friday, May 10, 2024	Approved
Sonarr 4.0.4.1650	77	Thursday, May 9, 2024	Approved
Sonarr 4.0.4.1616	137	Sunday, May 5, 2024	Approved
Sonarr 4.0.4.1572	148	Sunday, April 28, 2024	Approved
Sonarr 4.0.4.1515	239	Tuesday, April 16, 2024	Approved
Sonarr 4.0.4.1491	99	Saturday, April 13, 2024	Approved
Sonarr 4.0.3.1486	44	Saturday, April 13, 2024	Approved
Sonarr 4.0.3.1465	125	Wednesday, April 10, 2024	Approved
Sonarr 4.0.3.1442	135	Saturday, April 6, 2024	Approved
Sonarr 4.0.3.1413	142	Monday, April 1, 2024	Approved
Sonarr 4.0.2.1408	19	Thursday, March 28, 2024	Approved
Sonarr 4.0.2.1367	201	Friday, March 22, 2024	Approved
Sonarr 4.0.2.1341	233	Saturday, March 16, 2024	Approved
Sonarr 4.0.2.1312	204	Sunday, March 10, 2024	Approved
Sonarr 4.0.2.1262	197	Sunday, March 3, 2024	Approved
Sonarr 4.0.2.1223	26	Sunday, March 3, 2024	Approved
Sonarr 4.0.2.1183	212	Tuesday, February 27, 2024	Approved
Sonarr 4.0.1.1168	180	Wednesday, February 21, 2024	Approved
Sonarr 4.0.1.1131	221	Wednesday, February 14, 2024	Approved
Sonarr 4.0.1.1114	161	Saturday, February 10, 2024	Approved
Sonarr 4.0.1.1096	148	Wednesday, February 7, 2024	Approved
Sonarr 4.0.1.1047	84	Tuesday, February 6, 2024	Approved
Sonarr 4.0.0.752-v4beta	87	Saturday, January 6, 2024	Approved
Sonarr 4.0.0.751-v4beta	31	Thursday, January 4, 2024	Approved
Sonarr 4.0.0.749-v4beta	38	Tuesday, January 2, 2024	Approved
Sonarr 4.0.0.747-v4beta	41	Monday, January 1, 2024	Approved
Sonarr 4.0.0.746-v4beta	28	Sunday, December 31, 2023	Approved
Sonarr 4.0.0.742-v4beta	32	Saturday, December 30, 2023	Approved
Sonarr 4.0.0.740-v4beta	27	Friday, December 29, 2023	Approved
Sonarr 4.0.0.738-v4beta	41	Tuesday, December 19, 2023	Approved
Sonarr 4.0.0.737-v4beta	45	Friday, December 15, 2023	Approved
Sonarr 4.0.0.734-v4beta	31	Tuesday, December 12, 2023	Approved
Sonarr 4.0.0.733-v4beta	86	Sunday, November 26, 2023	Approved
Sonarr 4.0.0.731-v4beta	40	Monday, November 20, 2023	Approved
Sonarr 4.0.0.729-v4beta	26	Monday, November 20, 2023	Approved
Sonarr 4.0.0.725-v4beta	55	Friday, November 17, 2023	Approved
Sonarr 4.0.0.720-v4beta	49	Saturday, November 11, 2023	Approved
Sonarr 4.0.0.719-v4beta	37	Friday, November 10, 2023	Approved
Sonarr 4.0.0.717-v4beta	36	Friday, November 10, 2023	Approved
Sonarr 4.0.0.710-v4beta	77	Monday, October 30, 2023	Approved
Sonarr 4.0.0.709-v4beta	39	Sunday, October 29, 2023	Approved
Sonarr 4.0.0.703-v4beta	262	Friday, October 27, 2023	Approved
Sonarr 4.0.0.700-v4beta	60	Tuesday, October 17, 2023	Approved
Sonarr 4.0.0.697-v4beta	192	Tuesday, October 10, 2023	Approved
Sonarr 4.0.0.695-v4beta	73	Tuesday, October 10, 2023	Approved
Sonarr 4.0.0.688-v4beta	44	Sunday, October 1, 2023	Approved
Sonarr 4.0.0.686-v4beta	192	Thursday, September 28, 2023	Approved
Sonarr 4.0.0.685-v4beta	637	Wednesday, September 27, 2023	Approved
Sonarr 4.0.0.682-v4beta	66	Tuesday, September 19, 2023	Approved
Sonarr 4.0.0.676-v4beta	733	Monday, September 18, 2023	Approved
Sonarr 4.0.0.671-v4beta	146	Thursday, September 14, 2023	Approved
Sonarr 4.0.0.670-v4beta	65	Thursday, September 14, 2023	Approved
Sonarr 4.0.0.669-v4beta	251	Tuesday, September 12, 2023	Approved
Sonarr 4.0.0.665-v4beta	42	Friday, September 8, 2023	Approved
Sonarr 4.0.0.664-v4beta	67	Friday, September 8, 2023	Approved
Sonarr 4.0.0.657-v4beta	59	Saturday, September 2, 2023	Approved
Sonarr 4.0.0.655-v4beta	39	Friday, September 1, 2023	Approved
Sonarr 4.0.0.651-v4beta	56	Wednesday, August 30, 2023	Approved
Sonarr 4.0.0.650-v4beta	85	Tuesday, August 29, 2023	Approved
Sonarr 4.0.0.646-v4beta	65	Wednesday, August 23, 2023	Approved
Sonarr 4.0.0.645-v4beta	89	Monday, August 21, 2023	Approved
Sonarr 4.0.0.644-v4beta	53	Sunday, August 20, 2023	Approved
Sonarr 4.0.0.642-v4beta	39	Sunday, August 20, 2023	Approved
Sonarr 4.0.0.641-v4beta	50	Sunday, August 20, 2023	Approved
Sonarr 4.0.0.637-v4beta	48	Saturday, August 19, 2023	Approved
Sonarr 4.0.0.633-v4beta	73	Saturday, August 19, 2023	Approved
Sonarr 4.0.0.631-v4beta	41	Saturday, August 19, 2023	Approved
Sonarr 4.0.0.630-v4beta	46	Friday, August 18, 2023	Approved
Sonarr 4.0.0.629-v4beta	75	Wednesday, August 16, 2023	Approved
Sonarr 4.0.0.625-v4beta	68	Monday, August 14, 2023	Approved
Sonarr 4.0.0.621-v4beta	52	Sunday, August 13, 2023	Approved
Sonarr 4.0.0.620-v4beta	37	Sunday, August 13, 2023	Approved
Sonarr 4.0.0.618-v4beta	55	Sunday, August 13, 2023	Approved
Sonarr 4.0.0.616-v4beta	43	Sunday, August 13, 2023	Approved
Sonarr 4.0.0.615-v4beta	40	Saturday, August 12, 2023	Approved
Sonarr 4.0.0.614-v4beta	62	Saturday, August 12, 2023	Approved
Sonarr 4.0.0.610-v4beta	54	Thursday, August 10, 2023	Approved
Sonarr 4.0.0.605-v4beta	33	Wednesday, August 9, 2023	Approved
Sonarr 4.0.0.604-v4beta	59	Wednesday, August 9, 2023	Approved
Sonarr 4.0.0.603-v4beta	57	Tuesday, August 8, 2023	Approved
Sonarr 4.0.0.602-v4beta	71	Sunday, August 6, 2023	Approved
Sonarr 4.0.0.601-v4beta	62	Saturday, August 5, 2023	Approved
Sonarr 4.0.0.600-v4beta	62	Friday, August 4, 2023	Approved
Sonarr 4.0.0.599-v4beta	81	Friday, August 4, 2023	Approved
Sonarr 4.0.0.592-v4beta	38	Friday, August 4, 2023	Approved
Sonarr 4.0.0.588-v4beta	39	Wednesday, August 2, 2023	Approved
Sonarr 4.0.0.585-v4beta	45	Monday, July 31, 2023	Approved
Sonarr 4.0.0.584-v4beta	68	Sunday, July 30, 2023	Approved
Sonarr 4.0.0.582-v4beta	47	Saturday, July 29, 2023	Approved
Sonarr 4.0.0.578-v4beta	52	Wednesday, July 26, 2023	Approved
Sonarr 4.0.0.577-v4beta	43	Sunday, July 23, 2023	Approved
Sonarr 4.0.0.575-v4beta	66	Thursday, July 20, 2023	Approved
Sonarr 4.0.0.571-v4beta	49	Thursday, July 20, 2023	Approved
Sonarr 4.0.0.570-v4beta	76	Wednesday, July 19, 2023	Approved
Sonarr 4.0.0.569-v4beta	64	Tuesday, July 18, 2023	Approved
Sonarr 4.0.0.565-v4beta	41	Sunday, July 16, 2023	Approved
Sonarr 4.0.0.564-v4beta	53	Sunday, July 16, 2023	Approved
Sonarr 4.0.0.562-v4beta	58	Saturday, July 15, 2023	Approved
Sonarr 4.0.0.560-v4beta	45	Saturday, July 15, 2023	Approved
Sonarr 4.0.0.559-v4beta	37	Wednesday, July 12, 2023	Approved
Sonarr 4.0.0.557-v4beta	65	Wednesday, July 12, 2023	Approved
Sonarr 4.0.0.556-v4beta	72	Tuesday, July 11, 2023	Approved
Sonarr 4.0.0.555-v4beta	32	Tuesday, July 11, 2023	Approved
Sonarr 4.0.0.552-v4beta	65	Tuesday, July 4, 2023	Approved
Sonarr 4.0.0.551-v4beta	51	Monday, July 3, 2023	Approved
Sonarr 4.0.0.548-v4beta	51	Wednesday, June 28, 2023	Approved
Sonarr 4.0.0.547-v4beta	39	Tuesday, June 27, 2023	Approved
Sonarr 4.0.0.545-v4beta	47	Sunday, June 25, 2023	Approved
Sonarr 4.0.0.544-v4beta	51	Wednesday, June 21, 2023	Approved
Sonarr 4.0.0.542-v4beta	54	Wednesday, June 21, 2023	Approved
Sonarr 4.0.0.539-v4beta	120	Tuesday, June 13, 2023	Approved
Sonarr 4.0.0.538-v4beta	60	Monday, June 12, 2023	Approved
Sonarr 4.0.0.537-v4beta	93	Saturday, June 10, 2023	Approved
Sonarr 4.0.0.535-v4beta	51	Friday, June 2, 2023	Approved
Sonarr 4.0.0.534-v4beta	66	Monday, May 29, 2023	Approved
Sonarr 4.0.0.530-v4beta	52	Sunday, May 28, 2023	Approved
Sonarr 4.0.0.526-v4beta	65	Saturday, May 27, 2023	Approved
Sonarr 4.0.0.523-v4beta	63	Saturday, May 27, 2023	Approved
Sonarr 4.0.0.521-v4beta	59	Thursday, May 25, 2023	Approved
Sonarr 4.0.0.520-v4beta	45	Tuesday, May 23, 2023	Approved
Sonarr 4.0.0.517-v4beta	154	Monday, May 22, 2023	Approved
Sonarr 4.0.0.514-v4beta	64	Monday, May 22, 2023	Approved
Sonarr 4.0.0.513-v4beta	44	Sunday, May 21, 2023	Approved
Sonarr 4.0.0.508-v4beta	131	Sunday, May 21, 2023	Approved
Sonarr 4.0.0.507-v4beta	51	Saturday, May 20, 2023	Approved
Sonarr 4.0.0.506-v4beta	77	Friday, May 19, 2023	Approved
Sonarr 4.0.0.503-v4beta	129	Thursday, May 18, 2023	Approved
Sonarr 4.0.0.500-v4beta	49	Monday, May 15, 2023	Approved
Sonarr 4.0.0.497-v4beta	49	Sunday, May 14, 2023	Approved
Sonarr 4.0.0.495-v4beta	73	Sunday, May 14, 2023	Approved
Sonarr 4.0.0.494-v4beta	42	Saturday, May 13, 2023	Approved
Sonarr 4.0.0.493-v4beta	55	Friday, May 12, 2023	Approved
Sonarr 4.0.0.492-v4beta	39	Friday, May 12, 2023	Approved
Sonarr 4.0.0.491-v4beta	69	Thursday, May 11, 2023	Approved
Sonarr 4.0.0.488-v4beta	80	Wednesday, May 10, 2023	Approved
Sonarr 4.0.0.485-v4beta	59	Tuesday, May 9, 2023	Approved
Sonarr 4.0.0.484-v4beta	78	Monday, May 8, 2023	Approved
Sonarr 4.0.0.478-v4beta	65	Sunday, May 7, 2023	Approved
Sonarr 4.0.0.474-v4beta	179	Sunday, May 7, 2023	Approved
Sonarr 4.0.0.472-v4beta	102	Saturday, May 6, 2023	Approved
Sonarr 4.0.0.471-v4beta	97	Tuesday, May 2, 2023	Approved
Sonarr 4.0.0.470-v4beta	125	Sunday, April 30, 2023	Approved
Sonarr 4.0.0.466-v4beta	98	Saturday, April 29, 2023	Approved
Sonarr 3.0.10.1567	1327	Saturday, April 29, 2023	Approved
Sonarr 3.0.9.1555-beta	76	Monday, August 8, 2022	Approved
Sonarr 3.0.9.1553-beta	60	Sunday, August 7, 2022	Approved
Sonarr 3.0.9.1549	1227	Sunday, August 7, 2022	Approved
Sonarr 3.0.8.1548-beta	58	Wednesday, August 3, 2022	Approved
Sonarr 3.0.8.1540-beta	64	Wednesday, July 6, 2022	Approved
Sonarr 3.0.8.1538-beta	83	Friday, June 24, 2022	Approved
Sonarr 3.0.8.1537-beta	82	Monday, June 13, 2022	Approved
Sonarr 3.0.8.1536-beta	70	Sunday, June 12, 2022	Approved
Sonarr 3.0.8.1526-beta	85	Sunday, May 29, 2022	Approved
Sonarr 3.0.8.1525-beta	79	Sunday, May 29, 2022	Approved
Sonarr 3.0.8.1523-beta	75	Tuesday, May 24, 2022	Approved
Sonarr 3.0.8.1520-beta	83	Monday, May 16, 2022	Approved
Sonarr 3.0.8.1519-beta	70	Tuesday, May 10, 2022	Approved
Sonarr 3.0.8.1518-beta	71	Tuesday, May 10, 2022	Approved
Sonarr 3.0.8.1517-beta	86	Sunday, May 1, 2022	Approved
Sonarr 3.0.8.1510-beta	67	Friday, April 29, 2022	Approved
Sonarr 3.0.8.1507	721	Sunday, April 24, 2022	Approved
Sonarr 3.0.7.1506-beta	52	Sunday, April 24, 2022	Approved
Sonarr 3.0.7.1505-beta	70	Tuesday, April 19, 2022	Approved
Sonarr 3.0.7.1503-beta	76	Wednesday, April 13, 2022	Approved
Sonarr 3.0.7.1501-beta	73	Sunday, April 10, 2022	Approved
Sonarr 3.0.7.1494-beta	78	Thursday, April 7, 2022	Approved
Sonarr 3.0.7.1493-beta	87	Wednesday, April 6, 2022	Approved
Sonarr 3.0.7.1492-beta	53	Wednesday, April 6, 2022	Approved
Sonarr 3.0.7.1487-beta	71	Friday, March 25, 2022	Approved
Sonarr 3.0.7.1485-beta	87	Monday, March 21, 2022	Approved
Sonarr 3.0.7.1483-beta	57	Sunday, March 20, 2022	Approved
Sonarr 3.0.7.1479-beta	76	Monday, March 7, 2022	Approved
Sonarr 3.0.7.1477	500	Saturday, March 5, 2022	Approved
Sonarr 3.0.6.1476-beta	59	Saturday, March 5, 2022	Approved
Sonarr 3.0.6.1475-beta	61	Monday, February 28, 2022	Approved
Sonarr 3.0.6.1471-beta	58	Saturday, February 26, 2022	Approved
Sonarr 3.0.6.1470-beta	70	Tuesday, February 22, 2022	Approved
Sonarr 3.0.6.1468-beta	71	Tuesday, February 22, 2022	Approved
Sonarr 3.0.6.1467-beta	76	Tuesday, February 22, 2022	Approved
Sonarr 3.0.6.1460-beta	96	Thursday, February 17, 2022	Approved
Sonarr 3.0.6.1457-beta	72	Sunday, February 6, 2022	Approved
Sonarr 3.0.6.1451-beta	77	Monday, January 24, 2022	Approved
Sonarr 3.0.6.1432-beta	70	Thursday, December 30, 2021	Approved
Sonarr 3.0.6.1430-beta	92	Wednesday, December 29, 2021	Approved
Sonarr 3.0.6.1429-beta	78	Monday, December 27, 2021	Approved
Sonarr 3.0.6.1422-beta	80	Saturday, December 25, 2021	Approved
Sonarr 3.0.6.1414-beta	71	Friday, December 24, 2021	Approved
Sonarr 3.0.6.1412-beta	69	Tuesday, December 21, 2021	Approved
Sonarr 3.0.6.1410-beta	83	Sunday, December 19, 2021	Approved
Sonarr 3.0.6.1409-beta	73	Saturday, December 18, 2021	Approved
Sonarr 3.0.6.1405-beta	78	Thursday, December 16, 2021	Approved
Sonarr 3.0.6.1402-beta	64	Thursday, December 16, 2021	Approved
Sonarr 3.0.6.1401-beta	87	Tuesday, December 14, 2021	Approved
Sonarr 3.0.6.1399-beta	93	Tuesday, December 7, 2021	Approved
Sonarr 3.0.6.1397-beta	71	Sunday, December 5, 2021	Approved
Sonarr 3.0.6.1395-beta	75	Sunday, December 5, 2021	Approved
Sonarr 3.0.6.1394-beta	82	Saturday, December 4, 2021	Approved
Sonarr 3.0.6.1390-beta	75	Saturday, November 27, 2021	Approved
Sonarr 3.0.6.1388-beta	77	Friday, November 26, 2021	Approved
Sonarr 3.0.6.1386-beta	103	Monday, November 22, 2021	Approved
Sonarr 3.0.6.1385-beta	83	Sunday, November 21, 2021	Approved
Sonarr 3.0.6.1375-beta	77	Tuesday, November 16, 2021	Approved
Sonarr 3.0.6.1373-beta	91	Friday, November 5, 2021	Approved
Sonarr 3.0.6.1372-beta	73	Friday, November 5, 2021	Approved
Sonarr 3.0.6.1365-beta	74	Thursday, November 4, 2021	Approved
Sonarr 3.0.6.1357-beta	75	Tuesday, October 26, 2021	Approved
Sonarr 3.0.6.1355-beta	108	Wednesday, October 6, 2021	Approved
Sonarr 3.0.6.1352-beta	86	Tuesday, October 5, 2021	Approved
Sonarr 3.0.6.1350-beta	78	Monday, October 4, 2021	Approved
Sonarr 3.0.6.1348-beta	79	Monday, October 4, 2021	Approved
Sonarr 3.0.6.1347-beta	82	Sunday, October 3, 2021	Approved
Sonarr 3.0.6.1343-beta	81	Friday, October 1, 2021	Approved
Sonarr 3.0.6.1342	1081	Thursday, September 30, 2021	Approved
Sonarr 3.0.6.1341-beta	82	Thursday, September 30, 2021	Approved
Sonarr 3.0.6.1335	135	Wednesday, September 29, 2021	Approved
Sonarr 3.0.6.1334-beta	80	Wednesday, September 29, 2021	Approved
Sonarr 3.0.6.1333-beta	90	Monday, September 6, 2021	Approved
Sonarr 3.0.6.1332-beta	87	Saturday, September 4, 2021	Approved
Sonarr 3.0.6.1325-beta	70	Tuesday, August 31, 2021	Approved
Sonarr 3.0.6.1313-beta	83	Monday, August 30, 2021	Approved
Sonarr 3.0.6.1309-beta	81	Sunday, August 15, 2021	Approved
Sonarr 3.0.6.1305-beta	87	Wednesday, August 11, 2021	Approved
Sonarr 3.0.6.1301-beta	85	Saturday, August 7, 2021	Approved
Sonarr 3.0.6.1297-beta	84	Friday, August 6, 2021	Approved
Sonarr 3.0.6.1295-beta	83	Wednesday, August 4, 2021	Approved
Sonarr 3.0.6.1286-beta	88	Monday, August 2, 2021	Approved
Sonarr 3.0.6.1281-beta	92	Sunday, August 1, 2021	Approved
Sonarr 3.0.6.1278-beta	81	Tuesday, July 27, 2021	Approved
Sonarr 3.0.6.1277-beta	115	Tuesday, July 13, 2021	Approved
Sonarr 3.0.6.1276-beta	130	Sunday, July 4, 2021	Approved
Sonarr 3.0.6.1272-beta	103	Tuesday, June 22, 2021	Approved
Sonarr 3.0.6.1271-beta	86	Tuesday, June 22, 2021	Exempted
Sonarr 3.0.6.1266	767	Friday, June 18, 2021	Approved
Sonarr 3.0.6.1265	114	Thursday, June 17, 2021	Approved
Sonarr 3.0.6.1264-beta	99	Thursday, June 17, 2021	Approved
Sonarr 3.0.6.1263-beta	95	Tuesday, June 8, 2021	Approved
Sonarr 3.0.6.1262-beta	81	Thursday, May 27, 2021	Approved
Sonarr 3.0.6.1259-beta	77	Thursday, May 27, 2021	Approved
Sonarr 3.0.6.1241-beta	119	Thursday, May 20, 2021	Approved
Sonarr 3.0.6.1233-beta	90	Sunday, May 16, 2021	Approved
Sonarr 3.0.6.1227-beta	89	Thursday, May 13, 2021	Approved
Sonarr 3.0.6.1226-beta	99	Tuesday, May 11, 2021	Approved
Sonarr 3.0.6.1224-beta	103	Sunday, May 9, 2021	Approved
Sonarr 3.0.6.1222-beta	77	Saturday, May 8, 2021	Approved
Sonarr 3.0.6.1219-beta	112	Sunday, April 25, 2021	Approved
Sonarr 3.0.6.1214-beta	99	Friday, April 23, 2021	Approved
Sonarr 3.0.6.1213-beta	100	Friday, April 23, 2021	Approved
Sonarr 3.0.6.1209-beta	95	Thursday, April 22, 2021	Approved
Sonarr 3.0.6.1207-beta	103	Tuesday, April 13, 2021	Approved
Sonarr 3.0.6.1206-beta	112	Sunday, April 11, 2021	Approved
Sonarr 3.0.6.1205-beta	95	Sunday, April 11, 2021	Approved
Sonarr 3.0.6.1203-beta	116	Saturday, April 10, 2021	Approved
Sonarr 3.0.6.1201-beta	103	Tuesday, March 30, 2021	Approved
Sonarr 3.0.6.1196	873	Sunday, March 28, 2021	Approved
Sonarr 3.0.6.1195-beta	98	Sunday, March 28, 2021	Approved
Sonarr 3.0.5.1190-beta	125	Wednesday, March 24, 2021	Approved
Sonarr 3.0.5.1189-beta	97	Saturday, March 20, 2021	Approved
Sonarr 3.0.5.1164-beta	116	Thursday, March 18, 2021	Approved
Sonarr 3.0.5.1161-beta	131	Sunday, March 14, 2021	Approved
Sonarr 3.0.5.1159-beta	118	Sunday, March 14, 2021	Approved
Sonarr 3.0.5.1158-beta	113	Thursday, March 11, 2021	Approved
Sonarr 3.0.5.1157-beta	142	Thursday, March 11, 2021	Approved
Sonarr 3.0.5.1150-beta	111	Tuesday, March 9, 2021	Approved
Sonarr 3.0.5.1144	393	Tuesday, March 9, 2021	Approved
Sonarr 3.0.5.1143-phantom	118	Monday, March 8, 2021	Exempted
Sonarr 3.0.4.1139-phantom	115	Sunday, March 7, 2021	Exempted
Sonarr 3.0.4.1132-phantom	133	Friday, February 26, 2021	Approved
Sonarr 3.0.4.1131-phantom	170	Sunday, February 21, 2021	Approved
Sonarr 3.0.4.1130-phantom	111	Wednesday, February 17, 2021	Approved
Sonarr 3.0.4.1129-phantom	99	Wednesday, February 17, 2021	Approved
Sonarr 3.0.4.1126-phantom	127	Wednesday, February 10, 2021	Approved
Sonarr 3.0.4.1124-phantom	121	Tuesday, February 9, 2021	Approved
Sonarr 3.0.4.1120-phantom	127	Tuesday, February 9, 2021	Approved
Sonarr 3.0.4.1119-phantom	92	Monday, February 8, 2021	Approved
Sonarr 3.0.4.1117-phantom	105	Monday, February 8, 2021	Approved
Sonarr 3.0.4.1116-phantom	98	Monday, February 8, 2021	Approved
Sonarr 3.0.4.1113-phantom	109	Monday, February 8, 2021	Approved
Sonarr 3.0.4.1107-phantom	110	Sunday, February 7, 2021	Approved
Sonarr 3.0.4.1106-phantom	127	Sunday, February 7, 2021	Approved
Sonarr 3.0.4.1105-phantom	110	Sunday, February 7, 2021	Approved
Sonarr 3.0.4.1100-phantom	118	Thursday, February 4, 2021	Approved
Sonarr 3.0.4.1098-phantom	104	Wednesday, February 3, 2021	Approved
Sonarr 3.0.4.1096-phantom	139	Monday, February 1, 2021	Approved
Sonarr 3.0.4.1095-phantom	114	Sunday, January 31, 2021	Approved
Sonarr 3.0.4.1093-phantom	131	Sunday, January 31, 2021	Approved
Sonarr 3.0.4.1091-phantom	121	Monday, January 25, 2021	Approved
Sonarr 3.0.4.1088-phantom	110	Sunday, January 24, 2021	Approved
Sonarr 3.0.4.1085-phantom	108	Sunday, January 24, 2021	Approved
Sonarr 3.0.4.1083-phantom	132	Thursday, January 21, 2021	Approved
Sonarr 3.0.4.1080-phantom	120	Thursday, January 21, 2021	Approved
Sonarr 3.0.4.1077-phantom	128	Sunday, January 17, 2021	Approved
Sonarr 3.0.4.1076-phantom	111	Sunday, January 17, 2021	Approved
Sonarr 3.0.4.1075-phantom	104	Sunday, January 17, 2021	Approved
Sonarr 3.0.4.1073-phantom	123	Saturday, January 16, 2021	Approved
Sonarr 3.0.4.1070-phantom	109	Friday, January 15, 2021	Approved
Sonarr 3.0.4.1069-phantom	115	Friday, January 15, 2021	Approved
Sonarr 3.0.4.1066-phantom	111	Thursday, January 14, 2021	Approved
Sonarr 3.0.4.1062-phantom	127	Wednesday, January 13, 2021	Approved
Sonarr 3.0.4.1061-phantom	99	Tuesday, January 12, 2021	Approved
Sonarr 3.0.4.1060-phantom	123	Sunday, January 10, 2021	Approved
Sonarr 3.0.4.1059-phantom	116	Thursday, January 7, 2021	Approved
Sonarr 3.0.4.1058-phantom	111	Tuesday, January 5, 2021	Approved
Sonarr 3.0.4.1055-phantom	126	Monday, January 4, 2021	Approved
Sonarr 3.0.4.1052-phantom	103	Monday, January 4, 2021	Exempted
Sonarr 3.0.4.1042-phantom	114	Thursday, December 31, 2020	Approved
Sonarr 3.0.4.1041-phantom	106	Wednesday, December 30, 2020	Approved
Sonarr 3.0.4.1039-phantom	142	Friday, December 25, 2020	Approved
Sonarr 3.0.4.1035-phantom	135	Thursday, December 24, 2020	Approved
Sonarr 3.0.4.1033-phantom	114	Saturday, December 19, 2020	Approved
Sonarr 3.0.4.1026-phantom	135	Sunday, December 13, 2020	Approved
Sonarr 3.0.4.1024-phantom	143	Sunday, December 6, 2020	Approved
Sonarr 3.0.4.1023-phantom	124	Tuesday, December 1, 2020	Approved
Sonarr 3.0.4.1021-phantom	132	Monday, November 23, 2020	Approved
Sonarr 3.0.4.1020-phantom	105	Sunday, November 22, 2020	Approved
Sonarr 3.0.4.1019-phantom	117	Sunday, November 22, 2020	Approved
Sonarr 3.0.4.1018-phantom	118	Saturday, November 21, 2020	Approved
Sonarr 3.0.4.1017-phantom	105	Saturday, November 21, 2020	Approved
Sonarr 3.0.4.1016-phantom	118	Friday, November 20, 2020	Approved
Sonarr 3.0.4.1011-phantom	139	Wednesday, November 18, 2020	Approved
Sonarr 3.0.4.1009-phantom	117	Tuesday, November 17, 2020	Approved
Sonarr 3.0.4.1006-phantom	127	Monday, November 16, 2020	Approved
Sonarr 3.0.4.1003-phantom	111	Monday, November 16, 2020	Approved
Sonarr 3.0.4.1002-phantom	139	Sunday, November 15, 2020	Approved
Sonarr 3.0.4.1000-phantom	111	Sunday, November 15, 2020	Approved
Sonarr 3.0.4.999-phantom	125	Saturday, November 14, 2020	Approved
Sonarr 3.0.4.995-phantom	114	Saturday, November 14, 2020	Approved
Sonarr 3.0.4.994-phantom	146	Monday, November 9, 2020	Approved
Sonarr 3.0.4.993-phantom	121	Monday, November 2, 2020	Approved
Sonarr 3.0.4.991-phantom	164	Monday, October 26, 2020	Approved
Sonarr 3.0.4.990-phantom	125	Monday, October 26, 2020	Approved
Sonarr 3.0.4.988-phantom	119	Sunday, October 25, 2020	Approved
Sonarr 3.0.4.986-phantom	143	Monday, October 19, 2020	Approved
Sonarr 3.0.4.985-phantom	148	Monday, October 19, 2020	Approved
Sonarr 3.0.4.983-phantom	126	Monday, October 19, 2020	Approved
Sonarr 3.0.4.982-phantom	138	Tuesday, October 13, 2020	Approved
Sonarr 3.0.4.981-phantom	109	Tuesday, October 13, 2020	Approved
Sonarr 3.0.4.975-phantom	138	Monday, October 12, 2020	Approved
Sonarr 3.0.3.970-phantom	123	Sunday, October 11, 2020	Approved
Sonarr 3.0.3.967-phantom	145	Saturday, October 10, 2020	Approved
Sonarr 3.0.3.965-phantom	133	Friday, October 9, 2020	Approved
Sonarr 3.0.3.964-phantom	130	Friday, October 9, 2020	Approved
Sonarr 3.0.3.956-phantom	125	Tuesday, October 6, 2020	Approved
Sonarr 3.0.3.955-phantom	110	Tuesday, October 6, 2020	Approved
Sonarr 3.0.3.938-phantom	163	Saturday, October 3, 2020	Approved
Sonarr 3.0.3.937-phantom	138	Thursday, October 1, 2020	Approved
Sonarr 3.0.3.935-phantom	127	Wednesday, September 30, 2020	Approved
Sonarr 3.0.3.928-phantom	157	Thursday, September 17, 2020	Approved
Sonarr 3.0.3.927-phantom	126	Wednesday, September 16, 2020	Approved
Sonarr 3.0.3.925-phantom	115	Wednesday, September 16, 2020	Approved
Sonarr 3.0.3.924-phantom	128	Friday, September 11, 2020	Approved
Sonarr 3.0.3.913-phantom	184	Friday, September 4, 2020	Approved
Sonarr 3.0.3.911-phantom	152	Monday, August 17, 2020	Approved
Sonarr 3.0.3.907-phantom	149	Tuesday, August 11, 2020	Approved
Sonarr 3.0.3.906-phantom	170	Wednesday, August 5, 2020	Approved
Sonarr 3.0.3.905-phantom	131	Monday, August 3, 2020	Approved
Sonarr 3.0.3.904-phantom	159	Monday, July 27, 2020	Approved
Sonarr 3.0.3.899-phantom	159	Friday, July 10, 2020	Approved
Sonarr 3.0.3.896-phantom	162	Friday, June 26, 2020	Approved
Sonarr 3.0.3.895-phantom	155	Monday, June 22, 2020	Approved
Sonarr 3.0.3.894-phantom	134	Monday, June 22, 2020	Approved
Sonarr 3.0.3.892-phantom	167	Wednesday, June 17, 2020	Approved
Sonarr 3.0.3.885-phantom	199	Sunday, June 14, 2020	Approved
Sonarr 3.0.3.880-phantom	164	Wednesday, June 10, 2020	Approved
Sonarr 3.0.3.874-phantom	188	Tuesday, June 9, 2020	Approved
Sonarr 3.0.3.873-phantom	174	Monday, June 8, 2020	Approved
Sonarr 3.0.3.871-phantom	148	Monday, June 8, 2020	Approved
Sonarr 3.0.3.868-phantom	145	Sunday, June 7, 2020	Approved
Sonarr 3.0.3.862-phantom	148	Sunday, June 7, 2020	Approved
Sonarr 3.0.3.849-phantom	137	Wednesday, June 3, 2020	Approved
Sonarr 3.0.3.845-phantom	162	Tuesday, June 2, 2020	Approved
Sonarr 3.0.3.842-phantom	146	Monday, June 1, 2020	Approved
Sonarr 3.0.3.834-phantom	172	Thursday, May 28, 2020	Approved
Sonarr 3.0.3.833-phantom	172	Monday, May 25, 2020	Approved
Sonarr 3.0.3.832-phantom	170	Monday, May 25, 2020	Approved
Sonarr 3.0.3.830-phantom	178	Saturday, May 23, 2020	Approved
Sonarr 3.0.3.825-phantom	152	Wednesday, May 20, 2020	Approved
Sonarr 3.0.3.824-phantom	164	Monday, May 18, 2020	Approved
Sonarr 3.0.3.822-phantom	187	Saturday, May 16, 2020	Approved
Sonarr 3.0.3.809-phantom	197	Thursday, May 14, 2020	Approved
Sonarr 3.0.3.807-phantom	196	Wednesday, May 13, 2020	Approved
Sonarr 3.0.3.803-phantom	170	Sunday, May 10, 2020	Approved
Sonarr 3.0.3.790-phantom	190	Wednesday, May 6, 2020	Approved
Sonarr 3.0.3.789-phantom	185	Wednesday, May 6, 2020	Approved
Sonarr 3.0.3.784-phantom	182	Sunday, May 3, 2020	Approved
Sonarr 3.0.3.782-phantom	200	Sunday, May 3, 2020	Approved
Sonarr 3.0.3.781-phantom	170	Saturday, May 2, 2020	Approved
Sonarr 3.0.3.780-phantom	194	Wednesday, April 29, 2020	Approved
Sonarr 3.0.3.779-phantom	181	Wednesday, April 29, 2020	Approved
Sonarr 3.0.3.778-phantom	225	Wednesday, April 29, 2020	Approved
Sonarr 3.0.3.777-phantom	174	Tuesday, April 28, 2020	Approved
Sonarr 3.0.3.776-phantom	154	Monday, April 27, 2020	Approved
Sonarr 3.0.3.774-phantom	199	Monday, April 27, 2020	Approved
Sonarr 3.0.3.771-phantom	156	Sunday, April 26, 2020	Approved
Sonarr 3.0.3.770-phantom	203	Tuesday, April 21, 2020	Approved
Sonarr 3.0.3.765-phantom	196	Monday, April 20, 2020	Approved
Sonarr 3.0.3.764-phantom	206	Sunday, April 19, 2020	Approved
Sonarr 3.0.3.761-phantom	179	Saturday, April 18, 2020	Approved
Sonarr 3.0.3.757-phantom	184	Wednesday, April 15, 2020	Approved
Sonarr 3.0.3.754-phantom	194	Monday, April 13, 2020	Approved
Sonarr 3.0.3.750-phantom	244	Tuesday, March 31, 2020	Approved
Sonarr 3.0.3.748-phantom	169	Monday, March 30, 2020	Approved
Sonarr 3.0.3.744-phantom	177	Sunday, March 29, 2020	Approved
Sonarr 3.0.3.741-phantom	235	Monday, March 23, 2020	Approved
Sonarr 3.0.3.740-phantom	176	Sunday, March 22, 2020	Approved
Sonarr 3.0.3.737-phantom	196	Friday, March 20, 2020	Approved
Sonarr 3.0.3.735-phantom	203	Friday, March 20, 2020	Approved
Sonarr 3.0.3.731-phantom	189	Tuesday, March 17, 2020	Approved
Sonarr 3.0.3.729-phantom	192	Sunday, March 15, 2020	Approved
Sonarr 3.0.3.728-phantom	210	Saturday, March 14, 2020	Approved
Sonarr 3.0.3.727-phantom	189	Friday, March 13, 2020	Approved
Sonarr 3.0.3.721-phantom	179	Wednesday, March 11, 2020	Approved
Sonarr 3.0.3.717-phantom	183	Monday, March 9, 2020	Approved
Sonarr 3.0.3.713-phantom	241	Wednesday, March 4, 2020	Approved
Sonarr 3.0.3.711-phantom	187	Tuesday, March 3, 2020	Approved
Sonarr 3.0.3.707-phantom	167	Monday, March 2, 2020	Approved
Sonarr 3.0.3.706-phantom	193	Monday, March 2, 2020	Approved
Sonarr 3.0.3.703-phantom	230	Saturday, February 29, 2020	Approved
Sonarr 3.0.3.701-phantom	197	Saturday, February 22, 2020	Approved
Sonarr 3.0.3.698-phantom	198	Wednesday, February 12, 2020	Approved
Sonarr 3.0.3.690-phantom	254	Sunday, February 2, 2020	Approved
Sonarr 3.0.3.688-phantom	237	Monday, January 13, 2020	Approved
Sonarr 3.0.3.687-phantom	202	Wednesday, January 8, 2020	Approved
Sonarr 3.0.3.685-phantom	221	Sunday, January 5, 2020	Approved
Sonarr 3.0.3.684-phantom	195	Sunday, January 5, 2020	Approved
Sonarr 3.0.3.679-phantom	199	Monday, December 30, 2019	Approved
Sonarr 3.0.3.677-phantom	177	Sunday, December 29, 2019	Approved
Sonarr 3.0.3.671-phantom	177	Wednesday, December 25, 2019	Exempted
Sonarr 3.0.3.669-phantom	192	Tuesday, December 24, 2019	Exempted
Sonarr 3.0.3.668-phantom	210	Thursday, December 19, 2019	Approved
Sonarr 3.0.3.664-phantom	228	Saturday, December 7, 2019	Approved
Sonarr 3.0.3.663-phantom	228	Saturday, December 7, 2019	Approved
Sonarr 3.0.3.661-phantom	202	Thursday, December 5, 2019	Approved
Sonarr 3.0.3.659-phantom	200	Wednesday, November 27, 2019	Approved
Sonarr 3.0.3.658-phantom	201	Monday, November 25, 2019	Approved
Sonarr 3.0.3.657-phantom	210	Wednesday, November 20, 2019	Approved
Sonarr 3.0.3.655-phantom	237	Friday, November 15, 2019	Approved
Sonarr 3.0.3.654-phantom	267	Friday, November 8, 2019	Approved
Sonarr 3.0.3.653-phantom	217	Monday, November 4, 2019	Approved
Sonarr 3.0.3.652-phantom	223	Monday, October 21, 2019	Approved
Sonarr 3.0.3.645-phantom	228	Saturday, October 19, 2019	Approved
Sonarr 3.0.3.644-phantom	199	Wednesday, September 18, 2019	Approved
Sonarr 3.0.3.638-phantom	206	Friday, September 13, 2019	Approved
Sonarr 3.0.3.626-phantom	242	Wednesday, September 11, 2019	Approved
Sonarr 3.0.3.625-phantom	214	Tuesday, September 10, 2019	Approved
Sonarr 3.0.3.624-phantom	233	Saturday, September 7, 2019	Approved
Sonarr 3.0.3.622-phantom	248	Thursday, September 5, 2019	Approved
Sonarr 3.0.3.620-phantom	223	Sunday, September 1, 2019	Approved
Sonarr 3.0.3.619-phantom	207	Sunday, September 1, 2019	Approved
Sonarr 3.0.3.618-phantom	222	Saturday, August 31, 2019	Approved
Sonarr 3.0.3.616-phantom	248	Tuesday, August 27, 2019	Approved
Sonarr 3.0.3.610-phantom	226	Saturday, August 24, 2019	Approved
Sonarr 3.0.2.607-phantom	320	Friday, August 23, 2019	Approved
Sonarr 3.0.2.601-phantom	251	Tuesday, August 20, 2019	Approved
Sonarr 3.0.2.587-phantom	262	Friday, August 16, 2019	Approved
Sonarr 3.0.2.584-phantom	234	Thursday, August 15, 2019	Approved
Sonarr 3.0.2.582-phantom	199	Thursday, August 15, 2019	Approved
Sonarr 3.0.2.577-phantom	226	Tuesday, August 13, 2019	Approved
Sonarr 3.0.2.575-phantom	217	Monday, August 12, 2019	Approved
Sonarr 3.0.2.572-phantom	209	Friday, August 9, 2019	Approved
Sonarr 3.0.2.570-phantom	239	Thursday, August 8, 2019	Approved
Sonarr 3.0.2.565-phantom	212	Wednesday, August 7, 2019	Approved
Sonarr 3.0.2.564-phantom	209	Wednesday, August 7, 2019	Approved
Sonarr 3.0.2.560-phantom	211	Sunday, August 4, 2019	Approved
Sonarr 3.0.2.559-phantom	229	Saturday, August 3, 2019	Approved
Sonarr 3.0.2.553-phantom	235	Wednesday, July 31, 2019	Approved
Sonarr 3.0.2.552-phantom	232	Tuesday, July 30, 2019	Approved
Sonarr 3.0.2.551-phantom	218	Monday, July 29, 2019	Approved
Sonarr 3.0.2.537-phantom	253	Thursday, July 18, 2019	Approved
Sonarr 3.0.2.536-phantom	248	Wednesday, July 17, 2019	Approved
Sonarr 3.0.2.535-phantom	207	Wednesday, July 17, 2019	Approved
Sonarr 3.0.2.531-phantom	247	Wednesday, July 17, 2019	Approved
Sonarr 3.0.2.529-phantom	206	Monday, July 15, 2019	Approved
Sonarr 3.0.1.527-phantom	221	Wednesday, July 3, 2019	Approved
Sonarr 3.0.1.526-phantom	243	Monday, July 1, 2019	Approved
Sonarr 3.0.1.522-phantom	231	Thursday, June 20, 2019	Approved
Sonarr 3.0.1.520-phantom	237	Sunday, June 16, 2019	Approved
Sonarr 3.0.1.517-phantom	208	Saturday, June 15, 2019	Approved
Sonarr 3.0.1.514-phantom	275	Saturday, June 15, 2019	Approved
Sonarr 3.0.1.513-phantom	267	Wednesday, June 12, 2019	Approved
Sonarr 3.0.1.511-phantom	231	Tuesday, June 11, 2019	Approved
Sonarr 3.0.1.509-phantom	226	Monday, June 10, 2019	Approved
Sonarr 3.0.1.508-phantom	225	Monday, June 10, 2019	Approved
Sonarr 3.0.1.506-phantom	196	Saturday, June 8, 2019	Approved
Sonarr 3.0.1.503-phantom	233	Thursday, May 30, 2019	Approved
Sonarr 3.0.1.500-phantom	224	Thursday, May 23, 2019	Approved
Sonarr 3.0.1.499-phantom	233	Sunday, May 19, 2019	Approved
Sonarr 3.0.1.497-phantom	211	Thursday, May 16, 2019	Approved
Sonarr 3.0.1.493-phantom	223	Monday, May 13, 2019	Approved
Sonarr 3.0.1.492-phantom	212	Sunday, May 12, 2019	Approved
Sonarr 3.0.1.490-phantom	272	Thursday, May 9, 2019	Approved
Sonarr 3.0.1.486-phantom	266	Thursday, May 9, 2019	Approved
Sonarr 3.0.1.482-phantom	235	Monday, May 6, 2019	Approved
Sonarr 3.0.1.478-phantom	224	Monday, May 6, 2019	Approved
Sonarr 3.0.1.474-phantom	258	Sunday, May 5, 2019	Approved
Sonarr 3.0.1.473-phantom	174	Saturday, May 4, 2019	Approved
Sonarr 3.0.1.472-phantom	210	Saturday, May 4, 2019	Approved
Sonarr 3.0.1.470-phantom	214	Saturday, May 4, 2019	Approved
Sonarr 3.0.1.467-phantom	246	Monday, April 29, 2019	Approved
Sonarr 3.0.1.464-phantom	239	Sunday, April 28, 2019	Approved
Sonarr 3.0.1.458-phantom	284	Friday, April 26, 2019	Approved
Sonarr 3.0.1.454-phantom	242	Thursday, April 25, 2019	Approved
Sonarr 3.0.1.453-phantom	202	Wednesday, April 24, 2019	Approved
Sonarr 3.0.1.449-phantom	256	Sunday, April 21, 2019	Approved
Sonarr 3.0.1.441-phantom	245	Saturday, April 13, 2019	Approved
Sonarr 3.0.1.439-phantom	191	Friday, April 12, 2019	Approved
Sonarr 3.0.1.438-phantom	275	Friday, April 12, 2019	Approved
Sonarr 3.0.1.435-phantom	222	Thursday, April 11, 2019	Approved
Sonarr 3.0.1.430-phantom	220	Tuesday, April 9, 2019	Approved
Sonarr 3.0.1.429-phantom	253	Tuesday, April 9, 2019	Approved
Sonarr 3.0.1.418-phantom	210	Wednesday, March 27, 2019	Approved
Sonarr 3.0.1.411-phantom	214	Sunday, March 17, 2019	Approved
Sonarr 3.0.1.409-phantom	250	Saturday, March 16, 2019	Approved
Sonarr 3.0.1.408-phantom	218	Friday, March 15, 2019	Approved
Sonarr 3.0.1.407-phantom	261	Thursday, March 14, 2019	Approved
Sonarr 3.0.1.406-phantom	232	Wednesday, March 13, 2019	Approved
Sonarr 3.0.1.403-phantom	247	Sunday, March 10, 2019	Approved
Sonarr 3.0.1.400-phantom	255	Saturday, March 9, 2019	Approved
Sonarr 3.0.1.392-phantom	224	Thursday, March 7, 2019	Approved
Sonarr 3.0.1.390-phantom	250	Wednesday, March 6, 2019	Approved
Sonarr 3.0.1.388-phantom	208	Tuesday, March 5, 2019	Approved
Sonarr 3.0.1.384-phantom	231	Monday, March 4, 2019	Approved
Sonarr 3.0.1.378-phantom	226	Sunday, February 24, 2019	Approved
Sonarr 3.0.1.376-phantom	234	Saturday, February 23, 2019	Approved
Sonarr 3.0.1.375-phantom	211	Saturday, February 23, 2019	Approved
Sonarr 3.0.1.374-phantom	205	Thursday, February 21, 2019	Approved
Sonarr 3.0.1.373-phantom	226	Wednesday, February 20, 2019	Approved
Sonarr 3.0.1.371-phantom	239	Friday, February 15, 2019	Approved
Sonarr 3.0.1.370-phantom	218	Wednesday, February 13, 2019	Approved
Sonarr 3.0.1.368-phantom	258	Friday, February 8, 2019	Approved
Sonarr 3.0.1.367-phantom	202	Thursday, February 7, 2019	Approved
Sonarr 3.0.1.364-phantom	208	Tuesday, February 5, 2019	Approved
Sonarr 3.0.1.363-phantom	253	Tuesday, January 22, 2019	Exempted
Sonarr 3.0.1.359-phantom	260	Sunday, January 20, 2019	Exempted
Sonarr 2.0.0.5344	1877	Saturday, March 14, 2020	Approved
Sonarr 2.0.0.5343-beta	162	Friday, March 13, 2020	Approved
Sonarr 2.0.0.5338	1161	Thursday, August 15, 2019	Approved
Sonarr 2.0.0.5337-beta	218	Wednesday, July 3, 2019	Approved
Sonarr 2.0.0.5322	610	Tuesday, March 26, 2019	Approved
Sonarr 2.0.0.5321-beta	198	Sunday, March 24, 2019	Approved
Sonarr 2.0.0.5320-beta	240	Sunday, March 24, 2019	Approved
Sonarr 2.0.0.5318-beta	200	Monday, March 4, 2019	Approved
Sonarr 2.0.0.5303-beta	224	Thursday, February 7, 2019	Approved
Sonarr 2.0.0.5302-beta	225	Monday, February 4, 2019	Approved
Sonarr 2.0.0.5301	530	Thursday, January 24, 2019	Approved
Sonarr 2.0.0.5298-beta	274	Sunday, January 20, 2019	Approved
Sonarr 2.0.0.5252	313	Sunday, January 20, 2019	Approved
Sonarr 2.0.0.5250	610	Monday, October 8, 2018	Approved
Sonarr 2.0.0.5228	584	Sunday, June 24, 2018	Approved
Sonarr 2.0.0.5225	392	Tuesday, June 19, 2018	Approved
Sonarr 2.0.0.5163	606	Sunday, March 18, 2018	Approved
Sonarr 2.0.0.5153	437	Thursday, March 1, 2018	Approved
Sonarr 2.0.0.5085	503	Wednesday, December 13, 2017	Approved
Sonarr 2.0.0.5054	522	Monday, November 27, 2017	Approved
sonarr 2.0.0.4689	804	Thursday, April 6, 2017	Approved
sonarr 2.0.0.4645	475	Wednesday, March 8, 2017	Approved
sonarr 2.0.0.4613	502	Tuesday, February 21, 2017	Approved
sonarr 2.0.0.4472	442	Sunday, January 22, 2017	Approved
sonarr 2.0.0.4389	544	Tuesday, November 8, 2016	Approved
sonarr 2.0.0.4374	425	Thursday, November 3, 2016	Approved
sonarr 2.0.0.4326	497	Thursday, October 20, 2016	Approved
sonarr 2.0.0.4146	542	Thursday, May 12, 2016	Approved
sonarr 2.0.0.3953	452	Saturday, March 12, 2016	Approved
sonarr 2.0.0.3934	417	Tuesday, March 8, 2016	Approved
sonarr 2.0.0.3732	379	Sunday, February 21, 2016	Approved

Release Notes

Program

Changelog

Package

Automatically built and uploaded by JourneyOver

Dependencies

- dotnet4.6.1 (≥ 4.6.01055.20170308)

Discussion for the Sonarr Package

Ground Rules:

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

98,521

205

21 Feb 2019

Sonarr

Sonarr 3.0.1.374-phantom

Some Checks Are Exempted or Have Failed

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

Features

Community

Notes

Program

Package

Ground Rules: