Migrating from 2003 to 2012R2 using Windows Migration Tools Introduction

With effect from July 14, 2015, Microsoft will no longer support Windows Server 2003, but many companies are still using Windows Server 2003, and once Microsoft stops supporting Server 2003, means that third-party software developers will no longer program development for 2003, and the Server 2003 does not update patches, which means that the server operating system security is not well protected, which is dangerous for enterprise information systems.

So, this series of articles is designed to help it engineers understand how to upgrade applications on existing 2003 system platforms to the 2012R2 platform, ensuring the continuous and safe operation of enterprise business systems.

Windows Server 2012R2 is a relatively new Microsoft operating system, released October 18, 2013, after two years or so, with the gradual landing of the 2012R2 project, people also began to gradually accept the 2012R2 cloud operating system.

If compared to Windows Server 2003 with Windows Server 2012R2, I think is an essentially leap forward, talking about Windows Server 2003 is the author contacted earlier an operating system, 2003 gave me the impression of stability, lightness, convenience, Although some places are unsatisfactory, but compared to the previous 2000,nt4, I think there has been a great improvement, at that time I think 2003 is enough as a business network operating system, for enterprises to provide daily network services.

But with the development of the information Age, virtualization, high-level virtualization, private cloud, public cloud, big data, these technical words, people will find that if on the top of 2003, to achieve some highly virtualized applications, as well as the private cloud, there is no way to do, when Windows Server 2012R2 in the Information Age, Windwos server 2012R2 with multi-server centralized management, high-performance scaling, multi-tenant security isolation, cheap hardware fusion, intelligent application awareness, reliable business continuity and other characteristics, can say, 2012R2 is for today's enterprise's large-scale data center management, the private cloud architecture of an operating system, I think, every Windows engineer should go to understand Windows Server 2012R2, follow the information age of the pace of development, will not be left behind.

So, if the enterprise now has a Windows Server 2003 infrastructure environment, how to migrate to 2012R2, which applications can be migrated, and how they should be migrated, is the topic we need to discuss today.

first of all, stand in the technical perspective to think, in the process of system upgrade migration, I think there should be the following several steps.

1. Existing environmental assessment

Number of existing 2003 old operating systems in the collection environment

Collection of existing hardware assets in the environment to meet 2012R2 requirements

Collect server roles in existing environment, confirm migration feasibility, priority

2. Software classification

Collect software assets in the environment, view existing 03 with those business software, confirm support and not support applications running under 2012R2, and determine the migration priority.

3. Determine the migration target

Identify the 2003 servers that need to be migrated

Identify the server roles that need to be migrated

Identify applications that need to be migrated

4. Performing the Migration

Perform migrations in accordance with the standard migration SOP to ensure business continuity, reliability, and security.

5. Migration verification

Verify that the target that needs to be migrated is migrated properly.

Standing in the direction of standardization and management to think, in the process of system upgrade migration, I think there should be the following steps.

1. Initiating a migration service request from the requesting owner

In this step, it is up to the enterprise IT department to implement the primary person responsible for the migration of the business system to initiate the service request to be migrated, which should include, in a detailed migration description, the affected configuration items.

2. The Information Department manager confirms the service request and comments.

3. If the Information Department manager agrees to the service request, and the person responsible for the migration formally initiates a detailed change request, the change request should include the scope of the target scope of the change, the specific reason for the change, the risks and technical difficulties that may be encountered in the change, the time required for the change, the benefits of the change, the disadvantages, And a workable fallback plan.

4. The Change Review Committee, from the perspective of safety, feasibility, risk, timeliness and detailed assessment, and give changes to approve and comments.

5. If the Change Review committee passes the review, the implementation of the migration manager, in accordance with pre-planned activities, strictly in accordance with the changes within the time frame and operating scope, the implementation of standardized migration procedures, and the operation of the procedures in accordance with the standard configuration management mechanism to record.

6. If the migration owner successfully completes the migration, the procedures should be archived and collected into the Enterprise knowledge Management Library, and the entire change process should be recorded in the CMDB Database for future audit review.

7. If the implementing migration Manager fails to successfully complete the migration, it should follow the standard fallback plan, perform a gradual rollback, revert to the pre-migration, minimize the business impact, and return the rollback steps, the reason for the failure to complete the migration is recorded, and if necessary can be changed as a problem to conduct an in-depth research solution.

As with the migration steps above, it is entirely my own idea, regardless of any unit, and if the enterprise wants to do business migration in a standardized environment, I recommend using assessment tools such as Map,tco,azure Vmra to evaluate the existing data center IT environment in detail, for the implementation framework, I recommend the adoption of ITIL's standard framework for implementation.

Next, let's look at a tool that may be used during migration 2003 to 2012R2 implementation.

Windows Migration Tool is a system platform level Migration tool introduced by Microsoft in Windows Server 2008r2, which can help system administrators to migrate roles, functions, files, users, network card configuration, etc. in the same or different operating systems, in 2008R2 Windows Migration Tool, which is built into server 2008r2 and later servers roles and functions, can be directly added function to get the function, then, you might think, since it is the function of 2008r2, how to migrate 03? About this, the Windows Migration Tool has its own ingenious idea, everyone and slowly look.

The Windows Migration Tool supports migration of the following system platforms

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/5D/F0/wKiom1UnhuDikBa_AAJlQhxkiqY451.jpg "title=" Qq20150410161552.png "alt=" Wkiom1unhudikba_aajlqhxkiqy451.jpg "/>

1. To install the Windows Migration Tool, you can first choose to install on the target side, this example is the 2012R2 end

Open Server Management-add server roles and features

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/5D/EC/wKioL1UnmVLgel_FAAMUHyIYf1E530.jpg "title=" 1.png " alt= "Wkiol1unmvlgel_faamuhyiyf1e530.jpg"/>

Select the Windows Server Migration Tool in the feature

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/5D/F1/wKiom1UnmZmR3Ud_AALrlCritDk729.jpg "title=" 2.png " alt= "Wkiom1unmzmr3ud_aalrlcritdk729.jpg"/>

Select Next, install, wait for the installation to complete, and select Close.

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/5D/F1/wKiom1Unme2RPXCEAAG4DGLTcvc532.jpg "title=" 3.png " alt= "Wkiom1unme2rpxceaag4dgltcvc532.jpg"/>

After the installation is complete, you will find that the system's Start menu is filled with an extra

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/5D/F0/wKiom1UniPTAZYPJAAOTh5aF3UU529.jpg "title=" QQ picture 20150410162449.png "alt=" Wkiom1uniptazypjaaoth5af3uu529.jpg "/>

After the opening, he probably grew up like this, a PowerShell management interface.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/5D/EB/wKioL1UnicKRLUKeAADWhjjn6Pg842.jpg "title=" Qq20150410162156.png "alt=" Wkiol1unickrlukeaadwhjjn6pg842.jpg "/>

In this PowerShell interface, the Windows Migration Tool has some of its specific cmdlets that are more commonly used, for example.

• smigdeploy

• export-smigserversetting

• import-smigserversetting

• get-smigserverfeature

• send-smigserverdata

• receive-smigserverdata

Among them, Smigdeploy, is primarily used for generation, migration Toolkit for older versions of migrations, for example, 03 and 08 to migrate to 08r2 or 2012R2, in 08R2 and 2012, directly built-in features of the Windows Migration Tool, The PowerShell management tool can be obtained directly from the Add feature, but in 03 and 08, the default server management does not have the Windows Migration Tool server function, so we can install the Windows Migration Tool in the 2012R2 target machine. Build a migration toolkit that can be used for 2003 and then copy to 03 to install

Use the following method

First enter the 2012R2 server path C:\Windows\system32\ServerMigrationTools

then run smigdeploy/package/architecture x86/os ws03/path C:\Migur

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/5D/F0/wKiom1UnjArgI49UAAGMP6CZP2Q747.jpg "title=" Qq20150410163807.png "alt=" Wkiom1unjargi49uaagmp6czp2q747.jpg "/>

Each parameter of this command has the following meanings

/package

Create a Windows Migration toolkit that you can replicate to 03/08/08R2, which you typically need to work with/os/architecture/path

/architecture

Build the Migration Toolkit to run the source operating system, what is the CPU architecture, X86 or AMD64

/os

Build the Migration Toolkit to run the source operating system, what operating system, WS03/WS08/WS08R2/WS12

/path

The set of Migration Toolkit to store in what path must be a path that already exists.

The Windows Migration Tool works, in general, to perform the migration, the first on the source, that is, the 03 server, the export or send operation of the exported data needs to be migrated, export will be a MiG file, and then copy the MiG file to the target server, That is, the import operation is performed on the 2012R2 server.

What we do in this step is to allow 03 of the operating system to perform the export operation, copy the generated Migration Toolkit to the 03 service above the install,03 with the PowerShell management tool for the WINDWOS migration Tool.

Before copying the Migration Toolkit to 03 of servers, since 03 does not have PowerShell in itself, it is required to install at least 03 operating systems or other source operating systems. NET2.0 and powershell1.0 are as follows

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/5D/EC/wKioL1Unkfvi-iRxAAGIIWoEgYo618.jpg "title=" QQ picture 20150410165800.png "alt=" Wkiol1unkfvi-irxaagiiwoegyo618.jpg "/>

After you install the prerequisites, copy the Migration Toolkit to the 03 server, run the Smigdeploy in the directory, and if you eject the PowerShell management tool to prove that the installation was successful, we can now perform the export operation on the Windows Server 2003 source side.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/5D/F1/wKiom1UnkWyyLytlAALtiQhpOlU037.jpg "title=" Qq20150410170010.png "alt=" Wkiom1unkwyylytlaaltiqhpolu037.jpg "/>

As for the other cmdlets, I will explain them in detail later in the article.

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

Migrating from 2003 to 2012R2 using Windows Migration Tools Introduction