Windows Server Migration

Migration vs. In-Place Upgrade• Migration moves configurations and data

– Sources an existing server– Targets a computer with a clean installation of an Operating System

• In-place Upgrade replaces the Operating System on an existing computer– Configurations and data are carried forward– Just the OS is replaced

Benefits of Migration• 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)

• Clean operating system installs exhibit more stability• Reduces risk and downtime

– OS installation and most migration tasks are performed while the source server is still live– Allows migration verification and performance benchmarking prior to bringing the target

server “online”– Source server remains available if migration fails

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

Destination Server

ImportSetting

s

ExportSetting

s

Import-SmigServerSettingReceive-SmigServerData

Migration GuidelinesTechNet Migration Portal

Migration Process Overview

Temp Storage

Transfer Configuration and Shares

Source Server

Export-SmigServerSettingSend-SmigServerData

Discover

Prepare

Migration Server Setup

Destination Server SetupWindows Server 2008 R2

Step 1• Add the Windows

Server Migration Tools Feature

Step 2Generate Windows Server Migration Tools deployment folder for appropriate source OS

Step 3Use SmigDeploy with appropriate switches

Use SmigDeploy.exe located at %Windir%\System32\ServerMigrationTools\SmigDeploy.exe /package /architecture X86 /os WS03 /path <deployment folder path>SmigDeploy.exe /package /architecture amd64 /os WS03 /path <deployment folder path>SmigDeploy.exe /package /architecture X86 /os WS08 /path <deployment folder path>SmigDeploy.exe /package /architecture amd64 /os WS08 /path <deployment folder path>

Source Server SetupWindows Server 2003 SP2 / R2

Step 1• Ensure sufficient disk

space for the Windows Server Migration Tools deployment folder (~25MB)

Step 2Install prerequisites:

Microsoft .NET Framework 2.0 or higherWindows PowerShell 1.0 or higher

Step 3Copy the Windows Server Migration Tools deployment folder locally

Step 4Register the Windows Server Deployment Tools

Navigate to the location where you copied the Windows Server Migration Tools deployment folder SMT_ws03_amd64 or similarRun .\SmigDeploy.exe

Source Server SetupWindows Server 2008 Full

Step 1• Ensure sufficient disk

space for the Windows Server Migration Tools deployment folder (~23MB)

Step 2Install prerequisites:

Windows PowerShell 1.0 or higher

Step 3Copy the Windows Server Migration Tools deployment folder locally

Step 4Register the Windows Server Deployment Tools

Open an elevated command promptNavigate to the location where you copied the Windows Server Migration Tools deployment folder SMT_ws08_X86 or similarRun .\SmigDeploy.exe

File Server Migration

File Server MigrationPre-Migration

Step 1• On the Source:– Back up full server

or system state– If you are migrating

DFS, back up ADDS

Step 3 Step 4Notify users and ask them to stop using the serverProceed to migration

Step 2Inventory files, settings, DFS namespaces and replication settings to be migratedDetermine the File Services installed

On the Destination:Install OS and migration toolsJoin domainInstall the same File Services

Step 1On the Source:

Freeze administrative changesExport settings

Step 3 Step 4On the Destination:

Configure DFS replicationImport settings

Step 2Migrate local Users and GroupsMigrate the data from source to destination servers twice*

Migrate server identityOptional – Migrate IP address

*On the Destination server run:Receive-SmigServerData

On the Source server run: Send-SmigServerData -ComputerName <DestinationServer> -SourcePath d:\users -DestinationPath d:\shares\users -Recurse -Include All -Force

File Server Migration

File Server MigrationPost-Migration

Step 1• Verify the migration

Step 3Step 2Troubleshoot

migration if necessary

Roll back migration if necessary

Step 4Retire Source Server if migration successful

DHCP Migration

DHCP MigrationPre-Migration

Step 1• Verify that the

number of NICs match on the source and destination servers

Step 3 Step 4Proceed to Migration

Step 2On the Source:

Back upInstall the migration toolsRegister the migration toolsStop the DHCP service

On the Destination:Install OS and migration toolsJoin domainOptional – install DHCP and stop the service

DHCP MigrationMigration

Step 1• On the Source:– Use Export-

SmigServerSetting cmdlet

– Unauthorize DHCP

Step 3 Step 4Authorize the DHCP server

Step 2On the Destination:

Use Import-SmigServerSetting cmdlet

On the Destination:

Set the DHCP server service to start automaticallyStart the service

DHCP Migration Post-Migration

Step 1• Troubleshoot

migration if necessary

Step 3Step 2Roll back migration if necessary

Retire Source Server if migration successful

Print Server Migration

Print Server Migration

Pre-Migration

Access migration toolsPrepare source server

Migration

Back up printer settings on source serverRestore printer settings to the destination serverMigrate server identity

Post-Migration

Verify the migrationIf problems, troubleshoot migrationRoll back migrationIf successful, retire source server