Getting a 404 from WMSvc via MSDeploy.exe

On Windows 2012 R2 Server I followed mga911's advice.

I was stuck getting deploys working. Had installed Web Deploy 3.5 -> Enabled Management Service Delegation -> Ensured Services were started. The problem was the IIS Deployment handler had not been installed. Going through Web PI 4.6 I was not given the opportunity to install the IIS deployment handler. You need to go into the control panel -> Programs and Features Change Web Deploy 3.5's installation. Please note my instructions. In the change process it indicates all the sub packages will be installed but the text message says 0 of 3 sub components will be installed. One of those components is the IIS handler. Read carefully because I didn't and was frustrated :)

• Control Panel > Programs and Features
• Right Click on Microsoft Web Deploy 3.5
  • Select Change > click next > click change
  • You'll notice when Web Deployment Framework is selected you'll see in the message "It has 0 of 3 subfeatures selected"
  • Click on drop down select "Entire feature will be installed on local hard drive"
  • Next > Change >Finish

In case someone else is having the same issues than what I am having, I also got the same 404 error. The quickest way I found to check was to go on the server itself, and open up "https://<servername>:8172/MsDeploy.axd". Chrome & Firefox just showed a blank page, so I had to use the Network tab of the developer tools (F12) to see the actual 404 error message.

Somehow, while installing Web Deploy 3.0 from the Web Platform Installer, the IIS 7 Deployment Handler didn't get installed, even though the IIS Manager UI Module did. In my case, I downloaded the Web Deployment Tool Installation .msi from the following link: Web Deployment Tool Installation. Then I had to go back to IIS Admin Tool (Start -> Run -> inetmgr.exe) > {server name} > click on Management Service icon, and restart the management service before the MsDeploy.axd handler started working.

Enabling IIS Deployment Handler + Remote Agent Service

Have you installed Web Deploy on the server? Web Deploy registers a handler (/msdeploy.axd) with WMSVC, so a 404 would be the expected status code if it weren't installed.