Should I use the Windows Management Service or the Remote Agent service to publish to the remote server?

Question

I have a remote web server, I have full administrator access, and I want to deploy a website.

When I use the Visual Studio Publishing Tool, among other things that seem a little less convenient (FTP, etc.), I have the option to use either the Windows Management Service or the Remote Agent service. All documentation says the following:

Publish remotely through the Remote Agent, use http: // RemoteComputerName . This option is typically used to deploy network applications within the network (in an intranet scenario). You must have appropriate permissions to perform deployment to the destination server.

To publish on the hosting site using the Windows Management Service, use the value specified by the hosting provider. Usually you can use only the server name (HostedRemoteServer) or the full URL, which includes the server name, port number and the Internet Expand handler name ( https: // HostedRemoteServer: 8172 / MsDeploy.axd ). The hosting provider can tell you the server name and port number, if applicable.

This is not enough information for me to decide. Yes, I do not print over the network, but I have full access to the machine on which I deploy. At the same time, MsDeploy is a big bizarre thing that Scott Hanselman describes in his conversation and that I was convinced that this was a great way to deploy.

So what should I do? Are there any obscure security considerations or something else?

Answer 1

I recommend switching to a management service route. In addition to the msdeploy functions, the management service function enables you to remotely administer IIS 7 / 7.5 from your computer. With all IIS servers in one console, you can easily export the application to one computer and import it to another.

It seems that the most complex implementation of msdeploy is in terms of security and in terms of configuration. IIS Manager makes it easy to configure details around the endpoint (SSL certificate, port, etc.). Well, this is true for IIS 7 / 7.5 on Windows 2008 and R2, but not on Windows Vista or 7. For some strange reason, there is no user interface for managing web sites on non-server SKUs.

An agent is basically a standalone web server without any user level permissions. This is why it requires the person performing the remote deployment to have administrator privileges on the target machine. It looks like a simpler, bare metal implementation. Since you already have IIS serving HTTP / HTTPS, and since the IIS implementation in HTTP has kernel-level optimization, you don’t type anything by sending an agent route.

If you want to remotely administer Windows 2008 or R2 from Windows Vista / 7, install this on your workstation: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=32c54c37-7530-4fc0-bd20- 177a3e5330b7 ... it was icing on a cake for me.