Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

Web Deploy auto Provider

Updated: March 12, 2009

Applies To: Windows 7, Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Vista, Windows XP


The auto provider specifies that the provider on a destination will be the same as the source provider.


msdeploy.exe -verb:sync -source:appHostConfig="MySite" -dest:auto,computername=Server1

The auto provider enables you to avoid entering the full path for the -dest argument when the destination argument is the same as the -source argument. It also removes the need to copy the manifest file separately from an archive or package.

In a sync operation, use the auto provider to specify the destination. For example, to synchronize a source to the exact same corresponding location on a target computer, specify the destination by using the syntax -dest:auto.

How the auto provider works

The auto provider takes the source that you specify and uses a corresponding location on the destination computer. For example, if you specify appHostConfig=Site1 as the source, the destination on the target computer will be Site1. This is useful when you want to synchronize a Web site "as is" to a remote machine.

The following examples show how to use the auto provider in a variety of scenarios.

1) Synchronize an appHostConfig provider to the same site name on a different server.

msdeploy.exe -verb:sync -source:appHostConfig="contoso.com/fabrikam" -dest:auto,computername=Server1

2) Synchronize a manifest to a package, and then from the package to auto.

msdeploy.exe -verb:sync -source:manifest=custom.xml -dest:package=myapp.zip

msdeploy.exe -verb:sync -source:package=myapp.zip -dest:auto

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

© 2015 Microsoft