Using Web Deploy Remotely
Applies To: Windows 7, Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Vista, Windows XP
There are three main ways in which you can use the power of the Web Deployment Tool remotely: the Web Deployment Agent Service (MsDepSvc), also called the "remote agent service"; the Web Management Service (WMSvc), also called the Web Deploy "handler"; and the tempAgent provider setting feature, also called Web Deploy "on demand."
The Web Deployment Agent Service
The Web Deployment Agent service can be used only by administrators and requires that Web Deploy be installed. The remote agent service is not installed by default, but you can choose to do so when you install the Web Deployment Tool. For more information, see Web Deploy Remote Service.
The Web Management Service (WMSvc) Handler
The Web Deploy handler uses the Web Management Service (WMSvc) to allow non-administrative users to access the sites and applications to which they have been delegated access by using a URL argument with the computerName provider setting (for example, computername=https://serverName/agent.mwd?Site=Site1). The handler is useful in Web hosting and in enterprises where the users who publish to the Web are not server administrators. For more information, see Configuring the Web Deployment Handler.
Note
You cannot configure the Web Management Service in Windows Vista® or Windows® 7.
Web Deploy "On Demand"
The Web Deploy tempAgent feature provides administrators with a way of synchronizing computers without having to install Web Deploy or the remote service. This feature requires the use of WMI and administrative shares. In this usage, Web Deploy can be run from any network share or local computer folder that has the Web Deploy program files. The Web Deploy tempAgent copies temporary program binaries to the admin shares on the remote computer, performs an operation, and then removes the binaries after the operation has completed. For more information, see Web Deploy On Demand.
In This Section
Configuring the Web Deployment Handler