If you transfer a user’s settings using USMT into a client that they already have a profile in, what will happen?
In the config.xml file, you can create merge rules for your data. Below is an example of the xml code for a merge rule. You can read the complete article from Microsoft here.
During ScanState, all the files will be added to the store.
During LoadState, only C:\Data\SampleA.txt will be restored.
During ScanState, all the files will be added to the store.
During LoadState, all the files will be restored (overwriting the existing files on the destination computer).
During ScanState, all the files will be added to the store.
During LoadState, the following will occur:
<merge script>="MigXmlHelper.DestinationPriority()">
<objectSet>
<pattern type="file">c:\data\* [*]<pattern>
</objectSet>
</merge>
During ScanState, all the files will be added to the store.
During LoadState, only C:\Data\SampleA.txt will be restored.
<merge script>="MigXmlHelper.SourcePriority()">
<objectSet>
<pattern type="file">c:\data\* [*]<pattern>
</objectSet>
</merge>
During ScanState, all the files will be added to the store.
During LoadState, all the files will be restored (overwriting the existing files on the destination computer).
<merge script>="MigXmlHelper.SourcePriority()">
<objectSet>
<pattern type="file">c:\data\ [*]<pattern>
</objectSet>
</merge>
During ScanState, all the files will be added to the store.
During LoadState, the following will occur:
- C:\Data\SampleA.txt will be restored.
- C:\Data\SampleB.txt will be restored (overwriting the existing file on the destination computer).
- C:\Data\Folder\SampleB.txt will not be restored.
Comments