Step 1: Review Your Packages

Step 2: Choose Your Integration Method

Step 3: Copy Your Script or Download Config

Option 1: Copy Script

Option 2: Download Config

Step 4: Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

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

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

Option 2: Internalized Package (Reliable, Scalable)

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

Step 5: Copy Your Script

See options you can pass to upgrade.

See best practices for scripting.

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

### c. Other Requirements ###

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

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

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

## 2. TOP LEVEL VARIABLES ##

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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

- name: Install and Configure Chocolatey
  hosts: all

## 2. TOP LEVEL VARIABLES ##
  vars:

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

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

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

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

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

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

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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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

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

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

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

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

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

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

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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

chocolatey_feature 'useBackgroundService' do
  action :enable
end

chocolatey_feature 'useBackgroundServiceWithNonAdministratorsOnly' do
  action :enable
end

chocolatey_feature 'allowBackgroundServiceUninstallsFromUserInstallsOnly' do
  action :enable
end

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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


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

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

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

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

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


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


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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Need Help? View our docs or file an issue.

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

Current Version	New Version

Downloads:

205,475

Downloads of v 1.20.20:

672

Last Update:

20 Nov 2017

Package Maintainer(s):

majkinetor

Software Author(s):

Nir Sofer

Tags:

utility tools admin freeware system nirsoft

NirLauncher

This is not the latest version of NirLauncher available.

1.20.20 | Updated: 20 Nov 2017

Downloads:

205,475

Downloads of v 1.20.20:

672

Maintainer(s):

majkinetor

Software Author(s):

Nir Sofer

Tags:

utility tools admin freeware system nirsoft

NirLauncher 1.20.20

This is not the latest version of NirLauncher available.

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.20.20 --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.20.20'" [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.20.20'" 
$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.20.20'
    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.20.20'
end

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


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

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


package { 'nirlauncher':
  ensure   => '1.20.20',
  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.

WARNING

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

Package Approved

This package was approved as a trusted package on 20 Nov 2017.

Description

NirLauncher is a package of more than 180 portable freeware utilities for Windows, all of them developed by NirSoft.

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.

Package Parameters

/Sysinternals - Add sysinternals tools to the launcher.

Files

legal\License.txt

This utilities package is released as freeware, which means that you can freely use it at your home or in your company.
The only exception is NK2Edit utility, which requires to purchase a commercial license if you use it in a company/business organization.
Disclaimer: The software package is provided "AS IS" without any warranty, either expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The author will not be liable for any special, incidental, consequential or indirect damages due to loss of data or any other reason.

legal\redistribution.pdf

legal\VERIFICATION.txt

VERIFICATION

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

Package can be verified like this:

1. Go to http://launcher.nirsoft.net/downloads/index.html to download the zip file:

   x32: http://download.nirsoft.net/nirsoft_package_1.20.20.zip

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

   checksum32: 

File 'redistribution.pdf' presents written approval from Nir Softer that allows software
redistribution

tools\chocolateyInstall.ps1

$ErrorActionPreference = 'Stop'

$toolsDir = Split-Path $MyInvocation.MyCommand.Definition
$is64 = (Get-ProcessorBits 64) -and $env:chocolateyForceX86 -ne 'true'
$install_path  = "$(Get-ToolsLocation)\NirLauncher"

$packageArgs = @{
    PackageName    = 'nirlauncher'
    FileFullPath   = gi $toolsDir\*.zip
    FileFullPath64 = gi $toolsDir\*.zip
    Destination    = $install_path
}
Get-ChocolateyUnzip @packageArgs
rm $toolsDir\*.zip -ea 0

if ($is64) {
    Write-Host '64 bit architecture - overwriting x32 apps with x64 versions'
    mv $install_path\Nirsoft\x64\* $install_path\Nirsoft -force
    rm $install_path\Nirsoft\x64 -ea 0
}
Install-ChocolateyPath $install_path\Nirsoft "Machine"

$launcher_path = "$install_path\$packageName.exe"
Register-Application $launcher_path
Write-Host "$packageName registered as $packageName"

Install-BinFile $packageName $launcher_path

$pp = Get-PackageParameters
if ($pp.SysInternals) {
    Write-Host 'SysInternals utilities will be added'

    $sysinternals_dir = gcm autoruns.exe -ea 0 | select -Expand Source | Split-Path
    if (!$sysinternals_dir) { Write-Warning 'Sysinternals tools are not on the PATH'; return }

    mv $toolsDir\sysinternals2.nlp $sysinternals_dir -Force

    #Configure nirlauncher
    $nircfg = gc $install_path\NirLauncher.cfg -Raw
    if ($nircfg -notmatch '\[Package1\]') {
        $nircfg = $nircfg.Replace("PackageCount=1", "PackageCount=2")
        $nircfg += "[Package1]`nfilename=$sysinternals_dir\sysinternals2.nlp"
        $nircfg | Out-File $install_path\NirLauncher.cfg -Encoding ascii
    }
}

tools\chocolateyUninstall.ps1

$ErrorActionPreference = 'Stop'

$packageName  = 'nirlauncher'
$install_path = "$(Get-ToolsLocation)\NirLauncher"

Write-Host "Removing $packageName from the '$install_path'"
rm $install_path -Recurse -Force -ea 0

$new_path = $Env:Path.Replace(";$install_path\Nirsoft", '')
if ($new_path -eq $Env:PATH) { return }
Write-Host "Removing $packageName from system PATH"
[System.Environment]::SetEnvironmentVariable('PATH', $new_path, 'Machine')

Write-Host "Removing $packageName shim"
Uninstall-BinFile $packageName

tools\nirsoft_package_1.20.20.zip

md5: 82A984EF982ADD404512432EAE9AD6B7 | sha1: 19693B6888CCD83C8D97E018EC66288983511498 | sha256: 53F639A7DCB9572FA7643F39D6D4EB1E479D9BF68538C0BFDA3BF101BC23B16A | sha512: 196FB4A202B274CBD4022D04116655704EE08CE081FA0181673444CF90B3E3C09DDC29FE246B4D1FDF24EA3BE856218400D8B6569CC0D6D9208835857116FC31

tools\sysinternals2.nlp

Virus Scan Results

vncpassview.exe (816d76162389) - ## / 72
operapassview.exe (8e4b218bdbd8) - ## / 71
rdpv.exe (205818e10c13) - ## / 72
mspass.exe (7a313840d25a) - ## / 72
driverview.exe (103a608c796d) - ## / 72
driverview.exe (d2140501eb3a) - ## / 73
livecontactsview.exe (62160c59d186) - ## / 72
lsasecretsdump.exe (ab176354b7b8) - ## / 72
lsasecretsdump.exe (2a871c1837d5) - ## / 72
officeins.exe (a9440c1eb0fe) - ## / 72
officeins.exe (6845e843f392) - ## / 57
sniffpass.exe (c92580318be4) - ## / 72
sniffpass.exe (1e13fd79ad54) - ## / 72
userprofilesview.exe (0b9c04da6fb9) - ## / 70
quicksetdns.exe (c4f50950903b) - ## / 67
altstreamdump.exe (54939b60003d) - ## / 72
awatch.exe (556124fe0767) - ## / 72
axhelper.exe (22279965263d) - ## / 70
bluescreenview.exe (f5f52ec9c38e) - ## / 70
bluetoothcl.exe (cb98e5060dcf) - ## / 72
bluetoothview.exe (6a1ccee35e0a) - ## / 70
bulletspassview.exe (b19dfe440e51) - ## / 72
cleanafterme.exe (9eccb72f6129) - ## / 67
cprocess.exe (f0cf25602f19) - ## / 70
ctie.exe (5b903d6efc2e) - ## / 72
customexplorertoolbar.exe (9d42469f4691) - ## / 72
dotnetresourcesextract.exe (381bfc1b1b50) - ## / 59
downtester.exe (74c2aa066141) - ## / 72
eventlogsourcesview.exe (22a7eb0b912b) - ## / 67
exifdataview.exe (060c65db6cef) - ## / 72
fastresolver.exe (1fcfc602fb5c) - ## / 73
faview.exe (a68fae179a57) - ## / 72
filetypesman.exe (2c7673f4116e) - ## / 67
firefoxdownloadsview.exe (53ff753b1cce) - ## / 68
firmwaretablesview.exe (ee01b39d8788) - ## / 67
flashcookiesview.exe (e9f9bea54333) - ## / 69
heapmemview.exe (1296d8731ad8) - ## / 66
hotkeyslist.exe (327c57918a77) - ## / 70
htmlastext.exe (42624eb45a96) - ## / 72
htmldocedit.exe (a8ab1365b04a) - ## / 69
iconsext.exe (e22afd680ce7) - ## / 69
iehv.exe (d46f1a4ab60e) - ## / 72
installedcodec.exe (ca54c5bda1ce) - ## / 69
installeddriverslist.exe (3bca36911305) - ## / 70
mmcsnapinsview.exe (8026dcd96e0a) - ## / 72
monitorinfoview.exe (0395d0a47cc1) - ## / 69
muicacheview.exe (02e28fa84912) - ## / 70
netconnectchoose.exe (178fdde88539) - ## / 71
netresview.exe (83f0352c14fa) - ## / 72
netrouteview.exe (91041b616969) - ## / 72
networkinterfacesview.exe (a2fef2bc62e8) - ## / 68
openwithview.exe (6358b2d02131) - ## / 69
operacacheview.exe (3102c6953187) - ## / 70
pcanypass.exe (0db918e61645) - ## / 67
processactivityview.exe (b918db8655b5) - ## / 72
regdllview.exe (9938f8bcc502) - ## / 71
regfromapp.exe (2a1a4ec3b52b) - ## / 64
resourcesextract.exe (c9b93aa5d45f) - ## / 73
rtmpdumphelper.dll (daf438351674) - ## / 66
rtmpdumphelper.exe (e41ef53a0ed6) - ## / 67
runfromprocess.exe (e084933319b9) - ## / 72
safaricacheview.exe (bd8a13430ace) - ## / 69
safarihistoryview.exe (231fd04cbe98) - ## / 65
searchfilterview.exe (0749e8e0b169) - ## / 71
securitysoftview.exe (a54e3494461d) - ## / 72
seqdownload.exe (e09d4a718e26) - ## / 70
shellmenunew.exe (c47485958a03) - ## / 71
shexview.exe (f74416aab0a4) - ## / 68
shman.exe (82c6e2c666a5) - ## / 72
siteshoter.exe (eefdef80e5a5) - ## / 70
skypecontactsview.exe (6bafeab61149) - ## / 55
skypelogview.exe (b2af144ca1c3) - ## / 70
socketsniff.exe (ecb44a44ff92) - ## / 73
specialfoldersview.exe (315fdb91b17d) - ## / 72
tabletextcompare.exe (44109d47dffb) - ## / 72
urlprotocolview.exe (34cbe52cc935) - ## / 55
urlstringgrabber.exe (e4a17446c490) - ## / 70
userassistview.exe (bc11c4150bbc) - ## / 70
vlmshlp32.dll (2f32e2aed465) - ## / 71
volumouse.exe (92b3d1c7dd4b) - ## / 68
webcamimagesave.exe (5e3f311ae67f) - ## / 73
webvideocap.exe (266283fce7ef) - ## / 65
whatinstartup.exe (7d8e7090d530) - ## / 70
whatishang.exe (fc4e9f5abccf) - ## / 69
winfontsview.exe (1e25fa572959) - ## / 65
winprefetchview.exe (1be46efa4960) - ## / 68
winsockservicesview.exe (7abaa3b7753d) - ## / 72
wirelesskeydump.exe (7056c1f58eac) - ## / 68
wirelessnetconsole.exe (49279441e70a) - ## / 73
bluescreenview.exe (09f3023554be) - ## / 71
bulletspassview.exe (e71cda5e7c01) - ## / 72
eventlogsourcesview.exe (fb821854d62b) - ## / 72
filetypesman.exe (fa7cc2f9c3e6) - ## / 67
firmwaretablesview.exe (af43c56b754a) - ## / 66
heapmemview.exe (4ceb3cadc9ab) - ## / 72
installedcodec.exe (d194ddb62b97) - ## / 70
installeddriverslist.exe (583eaf01e0ba) - ## / 71
mmcsnapinsview.exe (fd769b5b165c) - ## / 72
networkinterfacesview.exe (5e04d1cb02a2) - ## / 68
processactivityview.exe (5709f63fbc11) - ## / 73
regdllview.exe (52d52b59561c) - ## / 73
regfromapp.exe (a74583103234) - ## / 72
resourcesextract.exe (a718da8b2a11) - ## / 72
rtmpdumphelper.dll (f7715a862f5e) - ## / 67
rtmpdumphelper.exe (db46be6af7e1) - ## / 67
runfromprocess.exe (0be466ef7607) - ## / 73
shexview.exe (8f771238a97b) - ## / 69
shman.exe (e15f5060b60e) - ## / 72
specialfoldersview.exe (9911e0e65221) - ## / 72
vlmshlp.dll (32ad4153f601) - ## / 69
volumouse.exe (29ad9108c2fc) - ## / 68
volumouse32.exe (02448530591c) - ## / 60
whatinstartup.exe (15099976118e) - ## / 71
whatishang.exe (e2095dbe5ff7) - ## / 72
winprefetchview.exe (2d54f8c752cd) - ## / 68
wirelesskeydump.exe (dc6dab07642b) - ## / 68
devmanview.exe (008230ef2763) - ## / 67
devmanview.exe (b43b9fd68309) - ## / 66
executedprogramslist.exe (e3af98717bf1) - ## / 70
browseraddonsview.exe (30f9c4542596) - ## / 66
browseraddonsview.exe (070f52257036) - ## / 64
deviceioview.exe (f02bf17765ec) - ## / 72
deviceioview.exe (5794412bac7a) - ## / 72
nircmd.exe (5bfa034f7555) - ## / 69
nircmdc.exe (fb5443d482c9) - ## / 66
nircmd.exe (31b3b228382d) - ## / 68
nircmdc.exe (12459a5e9afd) - ## / 66
winlister.exe (1659abf390ba) - ## / 69
winlister.exe (805b4fbf4243) - ## / 71
iecacheview.exe (9dd1f1f24504) - ## / 72
disksmartview.exe (95473d0f0962) - ## / 72
usblogview.exe (187848c327f9) - ## / 66
simpleprogramdebugger.exe (7e0bafddf225) - ## / 66
simpleprogramdebugger.exe (0a873ed07fd6) - ## / 65
mailpv.exe (26a3395a4115) - ## / 66
openedfilesview.exe (cd878e1ba5a5) - ## / 66
openedfilesview.exe (d6a0a6dc55bc) - ## / 67
dialupass.exe (325b1f4ef7d4) - ## / 66
wincrashreport.exe (6638857a3bf1) - ## / 72
wincrashreport.exe (edd9545c53eb) - ## / 72
whoisconnectedsniffer.exe (50615a297097) - ## / 66
whoisconnectedsniffer.exe (65e73c45a059) - ## / 68
netbscanner.exe (5906fd255354) - ## / 70
networkconnectlog.exe (cd06007b99bb) - ## / 65
dllexp.exe (721c14e33253) - ## / 72
dllexp.exe (95d32211101d) - ## / 72
iepv.exe (dbe98193aced) - ## / 69
imagecacheviewer.exe (ea883b556134) - ## / 68
videocacheview.exe (a691ceace90e) - ## / 65
videocacheview.exe (5d9d27aa45db) - ## / 67
webcacheimageinfo.exe (bc01e1702dcb) - ## / 67
webcookiessniffer.exe (30b2895f64eb) - ## / 67
webcookiessniffer.exe (bc588c24b4d3) - ## / 66
bluetoothlogview.exe (ef93532a5984) - ## / 72
myeventviewer.exe (4ebfebb9e3ff) - ## / 69
myeventviewer.exe (c53a642daf25) - ## / 71
whosip.exe (9428a8adb02b) - ## / 72
dnsdataview.exe (de58c6cd66e9) - ## / 68
pstpassword.exe (5e85446910e7) - ## / 72
diskcountersview.exe (62051a3f7b1f) - ## / 66
processthreadsview.exe (013196a88d06) - ## / 67
processthreadsview.exe (58a8830bae8a) - ## / 67
countrytraceroute.exe (b4330742ac68) - ## / 66
recentfilesview.exe (80930766283e) - ## / 71
myuninst.exe (a1efc78ec525) - ## / 69
smsniff.exe (d6f90e99a7c7) - ## / 68
smsniff.exe (c027cb09a82e) - ## / 68
dumpedid.exe (ebc89cbef583) - ## / 67
produkey.exe (96d654879f8b) - ## / 68
produkey.exe (bace5e41e07d) - ## / 67
wifichannelmonitor.exe (5d89fe20562f) - ## / 67
wifichannelmonitor.exe (3f913b30c0b9) - ## / 67
shadowcopyview.exe (020694eaaff7) - ## / 66
shadowcopyview.exe (a67f77d137c5) - ## / 64
advancedrun.exe (5fc663338a83) - ## / 67
advancedrun.exe (c23b7191f877) - ## / 67
previousfilesrecovery.exe (c656ec1e2402) - ## / 71
previousfilesrecovery.exe (a8641b0ef7aa) - ## / 72
hashmyfiles.exe (436bb3fc13e7) - ## / 67
hashmyfiles.exe (35e7f5f46c92) - ## / 68
searchmyfiles.exe (9297017d9180) - ## / 64
searchmyfiles.exe (8708f03fbf1e) - ## / 65
insideclipboard.exe (b74d220e672c) - ## / 68
ntfslinksview.exe (4f4548efa5f9) - ## / 66
ntfslinksview.exe (3624a17c9ea1) - ## / 69
httpnetworksniffer.exe (7ae0ac5d3cd8) - ## / 66
httpnetworksniffer.exe (35c93804d66b) - ## / 65
clipboardic.exe (fa854713de67) - ## / 71
dnsquerysniffer.exe (938afc924d9b) - ## / 67
dnsquerysniffer.exe (dfd13275dfc7) - ## / 66
nk2edit.exe (4c53642b8314) - ## / 65
nk2edit.exe (ecc9974d2b47) - ## / 67
chromehistoryview.exe (f53dc96c6be3) - ## / 67
chromecacheview.exe (642350490334) - ## / 67
esedatabaseview.exe (d0e28e23430a) - ## / 66
pinginfoview.exe (b42f683d4d0a) - ## / 68
routerpassview.exe (f84f67a3dfc7) - ## / 65
runasdate.exe (3b8becbfae0b) - ## / 66
runasdate.exe (a314df092ab6) - ## / 66
serviwin.exe (e7bce282c2d9) - ## / 67
batteryinfoview.exe (cadd8c7dbf3a) - ## / 67
chromepass.exe (66aa6b04a86f) - ## / 67
NirLauncher.exe (4c517f3b00d3) - ## / 66
dataprotectiondecryptor.exe (b4f9be2dc63b) - ## / 66
driveletterview.exe (5747fd12096e) - ## / 69
fulleventlogview.exe (c445d27bf1c5) - ## / 65
gdiview.exe (0a4087860904) - ## / 56
guipropview.exe (d610f80bfaaf) - ## / 67
hostednetworkstarter.exe (145944e86a8b) - ## / 64
iecv.exe (a31884195978) - ## / 71
loadeddllsview.exe (41ce7de0140a) - ## / 66
lsasecretsview.exe (2a0de4dff5ef) - ## / 72
multimonitortool.exe (523d127f5025) - ## / 67
netpass.exe (de374c1b9a05) - ## / 71
shmnview.exe (1d525119f4e2) - ## / 68
simplewmiview.exe (e5232db71577) - ## / 68
taskschedulerview.exe (c1cdc0a3af4d) - ## / 68
vaultpasswordview.exe (0a711226f4b9) - ## / 67
webbrowserpassview.exe (cb29097bc5b9) - ## / 66
websitesniffer.exe (050860cbf00e) - ## / 72
wirelessconnectioninfo.exe (647f6d53000c) - ## / 72
wirelesskeyview.exe (2047070cfb44) - ## / 69
wul.exe (d358d76123a8) - ## / 73
dataprotectiondecryptor.exe (daf941ba78f3) - ## / 67
driveletterview.exe (a36885e04b3a) - ## / 67
fulleventlogview.exe (43f78fc0211f) - ## / 68
gdiview.exe (c49560f7a206) - ## / 73
guipropview.exe (7007e1893005) - ## / 65
loadeddllsview.exe (8ca25ecd05f0) - ## / 68
lsasecretsview.exe (7983d178cce1) - ## / 72
multimonitortool.exe (7315d67bba1b) - ## / 66
netpass.exe (6a87226ed5cc) - ## / 71
serviwin.exe (87a40da75f5e) - ## / 67
shmnview.exe (2dd66ff9d485) - ## / 65
simplewmiview.exe (f77c2130afd6) - ## / 66
taskschedulerview.exe (93fdbd6bdd78) - ## / 67
vaultpasswordview.exe (d802731eb70f) - ## / 66
websitesniffer.exe (8dba456d2bc6) - ## / 72
wirelesskeyview.exe (9dbc262d0b45) - ## / 67
encryptedregview.exe (46a96e4580dd) - ## / 67
eventlogchannelsview.exe (ddcb71420aed) - ## / 66
ipnetinfo.exe (5343ce1ed678) - ## / 68
lastactivityview.exe (7874b82d07dc) - ## / 66
mweather.exe (32c70379fe41) - ## / 66
passwordscan.exe (220b492fc0bb) - ## / 69
registrychangesview.exe (a9594b107019) - ## / 68
regscanner.exe (f2050a25a909) - ## / 65
encryptedregview.exe (566bede52745) - ## / 66
eventlogchannelsview.exe (26a6abfe6be4) - ## / 67
registrychangesview.exe (14e743157032) - ## / 68
regscanner.exe (f177ac7ef2e3) - ## / 67
bulkfilechanger.exe (a94457ee99c8) - ## / 66
csvfileview.exe (39c2c25ff39b) - ## / 67
jumplistsview.exe (8a2516e23539) - ## / 67
mylastsearch.exe (4df8c8d545bc) - ## / 68
networkcounterswatch.exe (c172104f8679) - ## / 67
regfileexport.exe (e5a6c570cbff) - ## / 63
sysexp.exe (684bc4ea2fc1) - ## / 66
tcplogview.exe (118c4fc43ddd) - ## / 69
winlogonview.exe (4baa004ccd04) - ## / 67
wnetwatcher.exe (250eeb459386) - ## / 67
bulkfilechanger.exe (36996b1e6b10) - ## / 66
csvfileview.exe (0862d228190c) - ## / 68
sysexp.exe (d1df5ce22ad6) - ## / 66
tcplogview.exe (9391fd42e904) - ## / 68
folderchangesview.exe (c52a54ca1847) - ## / 67
networktrafficview.exe (bb9c93775e88) - ## / 67
whoiscl.exe (75f74583668a) - ## / 68
whoistd.exe (8f12a3408d5c) - ## / 67
wirelessnetview.exe (637175bedfe6) - ## / 70
networktrafficview.exe (4f0203420f77) - ## / 67
cports.exe (1f576522af90) - ## / 67
networkusageview.exe (20cc05cad748) - ## / 68
outlookattachview.exe (9e0049183e02) - ## / 67
turnedontimesview.exe (c7cff9918644) - ## / 68
wakemeonlan.exe (c3040b11b770) - ## / 66
wifiinfoview.exe (f594388db809) - ## / 65
cports.exe (1ca540a1a6c4) - ## / 67
networkusageview.exe (974ece0bf6c1) - ## / 67
outlookattachview.exe (e24b70e6e2c6) - ## / 67
wakemeonlan.exe (adb219d14553) - ## / 67
alternatestreamview.exe (05cf035294b8) - ## / 67
chromecookiesview.exe (71966b264218) - ## / 67
installedpackagesview.exe (fbef21bd43e2) - ## / 68
outlookstatview.exe (8d9ddaa1074d) - ## / 68
soundvolumeview.exe (555d08203779) - ## / 67
wifihistoryview.exe (b65d433fdfaf) - ## / 66
alternatestreamview.exe (669ce40107a2) - ## / 67
installedpackagesview.exe (7ebb5344ca1d) - ## / 66
outlookstatview.exe (cf386124b4df) - ## / 67
soundvolumeview.exe (b123681e1a7b) - ## / 67
appcrashview.exe (80c117c4d788) - ## / 68
credentialsfileview.exe (e62bc0337298) - ## / 72
ipinfooffline.exe (cf3ec6777a47) - ## / 66
mozillacacheview.exe (5024feafadcf) - ## / 68
mozillahistoryview.exe (e55fa7bdcfed) - ## / 67
uninstallview.exe (e440feb0ea93) - ## / 65
credentialsfileview.exe (96cd6464e9f8) - ## / 66
uninstallview.exe (1d80c314cba7) - ## / 68
macaddressview.exe (8346441a8a50) - ## / 68
mzcv.exe (a192ad6132ec) - ## / 69
networkopenedfiles.exe (00261e713ff5) - ## / 66
opensavefilesview.exe (192a676c2dbe) - ## / 69
outlookaddressbookview.exe (6cd80c67d752) - ## / 67
passwordfox.exe (e01b0e7feadd) - ## / 69
mzcv.exe (9c352276b7a7) - ## / 68
networkopenedfiles.exe (bf03011713a7) - ## / 67
opensavefilesview.exe (f1c64110cb99) - ## / 72
outlookaddressbookview.exe (70b51dc4f3b0) - ## / 66
passwordfox.exe (7fee96ae0ed1) - ## / 68
nirlauncher.1.20.20.nupkg (b27d8e75353a) - ## / 63
nirsoft_package_1.20.20.zip (53f639a7dcb9) - ## / 44
browsinghistoryview.exe (7518f7f6cdb5) - ## / 68
controlmymonitor.exe (810c65341d67) - ## / 65
domainhostingview.exe (41a1c2a75879) - ## / 67
fbcacheview.exe (18456fd1b64f) - ## / 67
foldertimeupdate.exe (f6c17026af9d) - ## / 68
networklatencyview.exe (04a321628d52) - ## / 67
shellbagsview.exe (673c761da2fe) - ## / 65
timezonesview.exe (a016b037465a) - ## / 72
usbdeview.exe (b694f844f9cb) - ## / 67
browsinghistoryview.exe (7eab8d0c6602) - ## / 68
foldertimeupdate.exe (433f722f4d93) - ## / 68
networklatencyview.exe (1f2d65ba5606) - ## / 68
usbdeview.exe (b47352cfcdf0) - ## / 68

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.11	12	Monday, April 22, 2024	Waiting for Maintainer
NirLauncher 1.30.5	5771	Saturday, August 26, 2023	Exempted
NirLauncher 1.30.4	1647	Tuesday, August 1, 2023	Exempted
NirLauncher 1.30.3	2350	Thursday, June 22, 2023	Exempted
NirLauncher 1.30.2	3155	Monday, May 1, 2023	Exempted
NirLauncher 1.23.66	8457	Monday, November 7, 2022	Exempted
NirLauncher 1.23.65	431	Sunday, October 16, 2022	Exempted
NirLauncher 1.23.56	11772	Monday, January 17, 2022	Exempted
NirLauncher 1.23.53	5464	Tuesday, October 26, 2021	Exempted
NirLauncher 1.23.52	68	Tuesday, October 5, 2021	Exempted
NirLauncher 1.23.44	8067	Tuesday, April 27, 2021	Approved
NirLauncher 1.23.43	1794	Tuesday, April 6, 2021	Approved
NirLauncher 1.23.42	1564	Tuesday, March 23, 2021	Approved
NirLauncher 1.23.41	1620	Tuesday, March 9, 2021	Approved
NirLauncher 1.23.40	1529	Tuesday, February 23, 2021	Approved
NirLauncher 1.23.39	1508	Tuesday, February 9, 2021	Approved
NirLauncher 1.23.38	1600	Tuesday, January 26, 2021	Approved
NirLauncher 1.23.37	1794	Tuesday, January 12, 2021	Approved
NirLauncher 1.23.36	3402	Tuesday, December 8, 2020	Approved
NirLauncher 1.23.35	2624	Tuesday, November 10, 2020	Approved
NirLauncher 1.23.34	1781	Tuesday, October 27, 2020	Approved
NirLauncher 1.23.33	1701	Tuesday, October 13, 2020	Approved
NirLauncher 1.23.32	1702	Tuesday, September 29, 2020	Approved
NirLauncher 1.23.31	1753	Tuesday, September 15, 2020	Approved
NirLauncher 1.23.30	1579	Tuesday, September 1, 2020	Approved
NirLauncher 1.23.28	2336	Tuesday, August 4, 2020	Approved
NirLauncher 1.23.27	1680	Monday, July 20, 2020	Approved
NirLauncher 1.23.26	126	Tuesday, July 7, 2020	Approved
NirLauncher 1.23.25	2240	Tuesday, June 23, 2020	Approved
NirLauncher 1.23.24	1682	Tuesday, June 9, 2020	Approved
NirLauncher 1.23.23	1042	Monday, June 1, 2020	Approved
NirLauncher 1.23.22	1443	Monday, May 18, 2020	Approved
NirLauncher 1.23.21	1179	Tuesday, May 12, 2020	Approved
NirLauncher 1.23.20	1068	Tuesday, May 5, 2020	Approved
NirLauncher 1.23.19	1063	Tuesday, April 28, 2020	Approved
NirLauncher 1.23.18	1705	Tuesday, April 14, 2020	Approved
NirLauncher 1.23.17	1668	Tuesday, March 31, 2020	Approved
NirLauncher 1.23.15	2516	Tuesday, March 3, 2020	Approved
NirLauncher 1.23.14	798	Tuesday, February 18, 2020	Approved
NirLauncher 1.23.13	709	Tuesday, February 11, 2020	Approved
NirLauncher 1.23.12	654	Tuesday, February 4, 2020	Approved
NirLauncher 1.23.11	605	Tuesday, January 28, 2020	Approved
NirLauncher 1.23.10	837	Tuesday, January 14, 2020	Approved
NirLauncher 1.23.9	783	Tuesday, December 31, 2019	Approved
NirLauncher 1.23.8	770	Tuesday, December 17, 2019	Approved
NirLauncher 1.23.7	792	Tuesday, December 3, 2019	Approved
NirLauncher 1.23.6	688	Monday, November 25, 2019	Approved
NirLauncher 1.23.5	635	Tuesday, November 19, 2019	Approved
NirLauncher 1.23.4	693	Tuesday, November 12, 2019	Approved
NirLauncher 1.23.3	612	Tuesday, November 5, 2019	Approved
NirLauncher 1.23.2	694	Tuesday, October 29, 2019	Approved
NirLauncher 1.23.1	851	Monday, October 14, 2019	Approved
NirLauncher 1.22.24	706	Monday, October 7, 2019	Approved
NirLauncher 1.22.23	563	Tuesday, October 1, 2019	Approved
NirLauncher 1.22.22	942	Thursday, September 12, 2019	Approved
NirLauncher 1.22.21	951	Tuesday, August 27, 2019	Approved
NirLauncher 1.22.20	877	Tuesday, August 6, 2019	Approved
NirLauncher 1.22.19	532	Tuesday, July 30, 2019	Approved
NirLauncher 1.22.18	565	Monday, July 22, 2019	Approved
NirLauncher 1.22.17	548	Tuesday, July 16, 2019	Approved
NirLauncher 1.22.16	572	Tuesday, July 9, 2019	Approved
NirLauncher 1.22.15	629	Tuesday, July 2, 2019	Approved
NirLauncher 1.22.14	566	Tuesday, June 25, 2019	Approved
NirLauncher 1.22.13	627	Tuesday, June 18, 2019	Approved
NirLauncher 1.22.12	574	Monday, June 10, 2019	Approved
NirLauncher 1.22.11	578	Tuesday, June 4, 2019	Approved
NirLauncher 1.22.10	528	Monday, May 27, 2019	Approved
NirLauncher 1.22.9	565	Monday, May 20, 2019	Approved
NirLauncher 1.22.8	548	Tuesday, May 14, 2019	Approved
NirLauncher 1.22.7	510	Tuesday, May 7, 2019	Approved
NirLauncher 1.22.6	534	Wednesday, May 1, 2019	Approved
NirLauncher 1.22.5	653	Tuesday, April 23, 2019	Approved
NirLauncher 1.22.4	609	Tuesday, April 16, 2019	Approved
NirLauncher 1.22.3	530	Thursday, April 11, 2019	Approved
NirLauncher 1.22.2	687	Tuesday, April 2, 2019	Approved
NirLauncher 1.22.1	649	Tuesday, March 26, 2019	Approved
NirLauncher 1.21.2	610	Wednesday, March 20, 2019	Approved
NirLauncher 1.20.76	754	Monday, March 11, 2019	Approved
NirLauncher 1.20.75	797	Tuesday, February 26, 2019	Approved
NirLauncher 1.20.74	698	Monday, February 18, 2019	Approved
NirLauncher 1.20.73	592	Tuesday, February 12, 2019	Approved
NirLauncher 1.20.72	610	Monday, February 4, 2019	Approved
NirLauncher 1.20.71	561	Wednesday, January 30, 2019	Approved
NirLauncher 1.20.70	659	Monday, January 21, 2019	Approved
NirLauncher 1.20.69	544	Wednesday, January 16, 2019	Approved
NirLauncher 1.20.68	591	Tuesday, January 8, 2019	Approved
NirLauncher 1.20.67	616	Tuesday, January 1, 2019	Approved
NirLauncher 1.20.66	568	Wednesday, December 26, 2018	Approved
NirLauncher 1.20.65	591	Wednesday, December 19, 2018	Approved
NirLauncher 1.20.64	710	Tuesday, December 11, 2018	Approved
NirLauncher 1.20.63	707	Tuesday, December 4, 2018	Approved
NirLauncher 1.20.62	580	Tuesday, November 27, 2018	Approved
NirLauncher 1.20.61	600	Monday, November 19, 2018	Approved
NirLauncher 1.20.60	574	Tuesday, November 13, 2018	Approved
NirLauncher 1.20.58	746	Tuesday, October 30, 2018	Approved
NirLauncher 1.20.57	767	Tuesday, October 16, 2018	Approved
NirLauncher 1.20.56	606	Tuesday, October 9, 2018	Approved
NirLauncher 1.20.55	588	Tuesday, October 2, 2018	Approved
NirLauncher 1.20.54	574	Tuesday, September 25, 2018	Approved
NirLauncher 1.20.53	581	Tuesday, September 18, 2018	Approved
NirLauncher 1.20.52	624	Tuesday, September 11, 2018	Approved
NirLauncher 1.20.51	582	Tuesday, September 4, 2018	Approved
NirLauncher 1.20.50	635	Monday, August 27, 2018	Approved
NirLauncher 1.20.49	567	Tuesday, August 21, 2018	Approved
NirLauncher 1.20.48	555	Tuesday, August 14, 2018	Approved
NirLauncher 1.20.47	885	Tuesday, July 31, 2018	Approved
NirLauncher 1.20.46	664	Tuesday, July 24, 2018	Approved
NirLauncher 1.20.45	731	Tuesday, July 10, 2018	Approved
NirLauncher 1.20.44	657	Tuesday, July 3, 2018	Approved
NirLauncher 1.20.43	560	Tuesday, June 26, 2018	Approved
NirLauncher 1.20.42	631	Tuesday, June 19, 2018	Approved
NirLauncher 1.20.41	601	Tuesday, June 12, 2018	Approved
NirLauncher 1.20.40	687	Tuesday, June 5, 2018	Approved
NirLauncher 1.20.39	759	Monday, May 21, 2018	Approved
NirLauncher 1.20.38	755	Tuesday, May 8, 2018	Approved
NirLauncher 1.20.37	675	Wednesday, April 25, 2018	Approved
NirLauncher 1.20.36	599	Tuesday, April 17, 2018	Approved
NirLauncher 1.20.35	909	Tuesday, April 3, 2018	Approved
NirLauncher 1.20.34	614	Monday, March 26, 2018	Approved
NirLauncher 1.20.33	725	Monday, March 19, 2018	Approved
NirLauncher 1.20.32	629	Tuesday, March 13, 2018	Approved
NirLauncher 1.20.31	522	Saturday, March 10, 2018	Approved
NirLauncher 1.20.27	1185	Sunday, January 21, 2018	Approved
NirLauncher 1.20.26	685	Tuesday, January 9, 2018	Approved
NirLauncher 1.20.25	611	Tuesday, January 2, 2018	Approved
NirLauncher 1.20.24	684	Tuesday, December 19, 2017	Approved
NirLauncher 1.20.23	621	Sunday, December 10, 2017	Approved
NirLauncher 1.20.22	544	Monday, December 4, 2017	Approved
NirLauncher 1.20.21	565	Tuesday, November 28, 2017	Approved
NirLauncher 1.20.20	672	Monday, November 20, 2017	Approved
NirLauncher 1.20.19	716	Tuesday, November 7, 2017	Approved
NirLauncher 1.20.18	594	Tuesday, October 31, 2017	Approved
NirLauncher 1.20.17	639	Monday, October 23, 2017	Approved
NirLauncher 1.20.16	616	Monday, October 16, 2017	Approved
NirLauncher 1.20.15	600	Sunday, October 8, 2017	Approved
NirLauncher 1.20.14	492	Thursday, October 5, 2017	Approved
NirLauncher 1.20.12	932	Monday, August 28, 2017	Approved
NirLauncher 1.20.11	627	Monday, August 14, 2017	Approved
NirLauncher 1.20.10	632	Monday, July 31, 2017	Approved
NirLauncher 1.20.9	554	Monday, July 24, 2017	Approved
NirLauncher 1.20.8	576	Monday, July 17, 2017	Approved
NirLauncher 1.20.7	574	Wednesday, July 5, 2017	Approved
NirLauncher 1.20.6	574	Monday, June 26, 2017	Approved
NirLauncher 1.20.5	647	Tuesday, June 13, 2017	Approved
NirLauncher 1.20.4	568	Monday, June 5, 2017	Approved
NirLauncher 1.20.3	557	Tuesday, May 30, 2017	Approved
NirLauncher 1.20.2	713	Monday, May 22, 2017	Approved
NirLauncher 1.20.1	582	Sunday, May 14, 2017	Approved
NirLauncher 1.19.121	587	Monday, May 8, 2017	Approved
NirLauncher 1.19.120	605	Sunday, April 23, 2017	Approved
NirLauncher 1.19.119	645	Sunday, April 9, 2017	Approved
NirLauncher 1.19.118	794	Saturday, March 11, 2017	Approved
NirLauncher 1.19.117	796	Sunday, February 19, 2017	Approved
NirLauncher 1.19.116	675	Tuesday, January 31, 2017	Approved
NirLauncher 1.19.115	604	Sunday, January 15, 2017	Approved
NirLauncher 1.19.114	667	Sunday, January 1, 2017	Approved
NirLauncher 1.19.113	621	Sunday, December 18, 2016	Approved
NirLauncher 1.19.112	607	Monday, December 5, 2016	Approved
NirLauncher 1.19.111	530	Thursday, November 24, 2016	Approved
NirLauncher 1.19.110	677	Tuesday, November 8, 2016	Approved
NirLauncher 1.19.109	482	Tuesday, November 1, 2016	Approved
NirLauncher 1.19.108	594	Tuesday, October 25, 2016	Approved
NirLauncher 1.19.107	524	Wednesday, October 19, 2016	Approved
NirLauncher 1.19.106	540	Tuesday, October 11, 2016	Approved
NirLauncher 1.19.105	442	Friday, October 7, 2016	Approved
NirLauncher 1.19.92	812	Tuesday, July 5, 2016	Approved
NirLauncher 1.19.91	376	Tuesday, June 21, 2016	Approved
NirLauncher 1.19.90	398	Monday, June 13, 2016	Approved
NirLauncher 1.19.89	391	Tuesday, June 7, 2016	Approved
NirLauncher 1.19.88	357	Tuesday, May 31, 2016	Approved
NirLauncher 1.19.87	352	Saturday, May 28, 2016	Approved
NirLauncher 1.19.86	307	Monday, May 16, 2016	Approved
NirLauncher 1.19.85	360	Monday, May 9, 2016	Approved
NirLauncher 1.19.84	427	Monday, May 2, 2016	Approved
NirLauncher 1.19.83	441	Monday, April 25, 2016	Approved
NirLauncher 1.19.82	465	Monday, April 18, 2016	Approved
NirLauncher 1.19.81	487	Tuesday, April 12, 2016	Approved
NirLauncher 1.19.80	406	Monday, April 11, 2016	Approved
NirLauncher 1.19.79.20160331	477	Thursday, March 31, 2016	Approved
NirLauncher 1.19.79	406	Thursday, March 31, 2016	Approved
NirLauncher 1.19.78	487	Tuesday, March 22, 2016	Approved
NirLauncher 1.19.77.20160315	467	Tuesday, March 15, 2016	Approved
NirLauncher 1.19.76	503	Monday, March 7, 2016	Approved
NirLauncher 1.19.75	479	Monday, February 29, 2016	Approved
NirLauncher 1.19.74	540	Tuesday, February 23, 2016	Approved
NirLauncher 1.19.73	484	Monday, February 15, 2016	Approved
NirLauncher 1.19.72	485	Wednesday, February 10, 2016	Approved
NirLauncher 1.19.71	468	Friday, February 5, 2016	Approved
NirLauncher 1.19.70	491	Monday, February 1, 2016	Approved
NirLauncher 1.19.69	527	Tuesday, January 19, 2016	Approved
NirLauncher 1.19.68	473	Tuesday, January 12, 2016	Approved
NirLauncher 1.19.67	445	Monday, January 4, 2016	Approved
NirLauncher 1.19.66	439	Wednesday, December 30, 2015	Approved
NirLauncher 1.19.65	480	Monday, December 21, 2015	Approved
NirLauncher 1.19.64	467	Tuesday, December 15, 2015	Approved
NirLauncher 1.19.63	451	Tuesday, December 8, 2015	Approved
NirLauncher 1.19.62	476	Tuesday, December 1, 2015	Approved
NirLauncher 1.19.61	463	Monday, November 23, 2015	Approved
NirLauncher 1.19.60	477	Tuesday, November 17, 2015	Approved
NirLauncher 1.19.59	423	Monday, November 9, 2015	Approved
NirLauncher 1.19.57	547	Tuesday, October 27, 2015	Approved
NirLauncher 1.19.56	456	Tuesday, October 20, 2015	Approved
NirLauncher 1.19.55	428	Wednesday, October 14, 2015	Approved
NirLauncher 1.19.54	467	Saturday, October 10, 2015	Approved
NirLauncher 1.19.53	481	Tuesday, September 29, 2015	Approved
NirLauncher 1.19.51	449	Thursday, September 17, 2015	Approved
NirLauncher 1.19.50	467	Tuesday, September 8, 2015	Approved
NirLauncher 1.19.49	448	Tuesday, September 1, 2015	Approved
NirLauncher 1.19.48	400	Tuesday, August 25, 2015	Approved
NirLauncher 1.19.47	412	Tuesday, August 18, 2015	Approved
NirLauncher 1.19.46	425	Tuesday, August 11, 2015	Approved
NirLauncher 1.19.44	459	Tuesday, July 28, 2015	Approved
NirLauncher 1.19.43	400	Tuesday, July 21, 2015	Approved
NirLauncher 1.19.42	429	Wednesday, July 15, 2015	Approved
NirLauncher 1.19.41	471	Tuesday, July 7, 2015	Approved
NirLauncher 1.19.40	387	Wednesday, July 1, 2015	Approved
NirLauncher 1.19.39	428	Tuesday, June 23, 2015	Approved
NirLauncher 1.19.38	427	Tuesday, June 16, 2015	Approved
NirLauncher 1.19.37	386	Tuesday, June 9, 2015	Approved
NirLauncher 1.19.36	428	Tuesday, June 2, 2015	Approved
NirLauncher 1.19.34	433	Wednesday, May 20, 2015	Approved
NirLauncher 1.19.33	442	Tuesday, May 12, 2015	Approved
NirLauncher 1.19.32	381	Friday, May 8, 2015	Approved
NirLauncher 1.19.31	410	Tuesday, April 28, 2015	Approved
NirLauncher 1.19.30	438	Monday, April 27, 2015	Approved
NirLauncher 1.19.29	466	Tuesday, April 14, 2015	Approved
NirLauncher 1.19.28	415	Wednesday, April 8, 2015	Approved
NirLauncher 1.19.27	402	Thursday, April 2, 2015	Approved

Release Notes

http://blog.nirsoft.net/?s=nirlauncher

Dependencies

- chocolatey (≥ 0.9.10)
- chocolatey-core.extension (≥ 1.3.1)

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

205,475

672

20 Nov 2017

NirLauncher

NirLauncher 1.20.20

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

Package Parameters

Ground Rules: