Chat now with support
Chat with Support

Metalogix ControlPoint 8.2 - User Guide

Preface Getting Started with ControlPoint Using Discovery to Collect Information for the ControlPoint Database Cache Searching for SharePoint Sites Managing SharePoint Objects
Accessing SharePoint Pages Viewing Properties of an Object within the SharePoint Hierarchy Creating Dashboards for Monitoring Statistics within Your SharePoint Farm Setting Object Properties Managing Site Collection and Site Features Managing Audit Settings Creating and Managing SharePoint Alerts Setting ControlPoint Alerts Managing Metadata Copying and Moving SharePoint Objects (Version 8.0 and Earlier) Moving a Site Collection to Another Content Database Deleting Sites Deleting Lists Archiving Audit Log Data Before Moving or Deleting a Site Collection Duplicating a Workflow Definition from one List or Site to Others Removing a Workflow from One or More Lists (or Sites)
Using ControlPoint Policies to Control Your SharePoint Environment Managing SharePoint User Permissions Data Analysis and Reporting
Specifying Parameters for Your Analysis Analysis Results Display Generating a SharePoint Summary Report Analyzing Activity Analyzing Object Properties Analyzing Storage Analyzing Content Generating a SharePoint Hierarchy Report Analyzing Trends Auditing Activities and Changes in Your SharePoint Environment Analyzing SharePoint Alerts Analyzing ControlPoint Policies Analyzing Users and Permissions The ControlPoint Task Audit Viewing Logged Errors
Scheduling a ControlPoint Operation Saving, Modifying and Executing Instructions for a ControlPoint Operation Using the ControlPoint Governance Policy Manager (SharePoint 2010 and Later) Using Sensitive Content Manager to Analyze SharePoint Content for Compliance Using ControlPoint Sentinel to Detect Anomalous Activity Default Menu Options for ControlPoint Users About Us

What a Copy or Move Does Not Do

ControlPoint copy and move site actions:

·are not backup and restore tools

·do not support ongoing synchronization or replication between two active sites

·do not perform a bit-for-bit copy of a site collection or site

·do not allow you to copy/move an entire farm or Web application or more than one site collection, site, or list

·do not copy application elements, including alerts, features, solutions, custom event handlers, recycle bin state, or any of the code necessary to support Web Parts.  Workflows can be copied only if your ControlPoint license includes Content Matrix functionality.

·at the site collection and site level, do not allow you to select which items within a list or library you want copy/move (that is, when you copy or move a list or library, all items are carried over).  

NOTE:  You can use a separate ControlPoint action for copying/moving individual items or folders from one list another.  See Copying and Moving List Items.

·do not copy site definitions (which are often referred to as site templates).  Site definitions must be installed on the destination system.

TIP:  The site definition is a combination of the fields Web Template and Web Template ID (often written as Template#ID, as in STS#1).  This information can be found in the ControlPoint Properties window for a site.


Permissions Required to Perform a Copy/Move

When ControlPoint default security trimming is in effect, you must either be a site collection administrator or have Full Control permissions in the Web application policy at both the source and destination location to perform a copy/move operation.

If the operation will result in the creation of a new site collection, you must be a farm administrator at the destination.


How Content is Handled When Copied or Moved

Different site templates can cause different behaviors when a new site is created.  The descriptions below provide some general guidelines for what you may expect.

Lists and Libraries -

·When copying or moving a site collection or site, default lists and libraries are always created on the destination site, regardless of whether you choose to carry over content.

·If you do choose to carry over site content:

§lists and libraries are carried over to the destination, including all documents, list items, and folders.  

§the contents of default lists and libraries at the destination are replaced by the contents of default lists and libraries on the source

§all versions of documents stored in the site are carried over.

Web Parts - A Web Part itself (that is, the installed code) is not copied.  Web Parts placed onto pages are normally copied if they are installed on the destination system, although this behavior may vary with the specific implementation of the Web Part.

Features -  As with Web Parts, installed code is not copied. If a site has a feature activated and the feature has not been installed on the destination farm, the copy will fail.  As a preventative measure, you may deactivate the feature on the source site collection/site or install it on the destination farm before performing the copy/move.

Content Types (which may include document templates and custom event handler definitions) -  

·If a list within a site references a content type defined at that site, the document template aspects of the site-level content will be copied with the site as a site-level content type.

·If a list within a site references a content type from a parent site or site collection, the document template aspects of the parent-level content type will be copied as a list-level content type.  This means that the field-level design of the list (and items in the list) will not change but any sharing/inheritance of a common content type definition will be lost.

·Event handlers are not carried over.

Columns -

·List-level columns are copied without complication.

·If a site-level column was defined in the site being copied/moved, it will become a site column in the destination location.

NOTE:  If the site being copied/moved is to become a child site at the destination location and the destination parent site has a site-level column definition with the same name, an error will occur during the import to the destination site.

·If a site-level column was defined in the parent of the site being copied/moved, it will become a list-level column in the destination location. The behavior of the column will be the same but any inheritance will be lost.

Urls - Urls that are internal to the site collection or site and which are managed by SharePoint will be "fixed up."  These include

·top link bar tabs

·Quick Launch, and

·in general, links that were placed in a Link List.

Links that are not fixed up include:

·those placed directly onto any custom page or custom list, and

·any inbound links from outside the site or list being copied or moved.


You can choose whether or not to copy/move workflows from the source to the destination.  If you choose this option:

·The operation will include definitions of SharePoint "out-of-the-box" workflows and workflows created in SharePoint Designer.  

·The operation will not include:

§running instances of workflows

§workflow history

§workflows created using a third party product

Miscellaneous - (Navigation Settings, Object IDs, and Version History)

·You can choose whether to include navigation settings at the ControlPoint interface.

·The copy/move operation creates an entirely new copy of the source, with new Item IDs for all SharePoint objects.

NOTE:  If you are running SharePoint Server 2010 or later and the Document ID Service is enabled, Document IDs will be retained as long as you are moving within the same site collection and the source objects are deleted immediately. (A Document ID cannot be used for more than one item within a site collection.)  A Document ID can be used to find the document in the new location after the Search Service has indexed it.


How Security Settings are Handled at the Copy/Move Destination

The following guidelines apply only if you are copying/moving between Web applications that use the same authentication method (Windows or Claims). If you are copying/moving between Claims-enabled and non-Claims-enabled Web applications, you cannot carry over security settings.

General Guidelines

The following table describes how security settings are handled at the copy/move destination depending on the option you choose.

If you choose to ...

Then ...

And, the account used to perform the copy/move ...

carry security settings from the source to the destination

NOTE:  This option is not available for sites that have inherited permissions.

·the security in the destination will be the same as that of the source


·groups and group members in the source site collection will be copied and any default groups specified by the template will be created, regardless of whether the sites and subsites where the groups were defined are copied (since groups are actually maintained at the site collection level)

NOTE:  If you are copying or moving a library or list which has (or whose items have) unique permissions, a user group and its members will be carried over only if the group does not already exist on the destination site.

·for most site types, will be granted Full Control permission to the site in the destination location, and

·depending on the template, will be added to some SharePoint user groups.


If the destination is a site collection, the account will also be added to the Site Collection Administrators list.


not carry security settings from the source to the destination

·all child sites, lists, libraries, and folders will inherit permissions from their parent in the destination location, even if they had unique permissions in the source location


·groups defined for the template are created and assigned default permissions defined by the template

Be aware that there may be significant security implications involved in this change.

·if the destination is a site collection:

§will be added to all groups except Visitors. Members, and Owners for Publishing sites

§will be added to all groups except Visitors and Members for other site types

·will be added to the Site Collection Administrator's list, and

·will be given Full Control permissions to the root site.

Additional Security Considerations for Sites that are Promoted/Demoted

If you want to ...

Then ...

"demote" a site collection so it becomes a site in the destination location

if security is carried over:

·groups from the source site collection will be added to the destination site collection, and

·if duplicate names exist, membership will be merged.

"promote" a site so that it becomes a site collection in the destination location

·most (but not all) groups and lists that are defined on the template of the source site will be created on the destination site, and

·if security is carried over, members of the group will come from the source site.

How Orphan Users are Handled

If a user who has been granted permissions in the source site is no longer in Active Directory (that is, is an "orphan"), those permissions will be copied to the destination location, so that they can be reassigned.

EXCEPTION:  If an orphaned user is a member of the Site Administrator's group in the source location, that permission will not be carried over to the destination.


Related Documents