Publishing to Azure Virtual Machine with Web Deploy - azure

I am trying to set up Web Deploy on Windows Server 2008 R2, I have installed Web Deploy and Web Management Service.
I know that I'm connecting to the server because I see the following in the log.
2015-06-19 12:13:59 100.72.108.11 HEAD /msdeploy.axd site=IAmAFish 8172 - 86.1.148.102 - 404 7 0 93
However, I'm receiving the standard error about checking that Web Deploy is running.
I suspect permissions are the issue and I'm currently trying to find 'IIS Manager Permssions' in IIS manager, after selecting the site. It's not there. How do I add this feature to IIS manager so that I can manage permissions?

It turns out that the version of Web Deploy installed by Web Platform Installer does not include the full suite of tools and should not be used for this.
Instead, download Web Deploy from:
http://www.iis.net/download/webdeploy
Be sure to restart IIS Manager to see the new icons.

Related

Deploy website to IIS from VS - options aren't present?

I am trying to get web deployment working, but following Microsoft: Publish to IIS
Prerequisites:
Must have VS2019 [yes]
Server is running Windows 2019 DataCenter
Running IIS 10
ASP 2.0, 3.0 and 4.7 installed
Web Deploy 3.6 for Hosting Server installed
Web Account Manager Service running
Web Deployment Agent Service running
Web Management Service Running
IIS Management Scripts and Tools installed
With the above installed, the instruction say to restart the IIS Console and chose Deploy > Configure Web Deploy Publishing from the Default website, but it's not showing (on the Default Site, or my App Services site)
To resolve the close iis manager if it is open.
Go to the "programs and feature".
Select web deploy -> click change.
Enable IIS Manager UI Module, IIS Deployment Handler, and Remote Agent Service.
Click next -> change -> finish.

Azure VM (Not Classic) - Cannot deploy website using Web Deploy from VS 2013

I'm getting a time out error in VS Publish Web module when trying to validate my http connection to our Azure VM. I'm simply looking for a better way for our small dev team to deploy our MVC website to the VM other than publishing to file or publishing to FTP.
I've got Web Deploy on our Windows 2016 server, and the proper
services are running.
Remote Service is installed with Web Deploy.
Port 8172 is open and I am able to connect using Telnet from my
remote box.
I updated the pubxml file with:
<AllowUntrustedCertificate>True</AllowUntrustedCertificate>
<UseMsDeployExe>true</UseMsDeployExe>
<UserName>un</UserName>
<Password>pw</Password>
Not sure what else to try at this point, but this has been a PITA to say the least. Thanks for any input! FYI - This is not Azure Classic.
Screenshot of Error

VS2013 Express Web Deployment: how to configure it on server side

I want to do publish of web-api application from VS2013Express to Windows 7 Professional. When I start publishing, the authentication fails, but my account is administrative one on server machine.
On server: WEb Deploy 3.5 is installed. But I dont see option Deploy - > Configure Web Deploy Publishing on any of my sites.
Where is the problem:)?
PS. I was following this document for Web Deploy installation/configuration:
http://www.iis.net/learn/install/installing-publishing-technologies/installing-and-configuring-web-deploy-on-iis-80-or-later

Web Deploy from Visual Studio 2012 to a remote IIS 8 server

I have a remote Windows 2012 server running IIS 8 from which I am hosting a web application. My local development box is running Visual Studio 2012. Currently I am publishing my app as a web deployment package (.zip), RDP'ing to the production server, copy + pasting to a folder and deploying the application from within IIS. My question is, what changes do I need to make to deploy directly to IIS from Visual Studio 2012 using the web deploy option?
I have tried to follow this guide but it refers to a service URL which I must obtain from my hosting company. I don't have a hosting company, my server is co-located.
I am presented with the following options:
Is the username and password the one I use for the RDP account? I already have Web Deploy 3.0 installed on IIS do I need to enable further settings?
OK I found the solution but it took me a whole day to get it working! Basically the steps are as follows. This is very sketchy but see the detailed guides below which helped me.
Enable the IIS Web Management role feature.
Install Web Deploy 3.0 (or higher). Make sure to customise the install to include the handlers (See notes below). If you're not presented with this option go to add/remove programs, find webdeploy, right click and select "change" option.
In IIS click on the server node and find the "Management Service" icon. Enable remote access and configure a dedicated IIS User for remote deployment (These will be the credentials that will go in the user name and password boxes).
At the site level in IIS assign this user to manage the website.
Make sure port 8172 is open on the web server (you can check this port here).
Try reconnecting from Visual Studio. There was some trial and error here for me but the error messages do link to a MS guide for decoding :)
Even after connecting successfully I had to wrangle with permissions, so my IIS user had sufficient privileges to create the app pool, directories and general file management jobs.
The following links really helped!
Configuring the handler on the web server:
http://www.iis.net/learn/publish/using-web-deploy/configure-the-web-deployment-handler
Connecting via Visual Studio:
http://msdn.microsoft.com/en-us/library/dd465337(v=vs.110).aspx
NOTES:
To ensure the handler is running, login into your IIS server and point your browser to the following URL.
https://<servername>:8172/MsDeploy.axd
F12 to open up the dev tools to see the HTTP response. Also MsDeploy also creates IIS logs in inetpub/logs which should give you some clue if you're having connectivity problems.
I had the same problem and this post was very useful to help me solve the issue. I had anyhow serious troubles while trying to install Web Deploy on my Windows Server 2012. The installation of Web Deploy 3.0 was giving me several errors and it couldn't be completed.
I tried to solve the problem installing "Microsoft Web Platform Installer 5.0" from http://www.microsoft.com/web/downloads/platform.aspx but it didn't solve it.
I thought it was due to Firewall Settings, Authorizations issues, Users without permissions or something like that. Finally I found out it wasn't due to any of the mentioned reasons.
I found the most simple solution and I hope it will help other users too: it was enough to download Web Deploy 3.5 installation directly from Microsoft Website:
http://www.microsoft.com/en-us/download/details.aspx?id=39277
This may sound banal but it solved it. I was able to install "Web Management Service" but not the second needed IIS service "Web Deployment Agent Service".

Disparity in options available in Web Deploy 2.0 on two matching servers

IIS 7.5 is installed on two servers (both Windows Server 2008 R2) with Web Deploy 2.0 installed (to enable me to Publish from Visual Studio 2010.) Publishing straight from VS requires the Web Management Service be running on the server. I've been publishing to the first server for months, no problem. The second server has just been spun up (not by me) but as far as I can tell has all the same versions of components (OS, IIS, Web Deploy). However, on the second server the Web Management Service isn't installed. There's a key difference:
Web Deploy 2.0 options available on the first server:
Web Deploy 2.0 options available on the second server:
Why is there a difference between the two?
(Follow-up: I tried the Web Deploy 3.0 installer and encountered the exact same dialog as the second server, above, except that it said "3.0" instead of "2.0".)
Verify the proper IIS roles are installed on your new server. In the Server Manager console, under Web Server (IIS), verify the following roles are installed:
Management Tools
IIS Management Console
IIS Management Scripts and Tools
Management Service
Then try re-running your Web Deploy installer. I think you'll find you get the options you desire.

Resources