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

225,985

Downloads of v 1.19.77.20160315:

520

Last Update:

15 Mar 2016

Package Maintainer(s):

Pauby

Software Author(s):

Nir Sofer

Tags:

nirsoft launcher updater suite admin utility tools

NirLauncher

This is not the latest version of NirLauncher available.

1.19.77.20160315 | Updated: 15 Mar 2016

Downloads:

225,985

Downloads of v 1.19.77.20160315:

520

Maintainer(s):

Pauby

Software Author(s):

Nir Sofer

Tags:

nirsoft launcher updater suite admin utility tools

NirLauncher 1.19.77.20160315

This is not the latest version of NirLauncher available.

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

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Hide Checks

Validation Testing Passed

Verification Testing Passed

Details

Scan Testing Resulted in Flagged:

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 NirLauncher, run the following command from the command line or from PowerShell:

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

To uninstall NirLauncher, 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 nirlauncher --internalize --version=1.19.77.20160315 --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 nirlauncher -y --source="'INTERNAL REPO URL'" --version="'1.19.77.20160315'" [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 nirlauncher -y --source="'INTERNAL REPO URL'" --version="'1.19.77.20160315'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode


- name: Install nirlauncher
  win_chocolatey:
    name: nirlauncher
    version: '1.19.77.20160315'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'nirlauncher' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '1.19.77.20160315'
end

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


cChocoPackageInstaller nirlauncher
{
    Name     = "nirlauncher"
    Version  = "1.19.77.20160315"
    Source   = "INTERNAL REPO URL"
}

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


package { 'nirlauncher':
  ensure   => '1.19.77.20160315',
  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 15 Mar 2016.

Description

NirLauncher is a package of more than 180 portable freeware utilities for Windows, all of them developed for NirSoft Web site during the last few years.

Screenshots
List of included utilities

Features

NirLauncher can be used from USB flash drive without need of any installation.
NirLauncher and all the utilities in the package are completely freeware, without any Spyware/Adware/Malware. This package doesn't contain any 3-party software, toolbars, Web browser plugins, or other unwanted surprises. It will not install any software on your system and it will not change your Web browser homepage or other settings on your system.
NirLauncher package includes variety of tools that you may need for your daily computer use, including utilities to recover lost passwords, to monitor your network, to view and extract cookies, cache, and other information stored by your Web browser, to search files in your system, and more...
For every utility in the package, you can easily run it, view the help file, or jump to the Web page of the utility.
When using it from USB flash drive, the configuration of every utility is saved into .cfg file on the flash drive.
On x64 systems, NirLauncher automatically run the x64 version of the utility, when there is a separated x64 version.
NirLauncher also allows to add more software packages in additional to the main NirSoft package.
NirLauncher allows you generate plugin files for BartPE (Launcher -> Generate BartPE Plugin Files), so you can easily use the utilities of NirSoft from a bootable live windows CD.

Known issues

Old Nirsoft utilities: The scripts of NirLauncher automatically take only utilities that have been updated since 01/10/2007. This means that some of the very old utilities of NirSoft are not included in this package. This restriction was added in order to avoid from including obsolete utilities that are not fully portable and may write their settings to the Registry.
False Positives: Many Antivirus programs display false alerts, saying that the password-recovery utilities of NirSoft are infected with Trojan/Virus/Malware; more info.
Reporting false alerts: If your Antivirus software shows a false alert, you can use the following article that explains how to send a report about a false positive issue to your Antivirus company: How to Report False Positives to Antivirus Vendors

Files

tools\chocolateyInstall.ps1

$packageName = 'nirlauncher'
$url = 'http://download.nirsoft.net/nirsoft_package_1.19.77.zip'
$checksum = 'f2209dad593879e7906db7adeba7448995a5a6c8'
$checksumType = 'sha1'
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$installFile = Join-Path $toolsDir "$($packageName).exe"

$chocTempDir = Join-Path $Env:Temp "chocolatey"
$tempDir = Join-Path $chocTempDir "$packageName"
if (![System.IO.Directory]::Exists($tempDir)) {[System.IO.Directory]::CreateDirectory($tempDir)}
$zipFile = Join-Path $tempDir "$($packageName).zip"

$referer = "http://launcher.nirsoft.net/download.html"
$wc = New-Object System.Net.WebClient
$wc.Headers.Add("Referer", $referer)
$wc.DownloadFile($url, $zipFile)

Get-ChecksumValid -File "$zipFile" `
                  -Checksum "$checksum" `
                  -ChecksumType "$checksumType"

Get-ChocolateyUnzip -FileFullPath "$zipFile" `
                    -Destination "$toolsDir" `
                    -PackageName "$packageName"

Set-Content -Path ("$installFile.gui") `
            -Value $null

Virus Scan Results

dialupass.exe (cc6c106b5b0c) - ## / 56
vncpassview.exe (816d76162389) - ## / 72
operapassview.exe (8e4b218bdbd8) - ## / 71
rdpv.exe (205818e10c13) - ## / 72
pstpassword.exe (94ff8fb29b20) - ## / 56
mspass.exe (7a313840d25a) - ## / 72
iepv.exe (31600e06ab7e) - ## / 55
driverview.exe (103a608c796d) - ## / 72
driverview.exe (d2140501eb3a) - ## / 73
livecontactsview.exe (62160c59d186) - ## / 73
lsasecretsdump.exe (ab176354b7b8) - ## / 72
lsasecretsdump.exe (2a871c1837d5) - ## / 72
lsasecretsview.exe (c484d47ee62d) - ## / 54
lsasecretsview.exe (8bab693de34e) - ## / 54
netpass.exe (ee0b88b252fc) - ## / 54
netpass.exe (c1c4953d9203) - ## / 54
officeins.exe (a9440c1eb0fe) - ## / 56
officeins.exe (6845e843f392) - ## / 73
passwordfox.exe (2b73ce10aa42) - ## / 52
passwordfox.exe (60da3148fc16) - ## / 54
shmnview.exe (c717a6b32b6d) - ## / 53
shmnview.exe (9b0fbba33f95) - ## / 55
sniffpass.exe (c92580318be4) - ## / 72
sniffpass.exe (1e13fd79ad54) - ## / 72
tcplogview.exe (f17276d111f5) - ## / 57
tcplogview.exe (beb94fa83f7f) - ## / 54
userprofilesview.exe (0b9c04da6fb9) - ## / 71
wirelessconnectioninfo.exe (1cc0c8c79ffd) - ## / 56
mailpv.exe (110bd48f6b14) - ## / 55
openedfilesview.exe (44e225741b3c) - ## / 54
openedfilesview.exe (c950d4e572de) - ## / 56
executedprogramslist.exe (771f8da1f0c4) - ## / 55
passwordscan.exe (93188922c20a) - ## / 57
opensavefilesview.exe (c4ad87c06585) - ## / 57
opensavefilesview.exe (e17a174feb49) - ## / 57
networklatencyview.exe (f0b79133cb42) - ## / 57
networklatencyview.exe (5b588316f2ef) - ## / 57
quicksetdns.exe (c4f50950903b) - ## / 67
chromecookiesview.exe (4c502f590cf5) - ## / 53
wirelesskeyview.exe (56e2c58b56c7) - ## / 56
wirelesskeyview.exe (221a30378e79) - ## / 56
networktrafficview.exe (a48259c7f287) - ## / 55
networktrafficview.exe (fa0e0df55ee5) - ## / 56
dumpedid.exe (3a54cfe0abba) - ## / 55
winlogonview.exe (814aa262384b) - ## / 56
gdiview.exe (bfc52cc56c57) - ## / 56
gdiview.exe (ec185428089f) - ## / 57
webcookiessniffer.exe (d7c079a479f3) - ## / 55
webcookiessniffer.exe (04ba3171144c) - ## / 57
bulkfilechanger.exe (385b26e8efe1) - ## / 55
bulkfilechanger.exe (6b86e7ba04eb) - ## / 56
httpnetworksniffer.exe (a86af11ae59d) - ## / 57
httpnetworksniffer.exe (68502746a07f) - ## / 56
chromecacheview.exe (38496a896798) - ## / 55
webbrowserpassview.exe (269c04554e95) - ## / 56
routerpassview.exe (8137d32289c1) - ## / 56
chromepass.exe (6e1011366ab2) - ## / 57
NirLauncher.exe (b2d7c67bc796) - ## / 54
alternatestreamview.exe (53ce862f73fe) - ## / 44
altstreamdump.exe (54939b60003d) - ## / 74
appcrashview.exe (097fe6029108) - ## / 65
awatch.exe (556124fe0767) - ## / 71
axhelper.exe (22279965263d) - ## / 69
batteryinfoview.exe (08ef9887b018) - ## / 64
bluescreenview.exe (f5f52ec9c38e) - ## / 71
bluetoothcl.exe (cb98e5060dcf) - ## / 70
bluetoothlogview.exe (2f53bf7b2b44) - ## / 57
bluetoothview.exe (6a1ccee35e0a) - ## / 74
browseraddonsview.exe (f34f2dd615bd) - ## / 57
browsinghistoryview.exe (79f3fd003d44) - ## / 56
bulletspassview.exe (b19dfe440e51) - ## / 72
chromehistoryview.exe (12a6da786a2d) - ## / 56
cleanafterme.exe (9eccb72f6129) - ## / 67
clipboardic.exe (4d6190558c83) - ## / 56
countrytraceroute.exe (e9fd582e3592) - ## / 56
cports.exe (7a14e2c130f1) - ## / 55
cprocess.exe (f0cf25602f19) - ## / 70
csvfileview.exe (012807bc65b1) - ## / 57
ctie.exe (5b903d6efc2e) - ## / 71
customexplorertoolbar.exe (9d42469f4691) - ## / 73
deviceioview.exe (feaa890d1850) - ## / 56
diskcountersview.exe (a73472247b5d) - ## / 57
disksmartview.exe (ea9cc7e7037b) - ## / 57
dllexp.exe (1900206940c2) - ## / 55
dnsdataview.exe (3791cc0af40b) - ## / 57
dnsquerysniffer.exe (91bb6ea0123d) - ## / 57
domainhostingview.exe (78f7a2306def) - ## / 57
dotnetresourcesextract.exe (381bfc1b1b50) - ## / 49
downtester.exe (74c2aa066141) - ## / 71
esedatabaseview.exe (87b63fd04b2d) - ## / 56
eventlogsourcesview.exe (22a7eb0b912b) - ## / 74
exifdataview.exe (060c65db6cef) - ## / 72
fastresolver.exe (1fcfc602fb5c) - ## / 71
faview.exe (a68fae179a57) - ## / 69
fbcacheview.exe (f2ef2871c11e) - ## / 57
filetypesman.exe (2c7673f4116e) - ## / 67
firefoxdownloadsview.exe (53ff753b1cce) - ## / 68
firmwaretablesview.exe (ee01b39d8788) - ## / 67
flashcookiesview.exe (e9f9bea54333) - ## / 73
folderchangesview.exe (d268f433aa21) - ## / 57
foldertimeupdate.exe (156bc9004be9) - ## / 56
hashmyfiles.exe (a8cc125bc1a4) - ## / 56
heapmemview.exe (1296d8731ad8) - ## / 73
hotkeyslist.exe (327c57918a77) - ## / 70
htmlastext.exe (42624eb45a96) - ## / 70
htmldocedit.exe (a8ab1365b04a) - ## / 71
iconsext.exe (e22afd680ce7) - ## / 70
iecacheview.exe (79aa56144a3b) - ## / 56
iecv.exe (cd907a607937) - ## / 53
iehv.exe (d46f1a4ab60e) - ## / 72
imagecacheviewer.exe (550c050346fd) - ## / 57
insideclipboard.exe (5d74fc85f0a9) - ## / 56
installedcodec.exe (ca54c5bda1ce) - ## / 73
installeddriverslist.exe (3bca36911305) - ## / 73
ipinfooffline.exe (8293c4d4a906) - ## / 57
ipnetinfo.exe (6845ff54f75e) - ## / 56
jumplistsview.exe (c86379431d4b) - ## / 56
lastactivityview.exe (6912adcb6b84) - ## / 56
macaddressview.exe (00c1155a436a) - ## / 56
mmcsnapinsview.exe (8026dcd96e0a) - ## / 74
monitorinfoview.exe (0395d0a47cc1) - ## / 69
mozillacacheview.exe (d22341669998) - ## / 64
mozillahistoryview.exe (99558d03fe59) - ## / 56
muicacheview.exe (02e28fa84912) - ## / 71
multimonitortool.exe (30c9238db57a) - ## / 56
mweather.exe (2892cc50b8de) - ## / 56
myeventviewer.exe (6ddb8ceb7167) - ## / 57
mylastsearch.exe (188bbf95fa79) - ## / 65
myuninst.exe (995eed6c555d) - ## / 51
mzcv.exe (1bc5481a096d) - ## / 57
netbscanner.exe (1a26f80ac2bb) - ## / 55
netconnectchoose.exe (178fdde88539) - ## / 71
netresview.exe (83f0352c14fa) - ## / 71
netrouteview.exe (91041b616969) - ## / 72
networkconnectlog.exe (6c7748951d4f) - ## / 57
networkinterfacesview.exe (a2fef2bc62e8) - ## / 68
nircmd.exe (379ea62a6c7a) - ## / 56
nircmdc.exe (6bea8acac681) - ## / 57
nk2edit.exe (55e1cb9929d1) - ## / 56
ntfslinksview.exe (7dc266fa295c) - ## / 57
openwithview.exe (6358b2d02131) - ## / 71
operacacheview.exe (3102c6953187) - ## / 68
outlookattachview.exe (3fccb2c8c5c3) - ## / 57
outlookstatview.exe (1bae0253f075) - ## / 57
pcanypass.exe (0db918e61645) - ## / 72
pinginfoview.exe (4c975c594a4e) - ## / 55
processactivityview.exe (b918db8655b5) - ## / 70
processthreadsview.exe (1c65d3abbebf) - ## / 57
produkey.exe (7088e86f4e70) - ## / 56
recentfilesview.exe (177908fc0051) - ## / 57
regdllview.exe (9938f8bcc502) - ## / 72
RegFileExport.exe (6f159e7e1f75) - ## / 62
regfromapp.exe (2a1a4ec3b52b) - ## / 72
regscanner.exe (93bd9235d348) - ## / 56
resourcesextract.exe (c9b93aa5d45f) - ## / 71
rtmpdumphelper.dll (daf438351674) - ## / 66
rtmpdumphelper.exe (e41ef53a0ed6) - ## / 67
runasdate.exe (12fd2d78bfdd) - ## / 54
runfromprocess.exe (e084933319b9) - ## / 72
safaricacheview.exe (bd8a13430ace) - ## / 74
safarihistoryview.exe (231fd04cbe98) - ## / 75
searchfilterview.exe (0749e8e0b169) - ## / 72
searchmyfiles.exe (0c1688504c59) - ## / 56
securitysoftview.exe (a54e3494461d) - ## / 73
seqdownload.exe (e09d4a718e26) - ## / 71
serviwin.exe (f088ee16e262) - ## / 57
shellbagsview.exe (19640bddc061) - ## / 66
shellmenunew.exe (c47485958a03) - ## / 71
shexview.exe (f74416aab0a4) - ## / 68
shman.exe (82c6e2c666a5) - ## / 72
simpleprogramdebugger.exe (a5709320a88f) - ## / 56
siteshoter.exe (eefdef80e5a5) - ## / 70
skypecontactsview.exe (6bafeab61149) - ## / 72
skypelogview.exe (b2af144ca1c3) - ## / 71
smsniff.exe (c11ede59bb98) - ## / 55
socketsniff.exe (ecb44a44ff92) - ## / 71
soundvolumeview.exe (9215d6407470) - ## / 57
specialfoldersview.exe (315fdb91b17d) - ## / 72
sysexp.exe (97fb23afac56) - ## / 57
tabletextcompare.exe (44109d47dffb) - ## / 57
turnedontimesview.exe (38a66cf50b35) - ## / 56
urlprotocolview.exe (34cbe52cc935) - ## / 70
urlstringgrabber.exe (e4a17446c490) - ## / 57
usbdeview.exe (ac534c09f6a9) - ## / 55
usblogview.exe (150ee484165f) - ## / 57
userassistview.exe (bc11c4150bbc) - ## / 69
videocacheview.exe (7567d411747a) - ## / 57
vlmshlp32.dll (2f32e2aed465) - ## / 71
volumouse.exe (92b3d1c7dd4b) - ## / 68
wakemeonlan.exe (72f783739791) - ## / 57
webcacheimageinfo.exe (ab6fa914ba18) - ## / 57
webcamimagesave.exe (5e3f311ae67f) - ## / 72
websitesniffer.exe (4fa71557cec8) - ## / 57
webvideocap.exe (266283fce7ef) - ## / 71
whatinstartup.exe (7d8e7090d530) - ## / 69
whatishang.exe (fc4e9f5abccf) - ## / 70
whoiscl.exe (85a056ace382) - ## / 57
whoisconnectedsniffer.exe (77af9bcafeb3) - ## / 57
whoistd.exe (9bb50c971498) - ## / 57
whosip.exe (444bb858d3c1) - ## / 57
wifichannelmonitor.exe (2598e359d8f4) - ## / 57
wifihistoryview.exe (781e9986a2e5) - ## / 57
wifiinfoview.exe (b775645454cf) - ## / 55
wincrashreport.exe (2e3c5c011166) - ## / 55
winfontsview.exe (1e25fa572959) - ## / 72
winlister.exe (86e17cf544d0) - ## / 56
winprefetchview.exe (1be46efa4960) - ## / 68
winsockservicesview.exe (7abaa3b7753d) - ## / 74
wirelesskeydump.exe (7056c1f58eac) - ## / 68
wirelessnetconsole.exe (49279441e70a) - ## / 71
wirelessnetview.exe (ec5fa512c1d4) - ## / 56
wnetwatcher.exe (2e158c781064) - ## / 56
wul.exe (b95d23652c3a) - ## / 55
alternatestreamview.exe (02238b150b15) - ## / 57
bluescreenview.exe (09f3023554be) - ## / 72
browseraddonsview.exe (69312587ca0d) - ## / 56
browsinghistoryview.exe (5ec558ab602c) - ## / 56
bulletspassview.exe (e71cda5e7c01) - ## / 72
cports.exe (69b9b67876a1) - ## / 56
csvfileview.exe (aaf7f00dc4df) - ## / 57
deviceioview.exe (257c50c0d02c) - ## / 56
dllexp.exe (54589698c1af) - ## / 55
dnsquerysniffer.exe (7c0cf3cace43) - ## / 57
eventlogsourcesview.exe (fb821854d62b) - ## / 72
filetypesman.exe (fa7cc2f9c3e6) - ## / 67
firmwaretablesview.exe (af43c56b754a) - ## / 66
foldertimeupdate.exe (f55f0674151d) - ## / 55
hashmyfiles.exe (7f65e32b7b94) - ## / 56
heapmemview.exe (4ceb3cadc9ab) - ## / 73
installedcodec.exe (d194ddb62b97) - ## / 72
installeddriverslist.exe (583eaf01e0ba) - ## / 74
mmcsnapinsview.exe (fd769b5b165c) - ## / 73
multimonitortool.exe (31827db6070e) - ## / 44
myeventviewer.exe (58dcc856b928) - ## / 56
networkinterfacesview.exe (5e04d1cb02a2) - ## / 68
nircmd.exe (b4f05627d196) - ## / 56
nircmdc.exe (c27a7472bd7d) - ## / 57
nk2edit.exe (d39ea5516d86) - ## / 54
ntfslinksview.exe (6fee63b323ed) - ## / 56
outlookattachview.exe (eccb79f9bccd) - ## / 54
outlookstatview.exe (3c299b0a01fe) - ## / 55
processactivityview.exe (5709f63fbc11) - ## / 71
processthreadsview.exe (24ab414d8e34) - ## / 57
produkey.exe (e3e1a754ff5a) - ## / 56
regdllview.exe (52d52b59561c) - ## / 73
regfromapp.exe (a74583103234) - ## / 73
regscanner.exe (16e2f962ef25) - ## / 57
resourcesextract.exe (a718da8b2a11) - ## / 72
rtmpdumphelper.dll (f7715a862f5e) - ## / 67
rtmpdumphelper.exe (db46be6af7e1) - ## / 67
runasdate.exe (7e8a3fa63049) - ## / 53
runfromprocess.exe (0be466ef7607) - ## / 73
searchmyfiles.exe (f94891059a6c) - ## / 58
serviwin.exe (86d8f63868b5) - ## / 55
shexview.exe (8f771238a97b) - ## / 69
shman.exe (e15f5060b60e) - ## / 72
simpleprogramdebugger.exe (861de48e15b8) - ## / 57
smsniff.exe (bc01b97142ef) - ## / 56
soundvolumeview.exe (4b5acf6f8bc6) - ## / 57
specialfoldersview.exe (9911e0e65221) - ## / 74
sysexp.exe (76ef7af61e46) - ## / 57
usbdeview.exe (6706dbaf7a45) - ## / 56
videocacheview.exe (64eaad76237b) - ## / 56
vlmshlp.dll (32ad4153f601) - ## / 73
volumouse.exe (29ad9108c2fc) - ## / 68
volumouse32.exe (02448530591c) - ## / 72
websitesniffer.exe (6c1c55dcde7e) - ## / 54
whatinstartup.exe (15099976118e) - ## / 72
whatishang.exe (e2095dbe5ff7) - ## / 72
whoisconnectedsniffer.exe (3d34a5710636) - ## / 56
wifichannelmonitor.exe (5dcb02f83dcc) - ## / 57
wincrashreport.exe (6b10fe60cabc) - ## / 55
winlister.exe (1bdc54f24679) - ## / 57
winprefetchview.exe (2d54f8c752cd) - ## / 68
wirelesskeydump.exe (dc6dab07642b) - ## / 68
advancedrun.exe (bb4cd3c88a52) - ## / 57
devmanview.exe (008230ef2763) - ## / 67
driveletterview.exe (3313fea6c499) - ## / 57
networkopenedfiles.exe (dfa11f5c6ca6) - ## / 57
outlookaddressbookview.exe (4854f1b30383) - ## / 57
simplewmiview.exe (2b710e7ba8d1) - ## / 57
taskschedulerview.exe (9fe87c398070) - ## / 57
advancedrun.exe (7ae0a93d5dc7) - ## / 57
devmanview.exe (b43b9fd68309) - ## / 66
networkopenedfiles.exe (8c7a5b76f91d) - ## / 57
outlookaddressbookview.exe (2f10b3a4ff5e) - ## / 57
taskschedulerview.exe (09c8a8bf0c92) - ## / 57
nirlauncher.1.19.77.20160315.nupkg (f019c9778a56) - ## / 57

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
NirLauncher 1.30.5	14948	Saturday, August 26, 2023	Exempted
NirLauncher 1.30.4	1719	Tuesday, August 1, 2023	Exempted
NirLauncher 1.30.3	2441	Thursday, June 22, 2023	Exempted
NirLauncher 1.30.2	3200	Monday, May 1, 2023	Exempted
NirLauncher 1.23.66	8532	Monday, November 7, 2022	Exempted
NirLauncher 1.23.65	520	Sunday, October 16, 2022	Exempted
NirLauncher 1.23.56	11851	Monday, January 17, 2022	Exempted
NirLauncher 1.23.53	5521	Tuesday, October 26, 2021	Exempted
NirLauncher 1.23.52	135	Tuesday, October 5, 2021	Exempted
NirLauncher 1.23.44	8116	Tuesday, April 27, 2021	Approved
NirLauncher 1.23.43	1846	Tuesday, April 6, 2021	Approved
NirLauncher 1.23.42	1605	Tuesday, March 23, 2021	Approved
NirLauncher 1.23.41	1665	Tuesday, March 9, 2021	Approved
NirLauncher 1.23.40	1575	Tuesday, February 23, 2021	Approved
NirLauncher 1.23.39	1560	Tuesday, February 9, 2021	Approved
NirLauncher 1.23.38	1651	Tuesday, January 26, 2021	Approved
NirLauncher 1.23.37	1848	Tuesday, January 12, 2021	Approved
NirLauncher 1.23.36	3455	Tuesday, December 8, 2020	Approved
NirLauncher 1.23.35	2668	Tuesday, November 10, 2020	Approved
NirLauncher 1.23.34	1829	Tuesday, October 27, 2020	Approved
NirLauncher 1.23.33	1744	Tuesday, October 13, 2020	Approved
NirLauncher 1.23.32	1754	Tuesday, September 29, 2020	Approved
NirLauncher 1.23.31	1797	Tuesday, September 15, 2020	Approved
NirLauncher 1.23.30	1645	Tuesday, September 1, 2020	Approved
NirLauncher 1.23.28	2402	Tuesday, August 4, 2020	Approved
NirLauncher 1.23.27	1733	Monday, July 20, 2020	Approved
NirLauncher 1.23.26	165	Tuesday, July 7, 2020	Approved
NirLauncher 1.23.25	2293	Tuesday, June 23, 2020	Approved
NirLauncher 1.23.24	1725	Tuesday, June 9, 2020	Approved
NirLauncher 1.23.23	1082	Monday, June 1, 2020	Approved
NirLauncher 1.23.22	1497	Monday, May 18, 2020	Approved
NirLauncher 1.23.21	1220	Tuesday, May 12, 2020	Approved
NirLauncher 1.23.20	1128	Tuesday, May 5, 2020	Approved
NirLauncher 1.23.19	1111	Tuesday, April 28, 2020	Approved
NirLauncher 1.23.18	1761	Tuesday, April 14, 2020	Approved
NirLauncher 1.23.17	1710	Tuesday, March 31, 2020	Approved
NirLauncher 1.23.15	2565	Tuesday, March 3, 2020	Approved
NirLauncher 1.23.14	833	Tuesday, February 18, 2020	Approved
NirLauncher 1.23.13	773	Tuesday, February 11, 2020	Approved
NirLauncher 1.23.12	704	Tuesday, February 4, 2020	Approved
NirLauncher 1.23.11	639	Tuesday, January 28, 2020	Approved
NirLauncher 1.23.10	893	Tuesday, January 14, 2020	Approved
NirLauncher 1.23.9	833	Tuesday, December 31, 2019	Approved
NirLauncher 1.23.8	817	Tuesday, December 17, 2019	Approved
NirLauncher 1.23.7	834	Tuesday, December 3, 2019	Approved
NirLauncher 1.23.6	733	Monday, November 25, 2019	Approved
NirLauncher 1.23.5	712	Tuesday, November 19, 2019	Approved
NirLauncher 1.23.4	739	Tuesday, November 12, 2019	Approved
NirLauncher 1.23.3	657	Tuesday, November 5, 2019	Approved
NirLauncher 1.23.2	734	Tuesday, October 29, 2019	Approved
NirLauncher 1.23.1	892	Monday, October 14, 2019	Approved
NirLauncher 1.22.24	759	Monday, October 7, 2019	Approved
NirLauncher 1.22.23	627	Tuesday, October 1, 2019	Approved
NirLauncher 1.22.22	1003	Thursday, September 12, 2019	Approved
NirLauncher 1.22.21	1000	Tuesday, August 27, 2019	Approved
NirLauncher 1.22.20	924	Tuesday, August 6, 2019	Approved
NirLauncher 1.22.19	574	Tuesday, July 30, 2019	Approved
NirLauncher 1.22.18	597	Monday, July 22, 2019	Approved
NirLauncher 1.22.17	595	Tuesday, July 16, 2019	Approved
NirLauncher 1.22.16	612	Tuesday, July 9, 2019	Approved
NirLauncher 1.22.15	687	Tuesday, July 2, 2019	Approved
NirLauncher 1.22.14	610	Tuesday, June 25, 2019	Approved
NirLauncher 1.22.13	667	Tuesday, June 18, 2019	Approved
NirLauncher 1.22.12	613	Monday, June 10, 2019	Approved
NirLauncher 1.22.11	633	Tuesday, June 4, 2019	Approved
NirLauncher 1.22.10	572	Monday, May 27, 2019	Approved
NirLauncher 1.22.9	618	Monday, May 20, 2019	Approved
NirLauncher 1.22.8	591	Tuesday, May 14, 2019	Approved
NirLauncher 1.22.7	565	Tuesday, May 7, 2019	Approved
NirLauncher 1.22.6	571	Wednesday, May 1, 2019	Approved
NirLauncher 1.22.5	708	Tuesday, April 23, 2019	Approved
NirLauncher 1.22.4	663	Tuesday, April 16, 2019	Approved
NirLauncher 1.22.3	606	Thursday, April 11, 2019	Approved
NirLauncher 1.22.2	738	Tuesday, April 2, 2019	Approved
NirLauncher 1.22.1	691	Tuesday, March 26, 2019	Approved
NirLauncher 1.21.2	647	Wednesday, March 20, 2019	Approved
NirLauncher 1.20.76	796	Monday, March 11, 2019	Approved
NirLauncher 1.20.75	840	Tuesday, February 26, 2019	Approved
NirLauncher 1.20.74	738	Monday, February 18, 2019	Approved
NirLauncher 1.20.73	642	Tuesday, February 12, 2019	Approved
NirLauncher 1.20.72	664	Monday, February 4, 2019	Approved
NirLauncher 1.20.71	628	Wednesday, January 30, 2019	Approved
NirLauncher 1.20.70	717	Monday, January 21, 2019	Approved
NirLauncher 1.20.69	597	Wednesday, January 16, 2019	Approved
NirLauncher 1.20.68	629	Tuesday, January 8, 2019	Approved
NirLauncher 1.20.67	659	Tuesday, January 1, 2019	Approved
NirLauncher 1.20.66	615	Wednesday, December 26, 2018	Approved
NirLauncher 1.20.65	642	Wednesday, December 19, 2018	Approved
NirLauncher 1.20.64	751	Tuesday, December 11, 2018	Approved
NirLauncher 1.20.63	764	Tuesday, December 4, 2018	Approved
NirLauncher 1.20.62	621	Tuesday, November 27, 2018	Approved
NirLauncher 1.20.61	647	Monday, November 19, 2018	Approved
NirLauncher 1.20.60	619	Tuesday, November 13, 2018	Approved
NirLauncher 1.20.58	786	Tuesday, October 30, 2018	Approved
NirLauncher 1.20.57	803	Tuesday, October 16, 2018	Approved
NirLauncher 1.20.56	653	Tuesday, October 9, 2018	Approved
NirLauncher 1.20.55	625	Tuesday, October 2, 2018	Approved
NirLauncher 1.20.54	619	Tuesday, September 25, 2018	Approved
NirLauncher 1.20.53	623	Tuesday, September 18, 2018	Approved
NirLauncher 1.20.52	670	Tuesday, September 11, 2018	Approved
NirLauncher 1.20.51	627	Tuesday, September 4, 2018	Approved
NirLauncher 1.20.50	669	Monday, August 27, 2018	Approved
NirLauncher 1.20.49	614	Tuesday, August 21, 2018	Approved
NirLauncher 1.20.48	605	Tuesday, August 14, 2018	Approved
NirLauncher 1.20.47	923	Tuesday, July 31, 2018	Approved
NirLauncher 1.20.46	706	Tuesday, July 24, 2018	Approved
NirLauncher 1.20.45	778	Tuesday, July 10, 2018	Approved
NirLauncher 1.20.44	707	Tuesday, July 3, 2018	Approved
NirLauncher 1.20.43	597	Tuesday, June 26, 2018	Approved
NirLauncher 1.20.42	685	Tuesday, June 19, 2018	Approved
NirLauncher 1.20.41	648	Tuesday, June 12, 2018	Approved
NirLauncher 1.20.40	725	Tuesday, June 5, 2018	Approved
NirLauncher 1.20.39	807	Monday, May 21, 2018	Approved
NirLauncher 1.20.38	815	Tuesday, May 8, 2018	Approved
NirLauncher 1.20.37	723	Wednesday, April 25, 2018	Approved
NirLauncher 1.20.36	644	Tuesday, April 17, 2018	Approved
NirLauncher 1.20.35	947	Tuesday, April 3, 2018	Approved
NirLauncher 1.20.34	661	Monday, March 26, 2018	Approved
NirLauncher 1.20.33	765	Monday, March 19, 2018	Approved
NirLauncher 1.20.32	672	Tuesday, March 13, 2018	Approved
NirLauncher 1.20.31	570	Saturday, March 10, 2018	Approved
NirLauncher 1.20.27	1228	Sunday, January 21, 2018	Approved
NirLauncher 1.20.26	725	Tuesday, January 9, 2018	Approved
NirLauncher 1.20.25	655	Tuesday, January 2, 2018	Approved
NirLauncher 1.20.24	732	Tuesday, December 19, 2017	Approved
NirLauncher 1.20.23	703	Sunday, December 10, 2017	Approved
NirLauncher 1.20.22	590	Monday, December 4, 2017	Approved
NirLauncher 1.20.21	608	Tuesday, November 28, 2017	Approved
NirLauncher 1.20.20	718	Monday, November 20, 2017	Approved
NirLauncher 1.20.19	756	Tuesday, November 7, 2017	Approved
NirLauncher 1.20.18	640	Tuesday, October 31, 2017	Approved
NirLauncher 1.20.17	683	Monday, October 23, 2017	Approved
NirLauncher 1.20.16	680	Monday, October 16, 2017	Approved
NirLauncher 1.20.15	650	Sunday, October 8, 2017	Approved
NirLauncher 1.20.14	537	Thursday, October 5, 2017	Approved
NirLauncher 1.20.12	985	Monday, August 28, 2017	Approved
NirLauncher 1.20.11	686	Monday, August 14, 2017	Approved
NirLauncher 1.20.10	685	Monday, July 31, 2017	Approved
NirLauncher 1.20.9	599	Monday, July 24, 2017	Approved
NirLauncher 1.20.8	628	Monday, July 17, 2017	Approved
NirLauncher 1.20.7	619	Wednesday, July 5, 2017	Approved
NirLauncher 1.20.6	625	Monday, June 26, 2017	Approved
NirLauncher 1.20.5	675	Tuesday, June 13, 2017	Approved
NirLauncher 1.20.4	610	Monday, June 5, 2017	Approved
NirLauncher 1.20.3	589	Tuesday, May 30, 2017	Approved
NirLauncher 1.20.2	760	Monday, May 22, 2017	Approved
NirLauncher 1.20.1	619	Sunday, May 14, 2017	Approved
NirLauncher 1.19.121	635	Monday, May 8, 2017	Approved
NirLauncher 1.19.120	646	Sunday, April 23, 2017	Approved
NirLauncher 1.19.119	679	Sunday, April 9, 2017	Approved
NirLauncher 1.19.118	829	Saturday, March 11, 2017	Approved
NirLauncher 1.19.117	829	Sunday, February 19, 2017	Approved
NirLauncher 1.19.116	717	Tuesday, January 31, 2017	Approved
NirLauncher 1.19.115	633	Sunday, January 15, 2017	Approved
NirLauncher 1.19.114	697	Sunday, January 1, 2017	Approved
NirLauncher 1.19.113	672	Sunday, December 18, 2016	Approved
NirLauncher 1.19.112	653	Monday, December 5, 2016	Approved
NirLauncher 1.19.111	566	Thursday, November 24, 2016	Approved
NirLauncher 1.19.110	707	Tuesday, November 8, 2016	Approved
NirLauncher 1.19.109	514	Tuesday, November 1, 2016	Approved
NirLauncher 1.19.108	633	Tuesday, October 25, 2016	Approved
NirLauncher 1.19.107	556	Wednesday, October 19, 2016	Approved
NirLauncher 1.19.106	574	Tuesday, October 11, 2016	Approved
NirLauncher 1.19.105	490	Friday, October 7, 2016	Approved
NirLauncher 1.19.92	842	Tuesday, July 5, 2016	Approved
NirLauncher 1.19.91	430	Tuesday, June 21, 2016	Approved
NirLauncher 1.19.90	431	Monday, June 13, 2016	Approved
NirLauncher 1.19.89	450	Tuesday, June 7, 2016	Approved
NirLauncher 1.19.88	395	Tuesday, May 31, 2016	Approved
NirLauncher 1.19.87	381	Saturday, May 28, 2016	Approved
NirLauncher 1.19.86	339	Monday, May 16, 2016	Approved
NirLauncher 1.19.85	398	Monday, May 9, 2016	Approved
NirLauncher 1.19.84	465	Monday, May 2, 2016	Approved
NirLauncher 1.19.83	471	Monday, April 25, 2016	Approved
NirLauncher 1.19.82	503	Monday, April 18, 2016	Approved
NirLauncher 1.19.81	526	Tuesday, April 12, 2016	Approved
NirLauncher 1.19.80	436	Monday, April 11, 2016	Approved
NirLauncher 1.19.79.20160331	543	Thursday, March 31, 2016	Approved
NirLauncher 1.19.79	444	Thursday, March 31, 2016	Approved
NirLauncher 1.19.78	517	Tuesday, March 22, 2016	Approved
NirLauncher 1.19.77.20160315	520	Tuesday, March 15, 2016	Approved
NirLauncher 1.19.76	540	Monday, March 7, 2016	Approved
NirLauncher 1.19.75	519	Monday, February 29, 2016	Approved
NirLauncher 1.19.74	584	Tuesday, February 23, 2016	Approved
NirLauncher 1.19.73	515	Monday, February 15, 2016	Approved
NirLauncher 1.19.72	540	Wednesday, February 10, 2016	Approved
NirLauncher 1.19.71	498	Friday, February 5, 2016	Approved
NirLauncher 1.19.70	527	Monday, February 1, 2016	Approved
NirLauncher 1.19.69	570	Tuesday, January 19, 2016	Approved
NirLauncher 1.19.68	514	Tuesday, January 12, 2016	Approved
NirLauncher 1.19.67	484	Monday, January 4, 2016	Approved
NirLauncher 1.19.66	475	Wednesday, December 30, 2015	Approved
NirLauncher 1.19.65	515	Monday, December 21, 2015	Approved
NirLauncher 1.19.64	502	Tuesday, December 15, 2015	Approved
NirLauncher 1.19.63	486	Tuesday, December 8, 2015	Approved
NirLauncher 1.19.62	511	Tuesday, December 1, 2015	Approved
NirLauncher 1.19.61	495	Monday, November 23, 2015	Approved
NirLauncher 1.19.60	509	Tuesday, November 17, 2015	Approved
NirLauncher 1.19.59	459	Monday, November 9, 2015	Approved
NirLauncher 1.19.57	583	Tuesday, October 27, 2015	Approved
NirLauncher 1.19.56	496	Tuesday, October 20, 2015	Approved
NirLauncher 1.19.55	456	Wednesday, October 14, 2015	Approved
NirLauncher 1.19.54	497	Saturday, October 10, 2015	Approved
NirLauncher 1.19.53	512	Tuesday, September 29, 2015	Approved
NirLauncher 1.19.51	479	Thursday, September 17, 2015	Approved
NirLauncher 1.19.50	528	Tuesday, September 8, 2015	Approved
NirLauncher 1.19.49	476	Tuesday, September 1, 2015	Approved
NirLauncher 1.19.48	447	Tuesday, August 25, 2015	Approved
NirLauncher 1.19.47	446	Tuesday, August 18, 2015	Approved
NirLauncher 1.19.46	461	Tuesday, August 11, 2015	Approved
NirLauncher 1.19.44	503	Tuesday, July 28, 2015	Approved
NirLauncher 1.19.43	452	Tuesday, July 21, 2015	Approved
NirLauncher 1.19.42	468	Wednesday, July 15, 2015	Approved
NirLauncher 1.19.41	501	Tuesday, July 7, 2015	Approved
NirLauncher 1.19.40	418	Wednesday, July 1, 2015	Approved
NirLauncher 1.19.39	461	Tuesday, June 23, 2015	Approved
NirLauncher 1.19.38	459	Tuesday, June 16, 2015	Approved
NirLauncher 1.19.37	428	Tuesday, June 9, 2015	Approved
NirLauncher 1.19.36	486	Tuesday, June 2, 2015	Approved
NirLauncher 1.19.34	466	Wednesday, May 20, 2015	Approved
NirLauncher 1.19.33	488	Tuesday, May 12, 2015	Approved
NirLauncher 1.19.32	414	Friday, May 8, 2015	Approved
NirLauncher 1.19.31	445	Tuesday, April 28, 2015	Approved
NirLauncher 1.19.30	475	Monday, April 27, 2015	Approved
NirLauncher 1.19.29	495	Tuesday, April 14, 2015	Approved
NirLauncher 1.19.28	452	Wednesday, April 8, 2015	Approved
NirLauncher 1.19.27	431	Thursday, April 2, 2015	Approved

Release Notes

Program

News

Package

Automatically built and uploaded by dtgm

Dependencies

This package has no dependencies.

Discussion for the NirLauncher Package

Ground Rules:

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

225,985

520

15 Mar 2016

NirLauncher

NirLauncher 1.19.77.20160315

Some Checks Have Failed or Are Not Yet Complete

Deployment Method: Individual Install, Upgrade, & Uninstall

Deployment Method:

1. Enter Your Internal Repository Url

2. Setup Your Environment

1. Ensure you are set for organizational deployment

2. Get the package into your environment

3. Copy Your Script

4. If applicable - Chocolatey configuration/installation

Features

Known issues

Program

Package

Ground Rules: