Step 1: Review Your Packages

Step 2: Choose Your Integration Method

Step 3: Copy Your Script or Download Config

Option 1: Copy Script

Option 2: Download Config

Step 4: Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

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

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

Option 2: Internalized Package (Reliable, Scalable)

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

Step 5: Copy Your Script

See options you can pass to upgrade.

See best practices for scripting.

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

### c. Other Requirements ###

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

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

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

## 2. TOP LEVEL VARIABLES ##

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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

- name: Install and Configure Chocolatey
  hosts: all

## 2. TOP LEVEL VARIABLES ##
  vars:

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

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

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

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

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

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

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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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

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

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

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

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

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

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

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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

chocolatey_feature 'useBackgroundService' do
  action :enable
end

chocolatey_feature 'useBackgroundServiceWithNonAdministratorsOnly' do
  action :enable
end

chocolatey_feature 'allowBackgroundServiceUninstallsFromUserInstallsOnly' do
  action :enable
end

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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


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

### b. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
$_choco_download_url = 'INTERNAL REPO URL/package/chocolatey.1.2.1.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,718,937

Downloads of v 8.0.26:

698

Last Update:

23 Nov 2022

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.

8.0.26 | Updated: 23 Nov 2022

Downloads:

1,718,937

Downloads of v 8.0.26:

698

Maintainer(s):

Software Author(s):

PHP Authors

Tags:

php development programming foss cross-platform admin

PHP (Hypertext Preprocessor) 8.0.26

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 as a Note:

At least one file within this package has greater than 0 detections, but less than 5

Details

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install 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=8.0.26 --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="'8.0.26'" [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="'8.0.26'" 
$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: '8.0.26'
    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  '8.0.26'
end

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


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

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


package { 'php':
  ensure   => '8.0.26',
  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 23 Nov 2022.

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"""'.

Notes

If the package is out of date please check Version History for the latest submitted version. If you have a question, please ask it in Chocolatey Community Package Discussions or raise an issue on the Chocolatey Community Packages Repository if you have problems with the package. Disqus comments will generally not be responded to.

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-8.0.26-Win32-vs16-x86.zip>
  64-Bit software (threadsafe): <http://windows.php.net/downloads/releases/php-8.0.26-Win32-vs16-x64.zip>
  32-Bit software (non-threadsafe): <http://windows.php.net/downloads/releases/php-8.0.26-nts-Win32-vs16-x86.zip>
  64-Bit software (non-threadsafe): <http://windows.php.net/downloads/releases/php-8.0.26-nts-Win32-vs16-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): 20EDA6CE4F2577590A2CC767EB1BE4C7A776B949C2D28F959EBD5E33A6BD0B8B
  checksum64 (threadsafe): 6010B059C3883332532B52482A32ABD1320B17908FE48E80CC0C9E7A74B61FCA
  checksum32 (non-threadsafe): 20216020E03E22A231C5CA08F252D9CFC0E372459C0149F2814219B1A297DFD3
  checksum64 (non-threadsafe): F83C10AB7330B2CC6922B4EB1E937637CB2F1B22CC8E413702636211F83458D3

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

md5: AD6FCA7B0FD0EFE81570F4CA410E17BA | sha1: 8355058A4A34C61599B0CAEFE17152E4C4066B74 | sha256: F83C10AB7330B2CC6922B4EB1E937637CB2F1B22CC8E413702636211F83458D3 | sha512: 9AEC994E3170034FE9E982B5FE62A6874C7626E27C915B1FA0BF3BDA75D19D81949777A7C765E087F6427CC17F2E3A9215F72C5FFD1E27BD27B7D3082D6C4DC3

tools\php-8.0.26-nts-Win32-vs16-x86.zip

md5: 3B710E3517F5AAE1B43444F8FF9F3765 | sha1: B6C0526AC1574761DFC6F93129012585DA4F9FA2 | sha256: 20216020E03E22A231C5CA08F252D9CFC0E372459C0149F2814219B1A297DFD3 | sha512: 0D9D2BFEA55275DF0030DA25EAEE37AC533284A8AEFE18812B1A583C92EEF5D91C56FE52C2FE3218F7802F819A09EFB9496AA8706858C106EC1AE3F8CF99EB05

tools\php-8.0.26-Win32-vs16-x64.zip

md5: E687B43B16B398EAA155AE8442B6AAC0 | sha1: F6A49F484B5D28B46A430E4E488B36EB1E16E4EA | sha256: 6010B059C3883332532B52482A32ABD1320B17908FE48E80CC0C9E7A74B61FCA | sha512: 82BA302936A6E8C873E545BF24AFC9E8F1ECF0572D59457CA9264BE037CAFABB8878166ACFE14F810CE248BED81DBF1D94829F4CDEA67B10FBB4CCE310AFE11F

tools\php-8.0.26-Win32-vs16-x86.zip

md5: 36161E13FF0049BCBEA3C52407D96227 | sha1: 5F552FD5492D704CAE5C063097B1D7295E022E5A | sha256: 20EDA6CE4F2577590A2CC767EB1BE4C7A776B949C2D28F959EBD5E33A6BD0B8B | sha512: CE08393B476B88E2AC263421104A3F3C8D2B552CE8F37A995D8C6CF2D08AB5C45F04D099467970C3E01BAE1CDE0AD040DCBE803B8214BDA095772DD7D29FC0BB

Virus Scan Results

libenchant2.dll (3ab82ce56ddf) - ## / 67
libpq.dll (b19b529f42cd) - ## / 67
libsasl.dll (da1da881fb90) - ## / 67
libsodium.dll (e664ecb63786) - ## / 70
libsqlite3.dll (619ab6247afb) - ## / 65
nghttp2.dll (60ce1c9dbe10) - ## / 70
libenchant2.dll (95a751bb0919) - ## / 70
libpq.dll (1d065df6cbb2) - ## / 68
libsasl.dll (f7dc4c1db85e) - ## / 71
libsodium.dll (b2a909522cac) - ## / 71
libsqlite3.dll (4958e1b939bb) - ## / 69
nghttp2.dll (554a21c530a7) - ## / 69
libenchant2_hunspell.dll (a36c34aa22ec) - ## / 67
libenchant2_hunspell.dll (99c109771a87) - ## / 70
icudt68.dll (b6a7cbb78ae7) - ## / 65
icuin68.dll (d1eade4923a0) - ## / 65
icuio68.dll (09a8fbc3e8fe) - ## / 60
icuuc68.dll (c9f1611fc7c3) - ## / 65
icudt68.dll (511f9e1230a0) - ## / 66
icuin68.dll (f8c1164bcd44) - ## / 70
icuio68.dll (bad8d429cbc6) - ## / 71
icuuc68.dll (7d484073fdd0) - ## / 66
glib-2.dll (94d07369ea7b) - ## / 69
gmodule-2.dll (dae2cf13a531) - ## / 69
glib-2.dll (528cf0686db3) - ## / 71
gmodule-2.dll (63b8221c7200) - ## / 71
libssh2.dll (3e60c16a0709) - ## / 69
libssh2.dll (502cc4bf36cc) - ## / 63
libcrypto-1_1-x64.dll (afa6ed14652f) - ## / 71
libssl-1_1-x64.dll (234c93196415) - ## / 70
libcrypto-1_1.dll (92477449e1e7) - ## / 70
libssl-1_1.dll (6e2871baab30) - ## / 70
php.8.0.26.nupkg (e5c3b5670a93) - ## / 57
php-8.0.26-nts-Win32-vs16-x64.zip (f83c10ab7330) - ## / 65
php-8.0.26-nts-Win32-vs16-x86.zip (20216020e03e) - ## / 61
php-8.0.26-Win32-vs16-x64.zip (6010b059c388) - ## / 64
php-8.0.26-Win32-vs16-x86.zip (20eda6ce4f25) - ## / 61
deplister.exe (d5458e498f97) - ## / 72
php-cgi.exe (6af6df029192) - ## / 71
php-win.exe (c32d7f7a8113) - ## / 72
php.exe (482637675b73) - ## / 72
php8.dll (2f6a2a59d7c3) - ## / 70
php8phpdbg.dll (ea98366eb896) - ## / 70
phpdbg.exe (97f2f8ce54b0) - ## / 71
deplister.exe (c008cc99a0d3) - ## / 72
php-cgi.exe (a19c460ef6be) - ## / 72
php-win.exe (f99f718ffbd6) - ## / 71
php.exe (ee9e32f0bae1) - ## / 72
php8.dll (51463e3b6b6e) - ## / 61
php8phpdbg.dll (26ce65a48bf6) - ## / 71
phpdbg.exe (1ef4561e41a8) - ## / 72
php_bz2.dll (8b48f06d31c2) - ## / 69
php_com_dotnet.dll (65b3dabe644e) - ## / 71
php_curl.dll (a9fc06a0dbfb) - ## / 70
php_dba.dll (b52336d8cf47) - ## / 71
php_enchant.dll (e91a6cac071d) - ## / 71
php_exif.dll (c925052af0d5) - ## / 71
php_ffi.dll (47c178a3da16) - ## / 71
php_fileinfo.dll (2c68a258145d) - ## / 71
php_ftp.dll (60032010c028) - ## / 69
php_gd.dll (ff3d0613c174) - ## / 71
php_gettext.dll (965a5cfbcca4) - ## / 71
php_gmp.dll (7d8ea078b962) - ## / 71
php_imap.dll (91dc479debae) - ## / 71
php_intl.dll (a7ec73b5bc8d) - ## / 71
php_ldap.dll (211e43f3d02e) - ## / 70
php_mbstring.dll (b592f4cba40f) - ## / 71
php_mysqli.dll (42f08985e158) - ## / 70
php_oci8_19.dll (771e8e48ffff) - ## / 71
php_odbc.dll (e005a052504d) - ## / 69
php_opcache.dll (74fbdf0c9c15) - ## / 70
php_openssl.dll (c32764e2aeca) - ## / 71
php_pdo_firebird.dll (cec9a985928c) - ## / 71
php_pdo_mysql.dll (e250cc851f0f) - ## / 71
php_pdo_oci.dll (c329e449996d) - ## / 71
php_pdo_odbc.dll (9ca73557802c) - ## / 71
php_pdo_pgsql.dll (9b463a4e718a) - ## / 70
php_pdo_sqlite.dll (aa332c73cd14) - ## / 71
php_pgsql.dll (81ad9975081a) - ## / 71
php_phpdbg_webhelper.dll (cb91ac209dd6) - ## / 70
php_shmop.dll (5326694c95da) - ## / 70
php_snmp.dll (9edcf91fdcd6) - ## / 65
php_soap.dll (c00e49a0bf5b) - ## / 70
php_sockets.dll (a0564701acda) - ## / 70
php_sodium.dll (8e12dd1edc11) - ## / 69
php_sqlite3.dll (dcfbf24fc640) - ## / 70
php_sysvshm.dll (b16e09f514ad) - ## / 71
php_tidy.dll (86024002e104) - ## / 71
php_xsl.dll (6630cc05aed8) - ## / 70
php_zend_test.dll (073b8799f025) - ## / 70
php_bz2.dll (ee42db6844c7) - ## / 71
php_com_dotnet.dll (0150a6e912b8) - ## / 71
php_curl.dll (a35f81528bf0) - ## / 71
php_dba.dll (706a9efbb41c) - ## / 71
php_enchant.dll (0d783a7a8e5a) - ## / 71
php_exif.dll (301a3d2d5687) - ## / 70
php_ffi.dll (c87b1e75aeb6) - ## / 71
php_fileinfo.dll (cb70790da406) - ## / 71
php_ftp.dll (917680862fdc) - ## / 71
php_gd.dll (6914fad5e649) - ## / 71
php_gettext.dll (8f31066ca482) - ## / 68
php_gmp.dll (15cb004cf218) - ## / 71
php_imap.dll (fdc0f7149597) - ## / 71
php_intl.dll (f75fbb2551ed) - ## / 71
php_ldap.dll (d89f4c2b71c4) - ## / 71
php_mbstring.dll (d077aba351ae) - ## / 71
php_mysqli.dll (06d2cc948ee2) - ## / 71
php_oci8_19.dll (1b2f79da4e40) - ## / 71
php_odbc.dll (9f5d26deb601) - ## / 71
php_opcache.dll (a66edea39d07) - ## / 71
php_openssl.dll (21b5d04f24f7) - ## / 71
php_pdo_firebird.dll (b3f2fc6c45bb) - ## / 70
php_pdo_mysql.dll (e669907fa7bf) - ## / 71
php_pdo_oci.dll (cf8ec7bd640a) - ## / 71
php_pdo_odbc.dll (a66e8cf6f3cd) - ## / 69
php_pdo_pgsql.dll (05b87ea43e2a) - ## / 71
php_pdo_sqlite.dll (08ce535fe3c4) - ## / 70
php_pgsql.dll (ac7820446987) - ## / 71
php_phpdbg_webhelper.dll (8f1339c6cf58) - ## / 71
php_shmop.dll (afe3fbf9b8b4) - ## / 71
php_snmp.dll (c66a6406ea61) - ## / 71
php_soap.dll (dd90d6aeaa52) - ## / 71
php_sockets.dll (0268b226435f) - ## / 71
php_sodium.dll (be56baf77d2e) - ## / 71
php_sqlite3.dll (f4d09a340d77) - ## / 70
php_sysvshm.dll (5b76387e1ba1) - ## / 71
php_tidy.dll (2f796ec1a7d5) - ## / 71
php_xsl.dll (d19ece4b2e79) - ## / 71
php_zend_test.dll (3d80e9baf0c3) - ## / 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.2.1	5592	Wednesday, January 4, 2023	Approved
PHP (Hypertext Preprocessor) 8.2.0	5759	Tuesday, December 6, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.14	239	Wednesday, January 4, 2023	Approved
PHP (Hypertext Preprocessor) 8.1.13	5254	Tuesday, November 22, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.12	8807	Wednesday, October 26, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.11	8536	Wednesday, September 28, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.10	9967	Wednesday, August 31, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.9	7953	Wednesday, August 3, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.8	7174	Wednesday, July 6, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.7	9656	Wednesday, June 8, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.6	9307	Wednesday, May 11, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.5	9822	Wednesday, April 13, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.4	9867	Wednesday, March 16, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.3	9701	Wednesday, February 16, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.2	10450	Wednesday, January 19, 2022	Approved
PHP (Hypertext Preprocessor) 8.1.1	12118	Wednesday, December 15, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.27	734	Wednesday, January 4, 2023	Approved
PHP (Hypertext Preprocessor) 8.0.26	698	Wednesday, November 23, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.25	521	Tuesday, October 25, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.24	594	Thursday, September 29, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.23	733	Tuesday, August 30, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.22	647	Tuesday, August 2, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.21	322	Tuesday, July 5, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.20	1064	Wednesday, June 8, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.19	1040	Tuesday, May 10, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.18	726	Wednesday, April 13, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.17	485	Tuesday, March 15, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.16	155	Wednesday, February 16, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.15	172	Tuesday, January 18, 2022	Approved
PHP (Hypertext Preprocessor) 8.0.14	307	Thursday, December 16, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.10	25613	Wednesday, August 25, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.9	7527	Thursday, July 29, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.8	7833	Wednesday, June 30, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.7	7254	Wednesday, June 2, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.6	6713	Wednesday, May 5, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.5	92	Wednesday, April 28, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.3	14290	Wednesday, March 3, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.2	1227	Thursday, February 4, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.1	16833	Wednesday, January 6, 2021	Approved
PHP (Hypertext Preprocessor) 8.0.0.20201221	4697	Monday, December 21, 2020	Approved
PHP (Hypertext Preprocessor) 8.0.0	8103	Friday, November 27, 2020	Approved
PHP (Hypertext Preprocessor) 7.4.33	766	Thursday, November 3, 2022	Approved
PHP (Hypertext Preprocessor) 7.4.32	437	Thursday, September 29, 2022	Approved
PHP (Hypertext Preprocessor) 7.4.30	888	Wednesday, June 8, 2022	Approved
PHP (Hypertext Preprocessor) 7.4.29	720	Thursday, April 14, 2022	Approved
PHP (Hypertext Preprocessor) 7.4.28	1970	Thursday, February 24, 2022	Approved
PHP (Hypertext Preprocessor) 7.4.27	4825	Wednesday, December 15, 2021	Approved
PHP (Hypertext Preprocessor) 7.4.23	997	Wednesday, August 25, 2021	Approved
PHP (Hypertext Preprocessor) 7.4.22	1208	Wednesday, July 28, 2021	Approved
PHP (Hypertext Preprocessor) 7.4.21	1048	Wednesday, June 30, 2021	Approved
PHP (Hypertext Preprocessor) 7.4.20	1018	Wednesday, June 2, 2021	Approved
PHP (Hypertext Preprocessor) 7.4.19	2278	Tuesday, May 4, 2021	Approved
PHP (Hypertext Preprocessor) 7.4.18	471	Wednesday, April 28, 2021	Approved
PHP (Hypertext Preprocessor) 7.4.16	2862	Tuesday, March 2, 2021	Approved
PHP (Hypertext Preprocessor) 7.4.14	2947	Tuesday, January 5, 2021	Approved
PHP (Hypertext Preprocessor) 7.4.13	7343	Tuesday, November 24, 2020	Approved
PHP (Hypertext Preprocessor) 7.4.11	17920	Tuesday, September 29, 2020	Approved
PHP (Hypertext Preprocessor) 7.4.9	16079	Wednesday, August 5, 2020	Approved
PHP (Hypertext Preprocessor) 7.4.7	15519	Wednesday, June 10, 2020	Approved
PHP (Hypertext Preprocessor) 7.4.6	5886	Thursday, May 28, 2020	Approved
PHP (Hypertext Preprocessor) 7.4.5	15244	Wednesday, April 15, 2020	Approved
PHP (Hypertext Preprocessor) 7.4.3	17336	Friday, February 21, 2020	Approved
PHP (Hypertext Preprocessor) 7.4.2	8568	Wednesday, January 22, 2020	Approved
PHP (Hypertext Preprocessor) 7.4.1	9350	Tuesday, December 24, 2019	Approved
PHP (Hypertext Preprocessor) 7.4.0	10971	Wednesday, November 27, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.30	5756	Wednesday, August 25, 2021	Approved
PHP (Hypertext Preprocessor) 7.3.29	1695	Wednesday, June 30, 2021	Approved
PHP (Hypertext Preprocessor) 7.3.28	3275	Wednesday, April 28, 2021	Approved
PHP (Hypertext Preprocessor) 7.3.26	3238	Tuesday, January 5, 2021	Approved
PHP (Hypertext Preprocessor) 7.3.25	3472	Tuesday, November 24, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.24	915	Tuesday, October 27, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.23	1936	Tuesday, September 29, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.22	1235	Tuesday, September 1, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.21	1328	Wednesday, August 5, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.20	981	Tuesday, July 7, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.19	1235	Wednesday, June 10, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.18	1103	Tuesday, May 12, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.17	1091	Wednesday, April 15, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.15	3285	Tuesday, February 18, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.14	1838	Tuesday, January 21, 2020	Approved
PHP (Hypertext Preprocessor) 7.3.13	2663	Wednesday, December 18, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.12	12586	Wednesday, November 20, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.11	9808	Tuesday, October 22, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.10	12045	Wednesday, September 25, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.9	10804	Wednesday, August 28, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.8	7934	Tuesday, August 6, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.7	15001	Wednesday, July 3, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.6	13173	Wednesday, May 29, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.5	9731	Wednesday, May 1, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.4	8410	Wednesday, April 3, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.3	7110	Thursday, March 14, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.1	60349	Thursday, January 10, 2019	Approved
PHP (Hypertext Preprocessor) 7.3.0	33044	Thursday, December 6, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.34	22935	Thursday, October 1, 2020	Approved
PHP (Hypertext Preprocessor) 7.2.33	2378	Wednesday, August 5, 2020	Approved
PHP (Hypertext Preprocessor) 7.2.32	1001	Wednesday, July 8, 2020	Approved
PHP (Hypertext Preprocessor) 7.2.31	2261	Tuesday, May 12, 2020	Approved
PHP (Hypertext Preprocessor) 7.2.30	1290	Wednesday, April 15, 2020	Approved
PHP (Hypertext Preprocessor) 7.2.29	1660	Tuesday, March 17, 2020	Approved
PHP (Hypertext Preprocessor) 7.2.28	1658	Tuesday, February 18, 2020	Approved
PHP (Hypertext Preprocessor) 7.2.27	1626	Thursday, January 23, 2020	Approved
PHP (Hypertext Preprocessor) 7.2.26	4495	Thursday, December 19, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.25	1896	Thursday, November 21, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.24	1519	Tuesday, October 22, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.23	4086	Friday, September 27, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.22	1869	Wednesday, August 28, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.20	4387	Friday, July 5, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.19	4813	Wednesday, May 29, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.18	122643	Wednesday, May 1, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.17	3194	Wednesday, April 3, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.15	7005	Friday, February 8, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.14	2500	Thursday, January 10, 2019	Approved
PHP (Hypertext Preprocessor) 7.2.13	5934	Thursday, December 6, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.12	28717	Thursday, November 8, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.10	46099	Thursday, September 13, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.9	23404	Thursday, August 16, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.8	21134	Wednesday, July 18, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.7	21837	Wednesday, June 20, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.5	60875	Thursday, April 26, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.4	5009	Thursday, March 29, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.3	11743	Thursday, March 1, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.2	6668	Thursday, February 1, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.1	7039	Saturday, January 6, 2018	Approved
PHP (Hypertext Preprocessor) 7.2.0	26459	Friday, December 1, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.33	13785	Wednesday, October 23, 2019	Approved
PHP (Hypertext Preprocessor) 7.1.32	2668	Wednesday, August 28, 2019	Approved
PHP (Hypertext Preprocessor) 7.1.31	975	Wednesday, July 31, 2019	Approved
PHP (Hypertext Preprocessor) 7.1.30	2939	Tuesday, May 28, 2019	Approved
PHP (Hypertext Preprocessor) 7.1.29	3696	Wednesday, May 1, 2019	Approved
PHP (Hypertext Preprocessor) 7.1.28	2539	Wednesday, April 3, 2019	Approved
PHP (Hypertext Preprocessor) 7.1.27	3199	Thursday, March 7, 2019	Approved
PHP (Hypertext Preprocessor) 7.1.26	3851	Thursday, January 10, 2019	Approved
PHP (Hypertext Preprocessor) 7.1.25	2985	Thursday, December 6, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.24	2616	Thursday, November 8, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.22	2268	Thursday, September 13, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.21	3403	Thursday, August 16, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.20	4003	Thursday, July 19, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.19	4584	Thursday, June 21, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.18	3647	Friday, May 25, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.17	2950	Thursday, April 26, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.16	3601	Thursday, March 29, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.15	5130	Thursday, March 1, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.14	5188	Thursday, February 1, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.13	2395	Saturday, January 6, 2018	Approved
PHP (Hypertext Preprocessor) 7.1.12	9778	Thursday, November 23, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.11	9288	Wednesday, October 25, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.10	9010	Wednesday, September 27, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.8	19714	Wednesday, August 2, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.7	14074	Thursday, July 6, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.6	18929	Thursday, June 8, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.5	17013	Wednesday, May 10, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.4	17557	Wednesday, April 12, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.3	19702	Thursday, March 16, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.2	31198	Wednesday, February 15, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.1.20170212	2055	Sunday, February 12, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.1	5932	Thursday, January 19, 2017	Approved
PHP (Hypertext Preprocessor) 7.1.0	8361	Friday, December 2, 2016	Approved
PHP (Hypertext Preprocessor) 7.0.33	17073	Friday, December 7, 2018	Approved
PHP (Hypertext Preprocessor) 7.0.32	5731	Thursday, September 13, 2018	Approved
PHP (Hypertext Preprocessor) 7.0.31	6685	Friday, July 20, 2018	Approved
PHP (Hypertext Preprocessor) 7.0.30	9595	Thursday, April 26, 2018	Approved
PHP (Hypertext Preprocessor) 7.0.28	2459	Thursday, March 1, 2018	Approved
PHP (Hypertext Preprocessor) 7.0.27	4634	Saturday, January 6, 2018	Approved
PHP (Hypertext Preprocessor) 7.0.26	3206	Thursday, November 23, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.25	1935	Wednesday, October 25, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.24	1970	Tuesday, September 26, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.23	2321	Tuesday, August 29, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.22	3242	Wednesday, August 2, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.21	3300	Thursday, July 6, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.20	4301	Wednesday, June 7, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.19	5510	Tuesday, May 9, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.18	3470	Wednesday, April 12, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.17	4404	Thursday, March 16, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.16	3837	Tuesday, February 14, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.15	393	Sunday, February 12, 2017	Approved
PHP (Hypertext Preprocessor) 7.0.13	1760	Monday, November 28, 2016	Approved
PHP (Hypertext Preprocessor) 7.0.9	134764	Wednesday, July 20, 2016	Approved
PHP (Hypertext Preprocessor) 7.0.8	464	Wednesday, June 22, 2016	Approved
PHP (Hypertext Preprocessor) 7.0.7	1198	Wednesday, May 25, 2016	Approved
PHP (Hypertext Preprocessor) 7.0.6	724	Sunday, May 8, 2016	Approved
PHP (Hypertext Preprocessor) 7.0.5	3553	Wednesday, March 30, 2016	Approved
PHP (Hypertext Preprocessor) 7.0.4	3041	Friday, March 4, 2016	Approved
PHP (Hypertext Preprocessor) 7.0.3	3831	Wednesday, February 3, 2016	Approved
PHP (Hypertext Preprocessor) 7.0.2	2535	Wednesday, January 6, 2016	Approved
PHP (Hypertext Preprocessor) 7.0.1	2152	Wednesday, December 16, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.40	12679	Thursday, January 10, 2019	Approved
PHP (Hypertext Preprocessor) 5.6.39	1609	Friday, December 7, 2018	Approved
PHP (Hypertext Preprocessor) 5.6.38	3029	Friday, September 14, 2018	Approved
PHP (Hypertext Preprocessor) 5.6.37	2239	Friday, July 20, 2018	Approved
PHP (Hypertext Preprocessor) 5.6.36	3504	Thursday, April 26, 2018	Approved
PHP (Hypertext Preprocessor) 5.6.35	1768	Friday, March 30, 2018	Approved
PHP (Hypertext Preprocessor) 5.6.34	1399	Thursday, March 1, 2018	Approved
PHP (Hypertext Preprocessor) 5.6.33	2871	Saturday, January 6, 2018	Approved
PHP (Hypertext Preprocessor) 5.6.32	2539	Thursday, October 26, 2017	Approved
PHP (Hypertext Preprocessor) 5.6.31	6154	Thursday, July 6, 2017	Approved
PHP (Hypertext Preprocessor) 5.6.30	18368	Sunday, February 12, 2017	Approved
PHP (Hypertext Preprocessor) 5.6.17	4671	Wednesday, February 3, 2016	Approved
PHP (Hypertext Preprocessor) 5.6.16	769	Thursday, November 26, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.15	448	Thursday, October 29, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.14	387	Thursday, October 1, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.13	453	Friday, September 4, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.12	469	Thursday, August 6, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.11	544	Sunday, July 12, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.10	445	Thursday, June 11, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.9	4255	Friday, May 15, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.8	542	Thursday, April 16, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.7	1298	Monday, March 23, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.6	474	Thursday, February 19, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.5	478	Thursday, January 22, 2015	Approved
PHP (Hypertext Preprocessor) 5.6.4	608	Friday, December 12, 2014	Approved
PHP (Hypertext Preprocessor) 5.6.3	20132	Thursday, November 13, 2014	Approved
PHP (Hypertext Preprocessor) 5.6.2	1066	Thursday, October 16, 2014	Approved
PHP (Hypertext Preprocessor) 5.6.1	778	Friday, September 26, 2014	Approved
PHP (Hypertext Preprocessor) 5.6.0	1277	Thursday, August 28, 2014	Approved
PHP (Hypertext Preprocessor) 5.5.38	8188	Thursday, February 9, 2017	Approved
PHP (Hypertext Preprocessor) 5.5.16	754	Thursday, August 21, 2014	Approved
PHP (Hypertext Preprocessor) 5.5.15	776	Tuesday, July 29, 2014	Approved
PHP (Hypertext Preprocessor) 5.5.14	742	Tuesday, July 1, 2014	Approved
PHP (Hypertext Preprocessor) 5.5.13	684	Thursday, June 5, 2014	Approved
PHP (Hypertext Preprocessor) 5.5.12	608	Wednesday, May 21, 2014	Approved
PHP (Hypertext Preprocessor) 5.5.11	1038	Tuesday, April 22, 2014	Approved
PHP (Hypertext Preprocessor) 5.4.45	2009	Thursday, February 9, 2017	Approved
PHP (Hypertext Preprocessor) 5.3.29	661	Thursday, February 9, 2017	Approved
PHP (Hypertext Preprocessor) 5.3.28	1132	Thursday, December 12, 2013	Approved
PHP (Hypertext Preprocessor) 5.3.27	819	Friday, July 12, 2013	Approved
PHP (Hypertext Preprocessor) 5.3.26	622	Thursday, June 6, 2013	Approved
PHP (Hypertext Preprocessor) 5.3.25	622	Thursday, May 9, 2013	Approved
PHP (Hypertext Preprocessor) 5.3.24	588	Thursday, April 11, 2013	Approved
PHP (Hypertext Preprocessor) 5.3.23	571	Friday, March 15, 2013	Approved
PHP (Hypertext Preprocessor) 5.3.22	586	Thursday, February 21, 2013	Approved
PHP (Hypertext Preprocessor) 5.3.21	614	Thursday, January 17, 2013	Approved
PHP (Hypertext Preprocessor) 5.3.20	589	Thursday, December 20, 2012	Approved
PHP (Hypertext Preprocessor) 5.3.19	583	Tuesday, November 27, 2012	Approved
PHP (Hypertext Preprocessor) 5.3.18	606	Thursday, October 18, 2012	Approved
PHP (Hypertext Preprocessor) 5.3.17	608	Thursday, September 13, 2012	Approved
PHP (Hypertext Preprocessor) 5.3.16	539	Thursday, August 16, 2012	Approved
PHP (Hypertext Preprocessor) 5.3.15	595	Friday, July 20, 2012	Approved
PHP (Hypertext Preprocessor) 5.3.14	540	Wednesday, June 27, 2012	Approved
PHP (Hypertext Preprocessor) 5.3.10	756	Monday, February 20, 2012	Approved
PHP (Hypertext Preprocessor) 5.3.9	647	Thursday, January 12, 2012	Approved
PHP (Hypertext Preprocessor) 5.3.6.2	671	Tuesday, August 23, 2011	Approved
PHP (Hypertext Preprocessor) 5.3.6.1	569	Tuesday, August 23, 2011	Approved
PHP (Hypertext Preprocessor) 5.3.6	899	Tuesday, August 23, 2011	Approved

Release Notes

https://www.php.net/ChangeLog-8.php#8.0.26

Dependencies

- vcredist140 (≥ 14.28.29325.2)
- 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,718,937

698

23 Nov 2022

PHP (Hypertext Preprocessor)

PHP (Hypertext Preprocessor) 8.0.26

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

Notes

Ground Rules: