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:

1,747

Downloads of v 1.77.0:

15

Last Update:

22 Apr 2024

Package Maintainer(s):

Software Author(s):

Nir Sofer

Tags:

data visualizer lists

SysExporter (Portable)

1.77.0 | Updated: 22 Apr 2024

Downloads:

1,747

Downloads of v 1.77.0:

Maintainer(s):

Software Author(s):

Nir Sofer

Tags:

data visualizer lists

SysExporter (Portable) 1.77.0

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Hide Checks

Validation Testing Passed

Verification Testing Passed

Details

Scan Testing Resulted in Flagged as a Note:

At least one file within this package has greater than 0 detections, but less than 5

Details

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install SysExporter (Portable), run the following command from the command line or from PowerShell:

To upgrade SysExporter (Portable), run the following command from the command line or from PowerShell:

To uninstall SysExporter (Portable), 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 sysexp.portable --internalize --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 sysexp.portable -y --source="'INTERNAL REPO URL'" [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 sysexp.portable -y --source="'INTERNAL REPO URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode


- name: Install sysexp.portable
  win_chocolatey:
    name: sysexp.portable
    version: '1.77.0'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'sysexp.portable' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '1.77.0'
end

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


cChocoPackageInstaller sysexp.portable
{
    Name     = "sysexp.portable"
    Version  = "1.77.0"
    Source   = "INTERNAL REPO URL"
}

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


package { 'sysexp.portable':
  ensure   => '1.77.0',
  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.

NOTE

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

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

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

Package Approved

This package was approved by moderator Windos on 23 Apr 2024.

Description

SysExporter (Portable)

SysExporter utility allows you to grab the data stored in standard list-views, tree-views, list boxes, combo boxes, text-boxes, and WebBrowser/HTML controls from
almost any application running on your system, and export it to text, HTML or XML file.

Here's some examples for data that you can export with SysExporter:

The files list inside archive file (.zip, .rar, and so on) as displayed by WinZip or 7-Zip File Manager.
The files list inside a folder.
The event log of Windows.
The list of emails and contacts in Outlook Express.
The Registry values displayed in the right pane of the Registry Editor.
The data displayed by SysInternals utilities (Registry Monitor, File Monitor, Process Explorer, and others.)
The text inside a standard message-box of Windows.
The HTML inside any instance of Internet Explorer.

Package-specific issue

If this package isn't up-to-date for some days, Create an issue

Support the package maintainer and

Files

legal\LICENSE.txt

This utility is released as freeware. You are allowed to freely distribute this utility via floppy disk, CD-ROM, Internet, or in any other way, as long as you don't charge anything for this and you don't sell it or distribute it as a part of commercial product. If you distribute this utility, you must include all files in the distribution package, without any modification !

legal\VERIFICATION.txt

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

The installer have been downloaded from the GitHub mirror and can be verified like this:

1. Download the following installer(s):

x86: https://www.nirsoft.net/utils/sysexp.zip
x64: https://www.nirsoft.net/utils/soundvolumeview-x64.zip

2. You can use one of the following methods to obtain the checksum(s):
  - Use powershell function 'Get-Filehash'
  - Use chocolatey utility 'checksum.exe'

checksum type: sha256
checksum: 
checksum64: 

The license is available here:
https://www.nirsoft.net/utils/sound_volume_view.html

tools\chocolateyInstall.ps1

$ErrorActionPreference = 'Stop'
$toolsDir       = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$file32         = "$(Join-Path $toolsDir -ChildPath 'sysexp.zip')"
$file64         = "$(Join-Path $toolsDir -ChildPath 'sysexp-x64.zip')"

$unzipArgs = @{
    PackageName     = $env:ChocolateyPackageName
    FileFullPath    = $file32
    FileFullPath64  = $file64
    Destination     = $toolsDir
}

Get-ChocolateyUnzip @unzipArgs

tools\readme.txt




SoundVolumeView v2.46
Copyright (c) 2013 - 2024 Nir Sofer
Web site: https://www.nirsoft.net



Description
===========

SoundVolumeView is a simple tool for Windows Vista/7/8/2008/10/11 that
displays general information and current volume level for all active
sound components on your system, and allows you to mute and unmute them
instantly.
SoundVolumeView also allows you to save a sound profile into a file,
containing the current volume level and the mute/unmute state of all
sound components, as well as the default sound devices, and then later,
load the same file to restore exactly the same volume levels and settings.
There is also extensive command-line support, which allows you to
save/load profiles, change current volume of every sound component, and
mute/unmute every sound component, without displaying any user interface.



System Requirements
===================

This utility works on Windows Vista, Windows 7, Windows 8, Windows 2008,
Windows 10, and Windows 11. Both 32-bit and 64-bit systems are supported.
Windows XP and older systems are not supported.



Versions History
================


* Version 2.46:
  o Added /SetBooleanFxProperty command-line option, which allows you
    to turn on/off different options of a device, like 'Loudness
    Equalization', 'Headphone Virtualization', 'Voice Cancellation', and
    others.

* Version 2.45:
  o Added /GetColumnValue command-line option, which allows to get a
    value of specific column for the specified item, for example:
    SoundVolumeView.exe /GetColumnValue "Realtek High Definition
    Audio\Device\Speakers\Render" "Speakers Config" | more

* Version 2.43:
  o The 'Device State' column now also displays state information for
    application items (Active/Inactive/Expired).

* Version 2.42:
  o Added /SaveDeviceFormat and /LoadDeviceFormat command-line
    options, which allow you to save the data of the device default
    format into a file, and then later load it back into the device.
  o You should use these new commands if you have a format that
    cannot be set with the /SetDefaultFormat command.

* Version 2.41:
  o Added 'Black Background' option (Under the View menu). When it's
    turned on, the main table is displayed in black background and white
    text, instead of default system colors.

* Version 2.40:
  o Added 'Use Mouse Wheel On Tray Icon' option. When it's turned on,
    you can increase/decrease the sound volume of the selected item while
    the mouse cursor is over the tray icon. The percent of change for
    every wheel move is according to the 'Mouse Wheel % Change' option.

* Version 2.38:
  o Added 'Sort By' toolbar button.

* Version 2.37:
  o The current volume level of the selected item is now displayed in
    the tooltip of the tray icon. This feature works only when both 'Put
    Icon On Tray' option and 'Auto Refresh' option are turned on.

* Version 2.36:
  o Added /SetSpeakersConfig command-line option, which allows you to
    set the desired speakers configuration (Stereo, Quadraphonic, 5.1
    Surround, 7.1 Surround) from command-line.
  o Added 'Speakers Config' column, which displays 3 Hexadecimal
    values that represent the current speakers configuration. You can use
    these values in the /SetSpeakersConfig command-line option.

* Version 2.35:
  o Added 'Show Mute On Tray Icon' option. When it's turned on,
    SoundVolumeView displays mute icon on the tray if the selected item
    is muted.
  o This feature works only when both 'Put Icon On Tray' option and
    'Auto Refresh' option are turned on.

* Version 2.31:
  o Fixed a few high DPI mode issues.

* Version 2.30:
  o Added /Columns command-line option, which allows you to set the
    columns to display or the columns to export from command-line, for
    example:
    SoundVolumeView.exe /scomma "c:\temp\sound-items.csv" /Columns
    "Name,Command-Line Friendly ID,Volume Percent"

* Version 2.29:
  o You can now use wildcard with the command-line friendly ID, for
    example:
    SoundVolumeView.exe /Switch "Realtek*\Device\Speakers\Render"

* Version 2.28:
  o You can now specify the number of channels in the
    /SetDefaultFormat command, for example:
    SoundVolumeView.exe /SetDefaultFormat "Speakers" 24 48000 4

* Version 2.27:
  o Updated the /SetAppDefault and /SetSpatial commands to work on
    Windows 11.

* Version 2.26:
  o You can now use any variable inside the .cfg file
    (SoundVolumeView.cfg) in order to set the configuration from command
    line, for example:
    SoundVolumeView.exe /SaveFileEncoding 3 /ShowUnpluggedDevices 1
    /ShowDisabledDevices 1

* Version 2.25:
  o You can now choose the desired encoding (ANSI, UTF-8, UTF-16) to
    save the csv/xml/text/html files. (Under the Options menu)
  o Updated the HTML export feature to HTML5.
  o Added option to export as JSON file.
  o You can now specify 'System Sounds' as the item name from
    command-line. For example, this command mutes the system sounds from
    command-line:
    SoundVolumeView.exe /Mute "System Sounds"

* Version 2.23:
  o Added secondary sorting support: You can now get a secondary
    sorting, by holding down the shift key while clicking the column
    header. Be aware that you only have to hold down the shift key when
    clicking the second/third/fourth column. To sort the first column you
    should not hold down the Shift key.
  o Added option to change the sorting column from the menu (View ->
    Sort By). Like the column header click sorting, if you click again
    the same sorting menu item, it'll switch between ascending and
    descending order. Also, if you hold down the shift key while choosing
    the sort menu item, you'll get a secondary sorting.

* Version 2.22:
  o Updated to work properly in high DPI mode.

* Version 2.21:
  o Added 'all' option to the /SetDefault and /SwitchDefault
    command-line options, which allow you to set all 3 default types
    (Console, Multimedia, Communications) at once, for example:
    SoundVolumeView.exe /SetDefault "High Definition Audio
    Device\Device\Speakers\Render" all
  o Added 'Set Default Device - All' to the Create Shortcut menu.

* Version 2.20:
  o You can now use the /SetListenToThisDevice and
    /SetPlaybackThroughDevice command-line options without running
    SoundVolumeView as Administrator.
  o Added /SetAllowExclusive command-line option to set the 'Allow
    applications to take exclusive control of this device' option of a
    device.
  o Added /SetExclusivePriority command-line option to set the 'Give
    exclusive mode applications priority' option of a device.

* Version 2.16:
  o Added 'all' option to the /SetAppDefault command-line option,
    which allows you to set all 3 default types (Console, Multimedia,
    Communications) at once, for example:
    SoundVolumeView.exe /SetAppDefault "High Definition Audio
    Device\Device\Speakers\Render" all "chrome.exe"

* Version 2.15:
  o Added /SetSpatial command-line option, which allows you to set
    the 'Spatial sound format' of sound device from command line on
    Windows 10, for example:
    SoundVolumeView.exe /SetSpatial "High Definition Audio
    Device\Device\Speakers\Render" "Windows Sonic For Headphones"

* Version 2.11:
  o Added support for 'focused' and 'focusedname' in the
    /SetAppDefault command for setting the default input or output device
    of the focused application on Windows 10, for example:
    SoundVolumeView.exe /SetAppDefault "High Definition Audio
    Device\Device\Speakers\Render" 0 focused
  o Added /SetDefaultFormat command line option, which allows you to
    set the default format of the device. For example: The following
    command sets the default format of the device to '24 bit, 192000
    Hz(Studio Quality)':
    SoundVolumeView.exe /SetDefaultFormat "Realtek High Definition
    Audio\Device\Speakers\Render" 24 192000

* Version 2.10:
  o Added /SetAppDefault command-line option, which allows you to set
    the default render/capture device for specific application on Windows
    10, for example:
    SoundVolumeView.exe /SetAppDefault "High Definition Audio
    Device\Device\Speakers\Render" 0 "chrome.exe"
  o Fixed bug: SoundVolumeView displayed the wrong device on
    application volume items.
  o Added 'Show Unplugged Devices' option.

* Version 2.06:
  o Added 'Select All' and 'Deselect All' to the 'Column Settings'
    window.

* Version 2.05:
  o Added 'Registry Key' column, which displays the Registry key of
    audio device.
  o Added 'Open Device Key In RegEdit' option, which allows you to
    open the device Registry key in RegEdit.

* Version 2.00:
  o Added option to easily create shortcuts on desktop that will
    execute one of the following actions: Mute,Unmute,Mute/Unmute
    Switch,Disable,Enable,Disable/Enable Switch, Set Default Device
    (Console, Multimedia, Communications), Increase Volume, Decrease
    Volume.
  o In order to create the desktop shortcut, simply select the
    desired item, and then go to File -> Create Desktop Shortcut and
    choose the desired action to execute when the shortcut is activated.
    You can also use the 'Create Desktop Shortcut' submenu in the
    right-click context menu.
  o The following actions can also be used with application items:
    Mute,Unmute,Mute/Unmute Switch,Increase Volume, Decrease Volume. For
    example, you can create 'Mute/Unmute Switch' shortcut for Firefox
    that will mute the sound of Firefox if it's turned on and unmute if
    it's turned off.
  o After creating the shortcut, you can right-click on it, choose
    'Properties' and then choose the desired key combination to activate
    the shortcut.

* Version 1.90:
  o Added 'Default Multimedia' and 'Default Communications' columns,
    which display the Multimedia and Communications default types. (The
    'Default' column displays the 'Console' default).
  o Added option to specify default Multimedia/Communications device
    instead of name: DefaultRenderDeviceMulti, DefaultCaptureDeviceMulti,
    DefaultRenderDeviceComm, DefaultCaptureDeviceComm.

* Version 1.87:
  o The 'Command-Line Friendly ID' now specifies whether the device
    is a capture or render device.

* Version 1.86:
  o Added new command-line options: /GetDecibel , /GetDecibelChannel

* Version 1.85:
  o Added new command-line options: /SetListenToThisDevice ,
    /SetPlaybackThroughDevice , /RunAsAdmin

* Version 1.83:
  o Fixed bug: SoundVolumeView failed to remember the last
    size/position of the properties window if it was not located in the
    primary monitor.
  o You can now send the data to stdout by specifying empty string as
    filename, for example:
    SoundVolumeView.exe /scomma "" | more

* Version 1.82:
  o You can now resize the properties window, and the last
    size/position of this window is saved in the .cfg file.

* Version 1.81:
  o Added /ChangeVolumeChannel command-line option, for changing the
    volume of specific channel.

* Version 1.80:
  o Added 'Selected Channel' option (Under the Options menu). If you
    want to change the volume of specific channel, you can choose the
    desired channel from this menu, and then use the Increase/Decrease
    1%/5%/10% options (under the Volume menu) or the mouse wheel to
    change the volume of the selected channel.

* Version 1.75:
  o Added support for setting the volume of specific channels for
    specific application from command-line. For example, the following
    command sets the volume of the left channel to 50% only for Chrome
    Web browser:
    SoundVolumeView.exe /SetVolumeChannels "chrome.exe" 50 100
  o Also, the current channels volume of application is displayed in
    the 'Channels Percent' column.
  o Added 'focusedname' to all command-line options, which allows you
    to change the volume all instances of the focused application.
  o Fixed bug: When using 'focused' in command-line and but there was
    no focused application, SoundVolumeView changed the 'System Sounds'
    items.

* Version 1.72:
  o Added 'Align Numeric Columns To Right' option.

* Version 1.71:
  o You can now specify "DefaultCaptureDevice" and
    "DefaultRenderDevice" in the [Name] parameter of all command-line
    options in order to refer the default render/capture device.

* Version 1.70:
  o Added /WaitForItem command-line option, which instructs
    SoundVolumeView to wait until the sound item appears. You can use
    this feature to change the application volume for applications that
    are currently not running. For example, if you want to mute the sound
    of Chrome Web browser and it's not running at this moment:
    SoundVolumeView.exe /Mute chrome.exe /WaitForItem 0
  o Disabled devices are now displayed with disabled icon.

* Version 1.66:
  o Added /GetPercentChannel command-line option.

* Version 1.65:
  o Added 'Command-Line Friendly ID' column. You can use the string
    displayed in this column in all command-line options when you have
    multiple items with the same name (For example: 2 'Speakers'
    devices). This ID is more friendly than the ID provided by Windows
    operating system ('Item ID' column), for example: "Realtek High
    Definition Audio\Device\Speakers" and "2- USB
    AUDIO\Device\Microphone".

* Version 1.60:
  o Added 'Disable Device' and 'Enable Device' options.
  o Added 'Show Disabled Devices' option, when it's turned on,
    SoundVolumeView displays disabled items.
  o Added 'Device State' column - Displays whether a device is active
    or disabled.
  o Added new command-line options - /Disable , /Enable ,
    /DisableEnable

* Version 1.57:
  o Added 'Copy Mute/Unmute Command' option (Ctrl+M), which copies to
    the clipboard a command to mute and unmute the selected sound
    component (Using the /Switch command-line option).

* Version 1.56:
  o Added /ChangeVolumeDecibel command-line option, which allows you
    to increase/decrease the volume of devices and subunits in Decibel,
    for example:
    SoundVolumeView.exe /ChangeVolumeDecibel "Microphone Boost" -10

* Version 1.55:
  o Added 'Decrease Volume Step (dB)' (Ctrl+7) and 'Increase Volume
    Step (dB)' (Ctrl+8) options which increase/decrease the volume
    accoding to the default volume step displayed in 'Volume Step' column.
  o Added 'Export All Items' option.

* Version 1.50:
  o Added 'Direction' column (Capture or Render)
  o Added /SetVolumeChannelsDecibel command-line option, which allows
    you to set the channel volume of devices and subunits in Decibel, for
    example:
    SoundVolumeView.exe /SetVolumeChannelsDecibel "Speakers" -20.5 -18.5
  o Added /SetVolumeDecibel command-line option, which allows you to
    set the volume of devices and subunits in Decibel, for example:
    SoundVolumeView.exe /SetVolumeDecibel "Speakers" -14
  o Added Subunits of capture devices (Like 'Microphone Boost')
  o You can set the 'Microphone Boost' value from command-line, for
    example:
    SoundVolumeView.exe /SetVolumeDecibel "Microphone Boost" 30
  o Fixed bug: When using '*' with devices on /SetVolumeChannels
    command-line option, SoundVolumeView set the volume channel to zero
    instead of leaving it without change.

* Version 1.45:
  o Added 'Save Sound Profile - Selected Items' option (Alt+S), which
    creates a profile only from the items you select.

* Version 1.43:
  o Added /GetMute command-line option that returns the current Mute
    status.

* Version 1.42:
  o Added option to return the current volume level in percent (for
    using in scripts and batch files). The return value is the percent
    value multiplied by 10, for example:
    SoundVolumeView.exe /GetPercent Speakers
    echo %errorlevel%

* Version 1.41:
  o Added option to set the percent of change for every wheel move in
    the 'Change Volume With Mouse Wheel' option ('Mouse Wheel % Change'
    menu)

* Version 1.40:
  o Added 'Change Volume With Mouse Wheel' option, which allows you
    to increase/decrease the volume of selected items by scrolling the
    mouse wheel. You can choose to change the volume with the mouse wheel
    when the Ctrl key is down or when the left mouse button is down or
    when the middle button is down. The default option is 'When Ctrl key
    is down'.

* Version 1.36:
  o You can now specify only a part of name or id of the sound item
    in all command-line options ( /SetVolume, /Mute , /Unmute , and so
    on...), for example: If ID of a subunit is
    "{2}.\\?\hdaudio#func_01&ven_10ec&dev_0889&subsys_1458a002&rev_1000#4&3
    828eb94&0&0201#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\singlelineouttopo
    /0002000c" , the following command will mute this subunit:
    SoundVolumeView.exe /Mute "singlelineouttopo/0002000c"

* Version 1.35:
  o Added 'Auto Size Columns On Update' option.

* Version 1.33:
  o You can now use the /SetVolumeChannels command-line option with
    devices.

* Version 1.32:
  o Added option to set from command-line the volume of focused
    application, for example:
    SoundVolumeView.exe /SetVolume focused 50

* Version 1.31:
  o Fixed bug: When there were multiple application volume items of
    the same process filename, and you tried to set one of them,
    SoundVolumeView set the wrong item.

* Version 1.30:
  o SoundVolumeView now displays the process names (Some of them
    without the full path) for most processes when you run it without
    elevation ('Run As Administrator').
  o Fixed the Ctrl+C (Copy Selected Items) key.
  o You can now specify the process ID in the /SetVolume
    /ChangeVolume /Mute /Unmute /Switch command-line options.

* Version 1.27:
  o Added 'Run As Administrator' option (Ctrl+F11), for viewing the
    icon and information of applications running as admin.

* Version 1.26:
  o Added /SwitchDefault command-line option, which allows you to
    switch between 2 default devices, for exmaple:
    SoundVolumeView.exe /SwitchDefault
    "{0.0.0.00000000}.{a77a09b2-1ec6-49c3-860a-68945904a2f1}"
    "{0.0.0.00000000}.{7747b192-73b2-47d3-a2c0-168e94af7f9e}" 0


* Version 1.25:
  o Added option to set from command-line the volume of all
    applications at once, for example:
    SoundVolumeView.exe /SetVolume AllAppVolume 50

* Version 1.22:
  o Fixed bug: SoundVolumeView failed to remember the last
    size/position of the main window if it was not located in the primary
    monitor.

* Version 1.21:
  o Added 'Always On Top' option.

* Version 1.20:
  o Added 'Process ID' and 'Window Title' columns (For application
    volume items).

* Version 1.15:
  o Added 'Copy Item ID' and 'Copy Item Name' options.

* Version 1.13:
  o Added accelerator keys to the 'Set Default' options.

* Version 1.12:
  o Fixed issue: /SaveProfile command-line option failed to save the
    sound settings file when running it from a batch file without
    specifying the full path of the sound settings file.

* Version 1.11:
  o Added option to choose another font (font name and size) to
    display the sound components list. (Options -> Select Another Font)

* Version 1.10:
  o Added 'Sort On Every Update' option. If it's turned on,
    SoundVolumeView will sort the list every time that a new item is
    added or an existing item is updated.

* Version 1.06:
  o Added 'Start As Hidden' option. When this option and 'Put Icon On
    Tray' option are turned on, the main window of SoundVolumeView will
    be invisible on start.
  o Added 'Clear Recent Files List' option.

* Version 1.05:
  o Added 'Set Default' options (Under the Volume menu) to set the
    default device.
  o Added documentation for /SetDefault command-line option (It was
    exist on v1.00, but I forgot to add it to the help file of
    SoundVolumeView...)

* Version 1.00 - First release.



Start Using SoundVolumeView
===========================

SoundVolumeView doesn't require any installation process or additional
dll files. In order to start using it, simply run the executable file -
SoundVolumeView.exe

After running SoundVolumeView, the main window is displays all sound
items found in your systems. There are 3 types of items: devices,
subunits, and application volume.
For every item, the current volume level is displayed in percent unit.
For devices and subunits, the volume level is also displayed in Decibel.
For subunits, the volume level is displayed for every channel separately.



Increase/Decrease/Mute Volume
=============================

In the main window of SoundVolumeView, you can select one or more items,
and then mute, unmute, increase, or decrease the volume of selected
items, using accelerator keys:
* Mute - F7
* Unmute - F8
* Mute/Unmute switch - F9
* Decrease volume 1% - Ctrl+1
* Increase volume 1% - Ctrl+2
* Decrease volume 5% - Ctrl+3
* Increase volume 5% - Ctrl+4
* Decrease volume 10% - Ctrl+5
* Increase volume 10% - Ctrl+6

The Increase/Decrease options can also be used for specific channel. In
order to do that, choose the desired channel from Options -> Selected
Channel.



Sound Profiles
==============

SoundVolumeView allows you to save all your current sound settings into a
sound profile filename, and then load it later when you want to restore
these settings.
The sound profile file stores the following information:
* Volume level of all active sound components on your system. (Devices,
  Subunits, and application volume) For Subunits, the volume level of
  every channel is stored separately.
* Mute/Unmute state of all active sound components on your system.
  (Devices, Subunits, and application volume)
* Default render/capture device.

You can save and load sound profiles by using the 'Save Sound Profile'
and 'Load Sound Profile' options under the File menu, or by using the
/SaveProfile and /LoadProfile command-line options. There is also a
recent menu located under the File menu, which allows you to easily load
the last 10 sound profiles you used, as well as you can also load the
recent 5 sound profiles from the tray menu (If the tray icon is turned on)

Be aware that sound profiles are bound to specific computer and its
devices. You cannot save a sound profile in one computer and then load it
into another computer.



Creating Desktop Shortcuts
==========================

Starting from version 2.00, you can easily create shortcuts on desktop
that will execute one of the following actions: Mute,Unmute,Mute/Unmute
Switch,Disable,Enable,Disable/Enable Switch, Set Default Device (Console,
Multimedia, Communications), Increase Volume, Decrease Volume.
In order to create the desktop shortcut, simply select the desired item,
and then go to File -> Create Desktop Shortcut and choose the desired
action to execute when the shortcut is activated. You can also use the
'Create Desktop Shortcut' submenu in the right-click context menu.
The following actions can also be used with application items:
Mute,Unmute,Mute/Unmute Switch,Increase Volume, Decrease Volume. For
example, you can create 'Mute/Unmute Switch' shortcut for Chrome Web
browser that will mute the sound of Chrome if it's turned on and unmute
if it's turned off.
After creating the shortcut, you can right-click on it, choose
'Properties' and then choose the desired key combination to activate the
shortcut.



Get sound level information from command line
=============================================

If you want to get the current sound volume or mute status from
command-line, there are 2 different methods you can use:
1. Use the get commands of SoundVolumeView - /GetPercent
   /GetPercentChannel, /GetDecibel, /GetDecibelChannel, /GetMute : These
   commands return the desired sound level information inside the Exit
   Status of the program. Because the Exit Status is an integer value,
   the percent value is multiplied by 10 and the Decibel value is
   multiplied by 1000. You can get more information about these commands
   in the 'Command-Line Options' section.
   You can get the desired value inside a batch file by using the
   %errorlevel% variable, for example.
   SoundVolumeView.exe /GetPercent Speakers
   echo %errorlevel%

   It's recommended to use the Get commands with the console version of
   this tool (SoundVolumeCommandLine), because this technique doesn't
   work well with GUI programs.
2. Use the combination of GetNir tool and SoundVolumeView to send the
   desired value to stdout.
   For example, the following command sends to stdout the current sound
   volume (in percent) of a device that its name is 'Speakers':
   SoundVolumeView.exe /stab "" | GetNir "Volume Percent" "Name=Speakers
   && Type=Device"

   The following command sends to stdout the current mute status (From
   the 'Muted' column) of the device that its friendly name is Realtek
   High Definition Audio\Device\Speakers\Render:
   SoundVolumeView.exe /stab "" | GetNir "Muted"
   "Command-LineFriendlyID='Realtek High Definition
   Audio\Device\Speakers\Render'"



Command-Line Options
====================

You can use the command-line options below to change the volume level and
mute/unmute status of every sound component on your system.
In the [Name] parameter , you can specify one of the following fields:
* The name of the item, as appeared under the 'Name' column. (If you
  have multiple items with identical name, you should use the ID field.)
* The ID of the item, as appeared under the 'Item ID' column.
* The ID of the item, as appeared under the 'Command-Line Friendly ID'
  column (This ID is generated by SoundVolumeView and it's designed to be
  more friendly than the 'Item ID' column). For Command-Line Friendly ID,
  you can also use wildcard, for example: USB*\Device\Speakers\Render
* You can also specify only a part of the 'Name' or 'Item ID'. For
  example, if the device name is 'Speakers1', specifying 'Speakers' will
  also work.
* For sound devices (Type = 'Device'), you can also use the value
  specified under the 'Device Name' column.
* For application items (type = 'Application), you can also specify the
  process filename, (for example: firefox.exe) or the process ID (for
  example: 3271).
* You can specify 'AllAppVolume' to change the volume of all
  applications at once. For example, in order to set the volume of all
  applications to 100%:
  SoundVolumeView.exe /SetVolume AllAppVolume 100
* You can specify 'Focused' to change the volume of focused application.
* You can specify 'FocusedName' to change the volume of all instances
  of focused application.
* You can specify "DefaultCaptureDevice" and "DefaultRenderDevice" in
  order to refer the default Console render/capture device. For default
  Communications device, you can specify DefaultCaptureDeviceComm and
  DefaultRenderDeviceComm, and for default Multimedia device you can
  specify DefaultRenderDeviceMulti and DefaultCaptureDeviceMulti.
* You can specify multiple commands in the same command-line, for
  example:
  SoundVolumeView.exe /Unmute "Speakers" /SetVolume AllAppVolume 100



/GetPercent [Name]
Returns the current volume level in percent, multiplied by 10, for using
in scripts and batch files.
It's recommended to use this command with the console version of this
tool (SoundVolumeCommandLine)

Example:
SoundVolumeView.exe /GetPercent Speakers
echo %errorlevel%


/GetMute [Name]
Returns the current Mute status. (1 = Muted, 0 = Not Muted)
It's recommended to use this command with the console version of this
tool (SoundVolumeCommandLine)

/GetPercentChannel [Name] [Channel Number]
Returns the current volume level of specific channel in percent,
multiplied by 10. In the [Channel Number] parameter you should specify 0
for the first channel, 1 for the second channel, and so on...
It's recommended to use this command with the console version of this
tool (SoundVolumeCommandLine)

/GetDecibel [Name]
Returns the current volume level in decibel, multiplied by 1000.
It's recommended to use this command with the console version of this
tool (SoundVolumeCommandLine)

Example:
SoundVolumeView.exe /GetDecibel Speakers
echo %errorlevel%


/GetDecibelChannel [Name] [Channel Number]
Returns the current volume level of specific channel in decibel,
multiplied by 1000. In the [Channel Number] parameter you should specify
0 for the first channel, 1 for the second channel, and so on...
It's recommended to use this command with the console version of this
tool (SoundVolumeCommandLine)

/GetColumnValue [Name] [Column Name]
Sends the value of the specified column to stdout. The [Column Name] is
the exact name of the column displayed in the GUI. Optionally, you can
omit the space characters from the column name (e.g: "DeviceState"
instead of "Device State")

Example:
The following command shows the state of the device that its Command-Line
Friendly ID is 'Realtek High Definition Audio\Device\Speakers\Render':
SoundVolumeView.exe /GetColumnValue "Realtek High Definition
Audio\Device\Speakers\Render" "Device State" | more

Be aware that the '| more' section is needed for viewing the output of
GUI application inside a command-prompt window. It's not needed if you
use the console version of this tool (SoundVolumeCommandLine).

/SetVolume [Name] [Volume]
Set the sound volume of the specified item. The [Volume] is a number
between 0 and 100.

/SetVolumeDecibel [Name] [Volume]
Set the sound volume of the specified item. The [Volume] is in decibels.

/ChangeVolumeDecibel [Name] [Volume]
Increase/decrease the sound volume of the specified item. The [Volume] is
in decibels.

/SetVolumeChannels [Name] [Volume Channel 1] [Volume Channel 2] ...
Set the sound volume of every channel separately. The [Volume Channel X]
is a number between 0 and 100, or '*' if you don't want to change the
volume of this channel.
You can use this command to set the audio balance of device or
application. If you have left and right channels, 0 is usually the left
channel and 1 is the right channel.

/SetVolumeChannelsDecibel [Name] [Volume Channel 1] [Volume Channel 2] ...
Only for subunit and device items. Set the sound volume of every channel
separately. The [Volume Channel X] is the volume in Decibels , or '*' if
you don't want to change the volume of this channel.

/ChangeVolume [Name] [Volume]
Changes the volume of the specified item. The [Volume] is a number
between -100 and 100, which specifies the percent of volume level to
increase (positive number) or decrease (negative number).

/ChangeVolumeChannel [Name] [Channel Number] [Volume]
Changes the channel volume of the specified item. In the [Channel Number]
parameter you should specify 0 for the first channel, 1 for the second
channel, and so on...
The [Volume] is a number between -100 and 100, which specifies the
percent of volume level to increase (positive number) or decrease
(negative number).
You can use this command to set the audio balance of device or
application. If you have left and right channels, 0 is usually the left
channel and 1 is the right channel.

/Mute [Name]
Mutes the volume of the specified item.

/Unmute [Name]
Unmutes the volume of the specified item.

/Disable [Name]
Disables the specified device

/Enable [Name]
Enables the specified device

/DisableEnable [Name]
Switches the specified device between active and disabled state.

/Switch [Name]
Switches the volume of the specified item between mute and unmute state.

/SetDefault [Name] [Default Type]
Sets the default device.
The [Default Type] parameter specifies one of the following values:
0 - Console
1 - Multimedia
2 - Communications
all - Set all default types (Console, Multimedia, and Communications)

/SwitchDefault [Name1] [Name2] [Default Type]
Switch between 2 default devices.
The [Default Type] parameter specifies one of the following values:
0 - Console
1 - Multimedia
2 - Communications
all - Set all default types (Console, Multimedia, and Communications)

/SetAppDefault [Name] [Default Type] [Process Name/ID]
Allows you to set the default render/capture device for specfic
application. This option is available only on Windows 10, starting from
Windows 10 April 2018 Update.
The [Name] parameter specifies the device name. If you want to set the
application back to the system default device, you should specify
DefaultCaptureDevice or DefaultRenderDevice as the device name.
The [Default Type] parameter specifies one of the following values:
0 - Console
1 - Multimedia
2 - Communications
all - Set all default types (Console, Multimedia, and Communications)
In the process paramater you can specify the process name (e.g:
firefox.exe) or process ID (e.g: 1524)

Examples:
SoundVolumeView.exe /SetAppDefault "High Definition Audio
Device\Device\Speakers\Render" 1 "chrome.exe"
SoundVolumeView.exe /SetAppDefault DefaultRenderDevice 0 firefox.exe
SoundVolumeView.exe /SetAppDefault "High Definition Audio
Device\Device\Speakers\Render" all vlc.exe

/SetDefaultFormat [Device Name] [Bits Per Sample] [Sample Rate - Hertz]
{Number Of Channels}
Sets the default format of the device. For example: The following command
sets the default format of the device to '24 bit, 192000 Hz(Studio
Quality)':
SoundVolumeView.exe /SetDefaultFormat "Realtek High Definition
Audio\Device\Speakers\Render" 24 192000

Another example: The following command sets the default format of the
device to '4 channel,24 bit, 48000 Hz(Studio Quality)':
SoundVolumeView.exe /SetDefaultFormat "Speakers" 24 48000 4

/SaveDeviceFormat [Device Name] [Filename]
Saves the data of the current default format of the specified device into
the specified filename. Later, You can load back the same format with the
/LoadDeviceFormat command.
You should use this command (together with /LoadDeviceFormat) if you have
formats that cannot be set with the /SetDefaultFormat command.

Example:
SoundVolumeView.exe /SaveDeviceFormat "Realtek High Definition
Audio\Device\Speakers\Render" "c:\temp\Speakers1.dat"

/LoadDeviceFormat [Device Name] [Filename]
Sets the default format of the device according to the format data you
previously saved with the /SaveDeviceFormat command. You can use this
command to set the default format if you cannot do it with the
/SetDefaultFormat command.

Example:
SoundVolumeView.exe /LoadDeviceFormat "Realtek High Definition
Audio\Device\Speakers\Render" "c:\temp\Speakers1.dat"

/SetSpeakersConfig [Device Name] [Channel Mask] [Optional Speakers] [Full
Range Speakers]
Sets the desired speakers configuration (Stereo, Quadraphonic, 5.1
Surround, 7.1 Surround, and so on..).
The [Channel Mask], [Optional Speakers] and [Full Range Speakers]
parameters are interger values that represent the speakers configuration.
You can use Hexadecimal numbers in these parameters by specifying '0x'
prefix.

You don't have to deeply understand the meaning of these values. Simply
set the desired speakers configuration from the user interface of
Windows, and then copy the 3 values from the 'Speakers Config' column.

Here's some examples:
Set the speakers configuration to Stereo (With all speakers selected) :
SoundVolumeView.exe /SetSpeakersConfig "Realtek High Definition
Audio\Device\Speakers\Render" 0x3 0x3 0x3


Set the speakers configuration to Quadraphonic (With all speakers
selected):
SoundVolumeView.exe /SetSpeakersConfig "Realtek High Definition
Audio\Device\Speakers\Render" 0x33 0x33 0x33


Set the speakers configuration to 5.1 Surround (With all speakers
selected):
SoundVolumeView.exe /SetSpeakersConfig "Realtek High Definition
Audio\Device\Speakers\Render" 0x3f 0x3f 0x3f

/SetSpatial [Device Name] [Spatial Sound Format]
Sets the 'Spatial sound format' of the specified sound device on Windows
10.
In the [Spatial Sound Format] parameter you can specify the full name of
the spatial sound format (e.g: Windows Sonic For Headphones), partial
name (e.g: Windows Sonic), or the GUID of the spatial sound format (e.g:
{b53d940c-b846-4831-9f76-d102b9b725a0} ).

If you want to disable the spatial sound format, simply use empty string
("")

Examples:
SoundVolumeView.exe /SetSpatial "High Definition Audio
Device\Device\Speakers\Render" "{b53d940c-b846-4831-9f76-d102b9b725a0}"
SoundVolumeView.exe /SetSpatial "High Definition Audio
Device\Device\Speakers\Render" "Windows Sonic For Headphones"
SoundVolumeView.exe /SetSpatial "High Definition Audio
Device\Device\Speakers\Render" "Windows Sonic"
SoundVolumeView.exe /SetSpatial "High Definition Audio
Device\Device\Speakers\Render" ""

/SetBooleanFxProperty [Device Name] [Property ID] [0 | 1 | 2]
Allows you to turn on/off different options of a device, like 'Loudness
Equalization', 'Headphone Virtualization', 'Voice Cancellation', and
others.

You can use one of the following values to turn on/off the specified
property:
0 - Turn Off
1 - Turn On
2 - Switch between on/off state.

Here's a list of some property IDs that you can use with this command:
Loudness Equalization - "{E0A941A0-88A2-4df5-8D6B-DD20BB06E8FB},4"
Headphone Virtualization - "{e0a941a0-88a2-4df5-8d6b-dd20bb06e8fb},3"
Voice Cancellation - "{4b361010-def7-43a1-a5dc-071d955b62f7},3"
Pitch Shift - "{9cc064e5-7fdc-4f03-9994-f24d4908aa26},1"
Equalizer - "{4b361010-def7-43a1-a5dc-071d955b62f7},5"
Environment - "{4b361010-def7-43a1-a5dc-071d955b62f7},1"
Virtual Surround - "{e0a941a0-88a2-4df5-8d6b-dd20bb06e8fb},2"

Examples:
SoundVolumeView.exe /SetBooleanFxProperty "Realtek High Definition
Audio\Device\Speakers\Render" "{E0A941A0-88A2-4df5-8D6B-DD20BB06E8FB},4" 1
SoundVolumeView.exe /SetBooleanFxProperty "Realtek High Definition
Audio\Device\Speakers\Render" "{e0a941a0-88a2-4df5-8d6b-dd20bb06e8fb},3" 2

/SetListenToThisDevice [Name] [0 | 1]
Sets the 'Listen to this device' value (For recording devices only).
0 = No, 1 = Yes.
Example: SoundVolumeView.exe /SetListenToThisDevice "Microphone" 1

/SetPlaybackThroughDevice [Recording Device] [Playback Device]
Sets the 'Playback through this device' value.
Example: SoundVolumeView.exe /SetPlaybackThroughDevice "Microphone"
"{0.0.0.00000000}.{7747b192-73b2-47d3-a2c0-168e94af7f9e}"

/SetAllowExclusive [Name] [0 | 1]
Sets the 'Allow applications to take exclusive control of this device'
option for the specified device.
0 = No, 1 = Yes.
Example: SoundVolumeView.exe /SetAllowExclusive "Realtek High Definition
Audio\Device\Speakers\Render" 1

/SetExclusivePriority [Name] [0 | 1]
Sets the 'Give exclusive mode applications priority' option for the
specified device.
0 = No, 1 = Yes.
Example: SoundVolumeView.exe /SetExclusivePriority "Realtek High
Definition Audio\Device\Speakers\Render" 1

/RunAsAdmin
Runs SoundVolumeView as administrator.

/WaitForItem [Number Of Seconds]
Instructs SoundVolumeView to wait the specified number of seconds until
the sound item appears. You can use this feature to change the
application volume for applications that are not running at this moment.
For example, if you want to mute the sound of Chrome Web browser and it's
not running at this moment:
SoundVolumeView.exe /Mute chrome.exe /WaitForItem 5000

In the above example, SoundVolumeView will wait up to 5000 seconds (The
process will remain in memory). If during the 5000 seconds period you run
the Chrome Web browser, SoundVolumeView will detect it, mute the sound of
Chrome application and then the process of SoundVolumeView will be
terminated. You can specify 0 in [Number Of Seconds] if you want to wait
infinitely.

/SaveProfile [Filename]
Saves the current sound settings into the specified profile filename.

/LoadProfile [Filename]
Restores the sound settings from the specified profile filename.

Here's some examples:
* SoundVolumeView.exe /GetPercent "Speakers"
* SoundVolumeView.exe /GetPercentChannel "Speakers" 0
* SoundVolumeView.exe /GetMute "Speakers"
* SoundVolumeView.exe /SetVolume
  "{0.0.0.00000000}.{a77a09b2-1ec6-49c3-860a-68945904a2f1}" 15
* SoundVolumeView.exe /SetVolume "Speakers" 22.5
* SoundVolumeView.exe /SetVolume "High Definition Audio
  Device\Device\Speakers" 50
* SoundVolumeView.exe /SetVolume "USB*\Device\Speakers\Render" 70
  /SetVolume "High Definition Audio Device\Device\Speakers" 35
* SoundVolumeView.exe /SetVolume AllAppVolume 100
* SoundVolumeView.exe /SetVolumeDecibel "Speakers" -11
* SoundVolumeView.exe /ChangeVolume "Front Green In" -10
* SoundVolumeView.exe /ChangeVolume
  "{2}.\\?\hdaudio#func_01&ven_10ec&dev_0889&subsys_1458a002&rev_1000#4&382
  8eb94&0&0201#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\singlelineouttopo/000
  2000c&" 5
* SoundVolumeView.exe /ChangeVolumeChannel "vlc.exe" 0 -20
* SoundVolumeView.exe /Mute "singlelineouttopo/0002000c&"
* SoundVolumeView.exe /Mute "DefaultRenderDevice"
* SoundVolumeView.exe /Mute "System Sounds"
* SoundVolumeView.exe /SetVolumeChannels "Front Pink In" 45 55
* SoundVolumeView.exe /SetVolumeChannels "Front" * 60 * 40
* SoundVolumeView.exe /SetVolumeDecibel "Microphone Boost" 20
* SoundVolumeView.exe /ChangeVolumeDecibel "Microphone Boost" 10
* SoundVolumeView.exe /Mute "Firefox.exe"
* SoundVolumeView.exe /Mute "Firefox.exe" /WaitForItem 3600
* SoundVolumeView.exe /SetVolume "chrome.exe" 75
* SoundVolumeView.exe /SetVolumeChannels "chrome.exe" 50 100
* SoundVolumeView.exe /Unmute "VLC media player"
* SoundVolumeView.exe /Switch "C:\Program Files\Firefox.exe"
* SoundVolumeView.exe /Switch 3217
* SoundVolumeView.exe /Switch Focused
* SoundVolumeView.exe /Switch FocusedName
* SoundVolumeView.exe /Switch "Realtek High Definition
  Audio\Device\Speakers"
* SoundVolumeView.exe /DisableEnable Speakers
* SoundVolumeView.exe /SetDefault
  "{0.0.0.00000000}.{a77a09b2-1ec6-49c3-860a-68945904a2f1}" 0
* SoundVolumeView.exe /SetDefault
  "{0.0.0.00000000}.{a77a09b2-1ec6-49c3-860a-68945904a2f1}" all
* SoundVolumeView.exe /SetDefault "DENON-AVAMP" 1
* SoundVolumeView.exe /SwitchDefault
  "{0.0.0.00000000}.{a77a09b2-1ec6-49c3-860a-68945904a2f1}"
  "{0.0.0.00000000}.{7747b192-73b2-47d3-a2c0-168e94af7f9e}" all
* SoundVolumeView.exe /SetAppDefault
  "{0.0.0.00000000}.{a77a09b2-1ec6-49c3-860a-68945904a2f1}" all
  "myapp.exe"
* SoundVolumeView.exe /SetAppDefault DefaultCaptureDevice 1 1952
* SoundVolumeView.exe /SaveProfile "C:\Temp\Profile1.spr"
* SoundVolumeView.exe /LoadProfile "C:\Temp\Profile2.spr"

You can also use the following command-line parameters to export the list
of all sound items info a file:

/stext <Filename>
Save the list of all sound items into a regular text file.

/stab <Filename>
Save the list of all sound items into a tab-delimited text file.

/scomma <Filename>
Save the list of all sound items into a comma-delimited text file (csv).

/stabular <Filename>
Save the list of all sound items into a tabular text file.

/shtml <Filename>
Save the list of all sound items into HTML file (Horizontal).

/sverhtml <Filename>
Save the list of all sound items into HTML file (Vertical).

/sxml <Filename>
Save the list of all sound items into XML file.

/sjson <Filename>
Save the list of all sound items into JSON file.

/Columns <Comma Delimited Columns List>
Allows you to set the columns to display or the columns to export from
command-line. You have to specify the column names, delimited by comma,
for example:
SoundVolumeView.exe /scomma c:\temp\sound-items.csv /Columns
"Name,Command-Line Friendly ID,Volume Percent"

You can also specify the column names without space characters, for
example:
SoundVolumeView.exe /Columns "Name,Command-LineFriendlyID,VolumePercent"

/SaveFileEncoding [0 - 3]
Set the character encoding for the other save commands. 0 = Default, 1 =
ANSI, 2 = UTF-16, 3 = UTF-8.
For example:
SoundVolumeView.exe /SaveFileEncoding 2 /scomma "c:\temp\sound_items.csv"



Translating SoundVolumeView to other languages
==============================================

In order to translate SoundVolumeView to other language, follow the
instructions below:
1. Run SoundVolumeView with /savelangfile parameter:
   SoundVolumeView.exe /savelangfile
   A file named SoundVolumeView_lng.ini will be created in the folder of
   SoundVolumeView utility.
2. Open the created language file in Notepad or in any other text
   editor.
3. Translate all string entries to the desired language. Optionally,
   you can also add your name and/or a link to your Web site.
   (TranslatorName and TranslatorURL values) If you add this information,
   it'll be used in the 'About' window.
4. After you finish the translation, Run SoundVolumeView, and all
   translated strings will be loaded from the language file.
   If you want to run SoundVolumeView without the translation, simply
   rename the language file, or move it to another folder.



License
=======

This utility is released as freeware. You are allowed to freely
distribute this utility via floppy disk, CD-ROM, Internet, or in any
other way, as long as you don't charge anything for this and you don't
sell it or distribute it as a part of commercial product. If you
distribute this utility, you must include all files in the distribution
package, without any modification !



Disclaimer
==========

The software 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.



Feedback
========

If you have any problem, suggestion, comment, or you found a bug in my
utility, you can send a message to [email protected]

tools\SoundVolumeView.chm

tools\SoundVolumeView.exe

md5: 32A27FF6B04649A2C222E212A44295FF | sha1: 4857372410BD49BB3788C59A3D8106D72AF37B42 | sha256: C3C3BDCAD8541C98CE7D0C929C32BA003125FFCFF42907BD4502221779BE5B18 | sha512: D9F7859052BF15FFA607800C38BFBB57C48C20E21470C0A336C09A952674CF20EDA8BF54689BE4E05B9FCEDEAA61A132D94FC5B9B343BE365758754163DA3370

tools\sysexp-x64.zip

md5: DAD230611ED1C0D804F4D3BAD74945A4 | sha1: 78DE5E755C055E88FBB10CA70A40EE66F32DB495 | sha256: 2B20CABAE2168A81501000510C45E2AE0B13FF97EDF8B31AC984D384628AD986 | sha512: DC4DE92DA5112E049E0EA674DFFB8F82B1320F15E348B4138398055B45530117900CF17A3CA60941A9CEBCAC47C6045EBA54461F77972755D9CFFC7F58086F4F

tools\sysexp.chm

tools\sysexp.exe

md5: EF80C5995837616C0B72A43FBE36CF13 | sha1: F7716A1F70BAA55307CD893D59E519F29AACE454 | sha256: 5154EA9EA77CC86A5709C5D79C442DAFC22893866DD2B9335B4434E88692101B | sha512: 2BB7B302B1ADBFD1FC23A831DA74D5F58C61C28CC8406970E26E555620C5AF825CDF18A96E097CD6CAF7A31D8E9C2E98FBDB58EE989F2DB2B849B2666E41B78F

tools\sysexp.zip

md5: AC7980FD2D23D4B3A1D8676AFC84DE1A | sha1: 3E6CC42078EE0067CF38BD711B2F18F668515ED8 | sha256: 7B1E5E8A3A4432D82064FAC051ED2415D2A6F243A778142AFB89F90BC408F77B | sha512: B7B335B33EF9A8CEDF45AD4C6452AA695E90DDDE38A7A96209184747C3A243782BF65246733BF013636D625E269FAB50E95341DAD5DB3BC6895DBFF4CE236B1B

Virus Scan Results

sysexp.exe (5154ea9ea77c) - ## / 70
SoundVolumeView.exe (c3c3bdcad854) - ## / 64
sysexp-x64.zip (2b20cabae216) - ## / 63
sysexp.portable.1.77.0.nupkg (31e7010bc3ea) - ## / 64
sysexp.zip (7b1e5e8a3a44) - ## / 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
SysExporter (Portable) 1.77.0	15	Monday, April 22, 2024	Approved
SysExporter (Portable) 1.76	825	Friday, September 29, 2017	Approved
SysExporter (Portable) 1.75	481	Thursday, June 2, 2016	Approved
SysExporter (Portable) 1.72	426	Sunday, June 14, 2015	Approved

Release Notes

https://www.nirsoft.net/utils/sysexp.html

Dependencies

This package has no dependencies.

Discussion for the SysExporter (Portable) Package

Ground Rules:

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

Resources

Events

Courses

1,747

15

22 Apr 2024

SysExporter (Portable)

SysExporter (Portable) 1.77.0

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

SysExporter (Portable)

Package-specific issue

Ground Rules: