Migrating 2003 to 2012R2 by using Windows Migration Tools IP Migration

Source: Internet
Author: User

when it comes to IP migration, I really want to write a blog, this technology, at that time is probably the 2013 time to learn the technology, but has not found a good opportunity to practice, a while ago, the author is responsible for a research and development project, project background, using MVMC 3.1 powershell Migrate VMware to Hyper-V while writing heterogeneous hybrid cloud portals. NET program, invoke Mvmc's PowerShell in the UI interface, and then use variables to pass in to the program.


In doing this work, I found a problem, for example, I need to move the virtual machine from ESXI5.1 to hyper-v3.0, my esxi is 192.168.6.0 this network segment, hyper-v3.0 is 192.168.2.0 this segment, when I in MVMC When the UI interface executes, essentially, MVMC reads the configuration of the virtual machine inside ESXi, and then creates an identical virtual machine configuration entirely on top of hyper-V, but If the IP address of a virtual machine in ESXi is 192.168.6.1, when I migrate this virtual machine, in essence, the network card information is emptied, when I migrate 192.168.6.1 this virtual machine to the Hyper-V platform, Hyper-V will re-mount the new network card for this virtual machine, instead of Completely synchronize the network card information of the virtual machine in the original ESXi, so the effect is that after the virtual machine is migrated to the Hyper-V platform, it will get to an IP address again through the Hyper-V network segment DHCP, if there is no DHCP in the Hyper-V network segment, Then the migrated virtual opportunity gets a 169 IP address.


This is what I do in the UI interface, but when I use MVMC PowerShell to migrate, for example I have a virtual machine in ESXI5.1 that is 192.168.6.1, then after the migration, the network card of Hyper-V is not connected, You need to manually go to the Hyper-V to manually connect the network card, manually connected after the network card information is also emptied, so when the network card is connected, also in the Hyper-V network segment, re-DHCP get to a Hyper-V network segment address, I do not know is not due to my environment, VMware and Hyper-V are not on the same network segment, but I guess it's more likely that the process of VMDK to VHDX, the IP address is lost, if you test the migration under the same network segment, the IP address can be synchronized, you are welcome to tell me the result.


Then I thought, how can I transfer the network card information from VMware to Hyper-V, so I immediately thought of a way to use three PowerShell.


The first sentence, very simple, after the mvmc conversion of PowerShell, according to the previous variable, that is, after migrating to Hyper-V Hyper-V host, add a mount the network card command, first let the migration after the network card mounted again.

The second sentence, is the use of the Windows Migration Tool, this command, I added in the previous step of conversion, first of all, the conversion needs to determine the need to convert the virtual machine in VMware, then I put this conversion of virtual machine variables, passed to the back of the Windwos Migration Tool module, first, After acquiring the virtual machine that needs to be converted, use the remote session to connect, run the Export-smigserversetting-ipconfig command, save the virtual machine's IP address information to a network path,

The third sentence, when the migration is complete, also successfully migrated the virtual machine to the Hyper-V platform, also successfully executed the Mount network card, after the Mount Nic, plus a powershell,import-smigserversetting-ipconfig, Before the IP address saved to the network path and then migrated back, this way, the network card information in VMware can be synchronized to Hyper-V inside, to some extent, the transfer of network card information, but also reduce the amount of downtime and risk.


This is what I think of an IP address migration, can be used in the scene, or for example, the current 2003 of my server is configured with a lot of block network cards, each NIC also includes a lot of settings, such as DNS suffix, TCP/IP connection, etc., I hope, in the retention of the existing 2003 network card configuration, Migrating to the 2012 platform, and I want this step to be automated to avoid manual errors, you can also try migrating IP information using the Windows Migration Tool.

OK, then to the back, first to help you review


1.Windwos Migration Tool, if you need to migrate, first, you need to install the Windows Migration Tool on both the source and target side to be implemented.

2. If the source side is 2008r2 and above, you can directly by adding the Windows Migration Tool feature, if the source is 2008/2003, you need to build the Migration toolkit on the target side, available on the 03 side, and then copy the Migration Toolkit to 03 for installation. 03 can also have Windows Migration Tool features.

3. Since the Windwos Migration tool is primarily executed under the PowerShell tool, it is required, at least, to install powershell1.0 at the source end. NET2.0

4. Using the Windows Migration Tool, mainly to perform import/export operations, export at the source, import on the target side, this sentence if you do not understand it is OK, as we step in depth, you will see.


describe today's environment.


1 Windows Server 2003 VM Virtual Environments

Two NICs are configured with an IP address, respectively

The Windows Migration Tool was installed through the Migration Toolkit


1 Windows Server 2012R2 VM Virtual Environments

Two NICs, which are currently DHCP-to-IP addresses

The Windows Migration Tool has been installed through server roles and features

What I want to do is to migrate all the information of the two NIC in 2003 to the 2012R2 corresponding network card, and then completely replace the 2003 of this server to external connection.


First, we can open the Server 2003 network card information to view


Record the information of the two network cards, the first management network card IP address is 10.0.0.3, the second intranet network card information is 20.0.0.2, but also note the MAC address of two network cards

650) this.width=650; "Src=" http://s3.51cto.com/wyfs02/M01/5D/FE/wKiom1Uok5zjy2h2AANsIfyOP5M919.jpg " Title= "2015-04-11_112236.png" alt= "Wkiom1uok5zjy2h2aansifyop5m919.jpg"/>

On the source side of Windows Server 2003, open the Windows Migration Tool's PowerShell tools

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/5D/FE/wKiom1UolGSDuWzlAAKjJyPquk8243.jpg "title=" 2015-04-11_112554.png "alt=" Wkiom1uolgsduwzlaakjjypquk8243.jpg "/>

Execute the command as follows

Export-smigserversetting-ipconfig-path C:\ipconfig-verbose

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/5D/FE/wKiom1UolZrDPJ2bAAFApF0JJ2k256.jpg "title=" 2015-04-11_113110.png "alt=" Wkiom1uolzrdpj2baafapf0jj2k256.jpg "/>

The meaning of this command is as follows

Export-smigserversetting exporting the source-side server configuration

-ipconfig Export the IP address information of the source-side server

-path path to the exported file

-verbose whether the export information is displayed on the output side


When this command is executed, you will be prompted to enter a password, which is primarily used to encrypt the MiG migration file, and to prevent the MiG file from being used maliciously.


As soon as you enter a password you like, Smigserver will start to do the export IP address, not only the IP address, you can see that the entire network card information, will be exported.


650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/5D/FE/wKiom1UoluyBYv8cAAOQk-XdRVE507.jpg "style=" float: none; "title=" 2015-04-11_113611.png "alt=" Wkiom1uoluybyv8caaoqk-xdrve507.jpg "/>

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/5D/FA/wKioL1UomDnQ-h-cAAQ72QiM4so818.jpg "style=" float: none; "title=" 2015-04-11_113623.png "alt=" Wkiol1uomdnq-h-caaq72qim4so818.jpg "/>

After executing the export command, we copy the exported encrypted MiG file to the 2012R2 server.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/5D/FE/wKiom1Uol5DzbejWAAEuFX-FCi4557.jpg "title=" 2015-04-11_113810.png "alt=" Wkiom1uol5dzbejwaaeufx-fci4557.jpg "/>

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/5D/FE/wKiom1Uol9ODv9lrAAFgcUCR8K4908.jpg "title=" 2015-04-11_114042.png "alt=" wkiom1uol9odv9lraafgcucr8k4908.jpg "/> open windows Migration Tools PowerShell management on 2012R2 server

Executive Import-smigserversetting

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/5D/FA/wKioL1UomebjQQrSAADn9Xty51o869.jpg "title=" 2015-04-11_114238.png "alt=" Wkiol1uomebjqqrsaadn9xty51o869.jpg "/>

Or you can run Add-pssnapin in Windwos PowerShell with this command, load the migration Tools command

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/5D/FE/wKiom1UomNGyz6F2AAEQNXyxoNE227.jpg "title=" 2015-04-11_114340.png "alt=" Wkiom1uomngyz6f2aaeqnxyxone227.jpg "/>

Always if you want to run with a command prompt, enter the following command at the command prompt

Powershell.exe-psconsolefile%SYSTEMROOT%\SYSTEM32\SERVERMIGRATIONTOOLS\SERVERMIGRATION.PSC1

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/5D/FF/wKioL1Uo66_SasT1AAGExkiYGFU653.jpg "title=" Qq20150411173253.png "alt=" Wkiol1uo66_sast1aagexkiygfu653.jpg "/>

Note: If your migration source and target in the same communication network environment, here you need to choose a suitable point of time, the Windows Server 2003 inside the network card disabled, in short, must be executed before the import, otherwise there will be two machines, IP address conflict situation!!!


650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/5D/FB/wKioL1UonKCA84-yAAFWjT5oEtg740.jpg "title=" 2015-04-11_115539.png "alt=" Wkiol1uonkca84-yaafwjt5oetg740.jpg "/>

Here we choose to perform the import-smigserversetting import operation in Windwos PowerShell

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/5D/FF/wKiom1Uom82iKueaAAPOj4dGzDQ377.jpg "title=" 2015-04-11_115739.png "alt=" Wkiom1uom82ikueaaapoj4dgzdq377.jpg "/>

Import-smigserversetting-ipconfig all-sourcephysicaladdress "00-0c-29-e4-b5-92", "00-0C-29-E4-B5-9C"- Targetphysicaladdress "00-0c-29-5e-9e-84", "00-0c-29-5e-9e-8e"-path c:\ipconfig-Verbose


The meaning of this command is as follows


Import-smigserversetting Import Server Configuration

-ipconfig Import server configuration information type, ipconfig for IP information

All for all NICs

-sourcephysicaladdress

-targetphysicaladdress

See here, I guess you should know, Windows Migration Tool, when doing network card information mapping, is based on the MAC address mapping, for example, 2003 inside the first NIC, management MAC address information is 00-0c-29-e4-b5-92, 2012R2 inside the first NIC's MAC address information is the 00-0c-29-5e-9e-84,windows migration Tool, will be the MAC address of 00-0c-29-e4-b5-92 all network card information, all mapped to 00-0c-29-5e-9e-84. I use an English here, separated from the number of MAC address information, on behalf of me can be a number of network cards, in order to map.

-path the path of the MiG file to import

-verbose Output Import Information


Enter the password you set at the time of export, using ciphertext input


650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/5D/FB/wKioL1UonpWTO4lfAALbQy55LA8087.jpg "title=" Qq20150411120355.png "alt=" Wkiol1uonpwto4lfaalbqy55la8087.jpg "/>

When the input is complete, the Windows Migration Tool will begin mapping network card information


650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/5E/00/wKiom1Uonf6C43EYAAHm7-3Y41k810.jpg "title=" Qq20150411120657.png "alt=" wkiom1uonf6c43eyaahm7-3y41k810.jpg "/>650" this.width=650; "src=" http://s3.51cto.com /wyfs02/m01/5d/fb/wkiol1uoocwynqhlaaenyaerjyq094.jpg "title=" 2015-04-11_121033.png "alt=" Wkiol1uoocwynqhlaaenyaerjyq094.jpg "/>

After the mapping is complete, we open the 2012R2 inside the network card information, found that 03 inside the multi-card information has been mapped in order to come over

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/5D/FB/wKioL1UooJyAmXmgAALNNeHjdB0495.jpg "style=" float: none; "title=" Qq20150411121212.png "alt=" Wkiol1uoojyamxmgaalnnehjdb0495.jpg "/>

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/5E/00/wKiom1Uon1DD84oZAALnvZj03Vs575.jpg "style=" float: none; "title=" Qq20150411121231.png "alt=" Wkiom1uon1dd84ozaalnvzj03vs575.jpg "/>


650) this.width=650, "src=" Http://img.baidu.com/hi/face/i_f01.gif "alt=" I_f01.gif "/> to this end, I hope you can get the harvest through this blog, Set out to meet old friends!

This article is from "a Stubborn island" blog, please be sure to keep this source http://wzde2012.blog.51cto.com/6474289/1631172

Migrating 2003 to 2012R2 by using Windows Migration Tools IP Migration

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.