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,913,401

Downloads of v 7.3.17:

1,122

Last Update:

15 Apr 2020

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.3.17 | Updated: 15 Apr 2020

Downloads:

1,913,401

Downloads of v 7.3.17:

1,122

Maintainer(s):

Software Author(s):

PHP Authors

Tags:

php development programming foss cross-platform admin

PHP (Hypertext Preprocessor) 7.3.17

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.3.17 --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.3.17'" [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.3.17'" 
$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.3.17'
    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.3.17'
end

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


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

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


package { 'php':
  ensure   => '7.3.17',
  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 15 Apr 2020.

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.3.17-Win32-VC15-x86.zip>
  64-Bit software (threadsafe): <http://windows.php.net/downloads/releases/php-7.3.17-Win32-VC15-x64.zip>
  32-Bit software (non-threadsafe): <http://windows.php.net/downloads/releases/php-7.3.17-nts-Win32-VC15-x86.zip>
  64-Bit software (non-threadsafe): <http://windows.php.net/downloads/releases/php-7.3.17-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): 75E529722CC49E38926948E73081A9DE9828537323FC4F303AD4FFCF16BCD5F5
  checksum64 (threadsafe): D4F8877B2EC13FA148C062E86B96F86B1D97B8CCAF832743343489E1F40FC081
  checksum32 (non-threadsafe): 25600FE13907E27215FE00E928EC59D211F63A919A93C569EB134B4D701D0B71
  checksum64 (non-threadsafe): 9867CB9FF5E7762D19B76183AD81625E6012671F73CA83BDD2D8D1E9CB1EB4D1

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.3.17-Win32-VC15-x86.zip"
  filets64  = "$toolsPath\php-7.3.17-Win32-VC15-x64.zip"
  filents32 = "$toolsPath\php-7.3.17-nts-Win32-VC15-x86.zip"
  filents64 = "$toolsPath\php-7.3.17-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.3.17-nts-Win32-VC15-x64.zip

md5: 0757E58F3512720EC240E08AAC2E5C0A | sha1: BC6DF4F652990B0D8C7F44E229B9B5F80A189B2E | sha256: 9867CB9FF5E7762D19B76183AD81625E6012671F73CA83BDD2D8D1E9CB1EB4D1 | sha512: 4F8596EFABAF253F4C0DBEDA3D0310F4844E301C7F5068F138FB525C17C45CCE4CDE895DC2045CCA8A98C1A551F64474206F08F96125301F3EEC4B06542C4AF8

tools\php-7.3.17-nts-Win32-VC15-x86.zip

md5: 8AD3D08868432A7369171DE73A3F0974 | sha1: FDD2D3CECAC6BD8B501ED891ADC4A75C97406CE2 | sha256: 25600FE13907E27215FE00E928EC59D211F63A919A93C569EB134B4D701D0B71 | sha512: D56AE384FB7FE0C92CAAB073F2DF0373B285E9D30D9E0F6AF8D7ADFD106D3E7CC2A800C9D408CB71B6FEB72C87E72D27F2E7FAF7D8B144157E633281FEF7CF2C

tools\php-7.3.17-Win32-VC15-x64.zip

md5: 4407BB33F85129DCFB6D0A028EDDA8D8 | sha1: 9974613E1672F1593D7C0E86079AB3129CDAC4BC | sha256: D4F8877B2EC13FA148C062E86B96F86B1D97B8CCAF832743343489E1F40FC081 | sha512: C149A80879CA885F92F8C377C75EC19C838039C597C84F6818518E1C90976E69362ABA7C362F2F2DAF3DB41BF52E552CD3772EA6F1307CA020E67056BA4DFDED

tools\php-7.3.17-Win32-VC15-x86.zip

md5: 388B60E36522BF84B4DCEAAD86EB4E12 | sha1: 8246C797CA2DD1B286831B5C0B11BE1104E18CA8 | sha256: 75E529722CC49E38926948E73081A9DE9828537323FC4F303AD4FFCF16BCD5F5 | sha512: F0B62E97CA4726217802C614B37B311CCE867525EFDECA81F5E7D3E521C648A667A0E81DC0DE6FE25111F0A0E382A18447AF6CDC90E74F731DA92CCD9A907D5B

Virus Scan Results

glib-2.dll (f1ebf915dd41) - ## / 67
gmodule-2.dll (d17b1baf2bbf) - ## / 66
libenchant.dll (d47e003888ba) - ## / 69
libsasl.dll (a1cb99510404) - ## / 71
glib-2.dll (0cc67a929b23) - ## / 64
gmodule-2.dll (051ea2d2e5c7) - ## / 67
libenchant.dll (7dc27deacc23) - ## / 67
libsasl.dll (7d30efb1fe86) - ## / 66
saslANONYMOUS.dll (808d150f2d6a) - ## / 70
saslCRAMMD5.dll (8e0be4071ba2) - ## / 70
saslDIGESTMD5.dll (882206fd6730) - ## / 70
saslLOGIN.dll (444da2731486) - ## / 70
saslNTLM.dll (f9ca3a471013) - ## / 70
saslOTP.dll (832d982de8f6) - ## / 70
saslPLAIN.dll (70f78d865817) - ## / 70
saslSASLDB.dll (d50ac595c6db) - ## / 68
saslSCRAM.dll (a3cbcd0bdd4e) - ## / 70
saslSQLITE.dll (382ab3e99061) - ## / 69
saslANONYMOUS.dll (e97ce8278076) - ## / 66
saslCRAMMD5.dll (95abfa448103) - ## / 66
saslDIGESTMD5.dll (79ac5a4ccb55) - ## / 69
saslLOGIN.dll (81c408aa8896) - ## / 68
saslNTLM.dll (f470372a0a34) - ## / 68
saslOTP.dll (fc9d19a69229) - ## / 66
saslPLAIN.dll (6baf8c0015f2) - ## / 71
saslSASLDB.dll (3e2a0a6c958b) - ## / 69
saslSCRAM.dll (06fd0f840473) - ## / 69
saslSQLITE.dll (c5a0421c08a1) - ## / 68
libenchant_ispell.dll (95018aa9f051) - ## / 68
libenchant_myspell.dll (1c399ba57d3b) - ## / 69
libenchant_ispell.dll (77d1c6588c0d) - ## / 68
libenchant_myspell.dll (a4fc73e5bb01) - ## / 68
libsodium.dll (53b3dc639571) - ## / 71
libsodium.dll (a473d8aa25e6) - ## / 67
libpq.dll (0b0dbe2f87a9) - ## / 68
libpq.dll (e302dfa913a8) - ## / 70
icudt64.dll (4d8ec1a9c38d) - ## / 70
icuin64.dll (654892a369d7) - ## / 70
icuio64.dll (21c996d76d99) - ## / 71
icuuc64.dll (826767fba73b) - ## / 72
icudt64.dll (cc439147ce9a) - ## / 69
icuin64.dll (1cb7db64a995) - ## / 68
icuio64.dll (fe0cd2f03d31) - ## / 69
icuuc64.dll (82803d62abfc) - ## / 69
libssh2.dll (843b3820e9aa) - ## / 67
libssh2.dll (ab9eb2f02364) - ## / 66
nghttp2.dll (5acf6537fb65) - ## / 67
nghttp2.dll (05a36b13fa6f) - ## / 69
php.7.3.17.nupkg (4a0b7ff84f84) - ## / 55
php-7.3.17-nts-Win32-VC15-x64.zip (9867cb9ff5e7) - ## / 57
php-7.3.17-nts-Win32-VC15-x86.zip (25600fe13907) - ## / 61
php-7.3.17-Win32-VC15-x64.zip (d4f8877b2ec1) - ## / 61
php-7.3.17-Win32-VC15-x86.zip (75e529722cc4) - ## / 59
deplister.exe (b37d9855333c) - ## / 73
libcrypto-1_1-x64.dll (515e63164123) - ## / 71
libssl-1_1-x64.dll (f282907274d2) - ## / 71
php-cgi.exe (0e57ac4f287b) - ## / 71
php-win.exe (2fd27457d486) - ## / 71
php.exe (7dcaa8a305c2) - ## / 71
php7.dll (a05d24a7ccd9) - ## / 68
php7phpdbg.dll (aea6d4bb6508) - ## / 72
phpdbg.exe (ad99d51f319f) - ## / 73
deplister.exe (aa01d8f61bba) - ## / 73
libcrypto-1_1.dll (228f58b55401) - ## / 71
libssl-1_1.dll (a942ce7e0e7d) - ## / 71
php-cgi.exe (f1c5c4188fe2) - ## / 73
php-win.exe (9a2021e9d7fe) - ## / 73
php.exe (7f5c9836a8b5) - ## / 73
php7.dll (f7a993c5c265) - ## / 72
php7phpdbg.dll (8c5bd1af1547) - ## / 70
phpdbg.exe (a14af78083e8) - ## / 72
php_bz2.dll (87ffef6e0b8c) - ## / 72
php_com_dotnet.dll (31d9f5adbbab) - ## / 70
php_curl.dll (2974b5bcc767) - ## / 70
php_dba.dll (7d1c4ed8c8ac) - ## / 70
php_enchant.dll (604b8f7e7254) - ## / 72
php_exif.dll (00a6af108921) - ## / 71
php_fileinfo.dll (1dde39db5353) - ## / 72
php_ftp.dll (64dd40e91fb7) - ## / 72
php_gd2.dll (96c1721af622) - ## / 72
php_gettext.dll (203528649496) - ## / 72
php_gmp.dll (109ca2f2b351) - ## / 72
php_imap.dll (75cae8f22574) - ## / 72
php_interbase.dll (983e76f8cd0a) - ## / 71
php_intl.dll (4382203a28ca) - ## / 71
php_ldap.dll (1d6a0967d475) - ## / 70
php_mbstring.dll (8281bc787c12) - ## / 72
php_mysqli.dll (6eea8ab98be0) - ## / 72
php_oci8_12c.dll (a25f52b267fa) - ## / 72
php_odbc.dll (f49b22eaad6c) - ## / 72
php_opcache.dll (1508bdf70057) - ## / 71
php_openssl.dll (9efedc2bf02d) - ## / 71
php_pdo_firebird.dll (29d6d575ef59) - ## / 71
php_pdo_mysql.dll (2f01945c09a1) - ## / 71
php_pdo_oci.dll (186c941935b1) - ## / 72
php_pdo_odbc.dll (96b180ae536a) - ## / 72
php_pdo_pgsql.dll (06d3eb1ee3a2) - ## / 69
php_pdo_sqlite.dll (7e4a624e9dda) - ## / 72
php_pgsql.dll (bb207a806db2) - ## / 69
php_phpdbg_webhelper.dll (d334b08a402c) - ## / 72
php_shmop.dll (46866702ded4) - ## / 71
php_snmp.dll (e93e26977971) - ## / 72
php_soap.dll (7c5f3721371b) - ## / 72
php_sockets.dll (f5db5b349745) - ## / 72
php_sodium.dll (bd22f2a944eb) - ## / 71
php_sqlite3.dll (768557707b07) - ## / 70
php_sysvshm.dll (ee5e79d99b2d) - ## / 70
php_tidy.dll (876637969480) - ## / 71
php_xmlrpc.dll (4a9bdb6ace3d) - ## / 72
php_xsl.dll (07f91ad5030c) - ## / 72
php_zend_test.dll (9e1c7d7f051c) - ## / 72
php_bz2.dll (5c54764810ef) - ## / 71
php_com_dotnet.dll (196b89851b1f) - ## / 71
php_curl.dll (4459227d9791) - ## / 72
php_dba.dll (e6dfbc29895c) - ## / 71
php_enchant.dll (e81e8374b7f5) - ## / 70
php_exif.dll (695806068c2a) - ## / 72
php_fileinfo.dll (d2fe56048fd0) - ## / 72
php_ftp.dll (f364b35f9012) - ## / 71
php_gd2.dll (92979261b5cf) - ## / 72
php_gettext.dll (064d2b3e4503) - ## / 69
php_gmp.dll (20fd160c86c8) - ## / 72
php_imap.dll (8ea5ca6b5d8b) - ## / 71
php_interbase.dll (25a9c788f316) - ## / 71
php_intl.dll (a3d82c9a9bfd) - ## / 72
php_ldap.dll (894bdb0ffeb3) - ## / 72
php_mbstring.dll (db9601c6f3bd) - ## / 72
php_mysqli.dll (972fe79f354a) - ## / 68
php_oci8_12c.dll (a66fbf16a1ce) - ## / 72
php_odbc.dll (e2acb2eaa1e0) - ## / 72
php_opcache.dll (b6a36e5551a3) - ## / 71
php_openssl.dll (2a653741d368) - ## / 71
php_pdo_firebird.dll (9640b746dcbc) - ## / 71
php_pdo_mysql.dll (b74c611f5d6f) - ## / 72
php_pdo_oci.dll (2de9433bea31) - ## / 72
php_pdo_odbc.dll (c3c7e12311e2) - ## / 70
php_pdo_pgsql.dll (4d3c7c7ef97f) - ## / 72
php_pdo_sqlite.dll (aa48079e88e7) - ## / 71
php_pgsql.dll (0f1ebea3e17e) - ## / 72
php_phpdbg_webhelper.dll (33904d829f2f) - ## / 71
php_shmop.dll (d7e163a6becc) - ## / 72
php_snmp.dll (24ff72d38ea7) - ## / 72
php_soap.dll (6352ca26e267) - ## / 72
php_sockets.dll (288039544514) - ## / 71
php_sodium.dll (6681fb5f6201) - ## / 71
php_sqlite3.dll (8b075b1d3e18) - ## / 72
php_sysvshm.dll (039773b14723) - ## / 72
php_tidy.dll (8595e82da2aa) - ## / 71
php_xmlrpc.dll (9b78a2266289) - ## / 71
php_xsl.dll (c5b4abf5aac7) - ## / 71
php_zend_test.dll (5a4970130dfc) - ## / 71

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.6	2458	Wednesday, April 10, 2024	Approved
PHP (Hypertext Preprocessor) 8.3.4	6836	Wednesday, March 13, 2024	Approved
PHP (Hypertext Preprocessor) 8.3.3	6803	Wednesday, February 14, 2024	Approved
PHP (Hypertext Preprocessor) 8.3.2	6369	Wednesday, January 17, 2024	Approved
PHP (Hypertext Preprocessor) 8.3.1	5591	Wednesday, December 20, 2023	Approved
PHP (Hypertext Preprocessor) 8.3.0	6165	Wednesday, November 22, 2023	Approved
PHP (Hypertext Preprocessor) 8.2.18	22	Wednesday, April 10, 2024	Approved
PHP (Hypertext Preprocessor) 8.2.17	140	Wednesday, March 13, 2024	Approved
PHP (Hypertext Preprocessor) 8.2.16	1201	Wednesday, February 14, 2024	Approved
PHP (Hypertext Preprocessor) 8.2.15	1498	Wednesday, January 17, 2024	Approved
PHP (Hypertext Preprocessor) 8.2.14	1367	Wednesday, December 20, 2023	Approved
PHP (Hypertext Preprocessor) 8.2.13	1937	Wednesday, November 22, 2023	Approved
PHP (Hypertext Preprocessor) 8.2.12	7245	Wednesday, October 25, 2023	Approved
PHP (Hypertext Preprocessor) 8.2.11	7377	Wednesday, September 27, 2023	Approved
PHP (Hypertext Preprocessor) 8.2.10	7359	Wednesday, August 30, 2023	Approved
PHP (Hypertext Preprocessor) 8.2.9	7448	Wednesday, August 2, 2023	Approved
PHP (Hypertext Preprocessor) 8.2.8	7404	Wednesday, July 5, 2023	Approved
PHP (Hypertext Preprocessor) 8.2.7	6840	Wednesday, June 7, 2023	Approved
PHP (Hypertext Preprocessor) 8.2.6	7010	Tuesday, May 9, 2023	Approved
PHP (Hypertext Preprocessor) 8.2.5	6555	Wednesday, April 12, 2023	Approved
PHP (Hypertext Preprocessor) 8.2.4	6733	Wednesday, March 15, 2023	Approved
PHP (Hypertext Preprocessor) 8.2.3	6687	Tuesday, February 14, 2023	Approved
PHP (Hypertext Preprocessor) 8.2.2	3922	Wednesday, February 1, 2023	Approved
PHP (Hypertext Preprocessor) 8.2.1	6481	Wednesday, January 4, 2023	Approved
PHP (Hypertext Preprocessor) 8.2.0	6462	Tuesday, December 6, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.28	64	Wednesday, April 10, 2024	Approved
PHP (Hypertext Preprocessor) 8.1.27	2220	Wednesday, December 20, 2023	Approved
PHP (Hypertext Preprocessor) 8.1.26	424	Wednesday, November 22, 2023	Approved
PHP (Hypertext Preprocessor) 8.1.25	387	Wednesday, October 25, 2023	Approved
PHP (Hypertext Preprocessor) 8.1.24	591	Wednesday, September 27, 2023	Approved
PHP (Hypertext Preprocessor) 8.1.23	1432	Saturday, September 2, 2023	Approved
PHP (Hypertext Preprocessor) 8.1.22	836	Wednesday, August 2, 2023	Approved
PHP (Hypertext Preprocessor) 8.1.21	515	Wednesday, July 5, 2023	Approved
PHP (Hypertext Preprocessor) 8.1.20	675	Wednesday, June 7, 2023	Approved
PHP (Hypertext Preprocessor) 8.1.19	350	Wednesday, May 10, 2023	Approved
PHP (Hypertext Preprocessor) 8.1.18	325	Wednesday, April 12, 2023	Approved
PHP (Hypertext Preprocessor) 8.1.17	328	Wednesday, March 15, 2023	Approved
PHP (Hypertext Preprocessor) 8.1.16	2648	Wednesday, February 15, 2023	Approved
PHP (Hypertext Preprocessor) 8.1.15	113	Wednesday, February 1, 2023	Approved
PHP (Hypertext Preprocessor) 8.1.14	460	Wednesday, January 4, 2023	Approved
PHP (Hypertext Preprocessor) 8.1.13	5383	Tuesday, November 22, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.12	10410	Wednesday, October 26, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.11	8652	Wednesday, September 28, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.10	23017	Wednesday, August 31, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.9	8402	Wednesday, August 3, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.8	7234	Wednesday, July 6, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.7	9714	Wednesday, June 8, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.6	9391	Wednesday, May 11, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.5	9885	Wednesday, April 13, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.4	10360	Wednesday, March 16, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.3	9769	Wednesday, February 16, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.2	10557	Wednesday, January 19, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.1	12228	Wednesday, December 15, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.30	1330	Friday, September 1, 2023	Approved
PHP (Hypertext Preprocessor) 8.0.29	932	Thursday, June 8, 2023	Approved
PHP (Hypertext Preprocessor) 8.0.28	3410	Wednesday, February 15, 2023	Approved
PHP (Hypertext Preprocessor) 8.0.27	1192	Wednesday, January 4, 2023	Approved
PHP (Hypertext Preprocessor) 8.0.26	989	Wednesday, November 23, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.25	569	Tuesday, October 25, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.24	623	Thursday, September 29, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.23	765	Tuesday, August 30, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.22	676	Tuesday, August 2, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.21	343	Tuesday, July 5, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.20	1099	Wednesday, June 8, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.19	1079	Tuesday, May 10, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.18	778	Wednesday, April 13, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.17	516	Tuesday, March 15, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.16	185	Wednesday, February 16, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.15	215	Tuesday, January 18, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.14	342	Thursday, December 16, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.10	25731	Wednesday, August 25, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.9	7563	Thursday, July 29, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.8	7884	Wednesday, June 30, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.7	7300	Wednesday, June 2, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.6	6764	Wednesday, May 5, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.5	126	Wednesday, April 28, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.3	14340	Wednesday, March 3, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.2	1356	Thursday, February 4, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.1	16919	Wednesday, January 6, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.0.20201221	4730	Monday, December 21, 2020	Approved
PHP (Hypertext Preprocessor) 8.0.0	8830	Friday, November 27, 2020	Approved
PHP (Hypertext Preprocessor) 7.4.33	2748	Thursday, November 3, 2022	Approved
PHP (Hypertext Preprocessor) 7.4.32	519	Thursday, September 29, 2022	Approved
PHP (Hypertext Preprocessor) 7.4.30	2628	Wednesday, June 8, 2022	Approved
PHP (Hypertext Preprocessor) 7.4.29	792	Thursday, April 14, 2022	Approved
PHP (Hypertext Preprocessor) 7.4.28	14977	Thursday, February 24, 2022	Approved
PHP (Hypertext Preprocessor) 7.4.27	4922	Wednesday, December 15, 2021	Approved
PHP (Hypertext Preprocessor) 7.4.23	1077	Wednesday, August 25, 2021	Approved
PHP (Hypertext Preprocessor) 7.4.22	1254	Wednesday, July 28, 2021	Approved
PHP (Hypertext Preprocessor) 7.4.21	1103	Wednesday, June 30, 2021	Approved
PHP (Hypertext Preprocessor) 7.4.20	1079	Wednesday, June 2, 2021	Approved
PHP (Hypertext Preprocessor) 7.4.19	2347	Tuesday, May 4, 2021	Approved
PHP (Hypertext Preprocessor) 7.4.18	500	Wednesday, April 28, 2021	Approved
PHP (Hypertext Preprocessor) 7.4.16	2909	Tuesday, March 2, 2021	Approved
PHP (Hypertext Preprocessor) 7.4.14	3052	Tuesday, January 5, 2021	Approved
PHP (Hypertext Preprocessor) 7.4.13	8129	Tuesday, November 24, 2020	Approved
PHP (Hypertext Preprocessor) 7.4.11	17994	Tuesday, September 29, 2020	Approved
PHP (Hypertext Preprocessor) 7.4.9	16139	Wednesday, August 5, 2020	Approved
PHP (Hypertext Preprocessor) 7.4.7	15643	Wednesday, June 10, 2020	Approved
PHP (Hypertext Preprocessor) 7.4.6	5959	Thursday, May 28, 2020	Approved
PHP (Hypertext Preprocessor) 7.4.5	15307	Wednesday, April 15, 2020	Approved
PHP (Hypertext Preprocessor) 7.4.3	17428	Friday, February 21, 2020	Approved
PHP (Hypertext Preprocessor) 7.4.2	8656	Wednesday, January 22, 2020	Approved
PHP (Hypertext Preprocessor) 7.4.1	9586	Tuesday, December 24, 2019	Approved
PHP (Hypertext Preprocessor) 7.4.0	12757	Wednesday, November 27, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.30	6773	Wednesday, August 25, 2021	Approved
PHP (Hypertext Preprocessor) 7.3.29	1728	Wednesday, June 30, 2021	Approved
PHP (Hypertext Preprocessor) 7.3.28	3312	Wednesday, April 28, 2021	Approved
PHP (Hypertext Preprocessor) 7.3.26	3306	Tuesday, January 5, 2021	Approved
PHP (Hypertext Preprocessor) 7.3.25	3507	Tuesday, November 24, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.24	981	Tuesday, October 27, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.23	1980	Tuesday, September 29, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.22	1296	Tuesday, September 1, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.21	1363	Wednesday, August 5, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.20	1015	Tuesday, July 7, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.19	1264	Wednesday, June 10, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.18	1140	Tuesday, May 12, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.17	1122	Wednesday, April 15, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.15	3358	Tuesday, February 18, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.14	1906	Tuesday, January 21, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.13	2702	Wednesday, December 18, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.12	12630	Wednesday, November 20, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.11	9844	Tuesday, October 22, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.10	12083	Wednesday, September 25, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.9	10862	Wednesday, August 28, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.8	7973	Tuesday, August 6, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.7	15071	Wednesday, July 3, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.6	13209	Wednesday, May 29, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.5	9765	Wednesday, May 1, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.4	8447	Wednesday, April 3, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.3	7193	Thursday, March 14, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.1	60399	Thursday, January 10, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.0	33474	Thursday, December 6, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.34	24077	Thursday, October 1, 2020	Approved
PHP (Hypertext Preprocessor) 7.2.33	2482	Wednesday, August 5, 2020	Approved
PHP (Hypertext Preprocessor) 7.2.32	1046	Wednesday, July 8, 2020	Approved
PHP (Hypertext Preprocessor) 7.2.31	2292	Tuesday, May 12, 2020	Approved
PHP (Hypertext Preprocessor) 7.2.30	1330	Wednesday, April 15, 2020	Approved
PHP (Hypertext Preprocessor) 7.2.29	1710	Tuesday, March 17, 2020	Approved
PHP (Hypertext Preprocessor) 7.2.28	1688	Tuesday, February 18, 2020	Approved
PHP (Hypertext Preprocessor) 7.2.27	1658	Thursday, January 23, 2020	Approved
PHP (Hypertext Preprocessor) 7.2.26	4531	Thursday, December 19, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.25	1940	Thursday, November 21, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.24	1582	Tuesday, October 22, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.23	4120	Friday, September 27, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.22	1909	Wednesday, August 28, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.20	4452	Friday, July 5, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.19	4853	Wednesday, May 29, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.18	127207	Wednesday, May 1, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.17	3853	Wednesday, April 3, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.15	7040	Friday, February 8, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.14	2530	Thursday, January 10, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.13	6016	Thursday, December 6, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.12	29118	Thursday, November 8, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.10	46140	Thursday, September 13, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.9	23487	Thursday, August 16, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.8	21184	Wednesday, July 18, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.7	21881	Wednesday, June 20, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.5	61122	Thursday, April 26, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.4	5076	Thursday, March 29, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.3	11786	Thursday, March 1, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.2	6840	Thursday, February 1, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.1	7095	Saturday, January 6, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.0	27051	Friday, December 1, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.33	14804	Wednesday, October 23, 2019	Approved
PHP (Hypertext Preprocessor) 7.1.32	2711	Wednesday, August 28, 2019	Approved
PHP (Hypertext Preprocessor) 7.1.31	1027	Wednesday, July 31, 2019	Approved
PHP (Hypertext Preprocessor) 7.1.30	2979	Tuesday, May 28, 2019	Approved
PHP (Hypertext Preprocessor) 7.1.29	3762	Wednesday, May 1, 2019	Approved
PHP (Hypertext Preprocessor) 7.1.28	2577	Wednesday, April 3, 2019	Approved
PHP (Hypertext Preprocessor) 7.1.27	3232	Thursday, March 7, 2019	Approved
PHP (Hypertext Preprocessor) 7.1.26	3885	Thursday, January 10, 2019	Approved
PHP (Hypertext Preprocessor) 7.1.25	3061	Thursday, December 6, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.24	2651	Thursday, November 8, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.22	2298	Thursday, September 13, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.21	3436	Thursday, August 16, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.20	4040	Thursday, July 19, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.19	4622	Thursday, June 21, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.18	3690	Friday, May 25, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.17	2983	Thursday, April 26, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.16	3635	Thursday, March 29, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.15	5165	Thursday, March 1, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.14	5625	Thursday, February 1, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.13	2435	Saturday, January 6, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.12	9816	Thursday, November 23, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.11	9325	Wednesday, October 25, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.10	9048	Wednesday, September 27, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.8	19758	Wednesday, August 2, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.7	14105	Thursday, July 6, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.6	18988	Thursday, June 8, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.5	17132	Wednesday, May 10, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.4	17602	Wednesday, April 12, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.3	19970	Thursday, March 16, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.2	31245	Wednesday, February 15, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.1.20170212	2161	Sunday, February 12, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.1	5985	Thursday, January 19, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.0	8489	Friday, December 2, 2016	Approved
PHP (Hypertext Preprocessor) 7.0.33	17332	Friday, December 7, 2018	Approved
PHP (Hypertext Preprocessor) 7.0.32	5763	Thursday, September 13, 2018	Approved
PHP (Hypertext Preprocessor) 7.0.31	6722	Friday, July 20, 2018	Approved
PHP (Hypertext Preprocessor) 7.0.30	9629	Thursday, April 26, 2018	Approved
PHP (Hypertext Preprocessor) 7.0.28	2495	Thursday, March 1, 2018	Approved
PHP (Hypertext Preprocessor) 7.0.27	4674	Saturday, January 6, 2018	Approved
PHP (Hypertext Preprocessor) 7.0.26	3260	Thursday, November 23, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.25	1969	Wednesday, October 25, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.24	2008	Tuesday, September 26, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.23	2361	Tuesday, August 29, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.22	3282	Wednesday, August 2, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.21	3335	Thursday, July 6, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.20	4338	Wednesday, June 7, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.19	5556	Tuesday, May 9, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.18	3506	Wednesday, April 12, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.17	4450	Thursday, March 16, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.16	4001	Tuesday, February 14, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.15	432	Sunday, February 12, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.13	1796	Monday, November 28, 2016	Approved
PHP (Hypertext Preprocessor) 7.0.9	134823	Wednesday, July 20, 2016	Approved
PHP (Hypertext Preprocessor) 7.0.8	503	Wednesday, June 22, 2016	Approved
PHP (Hypertext Preprocessor) 7.0.7	1240	Wednesday, May 25, 2016	Approved
PHP (Hypertext Preprocessor) 7.0.6	760	Sunday, May 8, 2016	Approved
PHP (Hypertext Preprocessor) 7.0.5	3589	Wednesday, March 30, 2016	Approved
PHP (Hypertext Preprocessor) 7.0.4	3085	Friday, March 4, 2016	Approved
PHP (Hypertext Preprocessor) 7.0.3	3873	Wednesday, February 3, 2016	Approved
PHP (Hypertext Preprocessor) 7.0.2	2573	Wednesday, January 6, 2016	Approved
PHP (Hypertext Preprocessor) 7.0.1	2208	Wednesday, December 16, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.40	13830	Thursday, January 10, 2019	Approved
PHP (Hypertext Preprocessor) 5.6.39	1651	Friday, December 7, 2018	Approved
PHP (Hypertext Preprocessor) 5.6.38	3060	Friday, September 14, 2018	Approved
PHP (Hypertext Preprocessor) 5.6.37	2321	Friday, July 20, 2018	Approved
PHP (Hypertext Preprocessor) 5.6.36	3544	Thursday, April 26, 2018	Approved
PHP (Hypertext Preprocessor) 5.6.35	1812	Friday, March 30, 2018	Approved
PHP (Hypertext Preprocessor) 5.6.34	1434	Thursday, March 1, 2018	Approved
PHP (Hypertext Preprocessor) 5.6.33	2909	Saturday, January 6, 2018	Approved
PHP (Hypertext Preprocessor) 5.6.32	2572	Thursday, October 26, 2017	Approved
PHP (Hypertext Preprocessor) 5.6.31	6196	Thursday, July 6, 2017	Approved
PHP (Hypertext Preprocessor) 5.6.30	18453	Sunday, February 12, 2017	Approved
PHP (Hypertext Preprocessor) 5.6.17	4733	Wednesday, February 3, 2016	Approved
PHP (Hypertext Preprocessor) 5.6.16	930	Thursday, November 26, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.15	492	Thursday, October 29, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.14	424	Thursday, October 1, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.13	491	Friday, September 4, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.12	515	Thursday, August 6, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.11	585	Sunday, July 12, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.10	478	Thursday, June 11, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.9	4315	Friday, May 15, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.8	589	Thursday, April 16, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.7	1371	Monday, March 23, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.6	522	Thursday, February 19, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.5	513	Thursday, January 22, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.4	672	Friday, December 12, 2014	Approved
PHP (Hypertext Preprocessor) 5.6.3	20194	Thursday, November 13, 2014	Approved
PHP (Hypertext Preprocessor) 5.6.2	1109	Thursday, October 16, 2014	Approved
PHP (Hypertext Preprocessor) 5.6.1	821	Friday, September 26, 2014	Approved
PHP (Hypertext Preprocessor) 5.6.0	1410	Thursday, August 28, 2014	Approved
PHP (Hypertext Preprocessor) 5.5.38	9040	Thursday, February 9, 2017	Approved
PHP (Hypertext Preprocessor) 5.5.16	791	Thursday, August 21, 2014	Approved
PHP (Hypertext Preprocessor) 5.5.15	815	Tuesday, July 29, 2014	Approved
PHP (Hypertext Preprocessor) 5.5.14	774	Tuesday, July 1, 2014	Approved
PHP (Hypertext Preprocessor) 5.5.13	734	Thursday, June 5, 2014	Approved
PHP (Hypertext Preprocessor) 5.5.12	648	Wednesday, May 21, 2014	Approved
PHP (Hypertext Preprocessor) 5.5.11	1080	Tuesday, April 22, 2014	Approved
PHP (Hypertext Preprocessor) 5.4.45	2223	Thursday, February 9, 2017	Approved
PHP (Hypertext Preprocessor) 5.3.29	725	Thursday, February 9, 2017	Approved
PHP (Hypertext Preprocessor) 5.3.28	1170	Thursday, December 12, 2013	Approved
PHP (Hypertext Preprocessor) 5.3.27	851	Friday, July 12, 2013	Approved
PHP (Hypertext Preprocessor) 5.3.26	663	Thursday, June 6, 2013	Approved
PHP (Hypertext Preprocessor) 5.3.25	660	Thursday, May 9, 2013	Approved
PHP (Hypertext Preprocessor) 5.3.24	619	Thursday, April 11, 2013	Approved
PHP (Hypertext Preprocessor) 5.3.23	609	Friday, March 15, 2013	Approved
PHP (Hypertext Preprocessor) 5.3.22	615	Thursday, February 21, 2013	Approved
PHP (Hypertext Preprocessor) 5.3.21	647	Thursday, January 17, 2013	Approved
PHP (Hypertext Preprocessor) 5.3.20	620	Thursday, December 20, 2012	Approved
PHP (Hypertext Preprocessor) 5.3.19	614	Tuesday, November 27, 2012	Approved
PHP (Hypertext Preprocessor) 5.3.18	651	Thursday, October 18, 2012	Approved
PHP (Hypertext Preprocessor) 5.3.17	642	Thursday, September 13, 2012	Approved
PHP (Hypertext Preprocessor) 5.3.16	567	Thursday, August 16, 2012	Approved
PHP (Hypertext Preprocessor) 5.3.15	629	Friday, July 20, 2012	Approved
PHP (Hypertext Preprocessor) 5.3.14	568	Wednesday, June 27, 2012	Approved
PHP (Hypertext Preprocessor) 5.3.10	785	Monday, February 20, 2012	Approved
PHP (Hypertext Preprocessor) 5.3.9	685	Thursday, January 12, 2012	Approved
PHP (Hypertext Preprocessor) 5.3.6.2	708	Tuesday, August 23, 2011	Approved
PHP (Hypertext Preprocessor) 5.3.6.1	600	Tuesday, August 23, 2011	Approved
PHP (Hypertext Preprocessor) 5.3.6	941	Tuesday, August 23, 2011	Approved

Release Notes

https://secure.php.net/ChangeLog-7.php#7.3.17

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,913,401

1,122

15 Apr 2020

PHP (Hypertext Preprocessor)

PHP (Hypertext Preprocessor) 7.3.17

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: