Puppet Agent (Portable)

  • 1
  • 2
  • 3

1.10.4 | Updated: 21 Jun 2017



Downloads of v 1.10.4:


Software Author(s):

  • Puppet

  • 1
  • 2
  • 3
Puppet Agent (Portable) 1.10.4

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Puppet Agent (Portable), run the following command from the command line or from PowerShell:


To upgrade Puppet Agent (Portable), run the following command from the command line or from PowerShell:


To uninstall Puppet Agent (Portable), run the following command from the command line or from PowerShell:


Deployment Method:

📝 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

  • 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

3. Copy Your Script

choco upgrade puppet-agent.portable -y --source="'INTERNAL REPO URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

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

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

choco upgrade puppet-agent.portable -y --source="'INTERNAL REPO URL'" 

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

Exit $exitCode

- name: Install puppet-agent.portable
    name: puppet-agent.portable
    version: '1.10.4'
    state: present

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

chocolatey_package 'puppet-agent.portable' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '1.10.4'

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

cChocoPackageInstaller puppet-agent.portable
    Name     = "puppet-agent.portable"
    Version  = "1.10.4"
    Source   = "INTERNAL REPO URL"

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

package { 'puppet-agent.portable':
  ensure   => '1.10.4',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

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

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

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

This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

This package was approved as a trusted package on 09 Jul 2020.


Puppet is a flexible, customizable framework available under the Apache 2.0 license designed to help system administrators automate the many repetitive tasks they regularly perform. As a declarative, model-based approach to IT automation, it lets you define the desired state – or the “what” – of your infrastructure using the Puppet configuration language. Once these configurations are deployed, Puppet automatically installs the necessary packages and starts the related services, and then regularly enforces the desired state. In automating the mundane, Puppet frees you to work on more challenging projects with higher business impact.

Puppet Open Source is the underlying technology for Puppet Enterprise and runs on all major Linux distributions, major Unix platforms like Solaris, HP-UX, and AIX, and Microsoft Windows.

Puppet Agent is an "All-in-One" package that installs Puppet, Ruby, Facter, Hiera, MCollective (mco) and supporting code. It is all you need to start using Puppet. See http://docs.puppetlabs.com/puppet/latest/reference/install_windows.html for more information.

Important Considerations

This is an experimental package. It will overwrite any settings you have in hiera.yaml or environment.conf.

Please Note: This is an automatically updated package. If you find it is
out of date by more than a day or two, please contact the maintainer(s) and
let them know the package is no longer updating correctly.

$packageName = 'puppet'
$toolsDir = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
$installDir = Join-Path "$toolsDir" 'puppet'
$fileName = "$($packageName).msi"
$file = Join-Path "$toolsDir" "$fileName"
$url = 'https://downloads.puppetlabs.com/windows/puppet-agent-1.10.4-x86.msi'
$url64 = 'https://downloads.puppetlabs.com/windows/puppet-agent-1.10.4-x64.msi'

Get-ChocolateyWebFile "$packageName" "$file" "$url" "$url64"

pushd "$toolsDir"
# the trailing backslash is required!
&lessmsi x "$fileName" "$installDir\"

function Create-DirectoryIfNotExists($folderName){
  if (![System.IO.Directory]::Exists($folderName)) { [System.IO.Directory]::CreateDirectory($folderName) | Out-Null }

$puppetProgramDataDir = Join-Path "$env:ALLUSERSPROFILE" 'PuppetLabs'
Create-DirectoryIfNotExists $puppetProgramDataDir

# Copy the source files
$progDataFilesDir = Join-Path "$installDir" 'SourceDir\CommonAppData\PuppetLabs'
Copy-Item "$($progDataFilesDir)\*" "$puppetProgramDataDir" -Force -Recurse

# Create the rest of the ProgramData structure if necessary
Create-DirectoryIfNotExists "$(Join-Path $puppetProgramDataDir 'code')"
Create-DirectoryIfNotExists "$(Join-Path $puppetProgramDataDir 'facter')"
Create-DirectoryIfNotExists "$(Join-Path $puppetProgramDataDir 'facter\facts.d')"
Create-DirectoryIfNotExists "$(Join-Path $puppetProgramDataDir 'hiera')"
Create-DirectoryIfNotExists "$(Join-Path $puppetProgramDataDir 'hiera\etc')"
Create-DirectoryIfNotExists "$(Join-Path $puppetProgramDataDir 'hiera\var')"
Create-DirectoryIfNotExists "$(Join-Path $puppetProgramDataDir 'mcollective')"
Create-DirectoryIfNotExists "$(Join-Path $puppetProgramDataDir 'mcollective\etc')"
Create-DirectoryIfNotExists "$(Join-Path $puppetProgramDataDir 'mcollective\var')"
Create-DirectoryIfNotExists "$(Join-Path $puppetProgramDataDir 'puppet')"
Create-DirectoryIfNotExists "$(Join-Path $puppetProgramDataDir 'puppet\etc')"
Create-DirectoryIfNotExists "$(Join-Path $puppetProgramDataDir 'puppet\var')"

# Add the BATs to choco bin
$binFilesDir = Join-Path "$installDir" 'SourceDir\Puppet Labs\Puppet\bin'
Add-BinFile -name 'puppet' -path "$binFilesDir\puppet.bat"
Add-BinFile -name 'facter' -path "$binFilesDir\facter.bat"
Add-BinFile -name 'hiera' -path "$binFilesDir\hiera.bat"
Add-BinFile -name 'mco' -path "$binFilesDir\mco.bat"
$ErrorActionPreference = 'SilentlyContinue';
$packageName = 'puppet'
$toolsDir = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
$installDir = Join-Path "$toolsDir" 'puppet'

# Remove the BATs from choco bin
$binFilesDir = Join-Path "$installDir" 'SourceDir\Puppet Labs\Puppet\bin'
Remove-BinFile -name 'puppet' -path "$binFilesDir\puppet.bat"
Remove-BinFile -name 'facter' -path "$binFilesDir\facter.bat"
Remove-BinFile -name 'hiera' -path "$binFilesDir\hiera.bat"
Remove-BinFile -name 'mco' -path "$binFilesDir\mco.bat"

Write-Warning "This package does not clean up ProgramData\PuppetLabs. You will need to do that manually."
tools\puppet\SourceDir\Puppet Labs\Puppet\facter\bin\facter.exe.ignore
tools\puppet\SourceDir\Puppet Labs\Puppet\facter\bin\libfacter_test.exe.ignore
tools\puppet\SourceDir\Puppet Labs\Puppet\facter\bin\test_convert.exe.ignore
tools\puppet\SourceDir\Puppet Labs\Puppet\facter\bin\test_env_proto.exe.ignore
tools\puppet\SourceDir\Puppet Labs\Puppet\facter\bin\test_env_win.exe.ignore
tools\puppet\SourceDir\Puppet Labs\Puppet\facter\bin\test_fstream.exe.ignore
tools\puppet\SourceDir\Puppet Labs\Puppet\facter\bin\test_iostream_shared.exe.ignore
tools\puppet\SourceDir\Puppet Labs\Puppet\facter\bin\test_iostream_static.exe.ignore
tools\puppet\SourceDir\Puppet Labs\Puppet\facter\bin\test_stdio.exe.ignore
tools\puppet\SourceDir\Puppet Labs\Puppet\facter\bin\test_system.exe.ignore
tools\puppet\SourceDir\Puppet Labs\Puppet\sys\ruby\bin\ruby.exe.ignore
tools\puppet\SourceDir\Puppet Labs\Puppet\sys\ruby\bin\rubyw.exe.ignore
tools\puppet\SourceDir\Puppet Labs\Puppet\sys\tools\bin\elevate.exe.ignore

Log in or click on link to see number of positives.

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.

Add to Builder Version Downloads Last Updated Status
Puppet Agent (Portable) 1.10.3 349 Wednesday, June 21, 2017 Approved
Puppet Agent (Portable) 1.10.2 375 Wednesday, June 21, 2017 Approved
Puppet Agent (Portable) 1.10.1 647 Friday, May 12, 2017 Approved
Puppet Agent (Portable) 1.10.0 402 Friday, April 7, 2017 Approved
Puppet Agent (Portable) 1.9.3 400 Thursday, March 9, 2017 Approved
Puppet Agent (Portable) 1.9.2 362 Monday, February 27, 2017 Approved
Puppet Agent (Portable) 1.9.1 376 Tuesday, February 14, 2017 Approved
Puppet Agent (Portable) 1.9.0 405 Friday, February 3, 2017 Approved

Discussion for the Puppet Agent (Portable) Package

Ground Rules:

  • This discussion is only about Puppet Agent (Portable) and the Puppet Agent (Portable) 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 Puppet Agent (Portable), 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.
comments powered by Disqus