Web Deploy 3.6 – Fixing the Proxy Server Issue

  Download version 3.6 from here: http://www.microsoft.com/en-us/download/details.aspx?id=43717 The newest version of Web Deploy (3.6) offers support for the user’s proxy server set within the browser. By default, Web Deploy 3.5 and below will ignore the proxy settings and use either port 8172 or 80 depending on the type of Web Deploy publishing activity. Thus, if…

0

Publishing to DMZ Server using Web Deploy Agent Service

  There are several options to configure Web Deploy for deployments to servers located in a DMZ, or a non-trusted domain environment. The Web Deploy Agent service is the easiest to configure and troubleshoot and preferred method if you have login rights to the IIS server. Meaning, you can RDP into the server and open…

0

How to Recycle Application Pool on Remote Server

  I work with several customers that release highly anticipated information on the web sites on specific days of the month and anticipation of the load, some of the customers recycle the application pool for the application to start out with a minimal memory footprint. In order to recycle the application pools, the customers were…

4

Quickly Generate XML List of Web Site’s Configuration

  The Web Deployment utility allows the administrator to quickly generate a list of configuration details about the web site in a readable format. This is helpful in situations of troubleshooting a web sites behavior by quickly seeing most of the configuration for the site in an easy readable format. The dump command is used…

3

How to Create Copy of Web Site on Same Server or Remote Server using Web Deploy

  Continuing with the different uses of Web Deploy to help with the management of the web site environment is the method to create an exact copy of the web site on the same server, or a remote server, with a Web Deployment script. This method differs from the typical manual method by automatically creating…

1

Using a 64-bit source and a 32-bit destination Error in Web Deploy

  Error Situation: When issuing the following Web Deploy statement: C:\Program Files (x86)\IIS\Microsoft Web Deploy V3>msdeploy -verb:sync -source:metakey=lm/w3svc/1,computername=10.0.0.10 -dest:metakey=lm/w3svc/1 -enableLink:appPool > msdeploy.log -verbose generates this error message: Microsoft.Web.Deployment.DeploymentException: Using a 64-bit source and a 32-bit destination with provider metaKey is not supported. at Microsoft.Web.Deployment.IISConfigFrom64To32RuleHandler.Check64To32… Cause: Using the x86 version of Web Deploy or the source…

0

Updated-Backup Strategies with Web Deploy

  Before running the Web Deploy commands to update a web site, make sure to create a backup of the target web files in case a rollback of the operation is required. The process to make a backup on the target server is quick and I would recommend adding these steps to any scripts used…

4

IIS Server and Site Comparison with Web Deploy

  This post is leveraging the information in this post http://blogs.iis.net/msdeploy/archive/2008/02/02/using-ms-deploy-to-compare-sites-or-see-what-components-your-site-uses.aspx  Housekeeping: Source server = Server sending the web files Target server = Server receiving the files (new server) For these examples, the Source server IP is 10.0.0.11 and the Target server is 10.0.0.12. IIS Configuration: Customers not using Shared Configuration feature in IIS can…

0

Migration from IIS 6 to IIS 7.x – 8.x

  I have completed numerous migrations for customers and the majority of the time is spent troubleshooting the migrated web applications on the new IIS platform. The migration process with Web Deploy is very quick and the testing and mitigation of the migrated applications will consume the bulk of the time spent on the project….

13

Using the Correct Version of Web Deploy

  If you have encountered the error Using a 64-bit source and a 32-bit destination with provider is not supported:   This is due to a package created on a 64-bit system (source) using a 64-bit version of Web Deploy and attempting to deploy the package on a 64-bit system (target) with the 32-bit version…

0