File migration under Windows Server 2012

For Windows Server R2 and the previous version of the system, file migration generally chooses to use the FSMT tool, which is very useful.

Recently did a department file migration project, found that Microsoft Official document introduction FSMT only support to Windows Server R2, and this migration needs to be completed under Windows Server 2012. Then use the official introduction of the Windows Server 2012 comes with the Server Migration Tool: WSMT, for file migration.

The Server Migration Tool supports Windows Server 2003 to the full range of Windows Server R2 operating systems. If you need to use the tool, you should first install the Windows Server Migration Tool on the source and destination servers that are running Windows Server R2 or Windows Server 2012. The method is installed on the source and destination servers: Click Add Server Role-Add features-Select the Windows Server Migration Tool to install.

Using this tool to migrate, you need to run the Windows Server Migration Tool as an administrator. There are two main commands involved in the migration process: running Send-smigserverdata on the source server and running Receive-smigserverdata on the target server in the following format: Send-smigserverdata [-force] [ -recurse]-computername <string>-destinationpath <string>-include <all | Data | share>-password <SecureString>-sourcepath <string> [-confirm] [<commonparameters>] Specific examples are: Send-smigserverdata-force-recurse-computername fs02-destinationpath e:\shares-include All-sourcepath E:\ FILES

During the migration process, after running the send-smigserverdata command on the source server, you are prompted for a password to wait for the destination server receiving the data to enter the receive-smigserverdata receive command.

650) this.width=650; "Src=" Http://s1.51cto.com/wyfs02/M01/88/76/wKioL1f4-c7hkNY1AANN22olwQo680.png-wh_500x0-wm_3 -wmp_4-s_2571510706.png "title=" Capture 1. PNG "alt=" Wkiol1f4-c7hkny1aann22olwqo680.png-wh_50 "/>

Enter receive-smigserverdata on the target server to receive the command and enter the correct accept password

650) this.width=650; "Src=" Http://s3.51cto.com/wyfs02/M01/88/7A/wKiom1f4-xShLOO3AAKGrIgUadY449.png-wh_500x0-wm_3 -wmp_4-s_3411255730.png "title=" Capture 2. PNG "alt=" Wkiom1f4-xshloo3aakgriguady449.png-wh_50 "/>

At this point the source server will start the collection of file information and the encryption and transmission of the startup file, after the file information collection is complete, will establish communication with the target server, start to encrypt and transfer data.

650) this.width=650; "Src=" Http://s4.51cto.com/wyfs02/M01/88/76/wKioL1f4_buxPfoQAAMCxGQcyOM434.png-wh_500x0-wm_3 -wmp_4-s_1157997582.png "title=" Capture 4. PNG "alt=" Wkiol1f4_buxpfoqaamcxgqcyom434.png-wh_50 "/>

The Server Migration Tool retains file and folder permissions during data migration. If the migrated files and folders inherit permissions from their parent files and folders, the inheritance settings are migrated during migration, not inherited permissions. Therefore, you must ensure that the parent folders on the source and destination servers have the same permissions to maintain the appropriate permissions on migrated data for inherited permissions. Therefore, the most secure way is to establish a folder on the target server with the same name on the source server, and according to the folder NTFS permissions on the source server settings, set the folder on the target server NTFS permissions, and then file migration, otherwise migrated subfolders will lose the permissions inherited from the parent folder.

Although Microsoft notes in the official documentation that the file migration portion of the Windows Server Migration Tool is targeted at small datasets (data less than one GB), it copies files one by one via HTTPS. However, this does not mean that data larger than 100G cannot be migrated, which is actually possible. There will be no errors during the migration, except that the migration will take a long time, a folder of nearly 400G I spent about 24 hours in the migration process, but waiting for the good, a little patience OK.

Reference Document: https://technet.microsoft.com/zh-cn/library/jj863563 (v=ws.11). aspx

This article from the "Ant Line" blog, reproduced please contact the author!

File migration under Windows Server 2012