Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

We had to restore a list (which has versionsing enabled) in our PROD enviornment SP 2010 August CU 2012. We used the following command metioned below:

Import-SPWeb http://example.com/projects/myList -path "E:\backups\myList\myList.cmp" -IncludeUserSecurity -UpdateVersions overwrite

The list was restored, however the users that did not exist in the organisation any longer were replaced with the user who performed the restore.

This is odd because we userd the correct flag as per the technet article Import-SPWeb. What's the point of having versioning if we loose the details?

Has anyone else faced this issue?

share|improve this question
1  
Was the -IncludeUserSecurity flag used during export? –  Jesus Shelby Apr 10 '13 at 4:02
    
Yes it was. We used CA unattach database restore a list option and include user security and all versions –  MicrosoftDevX Apr 10 '13 at 4:24

1 Answer 1

If the user no longer exists the info about the user is lost during the restore.

It is very similar to this situation: you want to create new item and there is a lookup field. You can only select existing values. That is what happens during import - the items are "recreated" and when the user is not found the "dummy" value is added. In this case the username who runs the restore.

The flag IncludeUserSecurity is for user permissions, not to include non-existing users.

Try to check ShareGate tool specifications, they might be successful in solving this problem.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.