I use MSDeploy for deploying asp.net sites to servers with IIS. I also use MSDeploy for deploying Windows Services to the same servers that have IIS.
My MSDeploy agents listen on https://computername:8172/MSDEPLOYAGENTSERVICE
I'm evaluating if it's feasible to deploy a Windows Service to a machine that does not have IIS installed.
Does the MSDeploy agent require IIS or can the agent run without it?
I have tested this in my own environment. MSDeploy can be installed without IIS. It works for deploying Windows Services to a machine that does not have IIS on it.
Related
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.
If I shut down the application pool of the site in IIS 7.5 first, can I still use MSDeploy to deploy web code to this site?
The basic command is to execute C:\Program Files\IIS\Microsoft Web Deploy\msdeploy.exe -source:package='......zip' -dest:auto,includeAcls='False' locally on the web server.
Yes, you can still deploy a site with MSDeploy if the AppPool is stopped.
How to create publishing profile for a website running on azure virtual machine?
I know how to do it for Azure Web Site, but can this be done if I have IIS running on a VM in azure?
I also have a console application running using task scheduler on this VM, it would be nice to automate that deployment too.
( After working with Rails and Php frameworks, I miss the common config file used by the website and CronJob to connect to the DB)
You need to set up Webdeploy in the azure VM. it is same as an on-premises server.
Web Deploy Installation.. You need to install prerequisites - .net framework.
Configuring IIS 7 with webdeploy / Or with IIS8
Set up endpoints on azure vm to do webdeploy. Port 8172 for Webdeploy.
Then you can create a publish profile in Visual Studio 2012/13 to deploy to this endpoint.
http://msdn.microsoft.com/en-us/library/dd465337(v=vs.110).aspx
or You can do it using Powershell scripts.
sample-
http://gallery.technet.microsoft.com/scriptcenter/Deploy-a-Web-App-to-Two-99f1a3bc
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.
The IIS Debug Diagnostics Tool installs the IISCrashHangAgent. What service is hosting the agent?
IIS Crash/Hang Agent is an obsolete tool, which still is available here
http://www.microsoft.com/downloads/details.aspx?familyid=01c4f89d-cc68-42ba-98d2-0c580437efcf&displaylang=en
But to debug IIS problems, now you should use DebugDiag
http://www.microsoft.com/DOWNLOADS/details.aspx?FamilyID=28bd5941-c458-46f1-b24d-f60151d875a3&displaylang=en