Administer Quick Deploy jobs
Updated: September 5, 2008
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: 2008-09-02
A Quick Deploy job provides a way for users such as authors and editors to quickly deploy content. In order for users to use the Quick Deploy feature, the publishing features must be enabled for either the site collection or the site, and the user must be a member of the Quick Deploy users group. For more information, see Enable publishing features.
Before a Quick Deploy job can be run, you must first create a new content deployment path. Content deployment paths specify a source and destination for content deployment and other related settings. For information about creating a new content deployment path, see Administer content deployment paths and jobs.
A Quick Deploy job is created automatically when a new content deployment path is created. Although a Quick Deploy job is created automatically, the job itself is not active until a farm administrator enables Quick Deploy jobs along a specific path. After the Quick Deploy job has been enabled, the farm administrator can then modify the settings for the Quick Deploy job, including the job schedule and notifications for the job. By default, a Quick Deploy job runs automatically every 15 minutes. When a user sets content for Quick Deployment, that content will be included in the next automatically scheduled Quick Deploy job. Alternatively, a farm administrator can manually run or cancel a Quick Deploy job at any time by using the Manage Content Deployment Paths and Jobs page, which is accessed from the Operations tab in Central Administration.
|If content is scheduled to be published at a specific date and time, the Quick Deploy job will copy that content to the destination location along with any other items contained in the job. The content itself will be copied to the destination location according to the publishing schedule associated with that content.|