IT Camp Content. Overview of Server Migration Tools to get from Windows Server 2003 (or newer) to Windows Server 2008 R2. The migration tools are valid for core Windows infrastructure components such as Certificate Services, DHCP, File and Print, etc. This deck covers the basic setup and walks through File and Print and DHCP migration.

1. Windows Server Migration

2. 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

3. 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

4. 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

5. Migration Process Overview
TechNet Migration Portal Migration Guidelines
Discover Prepare
Temp Storage
Export Import
Source Server Settings Settings
Destination Server
Transfer
Configuration
Export-SmigServerSetting and Shares Import-SmigServerSetting
Send-SmigServerData Receive-SmigServerData

6. Migration Server Setup

7. Destination Server Setup
Windows Server 2008 R2
Step 1 Step 2 Step 3
• Add the Windows Generate Use SmigDeploy
Server Migration Windows Server with appropriate
Tools Feature
Migration Tools switches
deployment
folder for
appropriate
source OS
Use SmigDeploy.exe located at %Windir%System32ServerMigrationTools
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>

8. Source Server Setup
Windows Server 2003 SP2 / R2
Step 1 Step 2 Step 3 Step 4
• Ensure sufficient Install prerequisites: Copy the Register the
disk space for the Microsoft .NET Windows Server Windows Server
Windows Server Framework 2.0 or
Migration Tools Migration Tools Deployment Tools
higher deployment
deployment
folder (~25MB) Windows folder locally
PowerShell 1.0 or
higher
Navigate to the location where you copied the Windows Server Migration Tools deployment folder
SMT_ws03_amd64 or similar
Run .SmigDeploy.exe

9. Source Server Setup
Windows Server 2008 Full
Step 1 Step 2 Step 3 Step 4
• Ensure sufficient Install Copy the Register the
disk space for the prerequisites: Windows Server Windows Server
Windows Server
Migration Tools Windows Migration Tools Deployment Tools
deployment PowerShell 1.0 deployment
folder (~23MB) or higher folder locally
Open an elevated command prompt
Navigate to the location where you copied the Windows Server Migration Tools deployment folder
SMT_ws08_X86 or similar
Run .SmigDeploy.exe

10. File Server Migration

11. File Server Migration
Pre-Migration
Step 1 Step 2 Step 3 Step 4
• On the Source: Inventory files, On the Destination: Notify users and
– Back up full server settings, DFS Install OS and ask them to stop
or system state namespaces and migration tools using the server
– If you are migrating replication settings
DFS, back up ADDS Join domain Proceed to
to be migrated
Install the same migration
Determine the File File Services
Services installed

12. File Server Migration
Step 1 Step 2 Step 3 Step 4
On the Source: Migrate local Migrate server On the
Freeze Users and Groups identity Destination:
administrative Migrate the data Optional – Configure DFS
changes from source to Migrate IP replication
Export settings destination address Import settings
servers twice*
*On the Destination server run:
Receive-SmigServerData
On the Source server run:
Send-SmigServerData -ComputerName <DestinationServer> -SourcePath d:users -DestinationPath
d:sharesusers -Recurse -Include All -Force

13. File Server Migration
Post-Migration
Step 1 Step 2 Step 3 Step 4
• Verify the migration Troubleshoot Roll back Retire Source
migration if migration if Server if
necessary necessary migration
successful

14. DHCP Migration

15. DHCP Migration
Pre-Migration
Step 1 Step 2 Step 3 Step 4
On the Source: On the Destination: Proceed to
• Verify that the
Back up Install OS and Migration
number of NICs
Install the migration migration tools
match on the tools
source and Register the migration
Join domain
destination tools Optional – install
servers Stop the DHCP service DHCP and stop the
service

16. DHCP Migration
Migration
Step 1 Step 2 Step 3 Step 4
• On the Source: On the On the Authorize the
– Use Export- Destination: Destination: DHCP server
SmigServerSetting
cmdlet Use Import- Set the DHCP
– Unauthorize DHCP SmigServerSetti server service to
ng cmdlet start
automatically
Start the service

17. DHCP Migration
Post-Migration
Step 1 Step 2 Step 3
• Troubleshoot Roll back Retire Source
migration if necessary
migration if Server if
necessary migration
successful

18. Print Server Migration

19. Print Server Migration
Pre-Migration Migration Post-Migration
Access migration tools Back up printer settings Verify the migration
Prepare source server on source server If
Restore printer settings to problems, troubleshoot
the destination server migration
Migrate server identity Roll back migration
If successful, retire
source server