I am trying to get msdeploy to work from the command line and can successfully test WMSVC directly (using HTTPS, port 8172) with both the local administrator account and the IIS manager user account. Here is the command line:
> msdeploy -verb:dump -source:appHostConfig=MyWebsite,wmsvc=myserver,username=iisuser,password=password -allowuntrusted
So wmsvc = directs msdeploy to use https: // myserver: 8172 / msdeploy.axd . However, since the target host firewall does not allow port 8172, I would really like to use the web interface deployment agent service on port 80. But it answers 401 when I change wmsvc to the computer name:
> msdeploy -verb:dump -source:appHostConfig=MyWebsite,computername=myserver,username=myserver\localadmin,password=password
where computername = directs msdeploy use http: // myserver / MSDEPLOYAGENTSERVICE . In the browser, this URL asks for the username / password and returns a blank page (if it is complete), so it seems to be listening and authenticating properly. In addition, I added full rights to the root of the site for NETWORK SERVICE.
What is the difference in using the web deployment agent service over the standard WMSVC? Thanks in advance!
source
share