Most people assume they need to install WebDeploy and the Agent Service on all their application servers to use WebDeploy but that is not always the case.
First, not all deployments require the Agent Service. For example, the dirPath provider can deploy files to a remote server without using the agent. It simply uses network file access to deploy the files. We have used this provider to deploy SSIS packages, Window Services and random file share changes using the AppDeploy Nuget package. The following blog post provides an example of this process:
The agent service is needed for deployments to IIS using the iisApp provider for example. That doesn’t mean you have to preinstall WebDeploy though.
WebDeploy supports a tempAgent feature which will install the WebDeploy agent temporarily to support your deployment and then remove the agent. This requires administrator level access and WMI to be enabled but is a great option if you want to avoid WebDeploy installation on your servers.
There are several options for how the tempAgent can be used. Read the following documentation for more details –