SharePoint Content Deployment Wizard 2.8 Beta
A tool for SharePoint that provides the means to deploy the following content
Usage notes:- The tool must be installed locally on the server which hosts the site
- Site URL - enter using format http://source.test.dev- Import web URL - enter using format http://target.com/targetweb
Import / Export characteristics:Since the Content Migration API is used, imports/exports have the following characteristics:- dependencies of selected content (e.g. referenced CSS files, master pages) are automatically included in the export - check 'Exclude dependencies of selected objects'
to disable this- all required content types, columns etc. are automatically included in the export- in contrast to STSADM export, it is possible to retain GUIDs during deployment (where objects are not being reparented) - check 'Retain object IDs and locations' to enable this- no filesystem files (assemblies, SharePoint Solutions/Features etc.) are deployed - these must already be present on the target for the import to succeed)- the following content does not get captured by the Content Migration API - alerts, audit trail, change log history, recycle-bin items, workflow tasks/state Reparenting:Reparenting of objects such as webs and lists is possible with the following usage on the import:- enter the URL for the target web in the 'Import web URL' textbox- ensure 'Retain object IDs and locations' is not checked Permissions:The Content Migration API (PRIME) is used to package the content as a .cmp file, which can be copied to another server for import. The application MUST be run from the SharePoint server(s), and MUST be run under the context of an account which has appropriate SharePoint permissions - currently the way to specify an alternative user to the currently-logged on user is by using the 'Run as..' feature in Windows 2003 (right-click on the .exe and select 'Run as..').
SharePoint Content Deployment Wizard
In a hurry? Add it to your Download Basket!
What's New in This Release:
- Fixes a common bug introduced in the last version (2.7). It took me some time to realize, but this happened very frequently and if you used 2.7 often you may well have seen this issue - apologies.
- Improves install experience on SharePoint 2010 (yes, this tool does support SP2010).