Downloads of v 3.6.20170627:


Last Update:

27 Jun 2017

Package Maintainer(s):

Software Author(s):

  • Microsoft


microsoft web deploy iis server admin

Web Deployment Tool

  • 1
  • 2
  • 3

3.6.20170627 | Updated: 27 Jun 2017



Downloads of v 3.6.20170627:


Software Author(s):

  • Microsoft

  • 1
  • 2
  • 3
Web Deployment Tool 3.6.20170627

  • 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


To install Web Deployment Tool, run the following command from the command line or from PowerShell:


To upgrade Web Deployment Tool, run the following command from the command line or from PowerShell:


To uninstall Web Deployment Tool, 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 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. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade webdeploy -y --source="'STEP 3 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 webdeploy -y --source="'STEP 3 URL'"

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

Exit $exitCode

- name: Ensure webdeploy installed
    name: webdeploy
    state: present
    version: 3.6.20170627
    source: STEP 3 URL

See docs at

chocolatey_package 'webdeploy' do
  action    :install
  version  '3.6.20170627'
  source   'STEP 3 URL'

See docs at

    Name: webdeploy,
    Version: 3.6.20170627,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller webdeploy
   Name     = 'webdeploy'
   Ensure   = 'Present'
   Version  = '3.6.20170627'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'webdeploy':
  provider => 'chocolatey',
  ensure   => '3.6.20170627',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install webdeploy version="3.6.20170627" source="STEP 3 URL"

See docs at

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 flcdrg on 06 Jul 2017.


Microsoft Web Deploy


The Web Deployment Tool simplifies the migration, management and deployment of IIS Web servers, Web applications and Web sites. Administrators can use command-line scripting with the Web Deployment Tool to synchronize IIS 6.0, IIS 7.0 and IIS 8.0 servers or to migrate an IIS 6.0 and IIS 7.0 servers to IIS 8.0. The Web Deployment Tool also enables administrators and delegated users to use IIS Manager to deploy ASP.NET and PHP applications to an IIS 7.0 and later servers.
Migrate Web applications between IIS 6.0, IIS 7.0 and IIS8.0 with ease
Simplify the planning of your IIS 7.0 to IIS 8.0 migrations by determining incompatibilities and previewing the proposed changes before starting the process. Learning about any potential issues in advance gives you the chance to take corrective measures and simplifies migration.
Synchronize your server farm efficiently
The Web Deployment Tool allows you to efficiently synchronize sites, applications or servers across your IIS 8.0 server farm by detecting differences between the source and destination content and transferring only those changes which need synchronization. The tool simplifies the synchronization process by automatically determining the configuration, content, databases and certificates to be synchronized for a specific site. In addition to the default behavior, you still have the option to specify additional providers for the synchronization, including COM, GAC and registry settings.
Package, archive and deploy Web applications more easily
The Web Deployment Tool enables you to package configuration and content of your installed Web applications, including SQL and MySQL databases, and use the packages for storage or redeployment. These packages can be deployed using IIS Manager without requiring administrative privileges. The tool also integrates with Visual Studio and WebMatrix to help developers streamline the deployment of Web applications to the Web server.


  • Install and uninstall via Chocolatey
  • Supports 32/64-bit version


2017-06-27 Build 3.6.20170627

2017-04-19 Build 3.6



choco install webdeploy -y

YAML (The Foreman puppelabs/chocolatey module)

  ensure: latest
  uninstall_options: "--force --all-versions"
  provider: chocolatey


  ensure: latest


$ErrorActionPreference = 'Stop';

$packageName        = 'webdeploy'
$scriptPath         = $(Split-Path $MyInvocation.MyCommand.Path)
$url_local          = ""
$url_remote         = ""
$url_local64        = ""
$url_remote64       = ""
$url_local_trans    = ""
$url_remote_trans   = ""
$url                = ""
$url_trans          = ""
$checksum           = "5a2176f4571948b362396b6c80ebf8404a9c8ab6cb91fb778ea065c65a666561"
$checksum64         = "721d9c3b8416518c0bb8a440e9d70ea927da151b9c3d428a1b04e49cffcdc484"
$logfile            = "$env:TEMP\chocolatey\$($packageName)\$($packageName).MsiInstall.log"
$logdir             = "$env:TEMP\chocolatey\$($packageName)"
$killexec           = 0
$killexecprocess    = ""
# Let's check if should we use local or remote install source
$statusCode = Test-Path $url_local
if ($statusCode) {
    else {
# Someone has won ;)

#Let's check your TEMP derectory

$statusCode = Test-Path $logdir
if ($statusCode) {

    else {


$packageArgs = @{
  packageName   = $packageName
  fileType      = 'msi'
  silentArgs    = "/qn /norestart ADDLOCAL=ALL"
  validExitCodes= @(0, 3010, 1603, 1641)
  url           = $url
  url64bit      = $url_remote64
  checksumType  = 'sha256'
  checksumType64= 'sha256'
  checksum      = $checksum
  checksum64    = $checksum64

# Should we kill some exec ?
if ($killexec) {
  Stop-Process -processname $killexecprocess -force

  Install-ChocolateyPackage @packageArgs


$ErrorActionPreference = 'Stop';

$packageName = 'webdeploy'
$softwareName = 'Microsoft Web Deploy*'
$installerType = 'MSI'
$silentArgs = '/qn /norestart'
$validExitCodes = @(0, 3010, 1605, 1614, 1641)
if ($installerType -ne 'MSI') {
  $validExitCodes = @(0)

$uninstalled = $false
[array]$key = Get-UninstallRegistryKey -SoftwareName $softwareName

if ($key.Count -eq 1) {
  $key | ForEach-Object {
    $file = "$($_.UninstallString)"

    if ($installerType -eq 'MSI') {
      $silentArgs = "$($_.PSChildName) $silentArgs"

      $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."
  Write-Warning "Please alert package maintainer the following keys were matched:"
  $key | ForEach-Object {Write-Warning "- $_.DisplayName"}

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.

Version Downloads Last Updated Status
Web Deployment Tool 3.6.0 86051 Wednesday, April 19, 2017 Approved
Web Deploy 3.5.2 206664 Friday, May 16, 2014 Unknown
Web Deploy 3.5.1 448 Tuesday, May 6, 2014 Unknown
Web Deploy 3.5 3.5 1984 Monday, May 5, 2014 Unknown

This package has no dependencies.

Discussion for the Web Deployment Tool Package

Ground Rules:

  • This discussion is only about Web Deployment Tool and the Web Deployment Tool 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 Web Deployment Tool, 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