Step 1: Review Your Packages

Step 2: Choose Your Integration Method

Step 3: Copy Your Script or Download Config

Option 1: Copy Script

Option 2: Download Config

Step 4: Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

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

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

Option 2: Internalized Package (Reliable, Scalable)

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

Step 5: Copy Your Script

See options you can pass to upgrade.

See best practices for scripting.

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

### c. Other Requirements ###

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

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

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

## 2. TOP LEVEL VARIABLES ##

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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

- name: Install and Configure Chocolatey
  hosts: all

## 2. TOP LEVEL VARIABLES ##
  vars:

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

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

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

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

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

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

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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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

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

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

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

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

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

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

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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

chocolatey_feature 'useBackgroundService' do
  action :enable
end

chocolatey_feature 'useBackgroundServiceWithNonAdministratorsOnly' do
  action :enable
end

chocolatey_feature 'allowBackgroundServiceUninstallsFromUserInstallsOnly' do
  action :enable
end

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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


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

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

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

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

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


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


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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Need Help? View our docs or file an issue.

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

Current Version	New Version

Downloads:

18,146

Downloads of v 4.0.8876.100:

3,569

Last Update:

01 Oct 2023

Package Maintainer(s):

dgalbraith

Software Author(s):

Microsoft

Tags:

sql server compact sql-server mssql mssqlce mssqlce4.0 sqlce sqlce4.0 4.0 microsoft

Microsoft SQLServer Compact 4.0 with SP1

4.0.8876.100 | Updated: 01 Oct 2023

Downloads:

18,146

Downloads of v 4.0.8876.100:

3,569

Maintainer(s):

dgalbraith

Software Author(s):

Microsoft

Tags:

sql server compact sql-server mssql mssqlce mssqlce4.0 sqlce sqlce4.0 4.0 microsoft

Microsoft SQLServer Compact 4.0 with SP1 4.0.8876.100

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

All Checks are Passing

3 Passing Tests

Show Checks

Validation Testing Passed

Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Microsoft SQLServer Compact 4.0 with SP1, run the following command from the command line or from PowerShell:

To upgrade Microsoft SQLServer Compact 4.0 with SP1, run the following command from the command line or from PowerShell:

To uninstall Microsoft SQLServer Compact 4.0 with SP1, 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 mssqlserver-compact4.0 --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 mssqlserver-compact4.0 -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 mssqlserver-compact4.0 -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 mssqlserver-compact4.0
  win_chocolatey:
    name: mssqlserver-compact4.0
    version: '4.0.8876.100'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'mssqlserver-compact4.0' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '4.0.8876.100'
end

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


cChocoPackageInstaller mssqlserver-compact4.0
{
    Name     = "mssqlserver-compact4.0"
    Version  = "4.0.8876.100"
    Source   = "INTERNAL REPO URL"
}

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


package { 'mssqlserver-compact4.0':
  ensure   => '4.0.8876.100',
  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 by moderator TheCakeIsNaOH on 07 Oct 2023.

Description

Microsoft SQL Server Compact 4.0 is a free, embedded database that software developers can use for building ASP.NET
websites and Windows desktop applications. SQL Server Compact 4.0 has a small footprint and supports private
deployment of its binaries within the application folder, easy application development in Visual Studio and
WebMatrix, and seamless migration of schema and data to SQL Server.

Features

Default database for Microsoft WebMatrix, which is a stack of web technologies for easily building and deploying
websites on the Windows platform
Visual Studio can be used to develop ASP.NET web applications and websites using SQL Server Compact 4.0
Enabled to work in the medium or partial trust environments in the web servers, and can be easily deployed along with
the website to the third party website hosting service providers
Private deployment of SQL Server Compact further simplified by having all the required managed assemblies, and the
x86 and x64 DLLs, including the Visual C++ 2008 runtime libraries (x86 and x64) SP1 in a single private folder in the
install location of SQL Server Compact
Stronger data security with the use of the SHA2 encryption algorithms for encrypting the databases
T-SQL syntax enhancement by adding support for OFFSET and FETCH that can be used to write paging queries and new APIs
like SqlCeConnection.GetSchema that provides the metadata information of the database
Used with ADO.NET Entity Framework, SQL Server Compact now supports the columns that have server generated keys like
identity, rowguid etc. and the code-first programming model

Package Parameters

The language package parameter can be set to install the package with the specified language. If no language is
specified the install will default to English.

/language=[language-code] - installs the package using the specified language. Supported languages are:
- br - Brazilian (Portuguese) - --params '"/language=br"'
- cz - Czech - --params '"/language=cz"'
- de - German - --params '"/language=de"'
- en - English - --params '"/language=en"'
- es - Spanish - --params '"/language=es"'
- fr - French - --params '"/language=fr"'
- it - Italian - --params '"/language=it"'
- ja - Japanese - --params '"/language=ja"'
- ko - Korean - --params '"/language=ko"'
- pl - Polish - --params '"/language=pl"'
- ru - Russian - --params '"/language=ru"'
- tr - Turkish - --params '"/language=tr"'
- zh - Chinese (Simplified) - --params '"/language=zh"'
- zh-CN - Chinese (Simplified) - --params '"/language=zh-CN"'
- zh-TW - Chinese (Tradition) - --params '"/language=gz-TW"'

For example: choco install mssqlserver-compact4.0 --params '"/language=fr"' to install the French version of the package

Notes

This package is manually updated
SQL Server compact edition was deprecated in February 2013
Although no new versions or updates are planned extended support is available through to July 2021
If the package does not represent the latest version please contact the maintainer(s) and let them know the package requires updating

Files

legal\LICENSE.txt

https://www.microsoft.com/download/details.aspx?id=30709

SQL Server Compact 4.0 is freely redistributable under a redistribution license agreement and application
developers redistributing SQL Server Compact 4.0 can optionally register at the SQL Server Compact redistribution
site. Registering will help the developers in getting information about SQL Server Compact critical security patches
and hot fixes that can be further applied to the client installations.

EULA_ENU.rtf

MICROSOFT SOFTWARE LICENSE TERMS
MICROSOFT SQL SERVER COMPACT 4.0 SERVICE PACK 1 (SP1) 
These license terms are an agreement between Microsoft Corporation (or based on where you live, one of its affiliates) and you. Please read them. They apply to the software named above, which includes the media on which you received it, if any. The terms also apply to any Microsoft
•	updates,
•	supplements,
•	Internet-based services, and
•	support services
for this software, unless other terms accompany those items. If so, those terms apply.
BY USING THE SOFTWARE, YOU ACCEPT THESE TERMS. IF YOU DO NOT ACCEPT THEM, DO NOT USE THE SOFTWARE.
If you comply with these license terms, you have the rights below.
1.	INSTALLATION AND USE RIGHTS. 
a.	Installation and Use. You may install and use any number of copies of the software on your devices to design, develop and test your programs for use with the software.
b.	Included Microsoft Programs. The software contains the Microsoft Visual C++ 2008 Express Edition components listed below. You may only use these components with the software. The Microsoft Visual C++ 2008 Express license terms located at %Program Files%\Microsoft SQL Server Compact Edition\v4.0 apply to your use of them, except that the components listed below may be used for commercial hosting services when used in conjunction with the software. 
•	Microsoft_VC90_CRT_x86.msm
•	policy_9_0_Microsoft_VC90_CRT_x86.msm
•	Microsoft_VC90_CRT_x86_x64.msm
•	policy_9_0_Microsoft_VC90_CRT_x86_x64.msm
•	VC90.CRT_X86_msvcr90.dll
•	VC90.CRT_X86_Microsoft.VC90.CRT.manifest
•	VC90.CRT_AMD64_msvcr90.dll
•	VC90.CRT_AMD64_Microsoft.VC90.CRT.manifest
2.	ADDITIONAL LICENSING REQUIREMENTS AND/OR USE RIGHTS.
a.	Distributable Code. The software contains code that you are permitted to distribute in programs you develop if you comply with the terms below.
i.	Right to Use and Distribute. The code and text files listed below are “Distributable Code.”
•	REDIST.TXT Files. You may copy and distribute the object code form of code listed in REDIST.TXT files.
•	Third Party Distribution. You may permit distributors of your programs to copy and distribute the Distributable Code as part of those programs.
ii.	Distribution Requirements. For any Distributable Code you distribute, you must
•	add significant primary functionality to it in your programs;
•	for any Distributable Code having a filename extension of .lib, distribute only the results of running such Distributable Code through a linker with your program;
•	distribute Distributable Code included in a setup program only as part of that setup program without modification;
•	require distributors and external end users to agree to terms that protect it at least as much as this agreement; 
•	display your valid copyright notice on your programs; and
•	indemnify, defend, and hold harmless Microsoft from any claims, including attorneys’ fees, related to the distribution or use of your programs.
iii.	Distribution Restrictions. You may not
•	alter any copyright, trademark or patent notice in the Distributable Code;
•	use Microsoft’s trademarks in your programs’ names or in a way that suggests your programs come from or are endorsed by Microsoft;
•	distribute Distributable Code to run on a platform other than the Windows platform;
•	include Distributable Code in malicious, deceptive or unlawful programs; or
•	modify or distribute the source code of any Distributable Code so that any part of it becomes subject to an Excluded License. An Excluded License is one that requires, as a condition of use, modification or distribution, that
•	the code be disclosed or distributed in source code form; or
•	others have the right to modify it.
3.	SCOPE OF LICENSE. The software is licensed, not sold. This agreement only gives you some rights to use the software. Microsoft reserves all other rights. Unless applicable law gives you more rights despite this limitation, you may use the software only as expressly permitted in this agreement. In doing so, you must comply with any technical limitations in the software that only allow you to use it in certain ways. You may not
•	work around any technical limitations in the software;
•	reverse engineer, decompile or disassemble the software, except and only to the extent that applicable law expressly permits, despite this limitation;
•	make more copies of the software than specified in this agreement or allowed by applicable law, despite this limitation;
•	publish the software for others to copy;
•	rent, lease or lend the software; or
•	transfer the software or this agreement to any third party. 
4.	BACKUP COPY. You may make one backup copy of the software. You may use it only to reinstall the software.
5.	DOCUMENTATION. Any person that has valid access to your computer or internal network may copy and use the documentation for your internal, reference purposes.
6.	EXPORT RESTRICTIONS. The software is subject to United States export laws and regulations. You must comply with all domestic and international export laws and regulations that apply to the software. These laws include restrictions on destinations, end users and end use. For additional information, see www.microsoft.com/exporting.
7.	SUPPORT SERVICES. Because this software is “as is,” we may not provide support services for it.
8.	ENTIRE AGREEMENT. This agreement, and the terms for supplements, updates, Internet-based services and support services that you use, are the entire agreement for the software and support services.
9.	APPLICABLE LAW.
a.	United States. If you acquired the software in the United States, Washington state law governs the interpretation of this agreement and applies to claims for breach of it, regardless of conflict of laws principles. The laws of the state where you live govern all other claims, including claims under state consumer protection laws, unfair competition laws, and in tort.
b.	Outside the United States. If you acquired the software in any other country, the laws of that country apply.
10.	LEGAL EFFECT. This agreement describes certain legal rights. You may have other rights under the laws of your country. You may also have rights with respect to the party from whom you acquired the software. This agreement does not change your rights under the laws of your country if the laws of your country do not permit it to do so.
11.	DISCLAIMER OF WARRANTY. THE SOFTWARE IS LICENSED “AS-IS.” YOU BEAR THE RISK OF USING IT. MICROSOFT GIVES NO EXPRESS WARRANTIES, GUARANTEES OR CONDITIONS. YOU MAY HAVE ADDITIONAL CONSUMER RIGHTS UNDER YOUR LOCAL LAWS WHICH THIS AGREEMENT CANNOT CHANGE. TO THE EXTENT PERMITTED UNDER YOUR LOCAL LAWS, MICROSOFT EXCLUDES THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.
12.	LIMITATION ON AND EXCLUSION OF REMEDIES AND DAMAGES. YOU CAN RECOVER FROM MICROSOFT AND ITS SUPPLIERS ONLY DIRECT DAMAGES UP TO U.S. $5.00. YOU CANNOT RECOVER ANY OTHER DAMAGES, INCLUDING CONSEQUENTIAL, LOST PROFITS, SPECIAL, INDIRECT OR INCIDENTAL DAMAGES.
This limitation applies to
•	anything related to the software, services, content (including code) on third party Internet sites, or third party programs; and
•	claims for breach of contract, breach of warranty, guarantee or condition, strict liability, negligence, or other tort to the extent permitted by applicable law.
It also applies even if Microsoft knew or should have known about the possibility of the damages. The above limitation or exclusion may not apply to you because your country may not allow the exclusion or limitation of incidental, consequential or other damages.


REDIST_ENU.txt

The listed .exe files each install its enclosed components to a specific location on the destination computer.  This helps to ensure serviceability and technical support.  The .dll files enclosed in these .exe files are also available separately in this redist.txt.  However, distributions of these separate .dlls may result in issues of serviceability.  For more details, please see http://go.microsoft.com/fwlink/?LinkId=94589

Private deployment detection via BreadCrumb:  Private deployment of just the native stack and explicit loading of SQL Server Compact Assembly via Assembly.LoadFrom(), .local file, or the use of DLL/COM redirection strategies are not supported and may result in serviceability issues.  For more information see http://support.microsoft.com/kb/835322 and http://msdn2.microsoft.com/en-us/library/aa375142.aspx


Microsoft SQL Server Compact 4.0 SP1
------------------------------------
SSCERuntime_x86-ENU.exe
SSCERuntime_x86-DEU.exe
SSCERuntime_x86-FRA.exe
SSCERuntime_x86-JPN.exe
SSCERuntime_x86-RUS.exe
SSCERuntime_x86-ESN.exe
SSCERuntime_x86-ITA.exe
SSCERuntime_x86-KOR.exe
SSCERuntime_x86-CHT.exe
SSCERuntime_x86-CHS.exe
SSCERuntime_x64-ENU.exe
SSCERuntime_x64-DEU.exe
SSCERuntime_x64-FRA.exe
SSCERuntime_x64-JPN.exe
SSCERuntime_x64-RUS.exe
SSCERuntime_x64-ESN.exe
SSCERuntime_x64-ITA.exe
SSCERuntime_x64-KOR.exe
SSCERuntime_x64-CHT.exe
SSCERuntime_x64-CHS.exe
sqlcese40.dll
sqlceqp40.dll
sqlceoledb40.dll
sqlceca40.dll
sqlceme40.dll
sqlcecompact40.dll
sqlceer40en.dll
sqlceer40cn.dll/sqlceer40zh-CHS.dll
sqlceer40de.dll 
sqlceer40es.dll 
sqlceer40fr.dll 
sqlceer40it.dll 
sqlceer40ja.dll 
sqlceer40ko.dll 
sqlceer40tw.dll/sqlceer40zh-CHT.dll 
sqlceer40ru.dll
System.Data.SqlServerCe.dll
System.Data.SqlServerCe.Entity.dll

legal\RedistributionAuthority.pdf

md5: 281DBEA695CB3D74C86E4323489242FB | sha1: 5BA6372CF8D5EBA2993C3B4FF5CD35B2EB7ABE89 | sha256: 92FB30866E64D3C11E135718BDC1EBF655AD2CEC7882D8692B779F86B0123E9C | sha512: 46B0B118956578BE4FDCBB683D9B630161C5CEA7D3685A14D33E5F2609AB1091FD4D0EAEC7F8BBAB44DE21D8C0A313D0EFE3C11A6B4E8C10641C34D2840194FC

legal\VERIFICATION.txt

VERIFICATION

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

The installers have been downloaded from the official distribution and can
be verified by:

1. Go to the software distribution page

  https://www.microsoft.com/download/details.aspx?id=30709

and retrieve the SSCERuntime files by selecting the relevant language in the
dropdown followed by the download button and file selection.

2. The archives can be validated by comparing checksums

  - Use powershell function 'Get-Filehash' - Get-Filehash -Algorithm sha256 SSCERuntime_x86-CHS.exe
  - Use chocolatey utility 'checksum.exe'  - checksum -t sha256 -f SSCERuntime_x86-CHS.exe

  File:     SSCERuntime_x86-CHS.exe
  Type:     sha256
  Checksum: EEB5218D93BF89DF18479DE3817D49811E8FD0D6108A5A4B8F1CD56354734256

  - Use powershell function 'Get-Filehash' - Get-Filehash -Algorithm sha256 SSCERuntime_x86-CHT.exe
  - Use chocolatey utility 'checksum.exe'  - checksum -t sha256 -f SSCERuntime_x86-CHT.exe

  File:     SSCERuntime_x86-CHT.exe
  Type:     sha256
  Checksum: 3C0F5C1D3A60072F31BB5834F73388CFA5D41466DB5B5B167ACF6076696B304F

  - Use powershell function 'Get-Filehash' - Get-Filehash -Algorithm sha256 SSCERuntime_x86-CSY.exe
  - Use chocolatey utility 'checksum.exe'  - checksum -t sha256 -f SSCERuntime_x86-CSY.exe

  File:     SSCERuntime_x86-CSY.exe
  Type:     sha256
  Checksum: 3767F675EBB6A08431B439BC6217A93CC7F70B9754A59FBE9CBB251EFBBA969D

  - Use powershell function 'Get-Filehash' - Get-Filehash -Algorithm sha256 SSCERuntime_x86-DEU.exe
  - Use chocolatey utility 'checksum.exe'  - checksum -t sha256 -f SSCERuntime_x86-DEU.exe

  File:     SSCERuntime_x86-DEU.exe
  Type:     sha256
  Checksum: 814BF99DF12696A7E98DA77B84AA84EA43C22C5B41A05895F577C9F288010CC4

  - Use powershell function 'Get-Filehash' - Get-Filehash -Algorithm sha256 SSCERuntime_x86-ENU.exe
  - Use chocolatey utility 'checksum.exe'  - checksum -t sha256 -f SSCERuntime_x86-ENU.exe

  File:     SSCERuntime_x86-ENU.exe
  Type:     sha256
  Checksum: 44CA2585C7BD9EF66979C1C903A8A053B922A69BEAAD4DCC47015CD99FCF3CD4

  - Use powershell function 'Get-Filehash' - Get-Filehash -Algorithm sha256 SSCERuntime_x86-ESN.exe
  - Use chocolatey utility 'checksum.exe'  - checksum -t sha256 -f SSCERuntime_x86-ESN.exe

  File:     SSCERuntime_x86-ESN.exe
  Type:     sha256
  Checksum: DE3D25C5EDB5CD5126121B92735CF974E90FDE471A4026B2B16321F15682F5FC

  - Use powershell function 'Get-Filehash' - Get-Filehash -Algorithm sha256 SSCERuntime_x86-FRA.exe
  - Use chocolatey utility 'checksum.exe'  - checksum -t sha256 -f SSCERuntime_x86-FRA.exe

  File:     SSCERuntime_x86-FRA.exe
  Type:     sha256
  Checksum: C9DA688C6F749AD55E52D0B783FCE5EE98CD29BBCA6D65E3A9E8F5DFE50661C7

  - Use powershell function 'Get-Filehash' - Get-Filehash -Algorithm sha256 SSCERuntime_x86-ITA.exe
  - Use chocolatey utility 'checksum.exe'  - checksum -t sha256 -f SSCERuntime_x86-ITA.exe

  File:     SSCERuntime_x86-ITA.exe
  Type:     sha256
  Checksum: CFB25AC4A7FD7EB71EF00270EC0E11AAB563D38F8E01EC73530BBC8D0345C98A

  - Use powershell function 'Get-Filehash' - Get-Filehash -Algorithm sha256 SSCERuntime_x86-JPN.exe
  - Use chocolatey utility 'checksum.exe'  - checksum -t sha256 -f SSCERuntime_x86-JPN.exe

  File:     SSCERuntime_x86-JPN.exe
  Type:     sha256
  Checksum: 2B48C0C7AC8147D14A3DC271DCD9FCCBA2A0CDF455665206EEE03C92A8F8A5D9

  - Use powershell function 'Get-Filehash' - Get-Filehash -Algorithm sha256 SSCERuntime_x86-KOR.exe
  - Use chocolatey utility 'checksum.exe'  - checksum -t sha256 -f SSCERuntime_x86-KOR.exe

  File:     SSCERuntime_x86-KOR.exe
  Type:     sha256
  Checksum: 06069E54827480E91DAF17012878D929F02AF8A279B46ADFEFEF4593C26F6310

  - Use powershell function 'Get-Filehash' - Get-Filehash -Algorithm sha256 SSCERuntime_x86-PLK.exe
  - Use chocolatey utility 'checksum.exe'  - checksum -t sha256 -f SSCERuntime_x86-PLK.exe

  File:     SSCERuntime_x86-PLK.exe
  Type:     sha256
  Checksum: 0B8AAA75BAFCF96DF141B91B1A4437B6F7ADAB5F88791CC436839058D01F291A

  - Use powershell function 'Get-Filehash' - Get-Filehash -Algorithm sha256 SSCERuntime_x86-PTB.exe
  - Use chocolatey utility 'checksum.exe'  - checksum -t sha256 -f SSCERuntime_x86-PTB.exe

  File:     SSCERuntime_x86-PTB.exe
  Type:     sha256
  Checksum: 1A2DFB186B3BC7BCC6DB1663AAC6BEE610346F7F7124F6734C3533FD894E17C4

  - Use powershell function 'Get-Filehash' - Get-Filehash -Algorithm sha256 SSCERuntime_x86-RUS.exe
  - Use chocolatey utility 'checksum.exe'  - checksum -t sha256 -f SSCERuntime_x86-RUS.exe

  File:     SSCERuntime_x86-RUS.exe
  Type:     sha256
  Checksum: 87C2BBEF40C59297893FAA562C7FF398822D621201FAA74DF76D8083B5AFE9BF

  - Use powershell function 'Get-Filehash' - Get-Filehash -Algorithm sha256 SSCERuntime_x86-TRK.exe
  - Use chocolatey utility 'checksum.exe'  - checksum -t sha256 -f SSCERuntime_x86-TRK.exe

  File:     SSCERuntime_x86-TRK.exe
  Type:     sha256
  Checksum: 5FE905F71907FAA7CEFDEE2C3439E5C3A6BA6F0334C67E8A6B3811B0653922E4

  - Use powershell function 'Get-Filehash' - Get-Filehash -Algorithm sha256 SSCERuntime_x64-CHS.exe
  - Use chocolatey utility 'checksum.exe'  - checksum -t sha256 -f SSCERuntime_x64-CHS.exe

  File:     SSCERuntime_x64-CHS.exe
  Type:     sha256
  Checksum: 6679A33F37BD37D2B1163465995AE09CB9EF6AF4B4026A20924CCB03FB03BC4B

  - Use powershell function 'Get-Filehash' - Get-Filehash -Algorithm sha256 SSCERuntime_x64-CHT.exe
  - Use chocolatey utility 'checksum.exe'  - checksum -t sha256 -f SSCERuntime_x64-CHT.exe

  File:     SSCERuntime_x64-CHT.exe
  Type:     sha256
  Checksum: C536AAA413F4EDB12B50D81E6FE5C6FDCFD03B39500F2CBD15BA02F488E9A865

  - Use powershell function 'Get-Filehash' - Get-Filehash -Algorithm sha256 SSCERuntime_x64-CSY.exe
  - Use chocolatey utility 'checksum.exe'  - checksum -t sha256 -f SSCERuntime_x64-CSY.exe

  File:     SSCERuntime_x64-CSY.exe
  Type:     sha256
  Checksum: 1853A00F79684A175243E9D5DED003A0E53BB3D4272452E04EF38A79CF16C578

  - Use powershell function 'Get-Filehash' - Get-Filehash -Algorithm sha256 SSCERuntime_x64-DEU.exe
  - Use chocolatey utility 'checksum.exe'  - checksum -t sha256 -f SSCERuntime_x64-DEU.exe

  File:     SSCERuntime_x64-DEU.exe
  Type:     sha256
  Checksum: F86BAC8C81C3F42DC7100EAFA7CA1FA6CB587ADB49774DD1C67CC0072E8FCA3C

  - Use powershell function 'Get-Filehash' - Get-Filehash -Algorithm sha256 SSCERuntime_x64-ENU.exe
  - Use chocolatey utility 'checksum.exe'  - checksum -t sha256 -f SSCERuntime_x64-ENU.exe

  File:     SSCERuntime_x64-ENU.exe
  Type:     sha256
  Checksum: 443D149C7A1A3D5C26189BF727A55287341FAD620225FD7AED610BA1762286E4

  - Use powershell function 'Get-Filehash' - Get-Filehash -Algorithm sha256 SSCERuntime_x64-ESN.exe
  - Use chocolatey utility 'checksum.exe'  - checksum -t sha256 -f SSCERuntime_x64-ESN.exe

  File:     SSCERuntime_x64-ESN.exe
  Type:     sha256
  Checksum: 3FB0C8BCF3C22F37A5A3BB4F4A8537149AAEA038442D1FBCBDA4780912E913FC

  - Use powershell function 'Get-Filehash' - Get-Filehash -Algorithm sha256 SSCERuntime_x64-FRA.exe
  - Use chocolatey utility 'checksum.exe'  - checksum -t sha256 -f SSCERuntime_x64-FRA.exe

  File:     SSCERuntime_x64-FRA.exe
  Type:     sha256
  Checksum: 6DE2AB2799BB4FEF47B6E677DC052C9927D8C2F7F2FB7A05B2AF8BB664D09C77

  - Use powershell function 'Get-Filehash' - Get-Filehash -Algorithm sha256 SSCERuntime_x64-ITA.exe
  - Use chocolatey utility 'checksum.exe'  - checksum -t sha256 -f SSCERuntime_x64-ITA.exe

  File:     SSCERuntime_x64-ITA.exe
  Type:     sha256
  Checksum: D00A3EAE732A8492FCE582B607E0CA2359FD5010368E3238A900FEC4CDADF0E2

  - Use powershell function 'Get-Filehash' - Get-Filehash -Algorithm sha256 SSCERuntime_x64-JPN.exe
  - Use chocolatey utility 'checksum.exe'  - checksum -t sha256 -f SSCERuntime_x64-JPN.exe

  File:     SSCERuntime_x64-JPN.exe
  Type:     sha256
  Checksum: 1B57600E4D69AF91D8B01FA6FD55FA2F2791F0C0B048E8F9B3B1AA8F918357E1

  - Use powershell function 'Get-Filehash' - Get-Filehash -Algorithm sha256 SSCERuntime_x64-KOR.exe
  - Use chocolatey utility 'checksum.exe'  - checksum -t sha256 -f SSCERuntime_x64-KOR.exe

  File:     SSCERuntime_x64-KOR.exe
  Type:     sha256
  Checksum: B1C9E335CD55131BBCE4C0F0EEBD9C15658ADA2812E48083EF1748C5A4C4A436

  - Use powershell function 'Get-Filehash' - Get-Filehash -Algorithm sha256 SSCERuntime_x64-PLK.exe
  - Use chocolatey utility 'checksum.exe'  - checksum -t sha256 -f SSCERuntime_x64-PLK.exe

  File:     SSCERuntime_x64-PLK.exe
  Type:     sha256
  Checksum: B9A6A18366C94E883BB5BD9DF87BB89A82115F170D457D9ABFCA827066F31B38

  - Use powershell function 'Get-Filehash' - Get-Filehash -Algorithm sha256 SSCERuntime_x64-PTB.exe
  - Use chocolatey utility 'checksum.exe'  - checksum -t sha256 -f SSCERuntime_x64-PTB.exe

  File:     SSCERuntime_x64-PTB.exe
  Type:     sha256
  Checksum: 5C1271D8F54135B5B84FBC20C0CD985F870495DB728047CFCAA04257209DA138

  - Use powershell function 'Get-Filehash' - Get-Filehash -Algorithm sha256 SSCERuntime_x64-RUS.exe
  - Use chocolatey utility 'checksum.exe'  - checksum -t sha256 -f SSCERuntime_x64-RUS.exe

  File:     SSCERuntime_x64-RUS.exe
  Type:     sha256
  Checksum: 440CAE3F6097CA69A999AFC7637B0640B64A589AD77DEE62830151D80FA3EC93

  - Use powershell function 'Get-Filehash' - Get-Filehash -Algorithm sha256 SSCERuntime_x64-TRK.exe
  - Use chocolatey utility 'checksum.exe'  - checksum -t sha256 -f SSCERuntime_x64-TRK.exe

  File:     SSCERuntime_x64-TRK.exe
  Type:     sha256
  Checksum: 09BBDDB3B16983EA1F6AEDDB93DBEA00C1035EAEBB70197F95B2041B484E1CAA

Contents of file LICENSE.txt is obtained from the software distribution page
under the Additional Information section (screenshot in the enclosed
RedistributionAuthority.pdf) and the software post installation in the files
EULA_ENU.rtf and REDIST_ENU.txt.  These files may also be located in the
distribution packages SSCERuntime_x86-ENU.exe and SSCERuntime_x64-ENU.exe as:

  SSCERuntime_x86-ENU.exe/SSCERuntime_x86-ENU.msi/EULA.rtf_x86
  SSCERuntime_x86-ENU.exe/SSCERuntime_x86-ENU.msi/REDIST.TXT_x86
  SSCERuntime_x64-ENU.exe/SSCERuntime_x64-ENU.msi/EULA.rtf_x64
  SSCERuntime_x64-ENU.exe/SSCERuntime_x64-ENU.msi/REDIST.TXT_x64

tools\SSCERuntime_x64-PTB.exe

md5: CF56F5EE41745F26B31C84A57E270E14 | sha1: 1631789CF3DE485C5166684791C04EC2B2544A54 | sha256: 5C1271D8F54135B5B84FBC20C0CD985F870495DB728047CFCAA04257209DA138 | sha512: BD16D04EED34D3557F0CA9DEB3E5A847263D2B52818290E74694AC0A1176D4C58EBCB7B74F3DE67BA543458D1731EA3AF0E988724F69ADEF4C95F8292D1AD68C

tools\SSCERuntime_x86-CHT.exe

md5: 5D7ABDC5CA1184194BAB030F7013C17E | sha1: EC8D1F146C3920D0306D2924EB8CA16C8EABEC88 | sha256: 3C0F5C1D3A60072F31BB5834F73388CFA5D41466DB5B5B167ACF6076696B304F | sha512: 21EF6968667AB092F254066995AC0B1B9A83FBF66ECD4AED8734239C1F85B9F2FD3032F35C96A9D040C3DFFF908C58E4DDB6EEEED56CA98ACAF3A0F62CF021FA

tools\SSCERuntime_x86-ESN.exe

md5: 0F5EE9E00B4013250824C39BF4C3B0B5 | sha1: F755F84C6B02E5BA80A13ED33655B035FC0B9516 | sha256: DE3D25C5EDB5CD5126121B92735CF974E90FDE471A4026B2B16321F15682F5FC | sha512: 3D6A0960949E71BEB51A4C8EF229C493C0D0FBEA42FBE453D0D02056A43EB1DC0538C74632C8C2EC671EC30895DC404908BE19CC19BA83083751C73EF93D6031

tools\SSCERuntime_x86-JPN.exe

md5: F61F116358DE4610E8834D7A5513E74B | sha1: B006956E600DE76522BF18DD846FDEC80AED925B | sha256: 2B48C0C7AC8147D14A3DC271DCD9FCCBA2A0CDF455665206EEE03C92A8F8A5D9 | sha512: 353FCA3D3CFC0F42D5B99E09A14F60533DE1F896C89472D2948C815CE7774BD5935F3515F4E08D8529B30C7E439FBF282062BF4C07F5C96E0D81C62B8FA09610

tools\SSCERuntime_x86-PTB.exe

md5: E97E09A7EB928B16419B27C59025B7BA | sha1: 8F08C74DC49248E6016F8D7CE2F6C5E97B3396CD | sha256: 1A2DFB186B3BC7BCC6DB1663AAC6BEE610346F7F7124F6734C3533FD894E17C4 | sha512: D2B5FE7563A50D6F8013CA9ACAF786903AEC3A8CA6B605DE6849CAA3AD549EF80072F813EB7400399C05A5D2D6D67572198181890D06C9FCAD6E64167C02C8D4

tools\chocolateyInstall.ps1

$ErrorActionPreference = 'Stop'

$toolsDir = $(Split-Path -parent $MyInvocation.MyCommand.Definition)

if ($env:ChocolateyForceX86 -eq 'true' -and (Get-ProcessorBits 64) -eq 'true') {
  Write-Error "32-bit install not supported on a 64-bit machine"
}

if ((Get-ProcessorBits 32) -eq 'true') {
  $architecture = 'x86'
} elseif ((Get-ProcessorBits 64) -eq 'true') {
  $architecture = 'x64'
} else {
  Write-Error 'Unsupported CPU architecture'
}

add-type @"
public struct Language {
   public string Code;
   public string Name;
   public string Mapping;
}
"@

$languages =  @{
    'br'    = [Language] @{ Code='br';    Name = 'Brazilian (Portuguese)';   Mapping = 'PTB' }
    'cz'    = [Language] @{ Code='cz';    Name = 'Czech';                    Mapping = 'CSY' }
    'de'    = [Language] @{ Code='de';    Name = 'German';                   Mapping = 'DEU' }
    'en'    = [Language] @{ Code='en';    Name = 'English';                  Mapping = 'ENU' }
    'es'    = [Language] @{ Code='es';    Name = 'Spanish';                  Mapping = 'ESN' }
    'fr'    = [Language] @{ Code='fr';    Name = 'French';                   Mapping = 'FRA' }
    'it'    = [Language] @{ Code='it';    Name = 'Italian';                  Mapping = 'ITA' }
    'ja'    = [Language] @{ Code='ja';    Name = 'Japanese';                 Mapping = 'JPN' }
    'ko'    = [Language] @{ Code='ko';    Name = 'Korean';                   Mapping = 'KOR' }
    'pl'    = [Language] @{ Code='pl';    Name = 'Polish';                   Mapping = 'PLK' }
    'ru'    = [Language] @{ Code='ru';    Name = 'Russian';                  Mapping = 'RUS' }
    'tr'    = [Language] @{ Code='tr';    Name = 'Turkish';                  Mapping = 'TRK' }
    'zh'    = [Language] @{ Code='zh';    Name = 'Chinese';                  Mapping = 'CHS' }
    'zh-CN' = [Language] @{ Code='zh-CN'; Name = 'Chinese (Simplified)';     Mapping = 'CHS' }
    'zh-TW' = [Language] @{ Code='zh-TW'; Name = 'Chinese (Traditional)';    Mapping = 'CHT' }
}

$pp = Get-PackageParameters

# check the language parameter and default to 'en' if not supplied
$language = $pp['Language']

if ($null -eq $language -or $language -eq '') {
  $language = 'en'
}

$relang = “(?i)^(br|cz|de|en|es|fr|it|ja|ko|pl|ru|tr|zh|zh-CN|zh-TW)$”

if ($language -notmatch $relang) {
  Write-Error "Unsupported language $($pp.Language)"
}

$mapping = $languages[$language].Mapping

# construct the filename and extract the relevant installer to a temp directory
$fileName = "{0}\SSCERuntime_{1}-{2}.exe" -f $toolsDir, $architecture, $mapping

$tempDir = Join-Path ([System.IO.Path]::GetTempPath()) ([System.IO.Path]::GetRandomFileName())
if (![System.IO.Directory]::Exists($tempDir)) { [System.IO.Directory]::CreateDirectory($tempDir) | Out-Null }

Start-Process "$fileName" -ArgumentList "/X:$tempDir /q" -Wait

$fileName = "{0}\SSCERuntime_{1}-{2}.msi" -f $tempDir, $architecture, $mapping

$packageArgs = @{
  PackageName    = $env:ChocolateyPackageName
  FileType       = 'msi'
  File           = $fileName
  SilentArgs     = '/quiet /qn /norestart'
  ValidExitCodes = @(0, 1641, 3010)
}

Install-ChocolateyInstallPackage @packageArgs

$files = Get-ChildItem $toolsDir -include *.exe -recurse

foreach ($file in $files) {
  New-Item "$file.ignore" -Type file -Force | Out-Null
}

Remove-Item -Path $tempDir -Recurse -Force -ErrorAction Ignore | Out-Null

tools\SSCERuntime_x64-DEU.exe

md5: E488E7C99A9C69C5D76E23F1E990D88A | sha1: 2FFC51B92488B67223B53176A5114AE56B8F91F4 | sha256: F86BAC8C81C3F42DC7100EAFA7CA1FA6CB587ADB49774DD1C67CC0072E8FCA3C | sha512: 987CFD028502EFEE8338C503661DB7D267DAADCB7C4B970DBE62DCB93F0D685B4D79C3516F003C29BDCCEA918557087801BAE91D86D98F519422BE91813A84F4

tools\SSCERuntime_x64-ITA.exe

md5: CAEC8BF6486B554BD34E8EF873D791D8 | sha1: 66FAE65131D33BE2610F44238CA8EABFE4CBCD1D | sha256: D00A3EAE732A8492FCE582B607E0CA2359FD5010368E3238A900FEC4CDADF0E2 | sha512: C0B84EA249A88A5B49A0931451E909E145CEEA8A02EC1F561243AF0F125A358E03280CE9762B206CC1E663DFAF00323BC8E371B101CFE398FE18E8162E8112DD

tools\SSCERuntime_x64-RUS.exe

md5: 4590510157B74B51B56A353581C194A6 | sha1: 469FF23C9605D7AD1790D38E8EB4AE2DE55C9337 | sha256: 440CAE3F6097CA69A999AFC7637B0640B64A589AD77DEE62830151D80FA3EC93 | sha512: 516347A177F4EFAB6BEC1A74A26A73604996374A081C48EDD9B0594D333086125FD5C411EF639B7F3BA3DB3A7E952D9F556CF8712E82040CBF830FC2817890BC

tools\SSCERuntime_x86-CSY.exe

md5: A520832EE6FDC3E39BA982DF64092050 | sha1: 9F27BA9067E83DF99C0FC6191B512E856DE96251 | sha256: 3767F675EBB6A08431B439BC6217A93CC7F70B9754A59FBE9CBB251EFBBA969D | sha512: 7B13E7D9F318B6524F507FDC2EEA9FE087074448DE93FEBABCE643D4AA0F61D67EA2133B98DA90D980D27E0EA6B2EFD2384360AE45009F2FDAEAD163B2C037A4

tools\SSCERuntime_x86-FRA.exe

md5: 43B88113B9CFC37C6AAB7AF9E8056FB6 | sha1: 0FD5B86C8C41F7B2995151B2F90001754953188E | sha256: C9DA688C6F749AD55E52D0B783FCE5EE98CD29BBCA6D65E3A9E8F5DFE50661C7 | sha512: 83768FDB30083F3CB3302A35EEC17530BBD355079BD17B9B5403EFB60CE95CFDA70659DED731B993A70B58E517CBC515694BD6DD2594FA37B75A762DF4017C23

tools\SSCERuntime_x86-KOR.exe

md5: D7242FCED331DB8512543286CFD68C94 | sha1: 2BEC6953329D6297F743B1F484E97A4F4AE4C5EA | sha256: 06069E54827480E91DAF17012878D929F02AF8A279B46ADFEFEF4593C26F6310 | sha512: EE5613D21D1E37D1E8AD832A31D973CE13154E9AE0980CBE5853DAFA793F33F5C5BB6479C05577EF31494577AC0920A89248C33B0B8D1675E49E9E8BBE5B8D2A

tools\SSCERuntime_x86-RUS.exe

md5: E6AD121BF0F5B074D9081CDAE9F77AA7 | sha1: 0FF6D1A44935D9FEE90AF1AF4D2D15CE3C015CE2 | sha256: 87C2BBEF40C59297893FAA562C7FF398822D621201FAA74DF76D8083B5AFE9BF | sha512: 1D5F392F36812EFF60A773E2E153ADFD1CC6C9B3435A75A43A2EA207BB6673AFC823DEE378CD6C523CB76D6AA0863913A40257BD76BB783D973E093A7E088160

tools\SSCERuntime_x64-CHS.exe

md5: 1ED9E7B1D209496DD4EA6AD417EFA9CD | sha1: 188613290E47618CFD4C75DED7E8106659A1BF00 | sha256: 6679A33F37BD37D2B1163465995AE09CB9EF6AF4B4026A20924CCB03FB03BC4B | sha512: 567BEF7A59040A680ABA7148B8733FB8A0D6B0064C38E1A99695A17BB2C5B2444D3E9DF9B9245E12220164CC14C6E51F421DEC3563D4E61CD60E3361F025AD07

tools\SSCERuntime_x64-ENU.exe

md5: 7137F10077B0F0D99ABB55595CA1ADC2 | sha1: D8CAA8B6953C02E0DAEF815B665FEFC37116C794 | sha256: 443D149C7A1A3D5C26189BF727A55287341FAD620225FD7AED610BA1762286E4 | sha512: F98C9E4C5D58D0C298D5CF8C8F3C103E6E809BC1E9478324261CACCC957E3BCB246CA49BE7600F9BA60376C8F1121524C7D64653D0F1957D5F3150DAEA36C784

tools\SSCERuntime_x64-JPN.exe

md5: 69198784A5392AEE35E8AC6C1FF91424 | sha1: 66AEFA69193E6A566D842D5C78745984AC38C4C0 | sha256: 1B57600E4D69AF91D8B01FA6FD55FA2F2791F0C0B048E8F9B3B1AA8F918357E1 | sha512: 027E63113108F9C1670D464697D50496323999D3424487C2E2885DFA53A2741F3C672AB18A472942290417A78732F56483932E45D989EDB7358E9C8C33D26DB2

tools\SSCERuntime_x64-TRK.exe

md5: A74EF1F05174F069F17131B0829AE418 | sha1: 681255E3859F04EF8D61ED2EBCB6F23063B68C54 | sha256: 09BBDDB3B16983EA1F6AEDDB93DBEA00C1035EAEBB70197F95B2041B484E1CAA | sha512: 9FD0016F339471D2C88227BC14F6517861EB60AB240DE02262281D5777D059A9CC6D56ED8CA7D9BAD06B8EB3D2DD117EAFA821CAFC4AE25DDAAEEC592F348DB5

tools\SSCERuntime_x86-DEU.exe

md5: BA692FDAA26E968917FFD0D0476F1DE4 | sha1: D364C18921C7AA1432C8BD6E81DCBEE2CA5A8384 | sha256: 814BF99DF12696A7E98DA77B84AA84EA43C22C5B41A05895F577C9F288010CC4 | sha512: D9EE799253EEAF00002AD2277704AACAE323CE8AE07B0002286C693E95E022D509ED2A85D7C97B6118FB95D9B4F57476F81F66220D3981AB72F36B2C1FDEFEC7

tools\SSCERuntime_x86-ITA.exe

md5: EEE121BEA55544BB7FE4DDBF6EA8D266 | sha1: C7486F71422EF872444F9553D0213225B870A444 | sha256: CFB25AC4A7FD7EB71EF00270EC0E11AAB563D38F8E01EC73530BBC8D0345C98A | sha512: 3FAC194A60AD0F4E4E323BBFFEB6EE3AAAC2D55FCACFC7ECF1F29ED365E75C2CDAC7C305182C670ACEAF503ECBB242A7F6A8000562394B5CF4487469EB92E420

tools\SSCERuntime_x86-PLK.exe

md5: 699D54DF9BDEB19C4DD9DC5B9A30639E | sha1: 5A09F5F28AC70A37A769CCAE6AEBE1C3F6EA151E | sha256: 0B8AAA75BAFCF96DF141B91B1A4437B6F7ADAB5F88791CC436839058D01F291A | sha512: DCF6F8CA05B582D60C1A63F535382E129F31AC7298B522BEE7D9F2B4B6E780038946C2D45F5911A63D085B9BE5780472A96CFF741BBF487BA32B101D3C189142

tools\SSCERuntime_x86-TRK.exe

md5: 4EE38D6B3D0318F6D2B8B12460FAF0BF | sha1: A4D893A9C3691FD5A2DE849FC94E4EE9B75557BC | sha256: 5FE905F71907FAA7CEFDEE2C3439E5C3A6BA6F0334C67E8A6B3811B0653922E4 | sha512: 71E87FACE0165BF8855204E4830B486BD1862964EB6886392944445CAA0B953EB4378B10E7374DE195FE3D13F617D58FCB2B3F354074A3F757331BCB9FC0C188

tools\SSCERuntime_x64-CHT.exe

md5: 345055CC96B3F27F87B325F28BA3323D | sha1: 4C19DC16D048764B6E32971228B3E760F212282C | sha256: C536AAA413F4EDB12B50D81E6FE5C6FDCFD03B39500F2CBD15BA02F488E9A865 | sha512: 021466DF2887E5C083D5DB5737E3543BE91F456A76129256E5E839838F7FB3212F6F1DD45DA441245BAD931654FA3C94F0B6AF730613ED1CBFB5E898624B57A6

tools\SSCERuntime_x64-ESN.exe

md5: CB8EDA03211EA0F138C45E86A0CE657A | sha1: ABAFE3AD4DF35D2AF5FF794A384417800130D82C | sha256: 3FB0C8BCF3C22F37A5A3BB4F4A8537149AAEA038442D1FBCBDA4780912E913FC | sha512: 83CF143F53B4013053579F000A48CCA6FE890ECFC4ECC732ED7C390510CCFC44837D18766F2FBE083C8391C4B6E5E18535AA4BFF4F119D59620F94789391C10D

tools\SSCERuntime_x64-KOR.exe

md5: 6438CA3E4A9EF2E890C571F86DC01C55 | sha1: 3CD0D928C6D621934D1759873CC5E4CE16222BBD | sha256: B1C9E335CD55131BBCE4C0F0EEBD9C15658ADA2812E48083EF1748C5A4C4A436 | sha512: 97031E571C04F2E51E3272483F4F11F7AB564C4947C87C6DFC9C7637198052361F0B2D34573FE27229CDC966A4FE225E16C980EE9C3D7448E7F6F05531921EDB

tools\SSCERuntime_x86-CHS.exe

md5: 034F9F00FE5560333EFD5153F9A63B72 | sha1: 48510BCB90CA54E10E721FE3AE195CAF0DC07FD0 | sha256: EEB5218D93BF89DF18479DE3817D49811E8FD0D6108A5A4B8F1CD56354734256 | sha512: C3CE3C7DD839ABDF26F952C062C8F4E807D4ECB64C1CB175F1A58CFB2AEB81E5F4CBAF872FF48983C2DFC4CDE5E5C9339B27FAB66795B408A7426DF8D2550396

tools\SSCERuntime_x86-ENU.exe

md5: 7AE4CB27DF6C41935F50F3138E0CD219 | sha1: C622A62B165132DCE5930B983C7C7FCE65115A26 | sha256: 44CA2585C7BD9EF66979C1C903A8A053B922A69BEAAD4DCC47015CD99FCF3CD4 | sha512: F1D42911A33B21890B3072FC170B27EBB61C9077398989871B5C9FBF261135A0D07B68885314D63F219C31C6219DB269F4DB82AAF817B96CFC0BF8EFE7CAD029

tools\SSCERuntime_x64-CSY.exe

md5: DAA74D903CF7845B589876B4934E7F78 | sha1: 865A7DE92D24C236F0E7DF0795DFD4846AC00727 | sha256: 1853A00F79684A175243E9D5DED003A0E53BB3D4272452E04EF38A79CF16C578 | sha512: 972D9AF386AADF44E5E7291A024F589071C829FF385B9FA687694633162BBD9AC6EE24CE8BA5FF2F5D1D58EBC335C29922A3CE2B08F378054A18D57473A01B4B

tools\SSCERuntime_x64-FRA.exe

md5: B5E1D6C053E0F7997E38B1D16948E8FC | sha1: 56D346EF4148A4E5C35005DCFDA08B9057FA4053 | sha256: 6DE2AB2799BB4FEF47B6E677DC052C9927D8C2F7F2FB7A05B2AF8BB664D09C77 | sha512: 149441A0055248567BBC9CF47B35B01C2C7BED6CD6E15C387BF9C1BC0F5E249019608ED558251B4B89947BE375CA16B6E3751C6E976A67470CF7A9A9D2C5F11A

tools\SSCERuntime_x64-PLK.exe

md5: EB5A1841A799402233B131B0B80BA9D0 | sha1: 9EF265A53F051B92FECFF5248C908437C5B363E2 | sha256: B9A6A18366C94E883BB5BD9DF87BB89A82115F170D457D9ABFCA827066F31B38 | sha512: C8FE3DAE7BEF0341CAC4333B8CB06C3BA276F6CEBE01D821580CA0A249092CFAB8A351BAB638E16AA7061F1EBC8AC17C20CEB53D0944714FE04F495851968BB9

Virus Scan Results

SSCERuntime_x64-CHS.exe (6679a33f37bd) - ## / 70
SSCERuntime_x64-CHT.exe (c536aaa413f4) - ## / 66
SSCERuntime_x64-CSY.exe (1853a00f7968) - ## / 69
SSCERuntime_x64-DEU.exe (f86bac8c81c3) - ## / 70
SSCERuntime_x64-ENU.exe (443d149c7a1a) - ## / 71
SSCERuntime_x64-ESN.exe (3fb0c8bcf3c2) - ## / 66
SSCERuntime_x64-FRA.exe (6de2ab2799bb) - ## / 70
SSCERuntime_x64-ITA.exe (d00a3eae732a) - ## / 69
SSCERuntime_x64-JPN.exe (1b57600e4d69) - ## / 67
SSCERuntime_x64-KOR.exe (b1c9e335cd55) - ## / 68
SSCERuntime_x64-PLK.exe (b9a6a18366c9) - ## / 69
SSCERuntime_x64-PTB.exe (5c1271d8f541) - ## / 70
SSCERuntime_x64-RUS.exe (440cae3f6097) - ## / 69
SSCERuntime_x64-TRK.exe (09bbddb3b169) - ## / 68
SSCERuntime_x86-CHS.exe (eeb5218d93bf) - ## / 65
SSCERuntime_x86-CHT.exe (3c0f5c1d3a60) - ## / 67
SSCERuntime_x86-CSY.exe (3767f675ebb6) - ## / 65
SSCERuntime_x86-DEU.exe (814bf99df126) - ## / 70
SSCERuntime_x86-ENU.exe (44ca2585c7bd) - ## / 69
SSCERuntime_x86-ESN.exe (de3d25c5edb5) - ## / 66
SSCERuntime_x86-FRA.exe (c9da688c6f74) - ## / 70
SSCERuntime_x86-ITA.exe (cfb25ac4a7fd) - ## / 70
SSCERuntime_x86-JPN.exe (2b48c0c7ac81) - ## / 69
SSCERuntime_x86-KOR.exe (06069e548274) - ## / 66
SSCERuntime_x86-PLK.exe (0b8aaa75bafc) - ## / 68
SSCERuntime_x86-PTB.exe (1a2dfb186b3b) - ## / 67
SSCERuntime_x86-RUS.exe (87c2bbef40c5) - ## / 69
SSCERuntime_x86-TRK.exe (5fe905f71907) - ## / 65
mssqlserver-compact4.0.4.0.8876.100.nupkg (ef5e55cf1dbe) - ## / 48

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

Add to Builder	Version	Downloads	Last Updated	Status
	Microsoft SQLServer Compact 4.0 with SP1 4.0.8876.100	3569	Sunday, October 1, 2023	Approved
	Microsoft SQLServer Compact 4.0 with SP1 4.0.8876.1	14577	Saturday, February 13, 2021	Approved

Dependencies

- dotnet3.5 (≥ 3.5.20160716)

Discussion for the Microsoft SQLServer Compact 4.0 with SP1 Package

Ground Rules:

This discussion is only about Microsoft SQLServer Compact 4.0 with SP1 and the Microsoft SQLServer Compact 4.0 with SP1 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 Microsoft SQLServer Compact 4.0 with SP1, 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

18,146

3,569

01 Oct 2023

Microsoft SQLServer Compact 4.0 with SP1

Microsoft SQLServer Compact 4.0 with SP1 4.0.8876.100

All Checks are Passing

Deployment Method: Individual Install, Upgrade, & Uninstall

Deployment Method:

1. Enter Your Internal Repository Url

2. Setup Your Environment

1. Ensure you are set for organizational deployment

2. Get the package into your environment

3. Copy Your Script

4. If applicable - Chocolatey configuration/installation

Features

Package Parameters

Notes

Ground Rules: