t& Priority & Business Value Analysis Target Platform Review

Windows Server 2003 Roles Migration Process Assessmen START Data Collection
High-level Business Case
High-level Application Portfolio Analysis
Architecture
High-level Planning
Planning
●
Migrate the platform into a new infrastructure environment ●
Change specific code and/or configuration 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,
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 difficult to make a decision from
Gartner’s 5R Platform Migration
●
Refactor, Revise, Rebuild Replace/Retire) platform methods defined by Gartner and establish an adequate 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

Migration tools and Use as a web application
Create deployment features provided by the OS Install Web Deploy

1 3 1 3
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
target server servers 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

2 4 2 4
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
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 Relatively easy and less c

omp
(Case by Case) ● A referential guideline is provided for typical migration scenarios among default roles and features of lex ● It is recommended that you first test Web Deploy in a test environment, carry out assessment through troubleshooting and then
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.

Active Directory Referential guideline: Active Directory

Referential guideline:
Domain Services http://technet.microsoft.com/library/ee126170
& DNS
http://technet.microsoft.com/library/dd379558.aspx Certificate Services
(WS.10).aspx
Make use of the
Related DNS records are
default roles and features DNS is the source server
hosting a web farm. updated to point new IIS 7.0 Deployment check
web farm on the browser.
provided by the OS ASP.contoso.com Check whether the migrated web applications running
Referential guideline: Referential guideline: Use as a web APS.contoso.com
192.168.202.202
PHP.contoso.com
on the new production server meet the stability,
DHCP Services File Services ▶Active Directory Services 192.168.202.200 performance and specific requirements of clients
http://technet.microsoft.com/library/dd379535.aspx http://technet.microsoft.com/library/dd379487.aspx application server IIS 6.0.
ASP.NET
PHP.contoso.com
192.168.202.195 Migration check
192.168.202.202
IIS, 7.0, ASP.NET, PHP through the final test and sign-off.
▶File Server Services 192.168.202.196

▶IIS + .NET
Apache, PHP
Once it is confirmed that new IIS 7.0 web farm
▶Domain Name Server works without problem, web applications are
▶Java WAS + J2EE
Windows Server Referential guideline: Local Users and Referential guideline: Services A copy of web farm is deployed
on IIS 7.0 staging server.
migrated into new IIS 7.0 web farm. Applications
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 affecting production web farm, and
http://technet.microsoft.com/library/dd365353.aspx ▶Routing & Remote this production web farm will continue to be hosted by the source server.
●
Pre-assessment is required
Access Services ●
The 3rd party software and applications
▶Etc… It is required to collect information and

own above.
work in collaboration with 3rd party
Windows Ser ve

sidered vendors (provider of 3rd party software

and application developers)
●
With simple guidelines, migration

pes as sh
be con

Migration method 4 – Use as database server cannot be performed

Migration method 3 – Install the 3rd party solution
r 2004

Install the 3rd party / use as the operating server

to

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

o 4 ty
have

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

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

d int
operating server
s

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

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

sifie
▶SQL ▶Groupware generalities because a number of things must be considered depending on the 3rd party solutions - and applications - installed.)
ore

clas
igra

▶Portal
dm

▶Oracle

1 3
Collect SQL informa- Configure SQL on the
Old SQL to New SQL: 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
tion

tion from the source destination server based on

ely
n

3rd party solutions (and applications) are installed:

Tools and Procedures ▶MySQL ▶ERP
a

server using MAP the information collected

larg
ult

(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-
is n

Toolkit using a MAP Toolkit

c

▶Etc… ▶CRM tions - or staffing of the client.)

i

be
f
ot

dif

●
Microsoft Assessment and Planning

can
a

ly

▶Etc…
me

ive

(MAP) Toolkit

m
t
re

la

Capable of collecting and checking

for
●
Re

1 2 3
OS

Cl
inventory information about the SQL Discovery/Raw Inventory Rationalization Categorize

lat
2 4 s
Back up the SQL database of
up

fp
server installed/configured on the Install a new SQL

as e
the source server and restore

eo
gr

l
source server server in the destina- Collect configuration information of applications Define rationalization rules that determine which Collect information and binary of solutions (or applications)
ad

it into SQL running on the ● ● ●

us
or
o
tion server e and software installed in the current environment software/applications would be migrated Determine priorities depending on critical business

sif
e

th
●

● MAP Toolkit Overview & Download: destination server

m dependencies and collect information of how much each

R
igr n; ●Record the information collected and store it in a ● Deduplication (driver, utility, other binary) solution (or application) is used
http://social.technet.microsoft.com/wiki/
pla
y
ati database

3
●Remove dummy configuration information ● Define type of applications, installation and configuration

on n
0
contents/articles/1640.microsoft- Output: Raw Application List

Win tio
Output: Rationalized Inventory methods
For more information about collecting information of Old SQL server using MAP, go to
.P
0 gra
Output: Categorized Inventory

2
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 lat i
dows Ser ver
for m
ms
acc quate
e
ord
ingl h an ad
y need lis
to be c estab
Collect information of Link the source lassified by their use in order to

1 3
Other DB to SQL: database from the database and the

4 5 6
Tools and Procedures source server using target SQL database Standardize/Prioritize Preparation Inflow Remediation/Packaging
MAP Toolkit from SSMA project
● Prioritize solutions (or applications) ● Examine the result of pre-assessment ● 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
(MAP) Toolkit ● Prioritize according to the deployment plan installation/configuration guidelines ● Change installation/configuration steps and

packaging/deployment methods (if required)

●
Microsoft SQL Server Migration Output: Raw Application List ● Configure the owner of task
Output: Packaged Applications
Output: Apps Ready for Packaging
Assistant (SSMA)

2 4
Install/set SSMA Perform schema mapping
●
Collect and check inventory informa- (separate computer) between the source database
tion of the 3rd party database (Oracle, and create SSMA and the destination SQL
MySQL, Sybase) using MAP Toolkit project database
●
Database migration using SSMA
Creating Assessment

5 7
●
SSMA Overview: Load the converted
Report: predict objects database objects into
http://blogs.msdn.com/b/ssma/

7 8 9
in the source database SQL database Receive Outflow/Initial Testing Acceptance Testing (AT) Deploy/Transition to Users
and the time required
● Prioritize tasks ● Designate server for AT, and install/configure ● 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
Install the 3rd party Output: Apps Ready for Deployment

6 8
Convert the source Migrate data in the
●
For more information about database migration (Oracle, MySQL, Sybase) using
SSMA, go to http://blogs.msdn.com/b/ssma/archive/2014/05/15/sql-server-
database schema into
SQL database schema
source database into
SQL server
Use as a database server solution / use as the
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.