Administer content deployment paths and jobs

Applies To: Office SharePoint Server 2007

This Office product will reach end of support on October 10, 2017. To stay supported, you will need to upgrade. For more information, see , Resources to help you upgrade your Office 2007 servers and clients.


Topic Last Modified: 2016-11-14

A content deployment path creates a connection between a source site collection and a destination site collection. That connection is then used to publish content from the source to the destination. These site collections can be in the same farms, or in separate farms.


The destination site collection can be created using the Blank Site template in the Central Administration Web site, or by creating an empty site without specifying a template using the Stsadm command-line tool. For information about using the createsite operation to create an empty site collection, see Createsite: Stsadm operation.

You use a content deployment job to schedule moving content along a content deployment path. You can create a job to run on a schedule you specify, and you can customize the frequency with which the job runs to best suit your content publishing requirements. When running a content deployment job, consider the following:

  • Do not allow authors to change content on the source site collection while a content deployment job is running. Consider either running hourly incremental deployments for each site collection and let the automatic job retry option handle any problems caused by authoring while deployment jobs are running, or scheduling content deployment jobs during off-peak hours.

  • Do not run content deployment jobs in parallel if the same site collection or site is used by both jobs.


Content deployment is a one-way process: content is copied from a source site collection to a destination site collection. The content deployment feature does not support round-trip synchronization from source to destination and back again. Creating new content or changing existing content on the destination site collection can cause content deployment jobs to fail. Because of this, you should consider restricting permissions on the destination site collection so that users cannot make changes directly to content stored within that site collection.

When you create a content deployment job, you can configure the job to copy the entire source site collection, or only a subset of sites. When you deploy a site, every item contained in the site is deployed. If any of these items depend on something that is defined at the site collection level or that is external to the site, deployment will not work. You must either deploy the whole site collection or write a custom tool to export the content to be deployed.

You can also specify whether the job only deploys new, changed, or deleted content, or have the job deploy all content, including content that was previously deployed in other jobs.


A Quick Deploy job enables content owners to quickly publish content independently of any scheduled jobs. For more information, see Administer Quick Deploy jobs.

For information about planning content deployment and more information about paths, jobs, and permissions, see Plan content deployment.

Task Requirements

To administer content deployment paths and jobs, perform the following procedures in the order listed:

After you have configured a content deployment path and job, you can perform the following procedures in any order:

After a content deployment job has successfully run for the first time, you can perform the following additional procedures in any order: