Priority & Business Value Analysis Target Platform Review Windows Server 2003 Roles Migration Process Assessment & START Data Collection High-level Application Portfolio Analysis High-level Planning Planning High-level Business Case Architecture

● Migrate the platform into a new infrastructure environment ● Change speci c code and/or con guration information to ● Migrate it into a new infrastructure environment in a way that ● Upgrade the version or rebuild the previously used solution ● Replace the previously used solution with another solution Categorize platforms through discovery, planning & assessment for migration by role; choose one from the 5R (Rehost, ● Refactor, Revise, Rebuild Replace/Retire) platform methods de ned by Gartner and establish an adequate migration as it is help ease its adoption within a new infrastructure environ- the previously used features and services remain intact or else or features/service in a way that they suit the new infrastruc- It is emotionally/practically dicult to make a decision from Gartner’s 5R Platform Migration ● plan accordingly. The simplest platform migration method ment are improved ture environment the standpoint of IT service team, but it is technically easy Rehost ● Relatively easy way to migrate the platform Refactor ● The most complex platform migration method Revise ● More complex than Rehost, but easier than Revise Rebuild Replace/Retire

Migration method 1 – Make use of the default roles and features provided by the OS Migration method 2 – Use as web application server

You can practice this migration method by referring to the technical documentation in the TechNet Library officially provided by Microsoft or by working in collaboration with the Microsoft Services team and/or your partners, Microsoft offers Web Deploy, which helps migrate ASP.NET and PHP applications developed/deployed in IIS 6.0 provided by Windows Server 2003 into IIS version 7.0 or later, and also apply this to the migration of both the physical and virtual servers. and you can use Web Deploy to first migrate into a new destination server and then change the application-specific code or configuration values in the new infrastructure environment.

Make use of the roles and Use as a web application Migration tools and Create deployment features provided by the OS Install Web Deploy Perform pre-configuration on procedures Install WSMT on the folders, with which server Web Deploy v3.5 Extension on both the the destination server based destination server WSMT works, in the by default source and destination on dependencies information 1 3 target server 1 servers 3 of the source server ● Windows Server Migration Tool (WSMT) ● A tool that simplifies the deployment of web ● Install/set on both source and destination servers With Rehost, Refactor, Replace/Retire among Gartner’s With Refactor, Revise Replace/Retire among Gartner’s applications and websites to the IIS server ● Migrate the role of server, features, operating 5R Platform Migration methods taken into account 5R Platform Migration methods taken into account ● It helps synchronize IIS servers, or migrate them system configuration, other data and shared files into newer versions of IIS server into the destination server Copy deployment ● For more information about Web Deploy, visit Create information Create a package file folders of the destina- Register WSMT on the about the dependencies on the source server tion server into the source server http://www.iis.net/downloads/microsoft/web-deploy of websites running on and migrate it into the 2 source server 4 2 the source server 4 destination server

For more details about how to install/set WSMT on source and migration-destination servers, For more information about IIS migration using Web Deploy, go to go to http://technet.microsoft.com/library/jj134202 http://technet.microsoft.com/en-us/library/ff633422(v=ws.10).aspx

latively easy an Next Step Re d less c om ● It is recommended that you first test Web Deploy in a test environment, carry out assessment through troubleshooting and then ● A referential guideline is provided for typical migration scenarios among default roles and features of ple (Case by Case) x use it in the actual operating environment because there are a number of things to be considered, including the deployment of Windows Server 2003 ASP.NET or PHP application to IIS and specific configuration. ● It is recommended that you first carry out assessment before migration because a number of things ● This guideline is provided for the IIS server, but you can migrate Java-based WAS and J2EE servers in the same way using the need to be considered in the actual operating environment DNS migration tool provided by the relevant solution provider.

Referential guideline: Active Directory Referential guideline: Active Directory Domain Services http://technet.microsoft.com/library/dd379558.aspx Certi cate Services http://technet.microsoft.com/library/ee126170 Make use of the & DNS (WS.10).aspx Related DNS records are DNS is the source server Deployment check default roles and features hosting a web farm. updated to point new IIS 7.0 web farm on the browser. provided by the OS ASP.contoso.com Check whether the migrated web applications running 192.168.202.202 on the new production server meet the stability, Referential guideline: Referential guideline: Use as a web APS.contoso.com PHP.contoso.com 192.168.202.200 performance and speci c requirements of clients DHCP Services File Services ▶ PHP.contoso.com 192.168.202.202 http://technet.microsoft.com/library/dd379535.aspx http://technet.microsoft.com/library/dd379487.aspx Active Directory Services IIS 6.0. application server 192.168.202.195 Migration check IIS, 7.0, ASP.NET, PHP through the nal test and sign-o. ASP.NET ▶ 192.168.202.196 File Server Services Apache, PHP ▶IIS + .NET Once it is con rmed that new IIS 7.0 web farm ▶Domain Name Server works without problem, web applications are ▶Java WAS + J2EE Windows Server Referential guideline: Referential guideline: Services A copy of web farm is deployed migrated into new IIS 7.0 web farm. Applications Local Users and on IIS 7.0 staging server. can be migrated individually or as group. Update Services http://technet.microsoft.com/library/hh852339.aspx Group http://technet.microsoft.com/library/dd379531.aspx ▶Etc… Web application migration ▶DHCP Services Staging server: IIS 7.0, ASP.net, PHP Web application deployment IIS 7.0, ASP.net, PHP

▶WSUS Services Test applications regarding whether they work without any compatibility Windows Server Migration Information : http://technet.microsoft.com/library/jj134039 problems. Problems can be solved without aecting production web farm, and ▶Routing & Remote this production web farm will continue to be hosted by the source server. http://technet.microsoft.com/library/dd365353.aspx ● Pre-assessment is required Access Services ● The 3rd party software and applications

▶Etc… It is required to collect information and .

W e

work in collaboration with 3rd party v

i

n

o

d

vendors (provider of 3rd party software b d

o a

e

w r

n

e and application developers) s

w

d S i

o s ● e With simple guidelines, migration h

r n

s v o

e c cannot be performed s r a

Migration method 4 – Use as database server e Migration method 3 – Install the 3rd party solution 2 s

b

0 e

0 o p t

4 Install the 3rd party y

t

You can refer to the technical documentation in the TechNet Library officially provided by Microsoft or work in collaboration with Microsoft Services e

v / use as the operating server p

4 l a

team and/or your partners to migrate the database into a newer version or re-configure it while migrating the OS environment. a h solution / use as the

o

t t When it comes down to migrating Windows Server 2003 hosting 3rd party solutions (and applications), there are many more things to be considered concerning f s

o n g Use as a database server i

r the migration of those solutions (applications) to a new infrastructure environment, rather than the migration of the OS itself, and moreover the procedure and

n operating server m i

d

h e methodology take on added significance. Microsoft recommends performing migration in 9 steps as shown below. (It is difficult to propose guidelines in broad

t i

m f

e i r ▶ generalities because a number of things must be considered depending on the 3rd party solutions - and applications - installed.)

i ▶ Groupware s

g SQL o s

a

r l

a m c

Collect SQL informa- Configure SQL on the t ▶

d ▶Oracle Portal

io y The following figure shows a detailed examination of the step-by-step activities proposed by Microsoft for the migration of Windows Server 2003 on which the Old SQL to New SQL: n

tion from the source destination server based on l

n a e

3rd party solutions (and applications) are installed: t the information collected l g

server using MAP is ▶MySQL ▶ERP r Tools and Procedures u

a

n c l (It is recommended to follow each step and activity involved, but some steps could be skipped depending on the size of the 3rd party solutions - and applica-

1 3 using a MAP Toolkit i

Toolkit

o f

f e

t i ▶ ▶ tions - or staffing of the client.)

d Etc… CRM b

● a

Microsoft Assessment and Planning y

m l n e a

v c

e i ▶

(MAP) Toolkit r t Etc… a

e l m

e r

● Capable of collecting and checking O R o S tf inventory information about the SQL u la Discovery/Raw Inventory Rationalization Categorize Back up the SQL database of p p g f server installed/configured on the Install a new SQL the source server and restore r o a e source server server in the destina- d C s 1 ● Collect configuration information of applications 2 ● Define rationalization rules that determine which 3 ● Collect information and binary of solutions (or applications) it into SQL running on the e s u tion server o l e and software installed in the current environment software/applications would be migrated ● Determine priorities depending on critical business ● 2 4 MAP Toolkit Overview & Download: destination server r e th dependencies and collect information of how much each m a l ; ● Record the information collected and store it in a ● Deduplication (driver, utility, other binary) ig s n solution (or application) is used http://social.technet.microsoft.com/wiki/ r la database ● ● a s o p Remove dummy configuration information Define type of applications, installation and configuration ti n Output: Raw Application List Output: Rationalized Inventory methods contents/articles/1640.microsoft- For more information about collecting information of Old SQL server using MAP, go to on i R io . f at Output: Categorized Inventory assessment-and-planning-toolkit.aspx http://blogs.technet.com/b/meamcs/archive/2012/09/24/how-to-use-map-tool-microsoft-assessment-and-planning-toolkit.aspx Pl y r atf 3 ig or W 0 e m ms 0 at ac i 2 qu co n r ade rdin do ve an gly ws Ser lish need stab to be er to e Collect information of Link the source classified by their use in ord Other DB to SQL: database from the database and the Tools and Procedures source server using target SQL database Standardize/Prioritize Preparation Inflow Remediation/Packaging 1 MAP Toolkit 3 from SSMA project 4 ● Prioritize solutions (or applications) 5 ● Examine the result of pre-assessment 6 ● Install/configure testing environment with the help ● Microsoft Assessment and Planning ● Check and designate business owner ● Prepare solution (or application) specific of solution (or application) provider and check ● Change installation/configuration steps and (MAP) Toolkit ● Prioritize according to the deployment plan installation/configuration guidelines packaging/deployment methods (if required) ● Output: Raw Application List ● Configure the owner of task Microsoft SQL Server Migration Output: Packaged Applications Output: Apps Ready for Packaging Assistant (SSMA) Install/set SSMA Perform schema mapping ● Collect and check inventory informa- (separate computer) between the source database tion of the 3rd party database (Oracle, 2 and create SSMA 4 and the destination SQL MySQL, Sybase) using MAP Toolkit project database ● Database migration using SSMA Creating Assessment ● SSMA Overview: Load the converted Report: predict objects http://blogs.msdn.com/b/ssma/ database objects into in the source database SQL database Receive Outflow/Initial Testing Acceptance Testing (AT) Deploy/Transition to Users 5 and the time required 7

7 ● Prioritize tasks 8 ● Designate server for AT, and install/configure 9 ● Deploy in the actual operating environment ● Binary packaging, synchronization of document applications ● Update Help Desk knowledge base

● and configuration information, source code Implement test scenarios ● Update documents

clean-up ● Correct errors and approve AT result ● Update IT assets management database Output: Apps Ready for AT Testing Output: Raw Application List Output: Apps Ready for Deployment Convert the source Migrate data in the Install the 3rd party For more information about database migration (Oracle, MySQL, Sybase) using database schema into source database into Use as a database server solution / use as the ● SSMA, go to http://blogs.msdn.com/b/ssma/archive/2014/05/15/sql-server- 6 SQL database schema 8 SQL server migration-assistant-ssma-v5-3-is-now-available.aspx operating server ● SSMA for Oracle: http://www.microsoft.com/en-us/download/details.aspx?id=42655 ● SSMA for MySQL: http://www.microsoft.com/en-us/download/details.aspx?id=42657 With Refactor, Revise, Rebuild and Replace/Retire among With Revise, Rebuild and Replace/Retire among ● SSMA for Sybase: http://www.microsoft.com/en-us/download/details.aspx?id=42654 Gartner’s 5R Platform Migration methods into account Gartner’s 5R Platform Migration methods taken into account

www.microsoft.com/ws2003eos © 2014 Microsoft Corporation. All rights reserved. This document is provided as-is. Information and views expressed in this document, including URL and other website references, may change without notice. You bear the risk of using it. This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may print and use this document for your internal, reference purposes.