Migration Manager allows storing data files as hardlinks locally on NTFS volumes. This for use with In-Place Operating System refreshes to reduce migration time and use less storage for the personality during migration. Instead of copying data to the personality data store, the data is Hardlinked to and remains in place.
When Migration Manager extracts with hardlinking, data files on NTFS volumes are hardlinked to instead of being copied into a data store. If multiple ntfs volumes exist, the specified datastore will be created on each ntfs volume for hardlinking files on that volume. Non-ntfs volumes will store data on the primary ntfs volume.
|Files on non-ntfs volumes, as well as locked files on ntfs volumes cannot be hardlinked and are copied into the specified data store location instead of being hardlinked.|
During the injection, files are hardlinked to their destination location. Any files that are being injected to a different volume will be copied as ntfs does not support hardlinks to different volumes.
The file attribute
read-only does not persist in a hardlink migration due to ntfs limitations.
|If using File Rules to redirect files from a single location to multiple locations, such as using a File Rule to redirect files from
start /w MigrationManager.EXE /autoextract /allusers /personalitypath C:\_data /hardlinks
|The specified data store location, in this example
start /w MigrationManager.EXE /autoinject /allusers /personalitypath C:\_data
|The personality storage type is automatically determined on injection. Specifying
Example Command-Line with SCCM/MDT
|Prior to the Task Sequence with the command line to run Migration Manager, a Task Sequence Variable must be set for
start /w MigrationManager.EXE /autoextract /allusers /personalitypath %OSDStateStorePath% /hardlinks
start /w MigrationManager.EXE /autoinject /allusers /personalitypath %OSDStateStorePath%