Windows Server Migration Tool II

Reference Links:

1. 1. https://technet.microsoft.com/zh-cn/library/dn486809 (v=ws.11). aspx

2. 2. https://technet.microsoft.com/zh-cn/library/jj863566 (v=ws.11). aspx

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

4. 4. https://technet.microsoft.com/zh-cn/library/jj863570 (v=ws.11). aspx#bkmk_freezeadministrationconfiguration

Necessary:

the source server and destination server must be open tcp/udp 7000 port and no programs are currently using this port.

Step One: Install the Migration tool on the target server (windows2008 R2) :

1. Make sure that Server Manager is off;

2. Open PowerShell then executes the Import-module servermanager load the Server Management module and then executes the add-windowsfeature migration Install the Migration tool;

Step Two: Install the Migration Tool on the source server (windows2008 or Windows 2003)

2. Create a deployment folder on the source server by using the Smigdeploy.exe tool that has the migration tools installed in the target server in step one .

4. A) Use the command line tool in the target server to enter the Migration Tool installation directory (CD%windir%\system32\servermigrationtools\);

6. b) perform the relevant actions to complete the deployment folder creation

8. l  Span style= "font-size:11px;font-family: ' The song body '; color: #000000;" > to create a copy to run Windows Server AMD64 deployment folder path represents the path of the deployment folder on the source computer, and then press Span style= "Font-size:11px;font-family:verdana, Sans-serif;color: #000000;" >enter .

smigdeploy.exe/package/architecture Amd64/os Ws08/path < Deploymentfolder Path>

• to create a copy to run Windows Server 2003 AMD64 deployment folder path represents the path of the deployment folder on the source computer, and then press Span style= "Font-size:11px;font-family:verdana, Sans-serif;color: #000000;" >enter .

smigdeploy.exe/package/architecture Amd64/os Ws03/path < Deploymentfolder Path>

• to create a copy to run Windows Server x86 deployment folder path represents the path of the deployment folder on the source computer, and then press Span style= "Font-size:11px;font-family:verdana, Sans-serif;color: #000000;" >enter .

smigdeploy.exe/package/architecture X86/os Ws08/path < Deploymentfolder Path>

• to create a copy to run Windows Server 2003 x86 deployment folder path represents the path of the deployment folder on the source computer, and then press Span style= "Font-size:11px;font-family:verdana, Sans-serif;color: #000000;" >enter .

Smigdeploy.exe/package/architecture X86/os Ws03/path <deploymentfolder path>

1. For example, our source server is the x86 schema for the Windows deployment path:E:\test_deploy, use the following command:

Smigdeploy.exe/package/architecture X86/os Ws08/path E:\test_deploy

2. Registering the Windows Server Migration Tool on the source server

3. A        will useto create a deployment folder on the destination computercreated by the procedure in theWindows ServerMigration Tools Deployment folder copy to runWindows Server 2008orWindows Server 2003The local drive on the source computer. Ensure that the operating system architecture of the deployment folder matches the operating system architecture of the source computer to which the folder is being copied. For example,Smt_ws08_amd64folders can only be copied to runWindows Server 2008of theAMD64the local drive of the source computer. The folder generated in our example above is namedSmt_ws08_x86, so the folder can only be copied to the runningWindows Server 2008of theX86the local drive of the source server. The resulting folder can be directlyTest_deployCopy to source serverE:\under the catalogue;

5. b) Use the command-line tool on the source server to enter the directory you just copied, such as E:\test_deploy\SMT_ws08_x86, and then enter . \smigdeploy.exe order to perform registration;

Step three: Using Windows Server Migration Tools

1. Start the Migration tool by executing the following command from the command-line tool (Windows R2) :

Powershell.exe-psconsolefile%systemroot%\system32\servermigrationtools\servermigration.psc1

1. in the Run on the Windows Server 2003 computer, click Start , point to Administrative Tools , and then open the windowsserver Migration Tool folder, and then click Windows Server Migration Tools .

Step four: Migrating Local Users and Groups

1. enter the following command to export the local users and groups to the migration store by entering the PowerShell in step three open or in step two 2 (b)

Export-smigserversetting-user <enabled | Disabled | all>-group-path <MigrationStorePath>-verbose

Use one of the following values in conjunction with the –user parameter, as shown in the previous cmdlet .

• enable export only enabled Local users

• Disabled only local users that are disabled are exported

• All export enabled and disabled Local Users

For example, we use the following command to export all local users and user groups to the under the E:\test_bak directory

Export-smigserversetting-user All-group-path E:\test_bak-Verbose

1. Copy the previously exported files to the destination server local disk and import them using the following command:

Import-smigserversetting-user <enabled | Disabled | all>-group-path <MigrationStorePath>-verbose

Use one of the following values in conjunction with the-user parameter, as shown in the previous cmdlet .

• Enabled to import only Local users

• Disabled only local users that are disabled are imported

• All import enabled and disabled Local Users

For example: import-smigserversetting -user all-group-path E:\test_bak-Verbose

Step Five: Migrating data

Use the command:

1. Send-smigserverdata

2. Receive-smigserverdata

To illustrate:

Source server name: sourcetest

Target server name:test2012

Send-smigserverdata–computername Test2012–sourcepath "D:\test folder" –destinationpath e:\receive–recurse–include All–force

Explanation: Sending the source server The TEST folder and the data contained below the folder (folder, document, etc.) are transferred to the target server TEST2012,destinationpath The path you specify must be accessible by the destination server and cannot be the root directory (shared folder or other network location).

：

650) this.width=650; "Src=" https://s1.51cto.com/wyfs02/M01/8E/0A/wKiom1iz4RCDVxwMAAAvdI5ijDA038.png-wh_500x0-wm_ 3-wmp_4-s_589638436.png "title=" Snipaste20170227_112004.png "alt=" Wkiom1iz4rcdvxwmaaavdi5ijda038.png-wh_50 "/>

Step six, migrating functional roles

1. Get-smigserverfeature role Service information installed by the collection server

650) this.width=650; "Src=" https://s4.51cto.com/wyfs02/M00/8E/0A/wKiom1iz4TzTe6MGAAAPM6rb-Zc127.png-wh_500x0-wm_ 3-wmp_4-s_1654328983.png "title=" 4.png "alt=" Wkiom1iz4tzte6mgaaapm6rb-zc127.png-wh_50 "/>

1. Export-smigserversetting–featureid Dhcp–path Z:\feature-verbo
   

Export DHCP role to the Z:\feature directory.

Note: Stop before this DHCP Service

650) this.width=650; "Src=" https://s2.51cto.com/wyfs02/M01/8E/08/wKioL1iz4VaDrQxBAAAOm9_KRuk692.png-wh_500x0-wm_ 3-wmp_4-s_3236182237.png "title=" Dhcp1.png "alt=" Wkiol1iz4vadrqxbaaaom9_kruk692.png-wh_50 "/>

650) this.width=650; "Src=" https://s1.51cto.com/wyfs02/M02/8E/08/wKioL1iz4XDRRRwmAACTQkbRo7A879.png-wh_500x0-wm_ 3-wmp_4-s_1153710542.png "title=" Dhcp2.png "alt=" Wkiol1iz4xdrrrwmaactqkbro7a879.png-wh_50 "/>

1. Target server import.

on the target server, POWERSHELL (Note that this is not the Migration Tool command-line window, running the IMPORT command in the Migration Tool command-line window will not be recognized) run the following command ;

1. 1 add-pssnapin microsoft* ( If you just want to load the migration command, run:add-pssnapin microsoft.windows.servermanager.migration

1.2 then enter import-smigserversetting–featureiddhcp–force–path e:\feature–verbose to import. such as:

650) this.width=650; "Src=" https://s3.51cto.com/wyfs02/M02/8E/0A/wKiom1iz4iSjDOOZAADOxtOEiSY954.png-wh_500x0-wm_ 3-wmp_4-s_2927821232.png "title=" 3.png "alt=" Wkiom1iz4isjdoozaadoxtoeisy954.png-wh_50 "/>

Step seven, migrating network configuration information

1. Export NIC configuration information

Export-smigserversetting–ipconfig-path Z:\ipcon–verbose

650) this.width=650; "Src=" https://s2.51cto.com/wyfs02/M01/8E/0A/wKiom1iz4m6RUPa4AAB5OygvBik209.png-wh_500x0-wm_ 3-wmp_4-s_1189747650.png "title=" 5.png "alt=" Wkiom1iz4m6rupa4aab5oygvbik209.png-wh_50 "/>

2. Import network card configuration information

Attention:

2. record the source and destination servers before importing MAC Address

4. if two servers in a network segment need to disable the source server's network card at the appropriate point in time, it will cause IP conflicts.

6. If there are multiple The MAC address information is delimited by ( comma ) .

8. the network card information map is based on MAC addresses are mapped, for example, the MAC address of the source server 00-15-5d-00-fc-57 the Mac address of the destination server 00-15-5d-00-fc-51 , Mac address 00-0c-27-e5-b7-1c the MAC address of the destination server is 00-2b-e2-ff-4c-78and sequentially mapped.

a command, for example, embodies many MAC address Import and address correspondence:

Import-smigserversetting–ipconfigall–sourcephysicaladdress "00-15-5d-00-fc-57", "00-0c-27-e5-b7-1c" – Targetphysicaladdress "00-15-5d-00-fc-51", "00-2b-e2-ff-4c-78" –path e:\ipcon–verbose

1. Import command:

Import-smigserversetting–ipconfig all–sourcephysicaladdress "00-15-5d-00-fc-67" –targetphysicaladdress " 00-15-5d-00-fc-51 "–path E:\ipcon–verbose

650) this.width=650; "Src=" https://s4.51cto.com/wyfs02/M02/8E/0A/wKiom1iz4piy6wzcAAB6p68k7q8823.png-wh_500x0-wm_ 3-wmp_4-s_3302264353.png "title=" 6.png "alt=" Wkiom1iz4piy6wzcaab6p68k7q8823.png-wh_50 "/>

For more commands and features, refer to the link at the beginning of the article.

This article is from the "Record Bit Technology" blog, please make sure to keep this source http://seawind.blog.51cto.com/6845370/1901698

Windows Server Migration Tool II