Company Domain has a 2008r2 1TB file server, used to store the files of various departments, recently almost full, prepare a 2TB server installed 2012R2, all the files migrated to 2012r2, the permissions and filenames remain unchanged.
Here are the steps to test the environment and the problems that occur:
File Server 1:pekdc1-fil-01 2008r2 source file server
File Server 2:pekdc1-fil-02 2012r2 destination file server
The following is the first demonstration of the migration of the error, the second is successful. The corresponding solution is also written.
One. First Test (not successful, migration Tool version is different)
The Windows Server Migration Tool is installed on all two units. and open with Administrator privileges
1. In the pekdc1-fil-02 2012r2 destination file server input Send-smigserverdata cmdlet prompts for a password, enter confirm, prompt: The link is being opened, run on the source server Send-smigserverdata
650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M00/79/BF/wKiom1aaNXCxseTlAAQpmmS2srM290.jpg "title=" Operations on the target server "width=" "height=" 370 "border=" 0 "hspace=" 0 "vspace=" 0 "style=" width:600px;height:370px; "alt=" Wkiom1aanxcxsetlaaqpmms2srm290.jpg "/>
2. The administrator on the source server opens the Migration Tool input: Send-smigserverdata-computername "pekdc1-fil-02"-sourcepath \ \ Group share-destinationpath c: \ Group Share- Recurse-include All-force
Description, PEKDC1-FIL-02 is the target server, the C: \ Group share is the shared folder of the file server, the folder of the target server I set the same as the source server.
650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M02/79/BE/wKioL1aaNzOBy4frAAS7h2YWceQ955.jpg "title=" 08 versions are different. jpg "width=" "height=" 385 "border=" 0 "hspace=" 0 "vspace=" 0 "style=" width:600px;height:385px; "alt=" Wkiol1aanzoby4fraas7h2ywceq955.jpg "/>
3. Depending on the prompt, the target server and the source server system version are different. After the query needs to export a copy of the Migration tool from 2012R2, put on the 08r2 to use.
Export command:. \smigdeploy/package/architecture Amd64/os Ws08r2/path C:\Migur
650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M02/79/BF/wKiom1aaO17hs3pfAAFv7bovJoM987.jpg "title=" 1111108 1232.jpg "width=" "height=" 136 "border=" 0 "hspace=" 0 "vspace=" 0 "style=" width:600px;height:136px; "alt=" Wkiom1aao17hs3pfaafv7bovjom987.jpg "/>
Access the 12R2 Server Replication Migration Tool on the source server to a local
650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M01/79/BF/wKiom1aaPAHyPNceAAFXbUPHZMY297.jpg "title=" 708 12322.jpg "width=" "height=" 193 "border=" 0 "hspace=" 0 "vspace=" 0 "style=" width:600px;height:193px; "alt=" Wkiom1aapahypnceaafxbuphzmy297.jpg "/>
Two. Start a successful migration.
1.
On the target server, enter: Receive-smigserverdata
On the source server, open the Export Migration Tool (Smigdeploy) input from the destination server: Send-smigserverdata-computername "pekdc1-fil-02"-sourcepath C + + group Sharing- DestinationPath c \ Group shared-recurse-include All-force
650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M02/79/BF/wKiom1aaPmvBp9w4AAPoop0sp0E505.jpg "title=" 08 123 quasi. jpg "width=" "height=" 351 "border=" 0 "hspace=" 0 "vspace=" 0 "style=" width:600px;height:351px; "alt=" Wkiom1aapmvbp9w4aapoop0sp0e505.jpg "/>
650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M02/79/BF/wKiom1aaP0KxOX51AAKgO3SbBwk627.jpg "title=" 08 successes. jpg "width=" "height=" 385 "border=" 0 "hspace=" 0 "vspace=" 0 "style=" width:600px;height:385px; "alt=" Wkiom1aap0kxox51aakgo3sbbwk627.jpg "/>
2. The file and permissions have been successfully seen on the destination server
650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M01/79/BE/wKioL1aaQBSzEV2-AAZ68GJzkr0822.jpg "title=" 12 on successful technical department. jpg "width=" "height=" 458 "border=" 0 "hspace=" 0 "vspace=" 0 "style=" width:600px;height:458px; "alt=" Wkiol1aaqbszev2-aaz68gjzkr0822.jpg "/>
650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M01/79/BE/wKioL1aaQN_Tus8oAAGaOrRv70A891.jpg "title=" Qq20160116210552.jpg "width=" "height=" 226 "border=" 0 "hspace=" 0 "vspace=" 0 "style=" WIDTH:600PX;HEIGHT:226PX; "alt = "Wkiol1aaqn_tus8oaagaorrv70a891.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 in TechNet). Here are the links I referenced in the operation of the document, detailed can go to Microsoft TechNet view inside the introduction more detailed.
Http://www.mamicode.com/info-detail-561944.html
Https://technet.microsoft.com/zh-cn/library/dn479285.aspx
This article is from the "10902195" blog, please be sure to keep this source http://10912195.blog.51cto.com/10902195/1735665
2008R2 file Server Migration to 2012R2