#### pdftk-server (Install)

2.02 | Updated: 22 Dec 2015

2,052

2,052

Maintainer(s):

Software Author(s):

• Sid Steward
• PDF labs

### All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed

Details

To install pdftk-server (Install), run the following command from the command line or from PowerShell:

>

To upgrade pdftk-server (Install), run the following command from the command line or from PowerShell:

>

To uninstall pdftk-server (Install), run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

#### 1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

• 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://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

#### 3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

#### 4. Choose your deployment method:


choco upgrade pdftk-server -y --source="'STEP 3 URL'" [other options]


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 pdftk-server -y --source="'STEP 3 URL'"
$exitCode =$LASTEXITCODE

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

Exit $exitCode   - name: Ensure pdftk-server installed win_chocolatey: name: pdftk-server state: present version: 2.02 source: STEP 3 URL  Coming early 2020! Central Managment Reporting available now! More information...  chocolatey_package 'pdftk-server' do action :install version '2.02' source 'STEP 3 URL' end   Chocolatey::Ensure-Package ( Name: pdftk-server, Version: 2.02, Source: STEP 3 URL );  Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.  cChocoPackageInstaller pdftk-server { Name = 'pdftk-server' Ensure = 'Present' Version = '2.02' Source = 'STEP 3 URL' }  Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.  package { 'pdftk-server': provider => 'chocolatey', ensure => '2.02', source => 'STEP 3 URL', }  Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.  salt '*' chocolatey.install pdftk-server version="2.02" source="STEP 3 URL"  #### 5. 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 was approved by moderator doc on 01 Jan 2016. Description PDFtk Server is a command-line tool for working with PDFs tools\chocolateyinstall.ps1 $ErrorActionPreference = 'Stop';

$packageName= 'pdftk-server'$toolsDir   = "$(Split-Path -parent$MyInvocation.MyCommand.Definition)"
$url = 'https://www.pdflabs.com/tools/pdftk-the-pdf-toolkit/pdftk_server-2.02-win-setup.exe'$packageArgs = @{
packageName   = $packageName unzipLocation =$toolsDir
fileType      = 'EXE'
url           = $url silentArgs = "/VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-" validExitCodes= @(0, 3010, 1641) softwareName = 'pdftk-server*' checksum = '' checksumType = 'md5' checksum64 = '' checksumType64= 'md5' } Install-ChocolateyPackage @packageArgs  tools\chocolateyuninstall.ps1 # IMPORTANT: Before releasing this package, copy/paste the next 2 lines into PowerShell to remove all comments from this file: #$f='c:\path\to\thisFile.ps1'
#   gc $f | ? {$_ -notmatch "^\s*#"} | % {$_ -replace '(^.*?)\s*?[^]#.*','$1'} | Out-File $f+".~" -en utf8; mv -fo$f+".~" $f # If this is an MSI, cleaning up comments is all you need. # If this is an exe, change installerType and silentArgs # Auto Uninstaller should be able to detect and handle registry uninstalls (if it is turned on, it is in preview for 0.9.9).$ErrorActionPreference = 'Stop'; # stop on all errors

$packageName = 'pdftk-server'$softwareName = 'pdftk-server*' #part or all of the Display Name as you see it in Programs and Features. It should be enough to be unique
$installerType = 'MSI' #$installerType = 'EXE'

$silentArgs = '/qn /norestart' # https://msdn.microsoft.com/en-us/library/aa376931(v=vs.85).aspx$validExitCodes = @(0, 3010, 1605, 1614, 1641)
if ($installerType -ne 'MSI') { # The below is somewhat naive and built for EXE installers # Uncomment matching EXE type (sorted by most to least common) #$silentArgs = '/S'           # NSIS
#$silentArgs = '/VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-' # Inno Setup #$silentArgs = '/s'           # InstallShield
#$silentArgs = '/s /v"/qn"' # InstallShield with MSI #$silentArgs = '/s'           # Wise InstallMaster
#$silentArgs = '-s' # Squirrel #$silentArgs = '-q'           # Install4j
#$silentArgs = '-s -u' # Ghost # Note that some installers, in addition to the silentArgs above, may also need assistance of AHK to achieve silence. #$silentArgs = ''             # none; make silent with input macro script like AutoHotKey (AHK)
#       https://chocolatey.org/packages/autohotkey.portable
$validExitCodes = @(0) }$uninstalled = $false$local_key     = 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*'
$machine_key = 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*'$machine_key6432 = 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*'

$key = Get-ItemProperty -Path @($machine_key6432,$machine_key,$local_key) 
-ErrorAction SilentlyContinue
| ? { $_.DisplayName -like "$softwareName" }

if ($key.Count -eq 1) {$key | % {
$file = "$($_.UninstallString)" if ($installerType -eq 'MSI') {
# The Product Code GUID is all that should be passed for MSI, and very
# FIRST, because it comes directly after /x, which is already set in the
# Uninstall-ChocolateyPackage msiargs (facepalm).
$silentArgs = "$($_.PSChildName)$silentArgs"

# Don't pass anything for file, it is ignored for msi (facepalm number 2)
# Alternatively if you need to pass a path to an msi, determine that and
# use it instead of the above in silentArgs, still very first
$file = '' } Uninstall-ChocolateyPackage -PackageName$packageName 
-FileType $installerType  -SilentArgs "$silentArgs" 
-ValidExitCodes $validExitCodes  -File "$file"
}
} elseif ($key.Count -eq 0) { Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) { Write-Warning "$key.Count matches found!"
Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
$key | % {Write-Warning "-$_.DisplayName"}
}

## OTHER HELPERS
## https://github.com/chocolatey/choco/wiki/HelpersReference
#Uninstall-ChocolateyZipPackage
#Uninstall-BinFile # Only needed if you added one in the installer script, choco will remove the ones it added automatically.


## Summary
How do I create packages? See https://github.com/chocolatey/choco/wiki/CreatePackages

If you are submitting packages to the community feed (https://chocolatey.org)
always try to ensure you have read, understood and adhere to the create

## Automatic Packages?
Consider making this package an automatic package, for the best
maintainability over time. Read up at https://github.com/chocolatey/choco/wiki/AutomaticPackages

## Shim Generation
Any executables you include in the package or download (but don't call
install against using the built-in functions) will be automatically shimmed.

This means those executables will automatically be included on the path.
Shim generation runs whether the package is self-contained or uses automation
scripts.

By default, these are considered console applications.

If the application is a GUI, you should create an empty file next to the exe
named 'name.exe.gui' e.g. 'bob.exe' would need a file named 'bob.exe.gui'.
See https://github.com/chocolatey/choco/wiki/CreatePackages#how-do-i-set-up-batch-redirects-for-applications-that-have-a-gui

If you want to ignore the executable, create an empty file next to the exe
named 'name.exe.ignore' e.g. 'bob.exe' would need a file named
'bob.exe.ignore'.
See https://github.com/chocolatey/choco/wiki/CreatePackages#how-do-i-exclude-executables-from-getting-batch-redirects

## Self-Contained?
If you have a self-contained package, you can remove the automation scripts
entirely and just include the executables, they will automatically get shimmed,
which puts them on the path. Ensure you have the legal right to distribute
the application though. See https://github.com/chocolatey/choco/wiki/Legal.

You should read up on the Shim Generation section to familiarize yourself
on what to do with GUI applications and/or ignoring shims.

## Automation Scripts
You have a powerful use of Chocolatey, as you are using PowerShell. So you
can do just about anything you need. Choco has some very handy built-in
functions that you can use, these are sometimes called the helpers.

### Built-In Functions
https://github.com/chocolatey/choco/wiki/HelpersReference

* Get-BinRoot - this is a horribly named function that doesn't do what new folks think it does. It gets you the 'tools' root, which by default is set to 'c:\tools', not the chocolateyInstall bin folder.
* Install-BinFile - used for non-exe files - executables are automatically shimmed...
* Uninstall-BinFile - used for non-exe files - executables are automatically shimmed

### Getting package specific information
Use the package parameters pattern - see https://github.com/chocolatey/choco/wiki/How-To-Parse-PackageParameters-Argument

### Need to mount an ISO?
https://github.com/chocolatey/choco/wiki/How-To-Mount-An-Iso-In-Chocolatey-Package

### Environment Variables
Chocolatey makes a number of environment variables available (You can access any of these with \$env:TheVariableNameBelow):

* TEMP = Overridden to the CacheLocation, but may be the same as the original TEMP folder
* ChocolateyInstall = Top level folder where Chocolatey is installed
* chocolateyPackageName = The name of the package, equivalent to the id in the nuspec (0.9.9+)
* chocolateyPackageVersion = The version of the package, equivalent to the version in the nuspec (0.9.9+)
* chocolateyPackageFolder = The top level location of the package folder

The following are more advanced settings:

* chocolateyPackageParameters = (0.9.8.22+)
* CHOCOLATEY_VERSION = The version of Choco you normally see. Use if you are 'lighting' things up based on choco version. (0.9.9+)
- Otherwise take a dependency on the specific version you need.
* chocolateyForceX86 = If available and set to 'true', then user has requested 32bit version. (0.9.9+)
- Automatically handled in built in Choco functions.
* OS_PLATFORM = Like Windows, OSX, Linux. (0.9.9+)
* OS_VERSION = The version of OS, like 6.1 something something for Windows. (0.9.9+)
* OS_NAME = The reported name of the OS. (0.9.9+)
* IS_PROCESSELEVATED = Is the process elevated? (0.9.9+)

#### Experimental Environment Variables
The following are experimental or use not recommended:

* OS_IS64BIT = This may not return correctly - it may depend on the process the app is running under (0.9.9+)
* CHOCOLATEY_VERSION_PRODUCT = the version of Choco that may match CHOCOLATEY_VERSION but may be different (0.9.9+)
- it's based on git describe
* IS_ADMIN = Is the user an administrator? But doesn't tell you if the process is elevated. (0.9.9+)
* chocolateyInstallOverride = Not for use in package automation scripts. (0.9.9+)
* chocolateyInstallArguments = the installer arguments meant for the native installer. You should use chocolateyPackageParameters intead. (0.9.9+)



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.

This package has no dependencies.

Discussion for the pdftk-server (Install) Package