-
Titre
Created By and Modified By metadata is not preserved -
Description
The Created By and Modified By metadata is not preserved when migrating documents or items.
-
Cause
This issue usually occurs since the tool does not know which user corresponds to the same user in the target environment. In order to handle this situation, a user mapping file is loaded during the copy process.
Other possibilities for this behavior include the user being disabled, blocked or not present in the target. The user must be available to be set in the target.
-
Résolution
User/Group Mapping
This option will allow you to map users and groups between different domains or to change the user account in the target environment during copy. This is highly useful when moving between domains or encountering users who have been deleted or disabled.
When a user cannot be created in the target environment, Essentials, by default, will replace that user account with the account of the user executing the operation. You may override this behavior by updating the Default User Login field in Help > Profile Manager > Global Variables.Account Mapping
- Generate a Site Users report for the source and target sites by right-clicking on the site or site collection, then selecting Reports> Site Users Report (csv).
- Open both user reports in Microsoft Excel and populate the first column with the source account, then copy the new account from the target report and paste it into the second column.
- Save the file in a .csv format and load it when copying items, a list or a site to perform this transformation.
NOTE: If the account IDs are the same, but the domain is different between the source and target SharePoint, you can add a wildcard domain remapping to the existing user mapping file.
In addition to the specified user mapping, all the domain prefixes will be mapped to ‘ACME-WEST’ during the operation. This function is extremely helpful if you have a large number of users with the same IDs between different source and target domains.
If you are migrating into or out of SharePoint 2013 or Office 365, you may see something like the following in the Site Users report:
i:0#.w|domain\USERNAME i:0#.f|membership|USERNAME@domain.com
If so, it is recommended that you put this value in for the source or target in question. It is more precise than using USERNAME@domain.com or domain\USERNAME and will generally yield better results. Wildcard mappings can be used with these values as well, so if i:0#.w|domain\USERNAME was your source and if i:0#.f|membership|USERNAME@domain2.com was your target, then your mapping CSV file with a wildcard could look like:
i:0#.w|domain\*,i:0#.f|membership|*@domain2.com
Remember that if your usernames do not exactly match, then a wildcard will not help you and you will have to map the names individually. One final point: only the first match will be used. If you put a wildcard mapping first and a user matches the wildcard on the left of the CSV, then the user will be mapped to the value on the right. For this reason, specific user mappings should go above your wildcard mappings.
This mapping would result in mapping anyone from ACME-EAST into ACME-WEST, but would not result in aklein being mapped into amy.klein, since the first mapping is always applied.