Step 1: Review Your Packages

Step 2: Choose Your Integration Method

Step 3: Copy Your Script or Download Config

Option 1: Copy Script

Option 2: Download Config

Step 4: Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

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

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

Option 2: Internalized Package (Reliable, Scalable)

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

Step 5: Copy Your Script

See options you can pass to upgrade.

See best practices for scripting.

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

### c. Other Requirements ###

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

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

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

## 2. TOP LEVEL VARIABLES ##

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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

- name: Install and Configure Chocolatey
  hosts: all

## 2. TOP LEVEL VARIABLES ##
  vars:

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

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

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

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

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

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

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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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

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

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

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

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

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

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

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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

chocolatey_feature 'useBackgroundService' do
  action :enable
end

chocolatey_feature 'useBackgroundServiceWithNonAdministratorsOnly' do
  action :enable
end

chocolatey_feature 'allowBackgroundServiceUninstallsFromUserInstallsOnly' do
  action :enable
end

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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


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

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

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

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

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


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


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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Need Help? View our docs or file an issue.

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

Current Version	New Version

Downloads:

159,097

Downloads of v 6.1.1:

4,060

Last Update:

21 Apr 2025

Package Maintainer(s):

Software Author(s):

Paolo Salvatori

Tags:

servicebusexplorer azure azureservicebus servicebus explorer eventhub queue subscription relay notificationhub

Service Bus Explorer

6.1.1 | Updated: 21 Apr 2025

Downloads:

159,097

Downloads of v 6.1.1:

4,060

Maintainer(s):

Software Author(s):

Paolo Salvatori

Tags:

servicebusexplorer azure azureservicebus servicebus explorer eventhub queue subscription relay notificationhub

Service Bus Explorer 6.1.1

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

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Hide Checks

Validation Testing Passed

Verification Testing Passed

Details

Scan Testing Resulted in Flagged 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 Service Bus Explorer, run the following command from the command line or from PowerShell:

To upgrade Service Bus Explorer, run the following command from the command line or from PowerShell:

To uninstall Service Bus Explorer, 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 servicebusexplorer --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 servicebusexplorer -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 servicebusexplorer -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 servicebusexplorer
  win_chocolatey:
    name: servicebusexplorer
    version: '6.1.1'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'servicebusexplorer' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '6.1.1'
end

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


cChocoPackageInstaller servicebusexplorer
{
    Name     = "servicebusexplorer"
    Version  = "6.1.1"
    Source   = "INTERNAL REPO URL"
}

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


package { 'servicebusexplorer':
  ensure   => '6.1.1',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

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

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Package Approved

This package was approved as a trusted package on 21 Apr 2025.

Description

The Service Bus Explorer allows users to connect to a Service Bus namespace and administer messaging entities in an easy manner. The tool provides advanced features like import/export functionality or the ability to test topic, queues, subscriptions, relay services, notification hubs and events hubs.

Files

tools\Azure.Core.Amqp.dll

md5: 806E85BDE8042997D50A8718BC199F4A | sha1: 7ED8EAC2141D98E2CE15DE99A911ADDB17ED6C97 | sha256: D53D832629B76FCAE7F0E0352788C43C79E13480247DBA11E37961B60E52C142 | sha512: 68E256114C21FB9858000C7BF540746980026E3A995D1E8BBD5B6F1A7E04371A617F3AA4A88E203B58F73A1234CCCB5A3A6E4969E17B774CC9A67801F5E8EAE7

tools\Azure.Core.dll

md5: BA78AB7C147FDABED9AF185239A23AA3 | sha1: 0FC69EF4AA5C543A2FF84AE20D0C0FF3FAF39F47 | sha256: 374771EBF3B6C5367C52D3A1B42DABC288C143C9D5A8AF144FE6283EF91C8634 | sha512: 37A8C85D69EE4C33A214685165B881A1245B18566F89922255909696A8EA8DDA81552E57A89F700AEC2D36DA5330261E9AB4B1468CBDD1CFB51779020415F323

tools\Azure.Identity.dll

md5: 32BA0F62189400ACCEA8EDC67FD5CD4F | sha1: 9C577067B676BB38AAB038DD21982BC3B12D6CA9 | sha256: 16F3067074F06485835E750D899BEC5174F317FED3EC77C199C9B8FE1B06929D | sha512: 3B51999C05E181AD4D9523D84AAE3FA3FA5AF119F9A7CFBD9F61085E487D8D1C2783A23A228458023529AB7C27696A881162FB916CE149E2DA4C3915074CFD03

tools\Azure.Messaging.EventGrid.dll

md5: 027B3A8A056AC0520D47AF3383CB478B | sha1: 6EBDDBF278B4D729A10A342C4CCA9BC364694697 | sha256: C88B4DA2BAF724CF333A90312C9CF702E56511BE459E47ED054D8880280043E9 | sha512: 0894B3E533D1BFA93D5B73F3A92AA576DD678F0E11DE20A95B42265BE5C2B0D2E623051351E4B90040149AD1AF6A13CCD94BC05A603B452C59CF3AD6B651540B

tools\Azure.Messaging.EventHubs.dll

md5: 9E421C4571283EF78D67FF84B22576D2 | sha1: 750E633F4C1BDCF516C6EEB5F7D98B17B3234F35 | sha256: 512F3855EEDE83EA659F10F7E76F86BA228B3AFEB3517814C2EA1558CA57C16C | sha512: 575FD222C428CF66145550FEFA91C1E23870D085D1F7EB017A7CD8A63249865E09F90FBF9201E682069E9DC4B429907D281AA38DDFAD46541FAE8952F9312948

tools\Azure.Messaging.ServiceBus.dll

md5: 7A32A7B5253915A5FADAE1EF2D985792 | sha1: A8419B8C291754AB4BC10A13528B5E075A71F772 | sha256: 8313A604596F53B2E0478BC8265431AC7701CA7AB1D9A242B71DD24E2D9F2C0D | sha512: BD1C7CA4FBA9E17EB1E14183442F5450714D93B7BDD6D67454158FA6D3C555CEBA7175968A09FF7BDDA370C9B00CF63F66AB3A5E1E253F185E1000DD4CF721E8

tools\Azure.ResourceManager.dll

md5: F09B509C34C5F229285473CFF74107A8 | sha1: F9DC3B4BF7AD488E1A36F507708E660FB54365EF | sha256: 1307BA9076BCC38AE95EF7B6774C0B299D87F8A6A2F733B5D6B65B360648E7BE | sha512: F94197F27FE67950FB845226067A7B4CFCE67A7F4994EDBD8524E1398D3350E87F870A2C9A2563E200D2F8CEBCA48AC8E63101707565E2C27E8672FFB23D951E

tools\Azure.ResourceManager.EventGrid.dll

md5: 8B1E25E1EC4916FEE196CBD0FDF45350 | sha1: B3855476E4FC8E13ECF3C775EA96B6BEB88B9C44 | sha256: 2CC0A1C1BCD592E31CD39A0994A3EEBF9B343EDDDCE00E8BA35F21AE442907DD | sha512: 1BDA3B116C244C9332AD7C0242B1EAFC95ABF393BD24324B9612B598D87EB594C98C886AF8EF4D38C4AEF3CDED284253DE2CB2D8CCFA8D47A52EBD3FAB18966E

tools\CommandLine.dll

md5: 2F345B6D207489E52DB3F85C2E4E617D | sha1: D0CD77AA88B8ED0AE5F07A8132EACA857DEA7795 | sha256: 2135B40FA819E58CF1942453E4409BFDEA2BE631077A354B878DE8402BE7E026 | sha512: 24AD3B3620E5E093EA57C1BEC486379853D625DBF962210B2DEB823115A45F9EC4083B6D4BB69610A9DAE4B6076284C11E3663430DB4EA739224E6DE93D88E8D

tools\FastColoredTextBox.dll

md5: 390A4781AA9913C1AC99CC117693E08F | sha1: 58FC4B2B5E938B0B68B5A7D271E1777211199C39 | sha256: 4A8EF87E29D8DF3D7624674E0FD31BF5E35194858EE75D9DF1C1D1654C82C8E6 | sha512: E134BD993A12213087053A5FB7D56FE10C0524BBDB6D4C8DD0DB3DFF7E9B3342E763FDE64A731996D048BF884A51AB344B8ED37177801DB5742FA8ECBD3E211B

tools\LICENSE.txt

The MIT License (MIT)

Copyright (c) 2015 Microsoft Azure

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

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

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

tools\Microsoft.Azure.Amqp.dll

md5: A8D1B4AA35CC4F8B297750F330067B2E | sha1: F33A390F5EFA29D5AE073D35D0A3994F0B0319B4 | sha256: 264F8D39091CD9D90A7289396173549AA080B361599CC15E0743E26DBDBBE3A6 | sha512: 5932BF21D672F296946752FB56382032DC513F6FBC09CF1384B3E1769F064D0A6E66127CDB26726ADA2B56ACA8FB4D57FF3904EDCC1192AE330A15B7A7F9B619

tools\Microsoft.Azure.NotificationHubs.dll

md5: C621424788313EE79E98671B276F9976 | sha1: F62622544874AE96218CE1304203F9286EB4E0DB | sha256: 053C655945285CB02D1709F8934E666D9F5140163057534E01881A721C002DA6 | sha512: 8AD3BAABEB2CE64459B14567F0D55BB611796E074C7CE7A178181372E9C344145E9EE91289F1BC09361D75A31E1312FA9171164346EE9D7ACEF5BA7DEAD7F0AF

tools\Microsoft.Azure.Relay.dll

md5: 20CE76A7781AD61CF4585DD6BD1E1AC4 | sha1: 257DE8FD8AB5FD1FEFF594EB7A9BFFF36C0FC058 | sha256: B0638BD879801186F38918BAE6C6EFA839C658535D0731B2C6EAB5EAB9819ED0 | sha512: 538ECE07C59CBFA7892843963A421BBC78F100D25DE75F5C28C5E9364900DF985B527583A9BC7C3CF608552AAB18B2EE8D2177652751A3EE76F0043496E9224C

tools\Microsoft.Azure.Services.AppAuthentication.dll

md5: 0ECCCB70C4D75D23E95DC3911FB4C5C8 | sha1: FA3A504A0F3F5FA7D30E0D5CF5E9161B0EDE542C | sha256: E999D795012F9C42C8714FDDADE702706FD0B6B4E4F7E87D88D673E39800CC12 | sha512: 2C8464FCCDC2553929E51D760E899EDE2425E270E82231F8F2390A65488C3D8E0586C6E94F97EBB9D2CF48A1525F9C05EE3F42C39784BD31355BCC9B671EAC23

tools\Microsoft.Bcl.AsyncInterfaces.dll

md5: 48EFE61D6CA3054309907B532D576D2A | sha1: F36403AABB16540C93FB35245EC0B4E435628AAE | sha256: 295AF2142D9214F3FD84EAFE4778DCA119BE7E0229F14B6BA8D5269C2F1E2E78 | sha512: 778E7C4675D8FDE9E083230213D2EFA19AA6924FE892ED74FA1EA2EC16743BB14B99B51856E75EAEF632D57BE7F36DD1BC7CE39A7C2B0435B2F3211BB19836A3

tools\Microsoft.Identity.Client.dll

md5: 375865A6F66C9C5BE8E3E9A1DB04C3A9 | sha1: 291A5B631DA5520B805D63AE2B6DBD4311F415C5 | sha256: 7CDC22BB95DF2538D427682B098C9CF84D0E3FF63F1211EF3503B2C0F6A95747 | sha512: 2D688F20D4ECA35B50D90870C22A15866EF79ED71EC05ACAA28A89EA1E115A1FC2323AF9168389611393A7B53643DF169740AC2A6963D87CFD09CBEA3D9D2B0A

tools\Microsoft.Identity.Client.Extensions.Msal.dll

md5: E3DC2C3F5C09E76FB1484A9C8B2328D6 | sha1: E365760C4E541777EA8404EDCE6F8D8CF655C0AB | sha256: 0768CC69604C6F6CC40549826DE9BD4A8D731522180376B2CEB80DB3B7B45081 | sha512: 27739A9D7B9AB6D6641FA90451607B69564A97991A65D3437660B5D2679D1C845D232BCC47C65D79FF2109502E75EB172DE1E973180B20F90937AC264971BF13

tools\Microsoft.IdentityModel.Abstractions.dll

md5: A11BD4DA1799D6983A662073CE40281F | sha1: 6E85ACA84BB83FD356A5F3018351A3152C696CC1 | sha256: D3265F1CAB1188EBAC29C78E0F114FF3A0B2701C8A2F5442BD4080AFE92519B0 | sha512: 424BDB2DB612DA935C570FED005DE6CC2B0BB718C0E9C9C6942B0658169A41AC0EA1EA24A4542F7181C4AB102D3CA9190DE695026304C834987E32417EF82825

tools\Microsoft.IdentityModel.Clients.ActiveDirectory.dll

md5: 82B4153A5D552E4731876A145FC3CEEE | sha1: 2FBA5D92D890EA54B2F32FA7BE7E9876672B8B41 | sha256: 9C530971BF1AC091C4200FB1D662FB5B8C388A4D92A418A31C738223A2247E73 | sha512: F14E21425792E4EA398B680971070EFC2A9791D9B3DCBBD5CBCCBB74E9C12236685EDAE125F0382ED5078FB1CB309754A2746175FE5480ADC08256F77781F210

tools\Microsoft.IdentityModel.JsonWebTokens.dll

md5: BCEA3A6F9113DA7C477BD57190793B48 | sha1: AAEF61367418330EF73DF23B5CD7A5A2FB396424 | sha256: F9D1376F30EFBC66AF818F4515AD298A865EDABFB0CB0FF6AEDD8A131B7595DC | sha512: 03F8E3D1465DF73C781B2079B31BE4BB6711E71FD50D5056B8C5CABFF76EB0F008851A81CF4643F26D713A1C2D82A4D5A88B9ACE8AF16BB2ACB7DA1EB30F19B3

tools\Microsoft.IdentityModel.Logging.dll

md5: 274F43F079DB665D1BBBABBF1A1BE712 | sha1: 208E2E7B3C3B915770B095C4AC0FBA6F80281FE9 | sha256: C25BBD7BA62A28424A83CB71470D0A9CBC98538D5601162013B0867E10C52769 | sha512: F7A4294B292FA35574467ED07CB2F797BF74BB30829355078748DBACE668C63F6EFC9092ABAC56A3AE9B97942634A81001F6324BFD1CF003A3BCE61CF9402D95

tools\Microsoft.IdentityModel.Tokens.dll

md5: 9A3A4D037A1624669A2ACF4EA0385492 | sha1: 7F6B09EB08AA9E59F93D216C522E2064D8707BBF | sha256: 43F9FE1CF13A13AA797B69166A073FCD0F675C43EE7F5104DDD7766C38D99E1D | sha512: 2177E289911A9C5D9950E3743987BA31197F892C320B050B20C0C418332F2B0D1DEB0957D982988C5110697843BE52C65BFD468C8E3FF6FE6290BCBA67AFC619

tools\Microsoft.Rest.ClientRuntime.Azure.dll

md5: A363F9824C1808052EA2B18E84A18CE2 | sha1: CD44211AEB0F768D1DD64B466D2C6FE45437A218 | sha256: 08C4FAFACC2498AAD72FC65DD75808CA36D6D19A48D47EB275446EC5C92BCC91 | sha512: F3A36F972AF49BD171911EE17DB9ED24A5217D993358A4AE71043A2CB205B1BEC806BD51F244C0A1A6BD97D56B2EC89EDD96D0667A1A3E01D658F997AA5F3917

tools\Microsoft.Rest.ClientRuntime.dll

md5: 09688DA885C75D87C11D0C9638ED40D6 | sha1: 5614F3CD37F391369BD134A706AA81144655983B | sha256: 08E1D859E575AD7D66BCB9D8B6DEC07CC5A7B909145B07FC4A6703AEBCA33F23 | sha512: 1D68D657381BF6EF433883457E962D7391D2892BD4A39601E7150F2EF02C4FF665E4F6781A7EE5A538AB3111A45A32ADFC738C5525375273EF90640E55E7FD3A

tools\Microsoft.ServiceBus.dll

md5: 5272479304CBFB4DE74D632FAA4F4E55 | sha1: C0537999DF8C8B73E99611639BC691080662D7A1 | sha256: 628E9342A4D4464D9B15FD91AE114F316B782BD6EBB07612EF52080578BB8F9E | sha512: 02B44FE04841115ACAD267AE26CF9AC53D77C2533D83726B58B7F3A1E8B16600EBCBEC21DF8126FA8128FC738150688D3E0883D2CE2819E1E92298EE12A177E7

tools\Newtonsoft.Json.dll

md5: 195FFB7167DB3219B217C4FD439EEDD6 | sha1: 1E76E6099570EDE620B76ED47CF8D03A936D49F8 | sha256: E1E27AF7B07EEEDF5CE71A9255F0422816A6FC5849A483C6714E1B472044FA9D | sha512: 56EB7F070929B239642DAB729537DDE2C2287BDB852AD9E80B5358C74B14BC2B2DDED910D0E3B6304EA27EB587E5F19DB0A92E1CBAE6A70FB20B4EF05057E4AC

tools\ServiceBusExplorer.Common.dll

md5: 1D4FE1ECEDD25E180B81276D226C642E | sha1: DA12E78FC98299F6472FCAE99EA7B27A0B03C382 | sha256: D75E5241AFE4D08B136FF54CB10FD93E63B737AD675309D1520250692F8CFFAA | sha512: 0701956FDB08E2D00E0FDC10BD77CCE2C32E9A2CA5AEC0CD9F0C4EA0C368514D94C8E10C96687A83A3688759219DF4BF6D0141636D5467EE977BF1B9F62D7285

tools\ServiceBusExplorer.Common.pdb

tools\ServiceBusExplorer.EventGridExplorerLibrary.dll

md5: 2CC73BD91FD12B98EB9B47E2790B487D | sha1: 75AD7F1DF66D70604C84AA465B0140B4D42D7419 | sha256: 80EB051D9815C79B930F1ACA26D5E1F871E91BEF08FD0EAC5BFC2D2896A8D2E0 | sha512: 0E8E266A8750EC1C491DD5A2FBDB568F1F7B1BC440EBCFEF41F62FE2A5816534F2B397BA29CBC1C21BFB29077E5AF4164B0D8E0C3051A4D8B8C9F4E1CB851DF8

tools\ServiceBusExplorer.EventGridExplorerLibrary.dll.config

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
</configuration>

tools\ServiceBusExplorer.EventGridExplorerLibrary.pdb

tools\ServiceBusExplorer.EventHubs.dll

md5: F1849559047939F6EFC16B7442C47DF6 | sha1: C0209F70BA9707B117DB6985C1B6E0938CB0D5D1 | sha256: EFA15FB00FFEC4380D4E8EF5742E92924FAFF006614C17E40EADA465CE14E4EC | sha512: 7F631DF8991C78A06E3417B626E264F7D64C36030656589ED40746A677C9D9C6D4880B63B4DECDF4BC4DD61740D3D2BB66D901576FB83358226AB9AE98C4A86B

tools\ServiceBusExplorer.EventHubs.pdb

tools\ServiceBusExplorer.exe

md5: 81F352A0634829E1B839D84CBDCE0A4E | sha1: F8F88AFD25191ED6336A1FC6610549AF4A2BA59B | sha256: 8EB593216E1532BDE26742351B2DBD629A5007617A096B2E79386B5B8E55487E | sha512: 108EC76E527F9BA982E051B508B11084FF4A412D7BBB3572F3F9F7397FC3303BD81CA0E36DE9738F0D700C0FE6EA9940279951B2F0A79BEBDA50FA9DD2D2E48F

tools\ServiceBusExplorer.exe.config

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <configSections>
    <section name="serviceBusNamespaces" type="System.Configuration.DictionarySectionHandler, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
    <section name="brokeredMessageInspectors" type="System.Configuration.DictionarySectionHandler, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
    <section name="eventDataInspectors" type="System.Configuration.DictionarySectionHandler, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
    <section name="brokeredMessageGenerators" type="System.Configuration.DictionarySectionHandler, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
    <section name="eventDataGenerators" type="System.Configuration.DictionarySectionHandler, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
  </configSections>
  <serviceBusNamespaces>
    <add key="SASConnectionString" value="Endpoint=sb://NAMESPACE.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX=" />
  </serviceBusNamespaces>
  <brokeredMessageInspectors>
    <add key="LogBrokeredMessageInspector" value="ServiceBusExplorer.Helpers.LogBrokeredMessageInspector,ServiceBusExplorer.Common" />
    <add key="ZipBrokeredMessageInspector" value="ServiceBusExplorer.Helpers.ZipBrokeredMessageInspector,ServiceBusExplorer.Common" />
  </brokeredMessageInspectors>
  <eventDataInspectors>
    <add key="LogEventDataInspector" value="ServiceBusExplorer.Helpers.LogEventDataInspector,ServiceBusExplorer.Common" />
    <add key="ZipEventDataInspector" value="ServiceBusExplorer.Helpers.ZipEventDataInspector,ServiceBusExplorer.Common" />
    <add key="DeflateEventDataInspector" value="ServiceBusExplorer.Helpers.DeflateEventDataInspector,ServiceBusExplorer.Common" />
  </eventDataInspectors>
  <brokeredMessageGenerators>
    <add key="OnOffDeviceBrokeredMessageGenerator" value="ServiceBusExplorer.Helpers.OnOffDeviceBrokeredMessageGenerator,ServiceBusExplorer.Common" />
    <add key="ThresholdDeviceBrokeredMessageGenerator" value="ServiceBusExplorer.Helpers.ThresholdDeviceBrokeredMessageGenerator,ServiceBusExplorer.Common" />
  </brokeredMessageGenerators>
  <eventDataGenerators>
    <add key="OnOffDeviceEventDataGenerator" value="ServiceBusExplorer.Helpers.OnOffDeviceEventDataGenerator,ServiceBusExplorer.Common" />
    <add key="ThresholdDeviceEventDataGenerator" value="ServiceBusExplorer.Helpers.ThresholdDeviceEventDataGenerator,ServiceBusExplorer.Common" />
  </eventDataGenerators>
  <appSettings>
    <add key="debug" value="true" />
    <add key="connectivityMode" value="AutoDetect" />
    <add key="selectedEntities" value="Queues,Topics,Relays,Event Hubs,Notification Hubs" />
    <add key="encoding" value="UTF8" />
    <add key="showMessageCount" value="true" />
    <add key="saveMessageToFile" value="true" />
    <add key="savePropertiesToFile" value="true" />
    <add key="saveCheckpointsToFile" value="true" />
    <add key="scheme" value="sb" />
    <add key="message" value="&lt;message&gt;Hi mate, how are you?&lt;/message&gt;" />
    <add key="file" value="" />
    <add key="label" value="Service Bus Explorer" />
    <add key="retryCount" value="10" />
    <add key="retryTimeout" value="100" />
    <add key="top" value="10" />
    <add key="receiveTimeout" value="20" />
    <add key="serverTimeout" value="30" />
    <add key="prefetchCount" value="0" />
    <add key="senderThinkTime" value="500" />
    <add key="receiverThinkTime" value="500" />
    <add key="monitorRefreshInterval" value="30" />
    <add key="useAscii" value="true" />
    <add key="subscriptionId" value="XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" />
    <add key="certificateThumbprint" value="XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" />
    <add key="messageDeferProvider" value="ServiceBusExplorer.Helpers.InMemoryMessageDeferProvider,ServiceBusExplorer.Common" />
    <add key="Microsoft.ServiceBus.X509RevocationMode" value="NoCheck" />
    <add key="ClientSettingsProvider.ServiceUri" value="" />
  </appSettings>
  <startup>
    <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.6.2" />
  </startup>
  <system.serviceModel>
    <extensions>
      <!-- In this extension section we are introducing all known service bus extensions. User can remove the ones they don't need. -->
      <behaviorExtensions>
        <add name="connectionStatusBehavior" type="Microsoft.ServiceBus.Configuration.ConnectionStatusElement, Microsoft.ServiceBus, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
        <add name="transportClientEndpointBehavior" type="Microsoft.ServiceBus.Configuration.TransportClientEndpointBehaviorElement, Microsoft.ServiceBus, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
        <add name="serviceRegistrySettings" type="Microsoft.ServiceBus.Configuration.ServiceRegistrySettingsElement, Microsoft.ServiceBus, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
      </behaviorExtensions>
      <bindingElementExtensions>
        <add name="netMessagingTransport" type="Microsoft.ServiceBus.Messaging.Configuration.NetMessagingTransportExtensionElement, Microsoft.ServiceBus,  Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
        <add name="tcpRelayTransport" type="Microsoft.ServiceBus.Configuration.TcpRelayTransportElement, Microsoft.ServiceBus, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
        <add name="httpRelayTransport" type="Microsoft.ServiceBus.Configuration.HttpRelayTransportElement, Microsoft.ServiceBus, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
        <add name="httpsRelayTransport" type="Microsoft.ServiceBus.Configuration.HttpsRelayTransportElement, Microsoft.ServiceBus, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
        <add name="onewayRelayTransport" type="Microsoft.ServiceBus.Configuration.RelayedOnewayTransportElement, Microsoft.ServiceBus, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
      </bindingElementExtensions>
      <bindingExtensions>
        <add name="basicHttpRelayBinding" type="Microsoft.ServiceBus.Configuration.BasicHttpRelayBindingCollectionElement, Microsoft.ServiceBus, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
        <add name="webHttpRelayBinding" type="Microsoft.ServiceBus.Configuration.WebHttpRelayBindingCollectionElement, Microsoft.ServiceBus, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
        <add name="ws2007HttpRelayBinding" type="Microsoft.ServiceBus.Configuration.WS2007HttpRelayBindingCollectionElement, Microsoft.ServiceBus, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
        <add name="netTcpRelayBinding" type="Microsoft.ServiceBus.Configuration.NetTcpRelayBindingCollectionElement, Microsoft.ServiceBus, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
        <add name="netOnewayRelayBinding" type="Microsoft.ServiceBus.Configuration.NetOnewayRelayBindingCollectionElement, Microsoft.ServiceBus, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
        <add name="netEventRelayBinding" type="Microsoft.ServiceBus.Configuration.NetEventRelayBindingCollectionElement, Microsoft.ServiceBus, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
        <add name="netMessagingBinding" type="Microsoft.ServiceBus.Messaging.Configuration.NetMessagingBindingCollectionElement, Microsoft.ServiceBus, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
      </bindingExtensions>
    </extensions>
  </system.serviceModel>
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Resources.Extensions" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-8.0.0.0" newVersion="8.0.0.0" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="Azure.Core" publicKeyToken="92742159e12e44c8" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-1.44.1.0" newVersion="1.44.1.0" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="Azure.Identity" publicKeyToken="92742159e12e44c8" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-1.13.2.0" newVersion="1.13.2.0" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="Microsoft.Azure.Amqp" publicKeyToken="31bf3856ad364e35" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-2.6.0.0" newVersion="2.6.0.0" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="Microsoft.Bcl.AsyncInterfaces" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-13.0.0.0" newVersion="13.0.0.0" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Buffers" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.0.3.0" newVersion="4.0.3.0" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Diagnostics.DiagnosticSource" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-6.0.0.1" newVersion="6.0.0.1" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Memory" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.0.1.2" newVersion="4.0.1.2" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Memory.Data" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Runtime.CompilerServices.Unsafe" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Text.Json" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-6.0.0.10" newVersion="6.0.0.10" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Threading.Tasks.Extensions" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.2.0.1" newVersion="4.2.0.1" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>
</configuration>

tools\ServiceBusExplorer.NotificationHubs.dll

md5: ECB8305EF53CAA2D7F9482E100D2BBBD | sha1: BACE405AC3778318A650FBAE38AA82B07E6F768B | sha256: 2ED808A2D080DC25B2BBF767E2DC91A74F6E09ADAA24B812E61C710F49DF7098 | sha512: 5724FAEB649F9C1C9C8443FA2BC7EE8B2CDDD12A6EEB6E6F2FD57C002C1E2A8FC637C05CA724D14AB352CE014DEC051BE2A40017529B758E89358FDBD1DD9463

tools\ServiceBusExplorer.NotificationHubs.pdb

tools\ServiceBusExplorer.pdb

tools\ServiceBusExplorer.Relay.dll

md5: 26E1E0007B01B45F2B350B97FFEF8165 | sha1: 5E50B432C44D490BA105C01A4BCC2DE601C43325 | sha256: 948E2AFCE143A398C94963A59442A655EAD70D22776A0008EDDA92773638576C | sha512: D0FDB8B282A05D8B073C9F60545AD4F148CD848D312565B9C24E1D78ECE4EEF49A43912034DBDEB9FDD8E87450AA541A4E02AC4EBFE7883EF1E9787DB55BD208

tools\ServiceBusExplorer.Relay.pdb

tools\ServiceBusExplorer.ServiceBus.dll

md5: 2C42D5F64CC8E78B814AAE8BFC436DEF | sha1: 9130FD554083589FAEBFCC3838616D4C1D8290D1 | sha256: 9D8E5E10D9421050EDB34BFB9660822E0CB5E79C57EB00797B54A480F16D37D3 | sha512: 5ADFEAC15DCD26F3DE05F9B35705342727D65D8D427248AB453D91E77F8347ECECEDF79B74C5CCA534DF163BE4956E1638E47E5113F90EA3B85D56FFDD52F411

tools\ServiceBusExplorer.ServiceBus.pdb

tools\ServiceBusExplorer.Utilities.dll

md5: 50EBA9575F323A71C91F662FB184A915 | sha1: D72E97C58AAE80DC69D945C50DEA10D2E6C2B445 | sha256: 04CF579BAD79F61E4AF0EC50FAEB174188AD454D79FEB7E85E2DE18FA70A9E3F | sha512: 3A092BF81E501D18A40C55B64242633D11F99358FDC62AEAF27873A3CC97C53738854B493DB5810A62F4CA1F55C66E5710B5D8187D9F7EF33B058022226E4E39

tools\ServiceBusExplorer.Utilities.pdb

tools\System.Buffers.dll

md5: ECDFE8EDE869D2CCC6BF99981EA96400 | sha1: 2F410A0396BC148ED533AD49B6415FB58DD4D641 | sha256: ACCCCFBE45D9F08FFEED9916E37B33E98C65BE012CFFF6E7FA7B67210CE1FEFB | sha512: 5FC7FEE5C25CB2EEE19737068968E00A00961C257271B420F594E5A0DA0559502D04EE6BA2D8D2AAD77F3769622F6743A5EE8DAE23F8F993F33FB09ED8DB2741

tools\System.ClientModel.dll

md5: 1BD711FEA3A17B1DAC458E303AB9AC6C | sha1: C8C529ECB7D6CDF390FB0F50A1D4F2F796451668 | sha256: 96DAC7BD625EB8C9EFF0639DBF530BD75B8A94C36E03D6AAA18D234E10B7B759 | sha512: BFEB1EB2C848C417CC85614E0DA8C3BE119B64ABB87CCCAE0EC9D7FB3CFDC309F49D2C32A098C9ADA4D03D5259928FC77CE660BB12362520DA0B4C36EB088FAE

tools\System.Diagnostics.DiagnosticSource.dll

md5: 35ABCDECF1CB76BAF0EF03DEA3A0167A | sha1: 3B34715164D27A039AC3E7966D4F7F1888098726 | sha256: 19BA42737C1C0500373736968F3D15CB7897CB195049FD5F492E6FE1629DAAAB | sha512: A51171B4A5E6E0ABB304FC438B6C01324C74CB01AAF95CE2C086CED132BDB0E9034982AAC1FC3F0A5C88254AEC156FCC5765016D88F7F8B0DB321AA33121AEA7

tools\System.IdentityModel.Tokens.Jwt.dll

md5: 51EECD0861CE90E5622A87CF9AB0E304 | sha1: 653C257A78CEFB098517066EAF8E67ECAE0E93FB | sha256: B28E14873544392596CF8E34B9BBBA6F682E9C18D96379D40856CB4F1BB50A6A | sha512: 5E27873598B291294E17E702D14C5B3CBEC959DA7C407635695D69D0B15361080C50F27BFD1BBF8E73A34202A2BC6B10C01E2C4F082E5FBAC9EDB4581E2A35DF

tools\System.IO.FileSystem.AccessControl.dll

md5: 3409C581F0C5083F0C2A93A7A5AC9790 | sha1: 18EA7BD41D31247148ABF184527C9368A26F39E7 | sha256: E6026501AD4056FF2F1655B0AFDFE8923BC6E8FBAD67E1E9EF56E3002F49FBB9 | sha512: AE877C6FDDAD0E4133274E6372D783EAA4DD6BDCBBF40AB66302FB89BD2F76B215130001186B5C9A135ABD16336C5BFD4D414177704D7D359539DA91918E82ED

tools\System.Memory.Data.dll

md5: D02FA972535E0405A650870317F35713 | sha1: 37C6F55D8FB8094A5A63F0F8BFFBBB49BDDE2997 | sha256: 2A6ECB7901E64147279E0D8A4A1EB99B3BE14F9264932213AE0921DB43D476E7 | sha512: 048FAE5BDAF860BCF236B19EAA5332EEC8B4C59AC832D8967439D27DB0F42DD17D31D798E6205863AAA9271D45207296459631B0E4CA1167EE66464C4DD8976A

tools\System.Memory.dll

md5: F09441A1EE47FB3E6571A3A448E05BAF | sha1: 3C5C5DF5F8F8DB3F0A35C5ED8D357313A54E3CDE | sha256: BF3FB84664F4097F1A8A9BC71A51DCF8CF1A905D4080A4D290DA1730866E856F | sha512: 0199AE0633BCCFEAEFBB5AED20832A4379C7AD73461D41A9DA3D6DC044093CC319670E67C4EFBF830308CBD9A48FB40D4A6C7E472DCC42EB745C6BA813E8E7C6

tools\System.Numerics.Vectors.dll

md5: AAA2CBF14E06E9D3586D8A4ED455DB33 | sha1: 3D216458740AD5CB05BC5F7C3491CDE44A1E5DF0 | sha256: 1D3EF8698281E7CF7371D1554AFEF5872B39F96C26DA772210A33DA041BA1183 | sha512: 0B14A039CA67982794A2BB69974EF04A7FBEE3686D7364F8F4DB70EA6259D29640CBB83D5B544D92FA1D3676C7619CD580FF45671A2BB4753ED8B383597C6DA8

tools\System.Reflection.TypeExtensions.dll

md5: 10303C3595AA9AC1D61C813A95342345 | sha1: 9937CA553C666328C98F7C11E77C2E2666D4653C | sha256: 4682C5211D69E0C40C39F044929ACEAF1CE6B4CBAC8F938A05F493E35DE83DBF | sha512: 2BAE4C0BEAA879360752B85637B1D850904E1CCC5B7CAAD52CA50920A9A933CA37405ECD44DDA1522F319D64378E3C939676EE75A94E844577F5B276053FE81C

tools\System.Resources.Extensions.dll

md5: 058062075DAE2F0DB660018D899358DA | sha1: 4489F30223D4F80AD7C220615BE2047AFA82F085 | sha256: B69C9547C7BF0D6E357993D41228B6CEF033F4F2E0ECBA9F07325C7E980139AE | sha512: D2A568D19A0DFE06F9D9916C335FA1D752ED7CA78844124079E41B34C2342CBE3486F1D77A68C6CDD576D30FE84D03B12A7C7A5AABD09EE98174B0A167AF01C7

tools\System.Runtime.CompilerServices.Unsafe.dll

md5: C610E828B54001574D86DD2ED730E392 | sha1: 180A7BAAFBC820A838BBACA434032D9D33CCEEBE | sha256: 37768488E8EF45729BC7D9A2677633C6450042975BB96516E186DA6CB9CD0DCF | sha512: 441610D2B9F841D25494D7C82222D07E1D443B0DA07F0CF735C25EC82F6CCE99A3F3236872AEC38CC4DF779E615D22469666066CCEFED7FE75982EEFADA46396

tools\System.Security.AccessControl.dll

md5: 996AAB294E1D369B148D732E5EC0DFDC | sha1: 28465FD34680A082506F160107F350B46140A1AA | sha256: 1FDA491EEBDB19EA0A83CF6C16AB5DD004A1BFDFC845EDE017EBE0945BEB927F | sha512: 5E6B172D2DE5928915B38EC80C7B76F42430AAC959F04AA3521C63495B6F3C4F82DF139C275E9FC5024B1A0A4F307DAADE6130B6028779F98F456282AE8B61CD

tools\System.Security.Cryptography.ProtectedData.dll

md5: 472BD4790E3638272C021779717CDDB4 | sha1: 4F0481A6C5EA3BD1BBFEB7A117D7B352C4FDCFB6 | sha256: A79AD1E9E7205BD790F40D6C1900BAF1A9C8CAA06089878D24ED3599AC3228A9 | sha512: 865E10F18A3BC4A9A810C652A3320FD8CF6EE1A8148E2588E8B64B4DBD64A6AA5DFA7050AE66C2A64D5A63CB50C664EE8CDDE5F7C70AA3AEEF982236865CE771

tools\System.Security.Principal.Windows.dll

md5: BE2962225B441CC23575456F32A9CF6A | sha1: 9A5BE1FCF410FE5934D720329D36A2377E83747E | sha256: B4D8E15ADC235D0E858E39B5133E5D00A4BAA8C94F4F39E3B5E791B0F9C0C806 | sha512: 3F7692E94419BFFE3465D54C0E25C207330CD1368FCDFAD71DBEED1EE842474B5ABCB03DBA5BC124BD10033263F22DC9F462F12C20F866AEBC5C91EB151AF2E6

tools\System.Text.Encodings.Web.dll

md5: BA1AF3BBFF4D457B6D3F730234C3C701 | sha1: 1B75BC14DAA093502C7C5814852928E28AB6659A | sha256: 78EB5B4FEE580E163D1BEA1FDB7D371FDFCFD30ACD8708FF62C4372AAA219F7C | sha512: 51895C9B0EDE088B034C581AB4574A36F80E41F2B04186B3C066B6D72DA85680E00EA5E07DC9C89DB7D997C1AD3D9686ACCDC827859EAAB2918376C4C9E469B2

tools\System.Text.Json.dll

md5: 35B0623746E769D4122A4D7DEA5B2B68 | sha1: E7EEC604FABD309A1E5E69CC51D553DD65E97A7A | sha256: BDE4850D39245F9758D1346BD67AC890EEC25473B7A7171AD6E631A4C5FD4734 | sha512: 4A11EF391BB1D2E186D20D45A3DC5AB03A8F740BF6CB2F519860DFF7DB113757B3B377FEEBB710C4EF80F1931B43072EDD415E25DCB0D2D72ADA1114AC90AFBE

tools\System.Threading.Channels.dll

md5: 1BC0F4FFA520FBB86A087D280F8621DF | sha1: F414C683BAB2DF055CC918FF42BADEF3C79F20BD | sha256: 401398F461799E242BB3CC3D24D901666A76C8F2A6617329A9C21D7A0564F0C3 | sha512: 22741A11AD5BD21711CB174C2032F7D714E562C35F86D176388EE4C11582EA4D1550C910CA9E934289704109BF59B40AC159BA9FC4488235ECE4733107E03DAC

tools\System.Threading.Tasks.Extensions.dll

md5: E1E9D7D46E5CD9525C5927DC98D9ECC7 | sha1: 2242627282F9E07E37B274EA36FAC2D3CD9C9110 | sha256: 4F81FFD0DC7204DB75AFC35EA4291769B07C440592F28894260EEA76626A23C6 | sha512: DA7AB8C0100E7D074F0E680B28D241940733860DFBDC5B8C78428B76E807F27E44D1C5EC95EE80C0B5098E8C5D5DA4D48BCE86800164F9734A05035220C3FF11

tools\System.ValueTuple.dll

md5: 23EE4302E85013A1EB4324C414D561D5 | sha1: D1664731719E85AAD7A2273685D77FEB0204EC98 | sha256: E905D102585B22C6DF04F219AF5CBDBFA7BC165979E9788B62DF6DCC165E10F4 | sha512: 6B223CE7F580A40A8864A762E3D5CCCF1D34A554847787551E8A5D4D05D7F7A5F116F2DE8A1C793F327A64D23570228C6E3648A541DD52F93D58F8F243591E32

tools\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 their official download link listed on <https://github.com/paolosalvatori/ServiceBusExplorer/releases>
and can be verified like this:

1. Download the following installers:
  64-Bit: <https://github.com/paolosalvatori/ServiceBusExplorer/releases/download/6.1.1/ServiceBusExplorer-6.1.1.zip>
2. You can use one of the following methods to obtain the checksum
  - Use powershell function 'Get-Filehash'
  - Use chocolatey utility 'checksum.exe'

  checksum type: md5
  checksum64: 81F352A0634829E1B839D84CBDCE0A4E

File 'LICENSE.txt' is obtained from <https://github.com/paolosalvatori/ServiceBusExplorer/blob/main/LICENSE.txt>

Virus Scan Results

System.ValueTuple.dll (e905d102585b) - ## / 70
System.Numerics.Vectors.dll (1d3ef8698281) - ## / 72
FastColoredTextBox.dll (4a8ef87e29d8) - ## / 73
System.Security.Cryptography.ProtectedData.dll (a79ad1e9e720) - ## / 68
System.Buffers.dll (accccfbe45d9) - ## / 70
System.Threading.Tasks.Extensions.dll (4f81ffd0dc72) - ## / 72
Microsoft.Azure.NotificationHubs.dll (053c65594528) - ## / 75
System.Security.AccessControl.dll (1fda491eebdb) - ## / 69
System.Security.Principal.Windows.dll (b4d8e15adc23) - ## / 70
System.IO.FileSystem.AccessControl.dll (e6026501ad40) - ## / 70
Microsoft.IdentityModel.Clients.ActiveDirectory.dll (9c530971bf1a) - ## / 73
Microsoft.Bcl.AsyncInterfaces.dll (295af2142d92) - ## / 72
System.Runtime.CompilerServices.Unsafe.dll (37768488e8ef) - ## / 72
System.Text.Encodings.Web.dll (78eb5b4fee58) - ## / 73
System.IdentityModel.Tokens.Jwt.dll (b28e14873544) - ## / 73
CommandLine.dll (2135b40fa819) - ## / 72
Microsoft.IdentityModel.JsonWebTokens.dll (f9d1376f30ef) - ## / 73
Microsoft.IdentityModel.Logging.dll (c25bbd7ba62a) - ## / 73
Microsoft.IdentityModel.Tokens.dll (43f9fe1cf13a) - ## / 65
System.Reflection.TypeExtensions.dll (4682c5211d69) - ## / 71
System.Memory.dll (bf3fb84664f4) - ## / 72
System.Threading.Channels.dll (401398f46179) - ## / 73
Newtonsoft.Json.dll (e1e27af7b07e) - ## / 72
System.Diagnostics.DiagnosticSource.dll (19ba42737c1c) - ## / 72
System.Resources.Extensions.dll (b69c9547c7bf) - ## / 73
Azure.Messaging.EventGrid.dll (c88b4da2baf7) - ## / 75
Azure.ResourceManager.dll (1307ba9076bc) - ## / 74
Azure.ResourceManager.EventGrid.dll (2cc0a1c1bcd5) - ## / 72
Microsoft.Azure.Relay.dll (b0638bd87980) - ## / 75
Microsoft.Rest.ClientRuntime.Azure.dll (08c4fafacc24) - ## / 73
Microsoft.Rest.ClientRuntime.dll (08e1d859e575) - ## / 73
Microsoft.ServiceBus.dll (628e9342a4d4) - ## / 74
System.ClientModel.dll (96dac7bd625e) - ## / 73
Microsoft.Azure.Services.AppAuthentication.dll (e999d795012f) - ## / 65
Microsoft.IdentityModel.Abstractions.dll (d3265f1cab11) - ## / 73
ServiceBusExplorer.6.1.1.nupkg (be35b2585e55) - ## / 55
Azure.Core.Amqp.dll (d53d832629b7) - ## / 74
Azure.Core.dll (374771ebf3b6) - ## / 72
Azure.Identity.dll (16f3067074f0) - ## / 71
Azure.Messaging.EventHubs.dll (512f3855eede) - ## / 71
Azure.Messaging.ServiceBus.dll (8313a604596f) - ## / 72
Microsoft.Azure.Amqp.dll (264f8d39091c) - ## / 73
Microsoft.Identity.Client.dll (7cdc22bb95df) - ## / 71
Microsoft.Identity.Client.Extensions.Msal.dll (0768cc69604c) - ## / 71
ServiceBusExplorer.Common.dll (d75e5241afe4) - ## / 72
ServiceBusExplorer.EventGridExplorerLibrary.dll (80eb051d9815) - ## / 72
ServiceBusExplorer.EventHubs.dll (efa15fb00ffe) - ## / 70
ServiceBusExplorer.exe (8eb593216e15) - ## / 72
ServiceBusExplorer.NotificationHubs.dll (2ed808a2d080) - ## / 72
ServiceBusExplorer.Relay.dll (948e2afce143) - ## / 72
ServiceBusExplorer.ServiceBus.dll (9d8e5e10d942) - ## / 72
ServiceBusExplorer.Utilities.dll (04cf579bad79) - ## / 70
System.Memory.Data.dll (2a6ecb7901e6) - ## / 73
System.Text.Json.dll (bde4850d3924) - ## / 73

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
Service Bus Explorer 6.1.1	4060	Monday, April 21, 2025	Approved
Service Bus Explorer 6.1.0	308	Sunday, April 20, 2025	Approved
Service Bus Explorer 6.0.3	14990	Monday, July 15, 2024	Approved
Service Bus Explorer 6.0.2	1294	Friday, July 5, 2024	Approved
Service Bus Explorer 6.0.1	885	Monday, July 1, 2024	Approved
Service Bus Explorer 6.0.0	1105	Monday, June 24, 2024	Approved
Service Bus Explorer 5.0.18	15849	Friday, September 8, 2023	Approved
Service Bus Explorer 5.0.17	3339	Sunday, July 30, 2023	Approved
Service Bus Explorer 5.0.15	16105	Wednesday, November 16, 2022	Approved
Service Bus Explorer 5.0.14	5573	Monday, September 19, 2022	Approved
Service Bus Explorer 5.0.7	12855	Wednesday, April 6, 2022	Approved
Service Bus Explorer 5.0.4	21137	Sunday, June 20, 2021	Approved
Service Bus Explorer 5.0.3	2804	Tuesday, May 18, 2021	Approved
ServiceBusExplorer 4.1.112	23123	Tuesday, March 12, 2019	Approved
ServiceBusExplorer 4.1.111	2294	Wednesday, January 23, 2019	Approved
ServiceBusExplorer 4.0.110	6864	Thursday, July 5, 2018	Approved
ServiceBusExplorer 4.0.109	3030	Wednesday, April 4, 2018	Approved
ServiceBusExplorer 4.0.108	786	Tuesday, March 20, 2018	Approved
ServiceBusExplorer 4.0.107	1122	Monday, February 12, 2018	Approved
ServiceBusExplorer 4.0.106	337	Friday, February 2, 2018	Approved
ServiceBusExplorer 4.0.105	2387	Monday, October 30, 2017	Approved
ServiceBusExplorer 4.0.104	998	Thursday, September 28, 2017	Approved
ServiceBusExplorer 4.0.102	814	Wednesday, September 6, 2017	Approved

Release Notes

https://github.com/paolosalvatori/ServiceBusExplorer/releases

Dependencies

This package has no dependencies.

Discussion for the Service Bus Explorer Package

Ground Rules:

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

159,097

4,060

21 Apr 2025

Service Bus Explorer

Service Bus Explorer 6.1.1

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

Ground Rules: