Step 1: Review Your Packages

Step 2: Choose Your Integration Method

Step 3: Copy Your Script or Download Config

Option 1: Copy Script

Option 2: Download Config

Step 4: Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

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

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

Option 2: Internalized Package (Reliable, Scalable)

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

Step 5: Copy Your Script

See options you can pass to upgrade.

See best practices for scripting.

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

### c. Other Requirements ###

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

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

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

## 2. TOP LEVEL VARIABLES ##

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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

- name: Install and Configure Chocolatey
  hosts: all

## 2. TOP LEVEL VARIABLES ##
  vars:

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

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

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

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

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

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

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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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

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

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

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

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

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

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

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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

chocolatey_feature 'useBackgroundService' do
  action :enable
end

chocolatey_feature 'useBackgroundServiceWithNonAdministratorsOnly' do
  action :enable
end

chocolatey_feature 'allowBackgroundServiceUninstallsFromUserInstallsOnly' do
  action :enable
end

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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


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

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

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

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

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


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


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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Need Help? View our docs or file an issue.

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

Current Version	New Version

Downloads:

1,922,925

Downloads of v 7.4.14:

3,056

Last Update:

05 Jan 2021

Package Maintainer(s):

Software Author(s):

PHP Authors

Tags:

php development programming foss cross-platform admin

PHP (Hypertext Preprocessor)

This is not the latest version of PHP (Hypertext Preprocessor) available.

7.4.14 | Updated: 05 Jan 2021

Downloads:

1,922,925

Downloads of v 7.4.14:

3,056

Maintainer(s):

Software Author(s):

PHP Authors

Tags:

php development programming foss cross-platform admin

PHP (Hypertext Preprocessor) 7.4.14

This is not the latest version of PHP (Hypertext Preprocessor) available.

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Hide Checks

Validation Testing Passed

Verification Testing Passed

Details

Scan Testing Resulted in Flagged:

This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.

We recommend clicking the "Details" link to make your own decision on installing this package.

Details

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install PHP (Hypertext Preprocessor), run the following command from the command line or from PowerShell:

To upgrade PHP (Hypertext Preprocessor), run the following command from the command line or from PowerShell:

To uninstall PHP (Hypertext Preprocessor), 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 php --internalize --version=7.4.14 --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 php -y --source="'INTERNAL REPO URL'" --version="'7.4.14'" [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 php -y --source="'INTERNAL REPO URL'" --version="'7.4.14'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode


- name: Install php
  win_chocolatey:
    name: php
    version: '7.4.14'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'php' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '7.4.14'
end

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


cChocoPackageInstaller php
{
    Name     = "php"
    Version  = "7.4.14"
    Source   = "INTERNAL REPO URL"
}

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


package { 'php':
  ensure   => '7.4.14',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

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

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Package Approved

This package was approved as a trusted package on 06 Jan 2021.

Description

PHP is an HTML-embedded scripting language. Much of its syntax is borrowed from C, Java and Perl with a couple of unique PHP-specific features thrown in. The goal of the language is to allow web developers to write dynamically generated pages quickly.

This product includes PHP software, freely available from http://www.php.net/software/

Package Parameters

/DontAddToPath - Do not add install directory to path
/InstallDir - Override the installation directory (needs to be specified both during install and update, until it is remembered by choco)
/ThreadSafe - Install the thread safe version of php that is compatible with Apache.

These parameters can be passed to the installer with the use of --package-parameters.
For example: choco install php --package-parameters='"/ThreadSafe ""/InstallDir:C:\PHP"""'.

Files

legal\LICENSE.txt

--------------------------------------------------------------------
                  The PHP License, version 3.01
Copyright (c) 1999 - 2018 The PHP Group. All rights reserved.
--------------------------------------------------------------------

Redistribution and use in source and binary forms, with or without
modification, is permitted provided that the following conditions
are met:

  1. Redistributions of source code must retain the above copyright
     notice, this list of conditions and the following disclaimer.

  2. Redistributions in binary form must reproduce the above copyright
     notice, this list of conditions and the following disclaimer in
     the documentation and/or other materials provided with the
     distribution.

  3. The name "PHP" must not be used to endorse or promote products
     derived from this software without prior written permission. For
     written permission, please contact [email protected].

  4. Products derived from this software may not be called "PHP", nor
     may "PHP" appear in their name, without prior written permission
     from [email protected].  You may indicate that your software works in
     conjunction with PHP by saying "Foo for PHP" instead of calling
     it "PHP Foo" or "phpfoo"

  5. The PHP Group may publish revised and/or new versions of the
     license from time to time. Each version will be given a
     distinguishing version number.
     Once covered code has been published under a particular version
     of the license, you may always continue to use it under the terms
     of that version. You may also choose to use such covered code
     under the terms of any subsequent version of the license
     published by the PHP Group. No one other than the PHP Group has
     the right to modify the terms applicable to covered code created
     under this License.

  6. Redistributions of any form whatsoever must retain the following
     acknowledgment:
     "This product includes PHP software, freely available from
     <http://www.php.net/software/>".

THIS SOFTWARE IS PROVIDED BY THE PHP DEVELOPMENT TEAM ``AS IS'' AND
ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE PHP
DEVELOPMENT TEAM OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
OF THE POSSIBILITY OF SUCH DAMAGE.

--------------------------------------------------------------------

This software consists of voluntary contributions made by many
individuals on behalf of the PHP Group.

The PHP Group can be contacted via Email at [email protected].

For more information on the PHP Group and the PHP project,
please see <http://www.php.net>.

PHP includes the Zend Engine, freely available at
<http://www.zend.com>.

legal\VERIFICATION.txt

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

The embedded software have been downloaded from the listed download
location on <http://windows.php.net/download>
and can be verified by doing the following:

1. Download the following:
  32-Bit software (threadsafe): <http://windows.php.net/downloads/releases/php-7.4.14-Win32-vc15-x86.zip>
  64-Bit software (threadsafe): <http://windows.php.net/downloads/releases/php-7.4.14-Win32-vc15-x64.zip>
  32-Bit software (non-threadsafe): <http://windows.php.net/downloads/releases/php-7.4.14-nts-Win32-vc15-x86.zip>
  64-Bit software (non-threadsafe): <http://windows.php.net/downloads/releases/php-7.4.14-nts-Win32-vc15-x64.zip>
2. Get the checksum using one of the following methods:
  - Using powershell function 'Get-FileHash'
  - Use chocolatey utility 'checksum.exe'
3. The checksums should match the following:

  checksum type: 
  checksum32 (threadsafe): 138ACA8B260C9242722D3BC780B61F5FD6C7E6D2F5F6D745219A6F813968D6A2
  checksum64 (threadsafe): EA87D15AA04E9F6EA189C437E276816C97E404F3AEBB850BE60FD637055AE81C
  checksum32 (non-threadsafe): ED3ACF8C9507487FFC028BB8EBAAB522961005482832D5FCAD703E908CD44BCC
  checksum64 (non-threadsafe): 669E8C437F9C7B056EC0BB7D075E7B845D62E1E08342C10686DE36008D4C0F23

The file 'LICENSE.txt' has been obtained from <http://www.php.net/license/3_01.txt>

tools\chocolateyInstall.ps1

$ErrorActionPreference = 'Stop'

$toolsPath = Split-Path $MyInvocation.MyCommand.Definition
. $toolsPath\helpers.ps1

$installLocation = GetInstallLocation "$toolsPath\.."

if ($installLocation) {
  Write-Host "Uninstalling previous version of php..."
  UninstallPackage -libDirectory "$toolsPath\.." -packageName $env:ChocolateyPackageName
  Uninstall-ChocolateyPath $installLocation
}

$pp = Get-PackageParameters

$filesInfo = @{
  filets32  = "$toolsPath\php-7.4.14-Win32-vc15-x86.zip"
  filets64  = "$toolsPath\php-7.4.14-Win32-vc15-x64.zip"
  filents32 = "$toolsPath\php-7.4.14-nts-Win32-vc15-x86.zip"
  filents64 = "$toolsPath\php-7.4.14-nts-Win32-vc15-x64.zip"
}

if ($pp.ThreadSafe) {
  $file32 = $filesInfo.filets32
  $file64 = $filesInfo.filets64
} else {
  $file32 = $filesInfo.filents32
  $file64 = $filesInfo.filents64
}

$packageArgs = @{
  packageName    = $env:ChocolateyPackageName
  file           = $file32
  file64         = $file64
}

$newInstallLocation = $packageArgs.Destination = GetNewInstallLocation $packageArgs.packageName $env:ChocolateyPackageVersion $pp

Get-ChocolateyUnzip @packageArgs

Get-ChildItem $toolsPath\*.zip | ForEach-Object { Remove-Item $_ -ea 0; if (Test-Path $_) { Set-Content "$_.ignore" } }

if (!$pp.DontAddToPath) { Install-ChocolateyPath $newInstallLocation 'Machine' }

$php_ini_path = $newInstallLocation + '/php.ini'

if (($installLocation -ne $newInstallLocation) -and (Test-Path "$installLocation\php.ini")) {
  Write-Host "Moving old configuration file."
  Move-Item "$installLocation\php.ini" "$php_ini_path"

  $di = Get-ChildItem $installLocation -ea 0 | Measure-Object
  if ($di.Count -eq 0) {
    Write-Host "Removing old install location."
    Remove-Item -Force -ea 0 $installLocation
  }
}

if (!(Test-Path $php_ini_path)) {
  Write-Host 'Creating default php.ini'
  Copy-Item $newInstallLocation/php.ini-production $php_ini_path

  Write-Host 'Configuring PHP extensions directory'
  (Get-Content $php_ini_path) -replace ';\s?extension_dir = "ext"', 'extension_dir = "ext"' | Set-Content $php_ini_path
}

if (!$pp.ThreadSafe) { Write-Host 'Please make sure you have CGI installed in IIS for local hosting' }

tools\chocolateyUninstall.ps1

$toolsPath = Split-Path $MyInvocation.MyCommand.Definition
. $toolsPath\helpers.ps1

$packageName = $env:ChocolateyPackageName

$installLocation = GetInstallLocation -libDirectory "$toolsPath\.."

if ($installLocation) {
  UninstallPackage -libDirectory "$toolsPath\.." -packageName $packageName

  $di = Get-ChildItem $installLocation -ea 0 | Measure-Object
  if ($di.Count -eq 0) {
    Remove-Item -Force -ea 0 $installLocation
  }

  Uninstall-ChocolateyPath $installLocation

} else {
  Write-Warning "$packageName install path was not found. It may already be uninstalled!"
}

tools\helpers.ps1

function GetInstallLocation {
  param(
    [string]$libDirectory
  )

  Write-Debug "Checking for uninstall text document in $libDirectory"

  if (Test-Path "$libDirectory\*.txt") {
    $txtContent = Get-Content -Encoding UTF8 "$libDirectory\*.txt" | Select-Object -first 1
    $index = $txtContent.LastIndexOf('\')
    if ($index -gt 0) {
      return $txtContent.Substring(0, $index)
    }
  }

  # If we got here, the text file doesn't exist or is empty
  # we don't return anything as it may be already uninstalled
}

function GetNewInstallLocation {
  param(
    [string]$PackageName,
    [string]$Version,
    $pp
  )

  if ($pp -and $pp.InstallDir) {
    return $pp.InstallDir
  }

  $toolsLocation = Get-ToolsLocation
  return "$toolsLocation\{0}{1}" -f $PackageName, ($Version -replace '\.').Substring(0,2)
}

function UninstallPackage {
  param(
    [string]$libDirectory,
    [string]$packageName
  )
  if (Test-Path "$libDirectory\*.txt") {
    $txtFile = Resolve-Path "$libDirectory\*.txt" | Select-Object -first 1
    $fileName = ($txtFile -split '\\' | Select-Object -last 1).TrimEnd('.txt')
    Uninstall-ChocolateyZipPackage -PackageName $packageName -ZipFileName $fileName
    if (Test-Path $txtFile) {
      Remove-Item -Force -ea 0 $txtFile
    }
  }
}

if (!(Test-Path function:\Uninstall-ChocolateyPath)) {
  function Uninstall-ChocolateyPath {
    param(
      [string]$pathToRemove,
      [System.EnvironmentVariableTarget] $pathType = [System.EnvironmentVariableTarget]::User
    )

    Write-Debug "Running 'Uninstall-ChocolateyPath' with pathToRemove: `'$pathToRemove`'"

    # get the PATH variable
    Update-SessionEnvironment
    $envPath = $env:PATH
    if ($envPath.ToLower().Contains($pathToRemove.ToLower())) {
      Write-Host "The PATH environment variable already contains the directory '$pathToRemove'. Removing..."
      $actualPath = Get-EnvironmentVariable -Name 'Path' -Scope $pathType -PreserveVariables

      $newPath = $actualPath -replace [regex]::Escape($pathToRemove + ';'),'' -replace ';;',';'

      if (($pathType -eq [System.EnvironmentVariableTarget]::Machine) -and !(Test-ProcessAdminRights)) {
        Write-Warning "Removing path from machine environment variable is not supported when not running as an elevated user!"
      } else {
        Set-EnvironmentVariable -Name 'Path' -Value $newPath -Scope $pathType
      }

      $env:PATH = $newPath
    }
  }
}

tools\php-7.4.14-nts-Win32-vc15-x64.zip

md5: 9C0AD81063ACFC5A44AC8748AFC9D9B8 | sha1: 4F8E0BC4F3B7331B2209F305AEED78111B8F0FD3 | sha256: 669E8C437F9C7B056EC0BB7D075E7B845D62E1E08342C10686DE36008D4C0F23 | sha512: 378D0C2570BBDCE04915EFE157BD231F2AED1876A457BED10257D4946190C642851AAAFF655DAF9CCBB20635B9B0844728201EC01B3A64A4808226FE4DD1C4C8

tools\php-7.4.14-nts-Win32-vc15-x86.zip

md5: C43F75B86BF69A3C230CBD9170A20089 | sha1: 54E5B78BDC1A840DA084B88230045BD1B36C7CD5 | sha256: ED3ACF8C9507487FFC028BB8EBAAB522961005482832D5FCAD703E908CD44BCC | sha512: 166D90F1A8FF4F4651D0D4482D1BA85E2569A3C276C9608AC0E4AEB5301F10E91FA4DB19CBA91D268D4C223E970FE63B094F6BD14FF369736081A51DC78FA170

tools\php-7.4.14-Win32-vc15-x64.zip

md5: 51B1096089525749045D6E62C895119D | sha1: 908CF6D51E5DD9B78A0034C89B38133A9F8982F2 | sha256: EA87D15AA04E9F6EA189C437E276816C97E404F3AEBB850BE60FD637055AE81C | sha512: C997E2C6564956F0BBD5962C0FD2BF20C95187784350B701555A598AF8C7FC28A2676A269990974702C546CE0517A08F8A2BD42A0F41691AFF7B4A62188E9960

tools\php-7.4.14-Win32-vc15-x86.zip

md5: 83BD8EE4161DC55F736712297FF63E03 | sha1: 44931AB36E02EA304A5BB40B189F2F518AF2E5B5 | sha256: 138ACA8B260C9242722D3BC780B61F5FD6C7E6D2F5F6D745219A6F813968D6A2 | sha512: C0FE85F7CBC43AD486F706792389619B6B0E216C267E25C59D1CA4B2DE4D8FE6B0745A8C7F03149FF555840CF4DCE3BBB6787EF2C7230FAA7459BB728D2A3336

Virus Scan Results

glib-2.dll (f1ebf915dd41) - ## / 67
gmodule-2.dll (d17b1baf2bbf) - ## / 66
libsasl.dll (a1cb99510404) - ## / 71
glib-2.dll (0cc67a929b23) - ## / 64
gmodule-2.dll (051ea2d2e5c7) - ## / 67
libsasl.dll (7d30efb1fe86) - ## / 66
libsodium.dll (53b3dc639571) - ## / 71
libsodium.dll (a473d8aa25e6) - ## / 67
libenchant.dll (dc9e1fe565cb) - ## / 69
libpq.dll (1bbc7e5e1e67) - ## / 67
libenchant.dll (8c4bc10b18dd) - ## / 67
libpq.dll (5cb145e7a641) - ## / 69
libsqlite3.dll (884111558804) - ## / 68
libssh2.dll (843b3820e9aa) - ## / 67
libsqlite3.dll (42e1f9d15b74) - ## / 66
libssh2.dll (ab9eb2f02364) - ## / 66
nghttp2.dll (5acf6537fb65) - ## / 67
nghttp2.dll (05a36b13fa6f) - ## / 69
icudt66.dll (2c796d089d4a) - ## / 69
icuin66.dll (cb6576b9ee0d) - ## / 67
icuio66.dll (248ff9d46ea2) - ## / 67
icuuc66.dll (f60adb68fcf7) - ## / 68
icudt66.dll (3b9d6ded85e1) - ## / 65
icuin66.dll (0c0298f4b6e8) - ## / 62
icuio66.dll (e277c472cf02) - ## / 68
icuuc66.dll (de3f82fd89a1) - ## / 70
php.7.4.14.nupkg (e75bcab9bd94) - ## / 62
php-7.4.14-nts-Win32-vc15-x64.zip (669e8c437f9c) - ## / 57
php-7.4.14-nts-Win32-vc15-x86.zip (ed3acf8c9507) - ## / 60
php-7.4.14-Win32-vc15-x64.zip (ea87d15aa04e) - ## / 58
php-7.4.14-Win32-vc15-x86.zip (138aca8b260c) - ## / 62
deplister.exe (af380773c7d7) - ## / 70
libcrypto-1_1-x64.dll (9561ef1e008f) - ## / 69
libssl-1_1-x64.dll (019248c91093) - ## / 64
php-cgi.exe (5b4c1c06b2c6) - ## / 69
php-win.exe (1535108cdf78) - ## / 69
php.exe (bb21b295a7ec) - ## / 69
php7.dll (b7193a28e69a) - ## / 69
php7phpdbg.dll (b9c4b36cfab7) - ## / 70
phpdbg.exe (ce6ab1c21af3) - ## / 69
deplister.exe (68f67c93a3a3) - ## / 69
libcrypto-1_1.dll (3b4ad5aa0655) - ## / 68
libssl-1_1.dll (163f85dc7aef) - ## / 68
php-cgi.exe (17549c5c570f) - ## / 68
php-win.exe (ba916e114001) - ## / 70
php.exe (1442fd55ff7b) - ## / 58
php7.dll (d034eef35afb) - ## / 70
php7phpdbg.dll (b8e8053a4610) - ## / 69
phpdbg.exe (a77108ec1e58) - ## / 69
php_bz2.dll (b54c8856f7f2) - ## / 70
php_com_dotnet.dll (64087065228a) - ## / 69
php_curl.dll (dd3a7983a235) - ## / 69
php_dba.dll (d41e0c1953e7) - ## / 69
php_enchant.dll (fbaea1215e23) - ## / 67
php_exif.dll (f19fa645c44b) - ## / 67
php_ffi.dll (c42eb527d3b3) - ## / 70
php_fileinfo.dll (5d47cf56e124) - ## / 67
php_ftp.dll (dc90cae56aa4) - ## / 68
php_gd2.dll (cca224113cd0) - ## / 70
php_gettext.dll (ad5a1f2348fe) - ## / 68
php_gmp.dll (9a6892d571e2) - ## / 69
php_imap.dll (ca539872524b) - ## / 70
php_intl.dll (136acd4035f7) - ## / 67
php_ldap.dll (e7455ae4ee21) - ## / 70
php_mbstring.dll (df25372b65f0) - ## / 69
php_mysqli.dll (e2eda4038764) - ## / 70
php_oci8_12c.dll (ac5b5839b639) - ## / 69
php_odbc.dll (b06999a63650) - ## / 69
php_opcache.dll (c3567b31e487) - ## / 68
php_openssl.dll (d853fbae661a) - ## / 70
php_pdo_firebird.dll (6f31ce0143d4) - ## / 70
php_pdo_mysql.dll (8aa518389458) - ## / 70
php_pdo_oci.dll (3b9d57c1309d) - ## / 70
php_pdo_odbc.dll (5fe70a430333) - ## / 68
php_pdo_pgsql.dll (e9c02d0dc5ef) - ## / 68
php_pdo_sqlite.dll (6b138ea37582) - ## / 69
php_pgsql.dll (b55caeefd90e) - ## / 69
php_phpdbg_webhelper.dll (8447d976296e) - ## / 68
php_shmop.dll (1ef8fd79c587) - ## / 69
php_snmp.dll (efe6c587ee9f) - ## / 69
php_soap.dll (a4bc59ee45fd) - ## / 68
php_sockets.dll (d662f5277c95) - ## / 69
php_sodium.dll (cf5df5e0cff7) - ## / 69
php_sqlite3.dll (12b624304fb5) - ## / 70
php_sysvshm.dll (871ca34fd0f6) - ## / 70
php_tidy.dll (d2cd7ef20e23) - ## / 69
php_xmlrpc.dll (3f13683370a4) - ## / 70
php_xsl.dll (0d05504c1ca7) - ## / 69
php_zend_test.dll (2326b61a1db9) - ## / 70

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
PHP (Hypertext Preprocessor) 8.3.7	746	Wednesday, May 8, 2024	Approved
PHP (Hypertext Preprocessor) 8.3.6	7387	Wednesday, April 10, 2024	Approved
PHP (Hypertext Preprocessor) 8.3.4	6850	Wednesday, March 13, 2024	Approved
PHP (Hypertext Preprocessor) 8.3.3	6842	Wednesday, February 14, 2024	Approved
PHP (Hypertext Preprocessor) 8.3.2	6382	Wednesday, January 17, 2024	Approved
PHP (Hypertext Preprocessor) 8.3.1	5618	Wednesday, December 20, 2023	Approved
PHP (Hypertext Preprocessor) 8.3.0	6186	Wednesday, November 22, 2023	Approved
PHP (Hypertext Preprocessor) 8.2.19	6	Wednesday, May 8, 2024	Approved
PHP (Hypertext Preprocessor) 8.2.18	224	Wednesday, April 10, 2024	Approved
PHP (Hypertext Preprocessor) 8.2.17	146	Wednesday, March 13, 2024	Approved
PHP (Hypertext Preprocessor) 8.2.16	1208	Wednesday, February 14, 2024	Approved
PHP (Hypertext Preprocessor) 8.2.15	1505	Wednesday, January 17, 2024	Approved
PHP (Hypertext Preprocessor) 8.2.14	1372	Wednesday, December 20, 2023	Approved
PHP (Hypertext Preprocessor) 8.2.13	1943	Wednesday, November 22, 2023	Approved
PHP (Hypertext Preprocessor) 8.2.12	7271	Wednesday, October 25, 2023	Approved
PHP (Hypertext Preprocessor) 8.2.11	7506	Wednesday, September 27, 2023	Approved
PHP (Hypertext Preprocessor) 8.2.10	7371	Wednesday, August 30, 2023	Approved
PHP (Hypertext Preprocessor) 8.2.9	7450	Wednesday, August 2, 2023	Approved
PHP (Hypertext Preprocessor) 8.2.8	7408	Wednesday, July 5, 2023	Approved
PHP (Hypertext Preprocessor) 8.2.7	6843	Wednesday, June 7, 2023	Approved
PHP (Hypertext Preprocessor) 8.2.6	7014	Tuesday, May 9, 2023	Approved
PHP (Hypertext Preprocessor) 8.2.5	6567	Wednesday, April 12, 2023	Approved
PHP (Hypertext Preprocessor) 8.2.4	6738	Wednesday, March 15, 2023	Approved
PHP (Hypertext Preprocessor) 8.2.3	6693	Tuesday, February 14, 2023	Approved
PHP (Hypertext Preprocessor) 8.2.2	3924	Wednesday, February 1, 2023	Approved
PHP (Hypertext Preprocessor) 8.2.1	6484	Wednesday, January 4, 2023	Approved
PHP (Hypertext Preprocessor) 8.2.0	6537	Tuesday, December 6, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.28	628	Wednesday, April 10, 2024	Approved
PHP (Hypertext Preprocessor) 8.1.27	2245	Wednesday, December 20, 2023	Approved
PHP (Hypertext Preprocessor) 8.1.26	433	Wednesday, November 22, 2023	Approved
PHP (Hypertext Preprocessor) 8.1.25	392	Wednesday, October 25, 2023	Approved
PHP (Hypertext Preprocessor) 8.1.24	599	Wednesday, September 27, 2023	Approved
PHP (Hypertext Preprocessor) 8.1.23	1436	Saturday, September 2, 2023	Approved
PHP (Hypertext Preprocessor) 8.1.22	838	Wednesday, August 2, 2023	Approved
PHP (Hypertext Preprocessor) 8.1.21	517	Wednesday, July 5, 2023	Approved
PHP (Hypertext Preprocessor) 8.1.20	677	Wednesday, June 7, 2023	Approved
PHP (Hypertext Preprocessor) 8.1.19	354	Wednesday, May 10, 2023	Approved
PHP (Hypertext Preprocessor) 8.1.18	329	Wednesday, April 12, 2023	Approved
PHP (Hypertext Preprocessor) 8.1.17	333	Wednesday, March 15, 2023	Approved
PHP (Hypertext Preprocessor) 8.1.16	2721	Wednesday, February 15, 2023	Approved
PHP (Hypertext Preprocessor) 8.1.15	117	Wednesday, February 1, 2023	Approved
PHP (Hypertext Preprocessor) 8.1.14	464	Wednesday, January 4, 2023	Approved
PHP (Hypertext Preprocessor) 8.1.13	5388	Tuesday, November 22, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.12	10922	Wednesday, October 26, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.11	8668	Wednesday, September 28, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.10	23140	Wednesday, August 31, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.9	8413	Wednesday, August 3, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.8	7242	Wednesday, July 6, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.7	9720	Wednesday, June 8, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.6	9402	Wednesday, May 11, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.5	9890	Wednesday, April 13, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.4	10398	Wednesday, March 16, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.3	9774	Wednesday, February 16, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.2	10602	Wednesday, January 19, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.1	12234	Wednesday, December 15, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.30	1433	Friday, September 1, 2023	Approved
PHP (Hypertext Preprocessor) 8.0.29	935	Thursday, June 8, 2023	Approved
PHP (Hypertext Preprocessor) 8.0.28	3414	Wednesday, February 15, 2023	Approved
PHP (Hypertext Preprocessor) 8.0.27	1198	Wednesday, January 4, 2023	Approved
PHP (Hypertext Preprocessor) 8.0.26	993	Wednesday, November 23, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.25	572	Tuesday, October 25, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.24	627	Thursday, September 29, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.23	767	Tuesday, August 30, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.22	681	Tuesday, August 2, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.21	346	Tuesday, July 5, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.20	1102	Wednesday, June 8, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.19	1083	Tuesday, May 10, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.18	781	Wednesday, April 13, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.17	520	Tuesday, March 15, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.16	192	Wednesday, February 16, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.15	219	Tuesday, January 18, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.14	346	Thursday, December 16, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.10	25733	Wednesday, August 25, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.9	7566	Thursday, July 29, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.8	7889	Wednesday, June 30, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.7	7305	Wednesday, June 2, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.6	6767	Wednesday, May 5, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.5	129	Wednesday, April 28, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.3	14342	Wednesday, March 3, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.2	1366	Thursday, February 4, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.1	16925	Wednesday, January 6, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.0.20201221	4734	Monday, December 21, 2020	Approved
PHP (Hypertext Preprocessor) 8.0.0	8864	Friday, November 27, 2020	Approved
PHP (Hypertext Preprocessor) 7.4.33	2803	Thursday, November 3, 2022	Approved
PHP (Hypertext Preprocessor) 7.4.32	521	Thursday, September 29, 2022	Approved
PHP (Hypertext Preprocessor) 7.4.30	2630	Wednesday, June 8, 2022	Approved
PHP (Hypertext Preprocessor) 7.4.29	797	Thursday, April 14, 2022	Approved
PHP (Hypertext Preprocessor) 7.4.28	14989	Thursday, February 24, 2022	Approved
PHP (Hypertext Preprocessor) 7.4.27	4926	Wednesday, December 15, 2021	Approved
PHP (Hypertext Preprocessor) 7.4.23	1082	Wednesday, August 25, 2021	Approved
PHP (Hypertext Preprocessor) 7.4.22	1257	Wednesday, July 28, 2021	Approved
PHP (Hypertext Preprocessor) 7.4.21	1105	Wednesday, June 30, 2021	Approved
PHP (Hypertext Preprocessor) 7.4.20	1085	Wednesday, June 2, 2021	Approved
PHP (Hypertext Preprocessor) 7.4.19	2348	Tuesday, May 4, 2021	Approved
PHP (Hypertext Preprocessor) 7.4.18	506	Wednesday, April 28, 2021	Approved
PHP (Hypertext Preprocessor) 7.4.16	2912	Tuesday, March 2, 2021	Approved
PHP (Hypertext Preprocessor) 7.4.14	3056	Tuesday, January 5, 2021	Approved
PHP (Hypertext Preprocessor) 7.4.13	8166	Tuesday, November 24, 2020	Approved
PHP (Hypertext Preprocessor) 7.4.11	18006	Tuesday, September 29, 2020	Approved
PHP (Hypertext Preprocessor) 7.4.9	16143	Wednesday, August 5, 2020	Approved
PHP (Hypertext Preprocessor) 7.4.7	15658	Wednesday, June 10, 2020	Approved
PHP (Hypertext Preprocessor) 7.4.6	5966	Thursday, May 28, 2020	Approved
PHP (Hypertext Preprocessor) 7.4.5	15315	Wednesday, April 15, 2020	Approved
PHP (Hypertext Preprocessor) 7.4.3	17439	Friday, February 21, 2020	Approved
PHP (Hypertext Preprocessor) 7.4.2	8663	Wednesday, January 22, 2020	Approved
PHP (Hypertext Preprocessor) 7.4.1	9601	Tuesday, December 24, 2019	Approved
PHP (Hypertext Preprocessor) 7.4.0	12833	Wednesday, November 27, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.30	6789	Wednesday, August 25, 2021	Approved
PHP (Hypertext Preprocessor) 7.3.29	1730	Wednesday, June 30, 2021	Approved
PHP (Hypertext Preprocessor) 7.3.28	3318	Wednesday, April 28, 2021	Approved
PHP (Hypertext Preprocessor) 7.3.26	3311	Tuesday, January 5, 2021	Approved
PHP (Hypertext Preprocessor) 7.3.25	3511	Tuesday, November 24, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.24	988	Tuesday, October 27, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.23	1988	Tuesday, September 29, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.22	1303	Tuesday, September 1, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.21	1368	Wednesday, August 5, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.20	1018	Tuesday, July 7, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.19	1266	Wednesday, June 10, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.18	1145	Tuesday, May 12, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.17	1132	Wednesday, April 15, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.15	3361	Tuesday, February 18, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.14	1911	Tuesday, January 21, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.13	2705	Wednesday, December 18, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.12	12635	Wednesday, November 20, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.11	9850	Tuesday, October 22, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.10	12088	Wednesday, September 25, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.9	10868	Wednesday, August 28, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.8	7977	Tuesday, August 6, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.7	15076	Wednesday, July 3, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.6	13215	Wednesday, May 29, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.5	9768	Wednesday, May 1, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.4	8451	Wednesday, April 3, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.3	7206	Thursday, March 14, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.1	60407	Thursday, January 10, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.0	33506	Thursday, December 6, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.34	24110	Thursday, October 1, 2020	Approved
PHP (Hypertext Preprocessor) 7.2.33	2486	Wednesday, August 5, 2020	Approved
PHP (Hypertext Preprocessor) 7.2.32	1049	Wednesday, July 8, 2020	Approved
PHP (Hypertext Preprocessor) 7.2.31	2296	Tuesday, May 12, 2020	Approved
PHP (Hypertext Preprocessor) 7.2.30	1336	Wednesday, April 15, 2020	Approved
PHP (Hypertext Preprocessor) 7.2.29	1716	Tuesday, March 17, 2020	Approved
PHP (Hypertext Preprocessor) 7.2.28	1696	Tuesday, February 18, 2020	Approved
PHP (Hypertext Preprocessor) 7.2.27	1662	Thursday, January 23, 2020	Approved
PHP (Hypertext Preprocessor) 7.2.26	4535	Thursday, December 19, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.25	1943	Thursday, November 21, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.24	1589	Tuesday, October 22, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.23	4125	Friday, September 27, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.22	1914	Wednesday, August 28, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.20	4459	Friday, July 5, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.19	4859	Wednesday, May 29, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.18	127214	Wednesday, May 1, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.17	3857	Wednesday, April 3, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.15	7044	Friday, February 8, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.14	2533	Thursday, January 10, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.13	6021	Thursday, December 6, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.12	29128	Thursday, November 8, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.10	46144	Thursday, September 13, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.9	23492	Thursday, August 16, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.8	21191	Wednesday, July 18, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.7	21887	Wednesday, June 20, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.5	61135	Thursday, April 26, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.4	5083	Thursday, March 29, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.3	11793	Thursday, March 1, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.2	6869	Thursday, February 1, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.1	7101	Saturday, January 6, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.0	27068	Friday, December 1, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.33	14820	Wednesday, October 23, 2019	Approved
PHP (Hypertext Preprocessor) 7.1.32	2716	Wednesday, August 28, 2019	Approved
PHP (Hypertext Preprocessor) 7.1.31	1031	Wednesday, July 31, 2019	Approved
PHP (Hypertext Preprocessor) 7.1.30	2986	Tuesday, May 28, 2019	Approved
PHP (Hypertext Preprocessor) 7.1.29	3768	Wednesday, May 1, 2019	Approved
PHP (Hypertext Preprocessor) 7.1.28	2581	Wednesday, April 3, 2019	Approved
PHP (Hypertext Preprocessor) 7.1.27	3237	Thursday, March 7, 2019	Approved
PHP (Hypertext Preprocessor) 7.1.26	3891	Thursday, January 10, 2019	Approved
PHP (Hypertext Preprocessor) 7.1.25	3066	Thursday, December 6, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.24	2654	Thursday, November 8, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.22	2304	Thursday, September 13, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.21	3441	Thursday, August 16, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.20	4045	Thursday, July 19, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.19	4627	Thursday, June 21, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.18	3694	Friday, May 25, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.17	2987	Thursday, April 26, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.16	3638	Thursday, March 29, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.15	5168	Thursday, March 1, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.14	5643	Thursday, February 1, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.13	2440	Saturday, January 6, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.12	9820	Thursday, November 23, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.11	9328	Wednesday, October 25, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.10	9052	Wednesday, September 27, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.8	19764	Wednesday, August 2, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.7	14111	Thursday, July 6, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.6	18993	Thursday, June 8, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.5	17140	Wednesday, May 10, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.4	17607	Wednesday, April 12, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.3	19988	Thursday, March 16, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.2	31248	Wednesday, February 15, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.1.20170212	2164	Sunday, February 12, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.1	5988	Thursday, January 19, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.0	8503	Friday, December 2, 2016	Approved
PHP (Hypertext Preprocessor) 7.0.33	17345	Friday, December 7, 2018	Approved
PHP (Hypertext Preprocessor) 7.0.32	5767	Thursday, September 13, 2018	Approved
PHP (Hypertext Preprocessor) 7.0.31	6725	Friday, July 20, 2018	Approved
PHP (Hypertext Preprocessor) 7.0.30	9634	Thursday, April 26, 2018	Approved
PHP (Hypertext Preprocessor) 7.0.28	2497	Thursday, March 1, 2018	Approved
PHP (Hypertext Preprocessor) 7.0.27	4679	Saturday, January 6, 2018	Approved
PHP (Hypertext Preprocessor) 7.0.26	3263	Thursday, November 23, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.25	1971	Wednesday, October 25, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.24	2011	Tuesday, September 26, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.23	2365	Tuesday, August 29, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.22	3286	Wednesday, August 2, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.21	3338	Thursday, July 6, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.20	4342	Wednesday, June 7, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.19	5561	Tuesday, May 9, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.18	3509	Wednesday, April 12, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.17	4455	Thursday, March 16, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.16	4011	Tuesday, February 14, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.15	437	Sunday, February 12, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.13	1801	Monday, November 28, 2016	Approved
PHP (Hypertext Preprocessor) 7.0.9	134831	Wednesday, July 20, 2016	Approved
PHP (Hypertext Preprocessor) 7.0.8	506	Wednesday, June 22, 2016	Approved
PHP (Hypertext Preprocessor) 7.0.7	1243	Wednesday, May 25, 2016	Approved
PHP (Hypertext Preprocessor) 7.0.6	765	Sunday, May 8, 2016	Approved
PHP (Hypertext Preprocessor) 7.0.5	3593	Wednesday, March 30, 2016	Approved
PHP (Hypertext Preprocessor) 7.0.4	3091	Friday, March 4, 2016	Approved
PHP (Hypertext Preprocessor) 7.0.3	3878	Wednesday, February 3, 2016	Approved
PHP (Hypertext Preprocessor) 7.0.2	2579	Wednesday, January 6, 2016	Approved
PHP (Hypertext Preprocessor) 7.0.1	2213	Wednesday, December 16, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.40	13855	Thursday, January 10, 2019	Approved
PHP (Hypertext Preprocessor) 5.6.39	1654	Friday, December 7, 2018	Approved
PHP (Hypertext Preprocessor) 5.6.38	3064	Friday, September 14, 2018	Approved
PHP (Hypertext Preprocessor) 5.6.37	2325	Friday, July 20, 2018	Approved
PHP (Hypertext Preprocessor) 5.6.36	3550	Thursday, April 26, 2018	Approved
PHP (Hypertext Preprocessor) 5.6.35	1815	Friday, March 30, 2018	Approved
PHP (Hypertext Preprocessor) 5.6.34	1439	Thursday, March 1, 2018	Approved
PHP (Hypertext Preprocessor) 5.6.33	2913	Saturday, January 6, 2018	Approved
PHP (Hypertext Preprocessor) 5.6.32	2576	Thursday, October 26, 2017	Approved
PHP (Hypertext Preprocessor) 5.6.31	6202	Thursday, July 6, 2017	Approved
PHP (Hypertext Preprocessor) 5.6.30	18506	Sunday, February 12, 2017	Approved
PHP (Hypertext Preprocessor) 5.6.17	4739	Wednesday, February 3, 2016	Approved
PHP (Hypertext Preprocessor) 5.6.16	937	Thursday, November 26, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.15	498	Thursday, October 29, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.14	430	Thursday, October 1, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.13	495	Friday, September 4, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.12	519	Thursday, August 6, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.11	589	Sunday, July 12, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.10	484	Thursday, June 11, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.9	4320	Friday, May 15, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.8	595	Thursday, April 16, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.7	1376	Monday, March 23, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.6	527	Thursday, February 19, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.5	517	Thursday, January 22, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.4	677	Friday, December 12, 2014	Approved
PHP (Hypertext Preprocessor) 5.6.3	20196	Thursday, November 13, 2014	Approved
PHP (Hypertext Preprocessor) 5.6.2	1113	Thursday, October 16, 2014	Approved
PHP (Hypertext Preprocessor) 5.6.1	827	Friday, September 26, 2014	Approved
PHP (Hypertext Preprocessor) 5.6.0	1424	Thursday, August 28, 2014	Approved
PHP (Hypertext Preprocessor) 5.5.38	9050	Thursday, February 9, 2017	Approved
PHP (Hypertext Preprocessor) 5.5.16	796	Thursday, August 21, 2014	Approved
PHP (Hypertext Preprocessor) 5.5.15	819	Tuesday, July 29, 2014	Approved
PHP (Hypertext Preprocessor) 5.5.14	776	Tuesday, July 1, 2014	Approved
PHP (Hypertext Preprocessor) 5.5.13	737	Thursday, June 5, 2014	Approved
PHP (Hypertext Preprocessor) 5.5.12	650	Wednesday, May 21, 2014	Approved
PHP (Hypertext Preprocessor) 5.5.11	1087	Tuesday, April 22, 2014	Approved
PHP (Hypertext Preprocessor) 5.4.45	2229	Thursday, February 9, 2017	Approved
PHP (Hypertext Preprocessor) 5.3.29	731	Thursday, February 9, 2017	Approved
PHP (Hypertext Preprocessor) 5.3.28	1173	Thursday, December 12, 2013	Approved
PHP (Hypertext Preprocessor) 5.3.27	855	Friday, July 12, 2013	Approved
PHP (Hypertext Preprocessor) 5.3.26	667	Thursday, June 6, 2013	Approved
PHP (Hypertext Preprocessor) 5.3.25	664	Thursday, May 9, 2013	Approved
PHP (Hypertext Preprocessor) 5.3.24	624	Thursday, April 11, 2013	Approved
PHP (Hypertext Preprocessor) 5.3.23	614	Friday, March 15, 2013	Approved
PHP (Hypertext Preprocessor) 5.3.22	620	Thursday, February 21, 2013	Approved
PHP (Hypertext Preprocessor) 5.3.21	652	Thursday, January 17, 2013	Approved
PHP (Hypertext Preprocessor) 5.3.20	623	Thursday, December 20, 2012	Approved
PHP (Hypertext Preprocessor) 5.3.19	619	Tuesday, November 27, 2012	Approved
PHP (Hypertext Preprocessor) 5.3.18	654	Thursday, October 18, 2012	Approved
PHP (Hypertext Preprocessor) 5.3.17	644	Thursday, September 13, 2012	Approved
PHP (Hypertext Preprocessor) 5.3.16	573	Thursday, August 16, 2012	Approved
PHP (Hypertext Preprocessor) 5.3.15	633	Friday, July 20, 2012	Approved
PHP (Hypertext Preprocessor) 5.3.14	573	Wednesday, June 27, 2012	Approved
PHP (Hypertext Preprocessor) 5.3.10	791	Monday, February 20, 2012	Approved
PHP (Hypertext Preprocessor) 5.3.9	688	Thursday, January 12, 2012	Approved
PHP (Hypertext Preprocessor) 5.3.6.2	713	Tuesday, August 23, 2011	Approved
PHP (Hypertext Preprocessor) 5.3.6.1	604	Tuesday, August 23, 2011	Approved
PHP (Hypertext Preprocessor) 5.3.6	947	Tuesday, August 23, 2011	Approved

Release Notes

https://www.php.net/ChangeLog-7.php#7.4.14

Dependencies

- vcredist140 (≥ 14.16.27012.6)
- chocolatey-core.extension (≥ 1.3.3)
- chocolatey (≥ 0.10.0)

Discussion for the PHP (Hypertext Preprocessor) Package

Ground Rules:

This discussion is only about PHP (Hypertext Preprocessor) and the PHP (Hypertext Preprocessor) 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 PHP (Hypertext Preprocessor), or tell us what needs improvement.
Share your experiences with the package, or extra configuration or gotchas that you've found.
If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.

Resources

Events

Courses

1,922,925

3,056

05 Jan 2021

PHP (Hypertext Preprocessor)

PHP (Hypertext Preprocessor) 7.4.14

Some Checks Have Failed or Are Not Yet Complete

Deployment Method: Individual Install, Upgrade, & Uninstall

Deployment Method:

1. Enter Your Internal Repository Url

2. Setup Your Environment

1. Ensure you are set for organizational deployment

2. Get the package into your environment

3. Copy Your Script

4. If applicable - Chocolatey configuration/installation

Package Parameters

Ground Rules: