Be cautious while using '-includeusersecurity' in Export/Import Tool

Applicable to MOSS 2007 and SP 2010. 

Just be aware that while using Export and Import commands with '-includeusersecurity' switch to move a SharePoint sub-site from one site collection to another site collection, along with sub-site contents the security groups and its members of entire source site collection will be moved to the target site collection whether the sub-site is having unique permission or not. 

As long as the Source and Destination site collections sharing the same security groups and members, the sub-site migration will not show any impact. 

If it is otherwise, you will notice all the Source Security Groups in the target site collection. 

After the migration, go to Target Home >> Site Permission >> Click on a Group Name >>  then click on 'More Groups' from left menu >> Browse all the groups and you will notice newly added Security Groups originated from Source Site collection.

In general, the newly added Security Groups will stay at top level and will not be visible any sub-sites permission. It will not be a security threat or breach unless you have the exactly same Security Group Names in the Target names before the migration. 

Assume a situation, both source and target using the same user directory (E.g.Active Directory) and a Security Group with identical name but with different members. Then after this migration, Target Security Group is updated members from Source group without the knowledge of the Site Owners. Worst!! 

You will see member names inside newly added security groups as long as source and targets are sharing the same user directory else blank or System account ID. 

You may use the switch '-includeusersecurity' for a sitecollection migration and for other situations (Sub-site/list/library move) use it when it is absolutely necessary.

The PS commands in this discussion..

 Export-SPWeb [-Identity] -Path [-AssignmentCollection ] [-CompressionSize ] [-Confirm []] [-Force ] [-HaltOnError ] [-HaltOnWarning ] [-IncludeUserSecurity ] [-IncludeVersions ] [-ItemUrl ] [-NoFileCompression ] [-NoLogFile ] [-UseSqlSnapshot ] 

 Import-SPWeb [-Identity] -Path [-AssignmentCollection ] [-CompressionSize ] [-Confirm []] [-Force ] [-HaltOnError ] [-HaltOnWarning ] [-IncludeUserSecurity ] [-IncludeVersions ] [-ItemUrl ] [-NoFileCompression ] [-NoLogFile ] [-UseSqlSnapshot ] 

Comments

Post a Comment

Popular posts from this blog

Notes to SharePoint Migration - Part2

Caution :  This series of articles is written for those who already having some acquaintance with Lotus Notes and SharePoint and involved/to be involved in the data migration to SharePoin t . Extract Attachments In some LN applications, response records might hold the attachments where as you need to migrate the contents only to a custom list and not to a discussion board (meaning, you cannot set the relation between parent & children records after migration into SharePoint application). So in the end, you left with migrated main data without the attachments from the response records. User may demand for main data migration along with response record attachments (only). In such case, you may need to work on the LN application to move the attachments of response records to the respective main records well before start of the migration. Here I have included the LN script program to extract the attachments from response records and move to the parent record. Create a new a
Read more

Notes to SharePoint Migration - Part1

Caution : This series of articles is written for those who already having some acquaintance with Lotus Notes and SharePoint and involved/to be involved in the data migration to SharePoin t . The data migration from IBM Lotus Notes to a Microsoft SharePoint application involves detailed analysis of portability between the source and the target. Indeed there are various aspects of migration have to be considered before carry out the real data migration that include feasibility study on the source application, effort estimation of migration, infrastructure flexibility, identification of the friendly tool to facilitate the migration process and so on. For my migration assignment, I have been using  the Quest Notes Migration tool. Please bear in mind that various reference mentioned with respect to the properties of facilitator tool design points to Quest NM and there might little or no change of the design in the other facilitator tools (or may not available at all!!). I like to b
Read more