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.1.1.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.1.1.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.1.1.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.1.1.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

Passing
Failing
Pending
Unknown / Exempted

Downloads:

148,277

Downloads of v 2017.1.1.3-patch:

346

Last Update:

30 Sep 2017

Package Maintainer(s):

jtcmedia

Software Author(s):

Unity Technologies

Tags:

unity admin games cross-platform unity3d ide editor 3d vr multiplatform

Unity (Install)

This is a prerelease version of Unity (Install).

2017.1.1.3-patch | Updated: 30 Sep 2017

Downloads:

148,277

Downloads of v 2017.1.1.3-patch:

346

Maintainer(s):

jtcmedia

Software Author(s):

Unity Technologies

Tags:

unity admin games cross-platform unity3d ide editor 3d vr multiplatform

1

2

3

Unity (Install) 2017.1.1.3-patch

This is a prerelease version of Unity (Install).

This Package Contains an Exempted Check

Not All Tests Have Passed

Hide Checks

Validation Testing Passed

Verification Testing Passed

Details

Scan Testing Exemption for this package version only:

Details

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Unity (Install), run the following command from the command line or from PowerShell:

To upgrade Unity (Install), run the following command from the command line or from PowerShell:

To uninstall Unity (Install), 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 unity --internalize --version=2017.1.1.3-patch --pre --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 unity -y --source="'INTERNAL REPO URL'" --version="'2017.1.1.3-patch'" --prerelease [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 unity -y --source="'INTERNAL REPO URL'" --version="'2017.1.1.3-patch'" --prerelease
$exitCode = $LASTEXITCODE

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

Exit $exitCode


- name: Install unity
  win_chocolatey:
    name: unity
    version: '2017.1.1.3-patch'
    source: INTERNAL REPO URL
    state: present
    allow_prerelease: yes

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


chocolatey_package 'unity' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '2017.1.1.3-patch'
  options  '--prerelease'
end

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


cChocoPackageInstaller unity
{
    Name        = "unity"
    Version     = "2017.1.1.3-patch"
    Source      = "INTERNAL REPO URL"
    chocoParams = "--prerelease"
}

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


package { 'unity':
  ensure          => '2017.1.1.3-patch',
  install_options => ['--prerelease'],
  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.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

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

This package was approved as a trusted package on 30 Sep 2017.

Description

Features

Multiplatform game engine (Note: Need to install separate package for some Target Platforms)

Android, iOS, Windows Store, Tizen
PC, MacOS, Linux
WebGL
PlayStation 4, PlayStation Vita, Xbox 360, Xbox One, Wii U, Nintendo 3DS
Oculus Rift, Google Cardboard, PlayStation VR, Gear VR, Microsoft Hololens
Android TV, Samsung SMART TV, tvOS

General

Scripting with C#, JavaScript
Debugging with IDE MonoDevelop and Visual Studio
Make game with Editor. Fully Extendible Editor.
2D/3D physics (NVIDIA PhysX 3™ and Box2D)
Native Code Plugin Support

Animation

Integrated Animation Editor
Blend Trees
Inverse Kinematics
State Machines
Sync Layers and Additional Curves

Graphics

Sprite Packer
Physically-Based Shading
Low-Level Rendering Access
Shuriken Particle System
Dynamic Fonts with Markup
Enlighten-powered Real-time Global Illumination
Static Batching
Dynamic Batching
Level of Detail
GPU Skinning for DirectX 11 and OpenGL ES 3.0
Deferred Rendering

Audio

Hierarchies of mixers
Native Audio Plugins
Transition the mood of your soundscape

Services

Asset store
Collaborate
Cloud builds
Analytics
Performance reporting
Ads
Multiplayer
Everyplay
Certification

Other

DLC: Assets Bundle
External Version Control Support
Multiplayer Networking with RakNet
.NET Socket Support
iOS Crash Reporter
Terrains
NavMeshes and Path-Finding
Integrated SpeedTree support
Command-line interface

Supported formats

Images: png, bmp, tif, tga, jpg, psd
3D formats: fbx, dae, 3DS, dxf, obj, max, mb, ma, blend
Audio: mp3, ogg, wav, aif, mod, it, s3m, xm
Movie: mov, mpg, mpeg, mp4, avi, asf

Package Specific

Package Parameters

The following package parameters can be set:

/InstallationPath: - Where to install the editor. Path must already exist. - defaults to "C:\Program Files\Unity"

To pass parameters, use --params "''" (e.g. choco install packageID [other options] --params="'/ITEM:value /ITEM2:value2 /FLAG_BOOLEAN'").

To have choco remember parameters on upgrade, be sure to set choco feature enable -n=useRememberedArgumentsForUpgrades.

Files

tools\chocolateyinstall.ps1

$ErrorActionPreference = 'Stop';

$packageName        = 'unity'
$toolsDir           = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url64              = 'https://beta.unity3d.com/download/929150d2fa14/Windows64EditorInstaller/UnitySetup64-2017.1.1p3.exe'
$checksum64         = '4a14b1e7853ac2c5e5d6ee679a817e9a9517b93e8b9d89ebd3317ccb8a88ad57'

$args = '/S'

$pp = Get-PackageParameters
if ($pp.InstallationPath) {
    $args += " /D=$($pp.InstallationPath)"
    Write-Host "Param: Installing to $($pp.InstallationPath)"
}

$packageArgs = @{
  packageName    = $packageName
  fileType       = 'EXE'
  url64bit       = $url64
  softwareName   = 'Unity'
  checksum64     = $checksum64
  checksumType64 = 'sha256'
  silentArgs     = $args
  validExitCodes = @(0)
}

Install-ChocolateyPackage @packageArgs

tools\chocolateyuninstall.ps1

$ErrorActionPreference = 'Stop';

$packageName = 'unity'
$softwareName = 'Unity'
$installerType = 'EXE' 
$silentArgs = '/S'
$validExitCodes = @(0)

$uninstalled = $false
[array]$key = Get-UninstallRegistryKey -SoftwareName $softwareName

if ($key.Count -eq 1) {
  $key | % { 
    $file = "$($_.UninstallString)"

    Uninstall-ChocolateyPackage -PackageName $packageName `
                                -FileType $installerType `
                                -SilentArgs "$silentArgs" `
                                -ValidExitCodes $validExitCodes `
                                -File "$file"
  }
} elseif ($key.Count -eq 0) {
  Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
  Write-Warning "$key.Count matches found!"
  Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
  Write-Warning "Please alert package maintainer the following keys were matched:"
  $key | % {Write-Warning "- $_.DisplayName"}
}

Virus Scan Results

unity.2017.1.1.3-patch.nupkg (454043108444) - ## / 60

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version History

Version	Downloads	Last Updated	Status
Unity (Install) 2022.1.17	24	Thursday, September 22, 2022	Waiting for Maintainer
Unity (Install) 2022.1.16	727	Saturday, September 10, 2022	Approved
Unity (Install) 2022.1.15	495	Friday, September 2, 2022	Approved
Unity (Install) 2022.1.14	433	Tuesday, August 23, 2022	Exempted
Unity (Install) 2022.1.13	510	Friday, August 12, 2022	Exempted
Unity (Install) 2022.1.12	369	Saturday, August 6, 2022	Exempted
Unity (Install) 2022.1.11	565	Thursday, July 28, 2022	Exempted
Unity (Install) 2022.1.10	448	Thursday, July 21, 2022	Exempted
Unity (Install) 2022.1.9	363	Friday, July 15, 2022	Exempted
Unity (Install) 2022.1.8	432	Friday, July 8, 2022	Exempted
Unity (Install) 2022.1.7	407	Thursday, June 30, 2022	Exempted
Unity (Install) 2022.1.6	345	Friday, June 24, 2022	Exempted
Unity (Install) 2022.1.5	406	Friday, June 17, 2022	Exempted
Unity (Install) 2022.1.4	520	Thursday, June 9, 2022	Exempted
Unity (Install) 2022.1.3	319	Thursday, June 2, 2022	Exempted
Unity (Install) 2022.1.2	25	Friday, May 27, 2022	Exempted
Unity (Install) 2022.1.1	616	Saturday, May 21, 2022	Exempted
Unity (Install) 2022.1.0	611	Friday, May 13, 2022	Exempted
Unity (Install) 2021.3.10	152	Saturday, September 17, 2022	Approved
Unity (Install) 2021.3.9	15	Friday, September 2, 2022	Approved
Unity (Install) 2021.3.8	14	Wednesday, August 10, 2022	Exempted
Unity (Install) 2021.3.7	20	Friday, July 29, 2022	Exempted
Unity (Install) 2021.3.6	31	Saturday, July 9, 2022	Exempted
Unity (Install) 2021.3.5	23	Thursday, June 23, 2022	Exempted
Unity (Install) 2021.3.4	35	Thursday, June 2, 2022	Exempted
Unity (Install) 2021.3.3	13	Friday, May 27, 2022	Exempted
Unity (Install) 2021.3.2	450	Sunday, May 8, 2022	Exempted
Unity (Install) 2021.3.1	646	Saturday, April 23, 2022	Exempted
Unity (Install) 2021.3.0	660	Wednesday, April 13, 2022	Exempted
Unity (Install) 2021.2.19	531	Thursday, April 7, 2022	Exempted
Unity (Install) 2021.2.18	481	Saturday, April 2, 2022	Exempted
Unity (Install) 2021.2.17	490	Friday, March 25, 2022	Exempted
Unity (Install) 2021.2.16	312	Friday, March 18, 2022	Exempted
Unity (Install) 2021.2.15	42	Saturday, March 12, 2022	Exempted
Unity (Install) 2021.2.14	30	Friday, March 4, 2022	Exempted
Unity (Install) 2021.2.13	787	Friday, February 25, 2022	Exempted
Unity (Install) 2021.2.12	38	Friday, February 18, 2022	Exempted
Unity (Install) 2021.2.11	90	Friday, February 11, 2022	Exempted
Unity (Install) 2021.2.10	911	Saturday, February 5, 2022	Exempted
Unity (Install) 2021.2.9	510	Friday, January 28, 2022	Exempted
Unity (Install) 2021.2.8	834	Friday, January 14, 2022	Exempted
Unity (Install) 2021.2.7	1052	Friday, December 17, 2021	Exempted
Unity (Install) 2021.2.6	446	Monday, December 13, 2021	Exempted
Unity (Install) 2021.2.5	576	Friday, December 3, 2021	Exempted
Unity (Install) 2021.2.4	424	Friday, November 26, 2021	Exempted
Unity (Install) 2021.2.3	453	Friday, November 19, 2021	Exempted
Unity (Install) 2021.2.2	500	Friday, November 12, 2021	Exempted
Unity (Install) 2021.2.1	487	Saturday, November 6, 2021	Exempted
Unity (Install) 2021.2.0	550	Tuesday, October 26, 2021	Exempted
Unity (Install) 2021.1.26	471	Thursday, October 21, 2021	Exempted
Unity (Install) 2021.1.25	513	Friday, October 15, 2021	Exempted
Unity (Install) 2021.1.24	541	Friday, October 8, 2021	Exempted
Unity (Install) 2021.1.23	459	Friday, October 1, 2021	Exempted
Unity (Install) 2021.1.22	455	Thursday, September 23, 2021	Exempted
Unity (Install) 2021.1.21	520	Thursday, September 16, 2021	Exempted
Unity (Install) 2021.1.20	639	Friday, September 10, 2021	Exempted
Unity (Install) 2021.1.19	387	Thursday, September 2, 2021	Exempted
Unity (Install) 2021.1.18	429	Friday, August 27, 2021	Exempted
Unity (Install) 2021.1.17	468	Tuesday, August 17, 2021	Exempted
Unity (Install) 2021.1.16	639	Saturday, July 31, 2021	Exempted
Unity (Install) 2021.1.15	817	Thursday, July 15, 2021	Exempted
Unity (Install) 2021.1.14	358	Friday, July 9, 2021	Exempted
Unity (Install) 2021.1.13	359	Thursday, July 1, 2021	Exempted
Unity (Install) 2021.1.12	68	Thursday, June 17, 2021	Exempted
Unity (Install) 2021.1.11	59	Thursday, June 10, 2021	Exempted
Unity (Install) 2021.1.10	1121	Saturday, June 5, 2021	Exempted
Unity (Install) 2021.1.9	46	Saturday, May 29, 2021	Exempted
Unity (Install) 2021.1.7	543	Friday, May 14, 2021	Exempted
Unity (Install) 2021.1.6	51	Friday, May 7, 2021	Exempted
Unity (Install) 2021.1.5	784	Wednesday, April 28, 2021	Exempted
Unity (Install) 2021.1.4	304	Friday, April 23, 2021	Approved
Unity (Install) 2021.1.3	413	Wednesday, April 14, 2021	Approved
Unity (Install) 2021.1.2	343	Thursday, April 8, 2021	Approved
Unity (Install) 2021.1.1	402	Wednesday, March 31, 2021	Approved
Unity (Install) 2021.1.0	412	Thursday, March 25, 2021	Approved
Unity (Install) 2020.3.39	9	Friday, September 16, 2022	Approved
Unity (Install) 2020.3.38	11	Thursday, August 18, 2022	Exempted
Unity (Install) 2020.3.37	11	Friday, July 22, 2022	Exempted
Unity (Install) 2020.3.36	16	Friday, June 17, 2022	Exempted
Unity (Install) 2020.3.35	22	Friday, May 27, 2022	Exempted
Unity (Install) 2020.3.34	27	Thursday, May 5, 2022	Exempted
Unity (Install) 2020.3.33	87	Friday, April 8, 2022	Exempted
Unity (Install) 2020.3.32	23	Thursday, March 24, 2022	Exempted
Unity (Install) 2020.3.31	23	Sunday, March 20, 2022	Exempted
Unity (Install) 2020.3.1	310	Tuesday, March 23, 2021	Approved
Unity (Install) 2020.3.0	1034	Thursday, March 11, 2021	Approved
Unity (Install) 2020.2.7	322	Saturday, March 6, 2021	Approved
Unity (Install) 2020.2.6	483	Thursday, February 25, 2021	Approved
Unity (Install) 2020.2.5	381	Friday, February 19, 2021	Approved
Unity (Install) 2020.2.4	321	Saturday, February 13, 2021	Approved
Unity (Install) 2020.2.3	479	Friday, February 5, 2021	Approved
Unity (Install) 2020.2.2	655	Friday, January 22, 2021	Approved
Unity (Install) 2020.2.1	826	Thursday, December 24, 2020	Approved
Unity (Install) 2020.2.0	839	Tuesday, December 15, 2020	Approved
Unity (Install) 2020.1.17	445	Wednesday, December 9, 2020	Approved
Unity (Install) 2020.1.16	478	Friday, December 4, 2020	Approved
Unity (Install) 2020.1.15	441	Saturday, November 28, 2020	Approved
Unity (Install) 2020.1.14	286	Saturday, November 21, 2020	Approved
Unity (Install) 2020.1.13	455	Thursday, November 12, 2020	Approved
Unity (Install) 2020.1.12	457	Friday, November 6, 2020	Approved
Unity (Install) 2020.1.11	510	Thursday, October 29, 2020	Approved
Unity (Install) 2020.1.10	486	Thursday, October 22, 2020	Approved
Unity (Install) 2020.1.9	407	Thursday, October 15, 2020	Approved
Unity (Install) 2020.1.8	763	Wednesday, October 7, 2020	Approved
Unity (Install) 2020.1.7	562	Friday, October 2, 2020	Approved
Unity (Install) 2020.1.6	863	Thursday, September 17, 2020	Approved
Unity (Install) 2020.1.5	446	Friday, September 11, 2020	Approved
Unity (Install) 2020.1.4	516	Wednesday, September 2, 2020	Approved
Unity (Install) 2020.1.3	568	Monday, August 24, 2020	Approved
Unity (Install) 2020.1.2	570	Thursday, August 13, 2020	Approved
Unity (Install) 2020.1.1	383	Thursday, August 6, 2020	Approved
Unity (Install) 2020.1.0	558	Friday, July 24, 2020	Approved
Unity (Install) 2019.4.40	16	Friday, June 17, 2022	Exempted
Unity (Install) 2019.4.39	23	Wednesday, May 18, 2022	Exempted
Unity (Install) 2019.4.37	26	Wednesday, March 23, 2022	Exempted
Unity (Install) 2019.4.36	16	Sunday, March 20, 2022	Exempted
Unity (Install) 2019.4.6	253	Friday, July 31, 2020	Approved
Unity (Install) 2019.4.5	612	Friday, July 24, 2020	Approved
Unity (Install) 2019.4.4	441	Thursday, July 16, 2020	Approved
Unity (Install) 2019.4.3	572	Thursday, July 9, 2020	Approved
Unity (Install) 2019.4.2	439	Thursday, July 2, 2020	Approved
Unity (Install) 2019.4.1	659	Friday, June 19, 2020	Approved
Unity (Install) 2019.4.0	572	Wednesday, June 10, 2020	Approved
Unity (Install) 2019.3.15	598	Thursday, May 28, 2020	Approved
Unity (Install) 2019.3.14	541	Wednesday, May 20, 2020	Approved
Unity (Install) 2019.3.13	621	Thursday, May 7, 2020	Approved
Unity (Install) 2019.3.12	478	Thursday, April 30, 2020	Approved
Unity (Install) 2019.3.11	458	Friday, April 24, 2020	Approved
Unity (Install) 2019.3.10	659	Friday, April 17, 2020	Approved
Unity (Install) 2019.3.9	482	Thursday, April 9, 2020	Approved
Unity (Install) 2019.3.8	279	Tuesday, April 7, 2020	Approved
Unity (Install) 2019.3.7	830	Thursday, March 26, 2020	Approved
Unity (Install) 2019.3.6	743	Friday, March 20, 2020	Approved
Unity (Install) 2019.3.5	702	Saturday, March 14, 2020	Approved
Unity (Install) 2019.3.4	591	Saturday, March 7, 2020	Approved
Unity (Install) 2019.3.3	652	Tuesday, March 3, 2020	Approved
Unity (Install) 2019.3.0	1710	Friday, January 31, 2020	Approved
Unity (Install) 2019.2.19	829	Thursday, January 23, 2020	Approved
Unity (Install) 2019.2.18	1213	Friday, January 17, 2020	Approved
Unity (Install) 2019.2.17	677	Tuesday, January 7, 2020	Approved
Unity (Install) 2019.2.16	1090	Saturday, December 14, 2019	Approved
Unity (Install) 2019.2.15	170	Thursday, December 5, 2019	Approved
Unity (Install) 2019.2.14	820	Thursday, November 28, 2019	Approved
Unity (Install) 2019.2.13	533	Thursday, November 21, 2019	Approved
Unity (Install) 2019.2.12	740	Tuesday, November 12, 2019	Approved
Unity (Install) 2019.2.11	714	Saturday, November 2, 2019	Approved
Unity (Install) 2019.2.10	621	Thursday, October 24, 2019	Approved
Unity (Install) 2019.2.9	792	Saturday, October 12, 2019	Approved
Unity (Install) 2019.2.8	764	Friday, October 4, 2019	Approved
Unity (Install) 2019.2.7	757	Tuesday, October 1, 2019	Approved
Unity (Install) 2019.2.6	797	Thursday, September 19, 2019	Approved
Unity (Install) 2019.2.5	622	Thursday, September 12, 2019	Approved
Unity (Install) 2019.2.4	530	Saturday, September 7, 2019	Approved
Unity (Install) 2019.2.3	725	Thursday, August 29, 2019	Approved
Unity (Install) 2019.2.2	602	Thursday, August 22, 2019	Approved
Unity (Install) 2019.2.1	837	Thursday, August 15, 2019	Approved
Unity (Install) 2019.2.0	1030	Wednesday, July 31, 2019	Approved
Unity (Install) 2019.1.13	170	Friday, August 9, 2019	Approved
Unity (Install) 2019.1.12	719	Saturday, July 27, 2019	Approved
Unity (Install) 2019.1.11	477	Saturday, July 20, 2019	Approved
Unity (Install) 2019.1.10	508	Saturday, July 13, 2019	Approved
Unity (Install) 2019.1.9	546	Saturday, July 6, 2019	Approved
Unity (Install) 2019.1.8	598	Monday, June 24, 2019	Approved
Unity (Install) 2019.1.7	467	Monday, June 17, 2019	Approved
Unity (Install) 2019.1.6	421	Tuesday, June 11, 2019	Approved
Unity (Install) 2019.1.5	501	Tuesday, June 4, 2019	Approved
Unity (Install) 2019.1.4	558	Saturday, May 25, 2019	Approved
Unity (Install) 2019.1.3	593	Saturday, May 18, 2019	Approved
Unity (Install) 2019.1.1	801	Saturday, May 4, 2019	Approved
Unity (Install) 2019.1.0.20190417	810	Wednesday, April 17, 2019	Approved
Unity (Install) 2019.1.0	244	Wednesday, April 17, 2019	Approved
Unity (Install) 2018.3.12	766	Tuesday, April 9, 2019	Approved
Unity (Install) 2018.3.11	797	Saturday, March 30, 2019	Approved
Unity (Install) 2018.3.10	530	Tuesday, March 26, 2019	Approved
Unity (Install) 2018.3.9	582	Wednesday, March 20, 2019	Approved
Unity (Install) 2018.3.8	746	Saturday, March 9, 2019	Approved
Unity (Install) 2018.3.7	567	Tuesday, March 5, 2019	Approved
Unity (Install) 2018.3.6	941	Saturday, February 16, 2019	Approved
Unity (Install) 2018.3.5	571	Saturday, February 9, 2019	Approved
Unity (Install) 2018.3.4	654	Friday, February 1, 2019	Approved
Unity (Install) 2018.3.3	537	Saturday, January 26, 2019	Approved
Unity (Install) 2018.3.2	716	Friday, January 18, 2019	Approved
Unity (Install) 2018.3.1	841	Friday, January 11, 2019	Approved
Unity (Install) 2018.3.0	1387	Friday, December 14, 2018	Approved
Unity (Install) 2018.2.19	730	Saturday, December 8, 2018	Approved
Unity (Install) 2018.2.18	663	Saturday, December 1, 2018	Approved
Unity (Install) 2018.2.17	638	Friday, November 23, 2018	Approved
Unity (Install) 2018.2.16	587	Friday, November 16, 2018	Approved
Unity (Install) 2018.2.15	657	Saturday, November 10, 2018	Approved
Unity (Install) 2018.2.14	974	Sunday, October 28, 2018	Approved
Unity (Install) 2018.2.13	678	Saturday, October 20, 2018	Approved
Unity (Install) 2018.2.12	475	Sunday, October 14, 2018	Approved
Unity (Install) 2018.2.11	742	Friday, October 5, 2018	Approved
Unity (Install) 2018.2.10	856	Thursday, September 27, 2018	Approved
Unity (Install) 2018.2.9	422	Monday, September 24, 2018	Approved
Unity (Install) 2018.2.8	531	Monday, September 17, 2018	Approved
Unity (Install) 2018.2.7	655	Monday, September 10, 2018	Approved
Unity (Install) 2018.2.6	795	Friday, August 31, 2018	Approved
Unity (Install) 2018.2.5	632	Thursday, August 23, 2018	Approved
Unity (Install) 2018.2.4	458	Monday, August 20, 2018	Approved
Unity (Install) 2018.2.3	506	Monday, August 13, 2018	Approved
Unity (Install) 2018.2.2	578	Monday, August 6, 2018	Approved
Unity (Install) 2018.2.1	536	Friday, July 27, 2018	Approved
Unity (Install) 2018.2.0	763	Thursday, July 12, 2018	Approved
Unity (Install) 2018.1.7	416	Sunday, July 8, 2018	Approved
Unity (Install) 2018.1.6	869	Friday, June 22, 2018	Approved
Unity (Install) 2018.1.5	548	Monday, June 18, 2018	Approved
Unity (Install) 2018.1.4	526	Monday, June 11, 2018	Approved
Unity (Install) 2018.1.3	511	Wednesday, June 6, 2018	Approved
Unity (Install) 2018.1.2	725	Monday, May 28, 2018	Approved
Unity (Install) 2018.1.1	548	Monday, May 21, 2018	Approved
Unity (Install) 2018.1.0	1068	Wednesday, May 2, 2018	Approved
Unity (Install) 2017.4.1	819	Friday, April 20, 2018	Approved
Unity (Install) 2017.3.1.4-patch	362	Wednesday, March 14, 2018	Approved
Unity (Install) 2017.3.1.3-patch	289	Wednesday, March 7, 2018	Approved
Unity (Install) 2017.3.1.2-patch	302	Wednesday, February 28, 2018	Approved
Unity (Install) 2017.3.1.1-patch	289	Friday, February 16, 2018	Approved
Unity (Install) 2017.3.1	1959	Wednesday, February 7, 2018	Approved
Unity (Install) 2017.3.0.4-patch	312	Wednesday, January 31, 2018	Exempted
Unity (Install) 2017.3.0.3-patch	341	Monday, January 22, 2018	Approved
Unity (Install) 2017.3.0.2-patch	303	Wednesday, January 17, 2018	Approved
Unity (Install) 2017.3.0.1-patch	347	Monday, December 25, 2017	Approved
Unity (Install) 2017.3.0	2025	Wednesday, December 20, 2017	Approved
Unity (Install) 2017.2.1.4-patch	324	Friday, February 16, 2018	Exempted
Unity (Install) 2017.2.1.3-patch	251	Friday, February 16, 2018	Approved
Unity (Install) 2017.2.1.1-patch	286	Friday, December 22, 2017	Approved
Unity (Install) 2017.2.1	1100	Wednesday, December 13, 2017	Approved
Unity (Install) 2017.2.0.4-patch	319	Wednesday, December 6, 2017	Approved
Unity (Install) 2017.2.0.3-patch	325	Monday, November 27, 2017	Approved
Unity (Install) 2017.2.0.1-patch	348	Monday, November 6, 2017	Approved
Unity (Install) 2017.2.0	1655	Friday, October 13, 2017	Approved
Unity (Install) 2017.1.2.2-patch	316	Friday, October 27, 2017	Approved
Unity (Install) 2017.1.2.1-patch	363	Friday, October 13, 2017	Approved
Unity (Install) 2017.1.2	709	Saturday, October 7, 2017	Approved
Unity (Install) 2017.1.1.4-patch	350	Wednesday, October 4, 2017	Approved
Unity (Install) 2017.1.1.3-patch	346	Saturday, September 30, 2017	Approved
Unity (Install) 2017.1.1.2-patch	368	Saturday, September 16, 2017	Approved
Unity (Install) 2017.1.1.1-patch	361	Friday, September 8, 2017	Approved
Unity (Install) 2017.1.1	1322	Tuesday, September 5, 2017	Approved
Unity (Install) 2017.1.0	1430	Wednesday, July 12, 2017	Approved
Unity (Install) 2017.1.0-p4	398	Friday, August 25, 2017	Exempted
Unity (Install) 5.6.2	930	Thursday, June 22, 2017	Approved
Unity (Install) 5.6.1	1141	Thursday, May 11, 2017	Approved
Unity (Install) 5.6.0	1487	Saturday, April 1, 2017	Approved
Unity (Install) 5.6.0-b11	386	Thursday, March 9, 2017	Exempted
Unity (Install) 5.5.2	1039	Saturday, February 25, 2017	Approved
Unity (Install) 5.5.1	1167	Wednesday, January 25, 2017	Approved
Unity (Install) 5.5.0	583	Tuesday, January 17, 2017	Approved
Unity 5.4.1	1177	Sunday, October 9, 2016	Approved
Unity 5.4.0	3196	Thursday, July 28, 2016	Approved
Unity 5.3.5.1	407	Sunday, May 22, 2016	Approved
Unity 5.3.4	601	Saturday, March 19, 2016	Approved
Unity 5.3.3	549	Thursday, February 25, 2016	Approved
Unity 5.3.2	376	Tuesday, February 16, 2016	Approved
Unity 5.3.1	536	Wednesday, December 23, 2015	Approved
Unity 5.0.1	985	Monday, April 13, 2015	Approved
Unity 4.6.2	601	Sunday, February 8, 2015	Approved
Unity 4.6.0	637	Monday, December 1, 2014	Approved
Unity 4.5.5	635	Tuesday, October 14, 2014	Approved
Unity 4.5.4	742	Thursday, September 11, 2014	Approved
Unity 4.5.3	540	Friday, September 5, 2014	Approved
Unity 4.5.2	446	Monday, August 11, 2014	Approved
Unity 4.5.1	573	Tuesday, June 24, 2014	Approved
Unity 4.5.0	527	Wednesday, May 28, 2014	Approved
Unity 4.3.4	590	Saturday, February 22, 2014	Approved
Unity 4.2.1	593	Monday, September 2, 2013	Approved
Unity 4.2.0	501	Sunday, July 28, 2013	Approved

Release Notes

Release Notes

Dependencies

- chocolatey-core.extension (≥ 1.3.1)

Discussion for the Unity (Install) Package

Ground Rules:

This discussion is only about Unity (Install) and the Unity (Install) 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 Unity (Install), 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.

148,277

346

30 Sep 2017

Unity (Install)

1 2 3 Unity (Install) 2017.1.1.3-patch

This Package Contains an Exempted Check

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

Multiplatform game engine (Note: Need to install separate package for some Target Platforms)

General

Animation

Graphics

Audio

Services

Other

Supported formats

Package Specific

Package Parameters

Ground Rules:

1

2

3

Unity (Install) 2017.1.1.3-patch