Windows_Server_2003_Roles_Migration_Process

Windows Server 2003 Roles Migration Process AsPselasnsmnienngt & START Data Collection Priority & Business Value Analysis High-level Application Portfolio Analysis Target Platform Review High-level Planning High-level Business Case ArchitectureCategorize platforms through discovery, planning & assessment for migration by role; choose one from the 5R (Rehost, ● Migrate the platform into a new infrastructure environment ● Migrate it into a new infrastructure environment in a way that ● Replace the previously used solution with another solutionRefactor, Revise, Rebuild Replace/Retire) platform methods de ned by Gartner and establish an adequate migration ● Change speci c code and/or con guration information to the previously used features and services remain intact or else ● Upgrade the version or rebuild the previously used solution ● It is emotionally/practically di cult to make a decision fromplan accordingly. Gartner’s 5R Platform Migration as it is help ease its adoption within a new infrastructure environ- are improved or features/service in a way that they suit the new infrastruc- ment ture environment the standpoint of IT service team, but it is technically easy ● The simplest platform migration method Rehost Revise● The most complex platform migration method Refactor● Relatively easy way to migrate the platform Rebuild● More complex than Rehost, but easier than Revise Replace/RetireMigration method 1 – Make use of the default roles and features provided by the OS Migration method 2 – Use as web application serverYou 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.Migration tools and 1 Install WSMT on the 3 Create deployment Make use of the roles and Use as a web application Web Deploy v3.5 1 Install Web Deploy 3 Perform pre-configuration onprocedures destination server folders, with which features provided by the OS server Extension on both the the destination server based WSMT works, in the by default ● A tool that simplifies the deployment of web source and destination on dependencies information● Windows Server Migration Tool (WSMT) target server With Refactor, Revise Replace/Retire among Gartner’s applications and websites to the IIS server servers of the source server● Install/set on both source and destination servers With Rehost, Refactor, Replace/Retire among Gartner’s 5R Platform Migration methods taken into account● Migrate the role of server, features, operating 5R Platform Migration methods taken into account ● It helps synchronize IIS servers, or migrate them into newer versions of IIS server system configuration, other data and shared files 2 Copy deployment 4 Register WSMT on the 2 Create information 4 Create a package file into the destination server folders of the destina- source server ● For more information about Web Deploy, visit about the dependencies on the source server tion server into the http://www.iis.net/downloads/microsoft/web-deploy of websites running on and migrate it into the source server the source server 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 Next Step ● A referential guideline is provided for typical migration scenarios among default roles and features of Relatively easy and less complex ● It is recommended that you first test Web Deploy in a test environment, carry out assessment through troubleshooting and then (Case by Case) Windows Server 2003 use it in the actual operating environment because there are a number of things to be considered, including the deployment of 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 DNS need to be considered in the actual operating environment ● This guideline is provided for the IIS server, but you can migrate Java-based WAS and J2EE servers in the same way using the migration tool provided by the relevant solution provider.Active Directory Referential guideline: Active Directory Referential guideline: Make use of theDomain Services http://technet.microsoft.com/library/dd379558.aspx Certi cate Services http://technet.microsoft.com/library/ee126170 default roles and features (WS.10).aspx & DNS provided by the OS DNS is the source server Related DNS records are Deployment check hosting a web farm. updated to point new IIS 7.0 Active Directory Services web farm on the browser. File Server Services ASP.contoso.com Check whether the migrated web applications running Domain Name Server Use as a web 192.168.202.202 on the new production server meet the stability, Referential guideline: Referential guideline: Services application server APS.contoso.com PHP.contoso.com performance and speci c requirements of clientsDHCP Services http://technet.microsoft.com/library/dd379535.aspx File Services http://technet.microsoft.com/library/dd379487.aspx DHCP Services 192.168.202.200 192.168.202.202 through the nal test and sign-o . IIS + .NET PHP.contoso.com Migration check IIS, 7.0, ASP.NET, PHP Java WAS + J2EE IIS 6.0. 192.168.202.195 Etc… ASP.NET 192.168.202.196 Apache, PHP Web application migration Once it is con rmed that new IIS 7.0 web farm works without problem, web applications are migrated into new IIS 7.0 web farm. ApplicationsWindows Server Referential guideline: Local Users and Referential guideline: A copy of web farm is deployed can be migrated individually or as group.Update Services http://technet.microsoft.com/library/hh852339.aspx Group http://technet.microsoft.com/library/dd379531.aspx on IIS 7.0 staging server. Staging server: IIS 7.0, ASP.net, PHP Web application deployment IIS 7.0, ASP.net, PHPWindows Server Migration Information : http://technet.microsoft.com/library/jj134039 WSUS Services Test applications regarding whether they work without any compatibility http://technet.microsoft.com/library/dd365353.aspx problems. Problems can be solved without a ecting production web farm, and Routing & Remote ● Pre-assessment is required Access Services ● The 3rd party software and applications this production web farm will continue to be hosted by the source server. Etc… It is required to collect information and Windows Server 2004 platform migration is not a mere OS upgradeRelatively difficult and more things have to be consideredwork in collaboration with 3rd party use of platform can be largely classified into 4 types as shown above.vendors (provider of 3rd party software and application developers)Migration method 4 – Use as database server ● With simple guidelines, migration Migration method 3 – Install the 3rd party solution / use as the operating serverYou can refer to the technical documentation in the TechNet Library officially provided by Microsoft or work in collaboration with Microsoft Services cannot be performedteam and/or your partners to migrate the database into a newer version or re-configure it while migrating the OS environment. When it comes down to migrating Windows Server 2003 hosting 3rd party solutions (and applications), there are many more things to be considered concerning Use as a database server Install the 3rd party the migration of those solutions (applications) to a new infrastructure environment, rather than the migration of the OS itself, and moreover the procedure andOld SQL to New SQL: 1 Collect SQL informa- 3 Configure SQL on the solution / use as the methodology take on added significance. Microsoft recommends performing migration in 9 steps as shown below. (It is difficult to propose guidelines in broadTools and Procedures tion from the source destination server based on SQL operating server generalities because a number of things must be considered depending on the 3rd party solutions - and applications - installed.) server using MAP the information collected Oracle● Microsoft Assessment and Planning Toolkit using a MAP Toolkit MySQL Groupware 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 (MAP) Toolkit Etc… Portal 3rd party solutions (and applications) are installed: ERP (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-● Capable of collecting and checking CRM tions - or staffing of the client.) inventory information about the SQL Etc… server installed/configured on the source server 2 Install a new SQL 4 Back up the SQL database of Classify Windows Server 2003 Rolesor migration. Platforms accordingly need to be classified by their use in order to establish an adequate migration plan; the 1 Discovery/Raw Inventory 2 Rationalization 3 Categorize server in the destina- the source server and restore● MAP Toolkit Overview & Download: tion server it into SQL running on the ● Collect configuration information of applications ● Define rationalization rules that determine which ● Collect information and binary of solutions (or applications) http://social.technet.microsoft.com/wiki/ destination server and software installed in the current environment software/applications would be migrated ● Determine priorities depending on critical business contents/articles/1640.microsoft- assessment-and-planning-toolkit.aspx For more information about collecting information of Old SQL server using MAP, go to ● Record the information collected and store it in a ● Deduplication (driver, utility, other binary) dependencies and collect information of how much each http://blogs.technet.com/b/meamcs/archive/2012/09/24/how-to-use-map-tool-microsoft-assessment-and-planning-toolkit.aspx database ● Remove dummy configuration information solution (or application) is used Output: Rationalized Inventory ● Define type of applications, installation and configuration Output: Raw Application List methods Output: Categorized InventoryOther DB to SQL: 1 Collect information of 3 Link the source 4 Standardize/Prioritize 5 Preparation Inflow 6 Remediation/PackagingTools and Procedures database from the database and the source server using target SQL database ● Prioritize solutions (or applications) ● Examine the result of pre-assessment ● Install/configure testing environment with the help● Microsoft Assessment and Planning MAP Toolkit from SSMA project ● Check and designate business owner ● Prepare solution (or application) specific of solution (or application) provider and check (MAP) Toolkit ● Prioritize according to the deployment plan Output: Raw Application List installation/configuration guidelines ● Change installation/configuration steps and● Microsoft SQL Server Migration ● Configure the owner of task packaging/deployment methods (if required) Assistant (SSMA) Output: Apps Ready for Packaging Output: Packaged Applications● Collect and check inventory informa- tion of the 3rd party database (Oracle, 2 Install/set SSMA 4 Perform schema mapping MySQL, Sybase) using MAP Toolkit (separate computer) between the source database and create SSMA and the destination SQL● Database migration using SSMA project database● SSMA Overview: 5 Creating Assessment 7 Load the converted 7 Receive Outflow/Initial Testing 8 Acceptance Testing (AT) 9 Deploy/Transition to Users http://blogs.msdn.com/b/ssma/ Report: predict objects database objects into in the source database SQL database ● Prioritize tasks ● Designate server for AT, and install/configure ● Deploy in the actual operating environment and the time required ● Binary packaging, synchronization of document applications ● Update Help Desk knowledge base ● Update documents 6 8 Migrate data in the Install the 3rd party and configuration information, source code ● Implement test scenarios ● Update IT assets management database source database into solution / use as the clean-up ● Correct errors and approve AT result Output: Apps Ready for Deployment SQL server operating server Output: Apps Ready for AT Testing Output: Raw Application List For more information about database migration (Oracle, MySQL, Sybase) using Convert the source Use as a database server With Revise, Rebuild and Replace/Retire among● SSMA, go to http://blogs.msdn.com/b/ssma/archive/2014/05/15/sql-server- database schema into Gartner’s 5R Platform Migration methods taken into account SQL database schema With Refactor, Revise, Rebuild and Replace/Retire among Gartner’s 5R Platform Migration methods into accountmigration-assistant-ssma-v5-3-is-now-available.aspx● 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● SSMA for Sybase: http://www.microsoft.com/en-us/download/details.aspx?id=42654 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.