Microsoft Official Course
Module 1
Planning Server Upgrade and
Migration
Module Overview
Considerations for Upgrades and Migrations
Creating a Server Upgrade and Migration Plan
• Planning for Virtualization
Lesson 1: Considerations for Upgrades and
Migrations
Windows Server 2012 Editions
Preinstallation Requirements
In-Place Upgrade vs. Server Migration
In-Place Upgrade Scenarios
Benefits of Migrating
Using MAP Toolkit to Plan for Upgrades and
Migrations
Planning For Server Consolidation
Planning For Cloud Server Deployments
• Demonstration: Using the Microsoft Assessment
Windows Server 2012 Editions
Windows Server 2012 R2 editions:
• Standard
• Datacenter
• Foundation
• Essentials
Preinstallation Requirements
Windows Server 2012 has the following minimum
hardware requirements:
• Processor architecture: x64
• Processor speed: 1.4 GHz
• Memory (RAM): 512 MB
• Hard disk drive space: 32 GB
In-Place Upgrade vs. Server Migration
• Upgrading to Windows Server 2012:
• Can upgrade from Windows Server 2008 SP2
• Can upgrade from Windows Server 2008 R2
• Can only upgrade to same or newer editions
• Requires same processor architecture
• Migrating to Windows Server 2012:
• Must migrate from x86 version of Windows Server
• Can use Windows Server Migration Tools feature
In-Place Upgrade Scenarios
Perform an in-place upgrade when:
• Existing servers meet hardware requirements
• Software products installed on an existing server
support an in-place upgrade
• You want to keep existing data and security
permissions
• You want to keep existing roles, features, and
settings
Benefits of Migrating
By performing a migration, you:
• Do not affect your current IT infrastructure with
the initial windows Server 2012 deployment
• Perform software product migration in a separate
environment
• Perform migration of server roles, features, and
settings in a separate environment
• Ensure new operating system enhancements are
installed by default
Using MAP Toolkit to Plan for Upgrades and
Migrations
• You can use MAP Toolkit for Windows Server
2012 to:
• Perform inventory of your organization’s IT
infrastructure
• Generate a report or proposal based on the Windows
Server 2012 Readiness Assessment to plan server
consolidation
• You can use Windows Server Migration Tools to
migrate:
• Server roles, feature, operating system settings, data
and shares
Planning For Server Consolidation
• Analyze if cohosting of multiple roles is supported
• Deploy roles that are not supported for cohosting
on additional servers
• Determine if cohosting multiple roles affects
server performance (it should not)
• Analyze if cohosted roles are supported for high
availability
Planning For Cloud Server Deployments
Use Windows Azure IaaS to:
• Create custom virtual machines in Windows
Azure:
• Deploy the Windows Server 2012 operating system on
virtual machines that are hosted in Windows Azure
• Upload a Windows Server 2012 image template VHD to
Windows Azure
• Upload a preconfigured Windows Server 2012 VHD to
Windows Azure
• Manage virtual machines in Windows Azure
Demonstration: Using the Microsoft Assessment
and Planning Toolkit
In this demonstration you will see how to:
• Review MAP options
• Perform an inventory assessment
• Review inventory from a sample database
Lesson 2: Creating a Server Upgrade and
Migration Plan
Developing a Deployment Plan
Windows Server 2012 Licensing and Activation
Discussion: Planning Volume Activation
Implementing Server Migrations
Implementing Server Migrations Across Domains
• Deploying Servers in the Cloud
Developing a Deployment Plan
When preparing your deployment plan, you
should:
• Analyze your current IT infrastructure
• Choose an appropriate edition of Windows
Server 2012
• Plan the in-place upgrade procedure
• Plan the migration procedure
• Plan the procedure of installing new servers
• Plan for backup, restore, monitoring and
maintenance
Windows Server 2012 Licensing and Activation
Organizations may choose between two activation
strategies
Activation strategy When used
Manual Suitable when deploying small
number of servers
Automatic Suitable when deploying larger
number of servers
Discussion: Planning Volume Activation
Discuss both scenarios. Based on the scenario,
what type of volume activation should you
implement?
10 minutes
Implementing Server Migrations
The roles that you can migrate from supported
earlier editions of Windows Server to Windows
Server 2012 are:
• AD FS Role Services
• Hyper-V
• Network Policy Server
• Print and Document Services
• Remote Access
• WSUS
Implementing Server Migrations Across Domains
When migrating a domain, you should:
• Create a new Windows Server 2012 AD DS forest
• Deploy applications on new servers
• Establish AD DS trust between the current and
the new AD DS forests
• Migrate AD DS objects
• Migrate application data and settings
• Decommission the old AD DS environment
Deploying Servers in the Cloud
Tools for deploying cloud servers include:
• System Center 2012 R2 Virtual Machine Manager
• Windows Azure virtual machine tools
• System Center 2012 R2 App Controller
• Windows PowerShell
Lesson 3: Planning for Virtualization
Considerations for Implementing Virtualization
Which Virtual Licenses are Included?
Guidelines for Configuring Hyper-V Hosts
Guidelines for Designing Virtual Machines
Designing Virtual Machines for Applications
Best Practices for Planning Application
Virtualization
• Discussion: Choosing Between Virtual and Physical
Deployments
Considerations for Implementing Virtualization
When identifying server workloads to virtualize,
consider:
• Hardware requirements
• Compatibility
• Supportability
• Licensing
• Availability requirements
Which Virtual Licenses are Included?
Examples of Windows Server 2012 Virtual Licenses
Windows Server 2012 Standard Total number of virtual machines
edition licenses for servers with
up to two processors
1 2
2 4
3 6
Windows Server 2012 Datacenter Total number of virtual machines
edition licenses for servers with
up to two processors
1 Unlimited
Guidelines for Configuring Hyper-V Hosts
When planning for optimal configuration of
Hyper-V hosts, consider:
• Memory
• Processors
• Storage
• Network
• High availability
• Backup and restore
• Management and monitoring
Guidelines for Designing Virtual Machines
• Standardize the virtual machine configuration
• Plan virtual machines for specific server roles by:
• Monitoring the servers before virtualization
• Configuring each virtual machine with a hardware
configuration that is similar to the hardware required
on a physical server
• Consider other options for ensuring physical
server utilization
Designing Virtual Machines for Applications
When designing virtual machines for applications,
you should:
• Ensure that business-critical applications are
highly available and responsive
• Consider the following applications carefully:
• AD DS
• SQL Server
• Exchange Server
Best Practices for Planning Application
Virtualization
When designing virtual machines for applications,
you should:
• Read the technical documentation
• Apply best practices appropriate to the
applications
• Test in an isolated environment
• Deploy or migrate
• Monitor performance, and edit virtual machine
configuration as required
Discussion: Choosing Between Virtual and
Physical Deployments
• When would you choose to deploy your business
applications or infrastructure services in a virtual
environment?
• Which server roles, features, or application
services do you currently have deployed in your
physical environment
• If you have a virtual environment for your
organization, which do you currently have
deployed in your virtual environment, and why?
10 minutes
Lab: Planning a Server Upgrade and Migration
Exercise 1: Planning a Strategy for Server Upgrade
and Migration
• Exercise 2: Evaluating Candidates for Server
Virtualization
Logon Information
Virtual machines:
• 20413C-LON-DC1
• 20413C-LON-CL1
User name Adatum\Administrator
Password Pa$$w0rd
Estimated Time: 50 minutes
Lab Scenario (1 of 5)
The head office for A. Datum Corporation, based
in London, England, has a mix of Windows Server
2008 and Windows Server 2008 R2 servers. The
AD DS environment is based around Windows
Server 2008 R2 domain controllers.
The regional hub sites (Toronto and Sydney)
predominantly have a Windows Server 2008–
based infrastructure, while the smaller, regional
branches and distribution centers have Windows
Server 2008 servers that support line-of-business
(LOB) applications.
Lab Scenario (2 of 5)
The management team at A. Datum has stipulated
that the new IT infrastructure must be more
efficient with respect to hardware utilization and
power consumption. This suggests that
consolidating server roles and virtualizing
workloads is an important part of the server
upgrade and migration plan.
Lab Scenario (3 of 5)
You have been involved with early discussions
surrounding A. Datum’s likely acquisition of two
companies. This has not been formally announced,
but is likely to occur in the coming months. You
understand that one of these organizations has no
Windows Server infrastructure in place, and you
may be required to develop a strategy for how best
to deploy Windows Server 2012 in that
environment. The second potential acquisition has
a Windows Server 2008 forest.
Lab Scenario (4 of 5)
However, before the server deployment can begin,
you must plan a server upgrade and migration
strategy. This plan will involve determining which
server roles will migrate, which you can consolidate
onto a single server, and whether a given workload
is suitable for virtualization. Initially, you will
perform this analysis on the servers in London and
its perimeter network only. You plan to analyze
Toronto and Sydney later.
Lab Scenario (5 of 5)
During this process, you must remain focused on
optimizing server resources and capacity. In
addition to these mainly technical considerations,
you must consider what implications there may be
with respect to server licensing.
Lab Review
Why would you want to use MAP when planning
your upgrade and migration strategy?
• Why would you choose Windows Server 2012
Datacenter edition for virtualization and
consolidation of both the A. Datum internal and
perimeter networks?
Module Review and Takeaways
Review Question
Real-world Issues and Scenarios
Tools
• Best Practice