Production environment Requirements: There is a 2008R2 1TB file server in the company domain, used to store the files of various departments, recently nearly full, prepare a 2TB server installed 2012R2, all the files migrated to 2012R2 , the permissions and file names remain the same.
File Server 1:pekdc1-fil-01 2008R2 source file server
File Server 2:pekdc1-fil-02 2012R2 destination file server
Migrate between the same versions, using the Windows Server Migration Tool in the feature. If the version is different, you need to export the appropriate tools from the higher version of the system to use on the lower version. In this example, if you use the Migration tool in the 08r2 function, there will be an error, at the end of this article there are examples
A. The following is a 12r2 export 08r2 Migration Tool Step
1.1 on 2012R2 target server cmd first enters C:\Windows\system32\ServerMigrationTools
1.2 Run the . \smigdeploy/package/architecture Amd64/os ws08r2/path C:\Migurand see if the program was successfully exported on C Drive ( verification process slightly )
650) this.width=650; "src=" http://s4.51cto.com/wyfs02/M01/79/D5/wKiom1acWrCDQ5a5AAG4cQ-4gxQ542.jpg "title=" 1.jpg " Width= "height=" border= "0" hspace= "0" vspace= "0" style= "width:700px;height:132px;" alt= " Wkiom1acwrcdq5a5aag4cq-4gxq542.jpg "/>
1.3 on the 08r2 source Server, the program folder is copied to the local, using the smigdeploy migration program.
650) this.width=650; "src=" http://s1.51cto.com/wyfs02/M01/79/D5/wKiom1acW-aBL13hAATHuoZW8t8668.jpg "title=" 2.jpg " Width= "height=" 417 "border=" 0 "hspace=" 0 "vspace=" 0 "style=" WIDTH:700PX;HEIGHT:417PX; "alt=" Wkiom1acw-abl13haathuozw8t8668.jpg "/>
Two Start migration
2.1 on the target server to open the Migration tool with an administrator, and enter receive-smigserverdata Press ENTER to confirm, prompt for a password, which is used to verify the source and destination server migration data, must be one to
650) this.width=650; "src=" http://s2.51cto.com/wyfs02/M01/79/D4/wKioL1acXOyjsq8yAAPpILtOpTo719.jpg "title=" 3.jpg " Width= "height=" 432 "border=" 0 "hspace=" 0 "vspace=" 0 "style=" width:700px;height:432px; "alt=" Wkiol1acxoyjsq8yaappiltopto719.jpg "/>
2.2 Open the Migration Tool (smigdeploy) input exported from the destination server on the source server:send-smigserverdata-computername "pekdc1-fil-02" – Sourcepathc:\ Group shared -destinationpath C + + Group shared -recurse-include All–force
Note: As can be seen from the command, the target server is pekdc1-fil-02. The folder to be migrated is a group share of the C Drive. I set the source and destination folder names the same.
650) this.width=650; "src=" http://s1.51cto.com/wyfs02/M01/79/D5/wKiom1acXO3wK4IyAAPoop0sp0E100.jpg "title=" 4.jpg " Width= "height=" 409 "border=" 0 "hspace=" 0 "vspace=" 0 "style=" WIDTH:700PX;HEIGHT:409PX; "alt=" Wkiom1acxo3wk4iyaapoop0sp0e100.jpg "/>
2.3 appears to indicate a successful migration. (The actual environment depends on the size of the time is different)
650) this.width=650; "src=" http://s5.51cto.com/wyfs02/M02/79/D4/wKioL1acXe2Bz-AHAAKgO3SbBwk290.jpg "title=" 5.jpg " Width= "height=" 449 "border=" 0 "hspace=" 0 "vspace=" 0 "style=" WIDTH:700PX;HEIGHT:449PX; "alt=" Wkiol1acxe2bz-ahaakgo3sbbwk290.jpg "/>
2.4 The file and permissions have been successfully seen on the target server
650) this.width=650; "src=" http://s2.51cto.com/wyfs02/M00/79/D5/wKiom1acXd6QSHYxAAZ68GJzkr0964.jpg "title=" 6.jpg " Width= "height=" 534 "border=" 0 "hspace=" 0 "vspace=" 0 "style=" width:700px;height:534px; "alt=" Wkiom1acxd6qshyxaaz68gjzkr0964.jpg "/>
2.5 Client validation succeeded
650) this.width=650; "src=" http://s4.51cto.com/wyfs02/M01/79/D5/wKiom1acXfqBFbxWAAGaOrRv70A202.jpg "title=" 7.jpg " Width= "height=" border= "0" hspace= "0" vspace= "0" style= "width:700px;height:264px;" alt= " Wkiom1acxfqbfbxwaagaorrv70a202.jpg "/>
To this migration is complete. (After the migration is completed, the source server back to the domain, the target server to the IP and the computer name is the source server, so that the client does not have to make any changes) the actual environment of the data is relatively large, preferably in the evening, so as not to affect user use. Disconnect the user before the official migration (described inTechnet ). The following are the documents I referenced in the operation of the connection, you can also go to Microsoft Technet Inside the introduction more detailed.
Http://www.mamicode.com/info-detail-561944.html
Https://technet.microsoft.com/zh-cn/library/dn479285.aspx
If you use the Migration tool in the 08r2 function, the following error will appear
650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/79/D4/wKioL1acXzqCnhweAAS7h2YWceQ813.jpg "title=" 8.jpg " Width= "height=" 449 "border=" 0 "hspace=" 0 "vspace=" 0 "style=" WIDTH:700PX;HEIGHT:449PX; "alt=" Wkiol1acxzqcnhweaas7h2ywceq813.jpg "/>
This article is from the "Zhao Dongwei Learning record" blog, so be sure to keep this source http://zhaodongwei.blog.51cto.com/4233742/1736096
2008R2 file Server Migration to 2012R2