As usual, it takes quite a bit of effort to get web deploy working properly on IIS 8.
Personally, I find the following articles more useful:
Here is my recommended checklist:
- Windows Server 2012 already has .NET 4.0 on it, so you don’t need to install it.
- Run Web Platform Installer and Add/Install the following:
- IIS: Management Service
- IIS: Basic Authentication
- Web Deploy 3.5
- Make sure your Web Deploy also has IIS Deployment Handler (and sub features) installed. That was missing for me.
- On IIS 8, enable “Basic Authentication” on the server level.
- On IIS 8, Management Service. Enable remote connections and start Web Management Service.
- Make sure Web Management Service has “Automatic” startup in Services.
- Make sure the Windows Firewall allows inbound port 8172 for the Web Management Service.
- Make sure Azure or AWS or 3rd party firewall allows inbound 8172.
In my case, I was encountered something like the following:
Could not connect to the destination computer (“deployserver”). On the destination computer, make sure that Web Deploy is installed and that the required process (“The Web Management Service”) is started.
The remote server returned an error: (404) Not Found.
Web Deploy was installed. However, IIS Deployment Handler was never installed.
- Control Panel –> Program and Features
- Microsoft Web Deploy 3.5 –> Change –> Change
- Make sure IIS Deployment Handler and sub features are installed.