Windows® Server 2008 R2: New Server Deployment and Migration

PRESENTER NAMETITLEDATE

Agenda

Windows Server 2008 R2 Migration Tools

Migrating Infrastructure Servers (AD, DNS & DHCP)

Migration Guidelines

Migrating File & Print Servers

Migration vs. In-Place Upgrade

Server migration is the process of migrating server configuration and data to a new server with a clean installed operating system

In-place upgrade assumes installation of a new operating system to replace the existing one on the same server

Benefits of Migration

Clean operating system installs exhibit more stability

Reduces risk and downtime Operating system installation and most migration tasks

are performed while the old server is still operational Allows verification of migration and benchmark

performance before switching to the new server Old server remains available if migration fails

Provides a transition path from: x86 to x64 OS (WS08R2 is x64 only) Physical to virtual (and vice versa) Full server to server core (and vice versa)

Destination Server

Import-SmigServerSettingReceive-SmigServerData

ImportSettings

Migration Guidelines

Prepare

TechNet Migration Portal

Migration Process Overview

Temp Storage

Discover

ExportSettings

Transfer Data & Shares

Source Server

Export-SmigServerSettingSend-SmigServerData

Supported Scenarios

Note: Migrations from x86 to x64, between physical and virtual, between full

server and server core are supported 32-bit applications are still supported on 64-bit platforms

Source Server OS

Category Supported

WS03, WS03R2, WS08, WS08R2, x86, x64; full server, WS08R2 server core; physical, virtualWS08R2, x64; full server, server core; physical, virtual

ADDS, DHCP, DNS, File, Print. Additional roles considered post RTM

BranchCache™

Local Users and Groups, IP Configuration (IPv4 and IPv6)

Destination Server OS

Server Roles

Server Features

OS Settings

Migration Guidelines

End-to-end instructions for all phases: Preparation Migration Validation Rollback Post migration steps (finalize, retire source server)

Focused on minimizing downtime and changes to the source server

Utilize both new and existing tools

TechNet Portal

Single place for all Windows Server 2008 R2 migration information

Provides links to important related docs and tools (e.g. Infrastructure Assessment and Planning, Solution Accelerators)

Links to the related community content (migration forums, blogs, tools and scripts)

Located at: http://go.microsoft.com/fwlink/?LinkID=128554 Search TechNet for “Migrate to Windows Server 2008

R2”

Windows Server 2008 R2Migration Guides

demo

Destination Server

ImportSettings

Windows Server Migration

Get-SmigServerFeature

Migration cmdlet Supported

Discovers features available for migration, and features in the migration store available for import

Exports specified role, feature, and operating system settings to a migration store

Imports specified role, feature, and operating system settings from a migration store

Transfers data and shares preserving local and domain permissions

Receives transferred data

Export-SmigServerSetting

Import-SmigServerSetting

Send-SmigServerData

Receive-SmigServerData

Import-SmigServerSettingReceive-SmigServerData

Temp Storage

Source Server

ExportSetting

s

Transfer Data & Shares

Export-SmigServerSettingSend-SmigServerData

Installing Migration ToolsA Tour

Demo

Active Directory & DNS Migration

Pre-Migration

Migration planning Number of NICs

(network interface cards)

Prepare source server Back up Collect migration

data

Prepare destination server

Install Windows® Server 2008 R2

Assign temporary server name

Assign temporary IP address

Join domain

Migration

Make destination server a domain controller

Manually migrate DNS server settings

Transfer FSMO roles Migrate IP address

and rename servers Perform verification

steps

Post-Migration

(Optional) Retire source server Roll back migration Troubleshoot

migration

Internet Protocol Migration

Prepare the source and destination servers

Step 1

Export IP configuration settings from source server and import to destination server

Step 2

Migrate IPv6 configuration manually

Step 3

Verify

Roll back

Troubleshoot migration

Step 4

DHCP Migration

Pre-Migration Migration planning

Post-Migration (Optional)

Verify the

migration

Migration

Export DHCP server settings

Unauthorize the source server

Prepare source server

Retire source server

Import DHCP server settings

Authorize the destination

server

Prepare destination

server

Roll back and troubleshoot

migration

DHCP Migration

demo

File Server Migration

Pre-Migration

Prepare source server

Prepare destination server

Prepare other computers

Migration

Freeze configuration

Export settings

Migrate local users\groups

Migrate data

Migrate server identity

Configure DFS replication

Import settings

Post-Migration

Verify the migration

Retire source server

Roll back migration

Troubleshoot migration

Print Server Migration

Pre-Migration

Access migration tools

Prepare source server

Migration

Back up printer settings on the source server

Restore printer settings to the destination server

Migrate server identity

Post-Migration

Verify the migration

Retire source server

Roll back migration

Troubleshoot migration

Learn More About Windows Server 2008 R2

Technical Resources

The New Efficiency Virtual Launch Experience www.thenewefficiency.com

Windows Server 2008 R2 evaluation www.microsoft.com/ws08eval

Windows Server TechCenter http://technet.microsoft.com/windowsserver

Get Hands on Training

Training Offers—Exclusive for Launch Attendees www.microsoft.com/learning/careeroffers

Windows Server 2008 Learning Resources www.microsoft.com/windowsserver2008/en/us/learning.aspx

Community Resources

Windows Server Division blog http://blogs.technet.com/windowsserver/

Windows Virtualization Team blog http://blogs.technet.com/virtualization/

Windows Server forums http://social.technet.microsoft.com/Forums/en-US/category/windowsserver

© 2009 Microsoft Corporation. All rights reserved. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the

date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.