View
275
Download
3
Tags:
Embed Size (px)
Citation preview
Introduction to Windows Server Migration Tools
Agenda
Windows Server 2008 R2 Migration ToolsMigration GuidelinesWindows Server MigrationMigrating Server Roles
ADDSDNSDHCPPrint File
Migration vs. In-Place UpgradeMigration moves configurations and
dataSources an existing serverTargets 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 forwardJust the OS is replaced
Benefits of MigrationProvides 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 stabilityReduces risk and downtime
OS installation and most migration tasks are performed while the source server is still liveAllows migration verification and performance benchmarking prior to bringing the target server “online”Source server remains available if migration fails
Migration GuidelinesEnd-to-end instructions for all phases:
PreparationMigrationValidationRollbackPost migration steps (finalize, retire source server)
Focused on minimizing downtime and changes to the source serverUtilize both new and existing tools
TechNet PortalSingle place for all Windows Server 2008 R2 migration informationProvides 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://www.microsoft.com/migration
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
Supported ScenariosSource Server OS WS03, WS03R2, WS08 Full, WS08 R2
Full, WS08R2 Server Core
Source Server Architecture
x86 or x64
Source Server Platform Physical or Virtual
Destination Server OS WS08R2, x64; Full Server, Server Core; Physical, Virtual
Server Roles ADDS, DHCP, DNS, File, Print
Server Features BranchCache ™
Settings and Data Local Users and Groups, IP Configuration (IPv4 and IPv6), Data and Shares
Destination Server SetupWindows Server 2008 R2
Step 1
Add the Windows Server Migration Tools Feature
Step 2
Generate Windows Server Migration Tools deployment folder for appropriate source OS
Step 3
Use 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 2
Install prerequisites:Microsoft .NET Framework 2.0 or higherWindows PowerShell 1.0 or higher
Step 3
Copy the Windows Server Migration Tools deployment folder locally
Step 4
Register 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 2
Install prerequisites:Windows PowerShell 1.0 or higher
Step 3
Copy the Windows Server Migration Tools deployment folder locally
Step 4
Register 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
Windows Server Migration
Get-SmigServerFeature Discovers features available for migration and features in the migration store available for import
Export-SmigServerSetting
Exports specified role, feature and OS settings to a migration store
Import-SmigServerSetting
Imports specified role, feature and OS settings from a migration store
Send-SmigServerData Transfers data and shares preserving local and domain permissions
Receive-SmigServerData
Receives transferred data
Active Directory & DNS MigrationPre-Migration
Step 1
Verify that the number of NICs match on the source and destination servers
Step 3 Step 4
Proceed to Migration
Step 2
On the Source:Back upCollect migration data
On the Destination:Install OSAssign temporary name and IPJoin domain
Active Directory & DNS MigrationMigration
Step 1
Make the Destination Server a domain controller
Step 3 Step 4
Perform verification steps
Step 2
Manually migrate the DNS settingsTransfer FSMO roles
Migrate IP addresses and rename Source and Destination servers
Active Directory & DNS MigrationPost-Migration
Step 1
Troubleshoot migration if necessary
Step 3Step 2
Roll back migration if necessary
Retire Source Server if migration successful
Internet Protocol Migration
Step 1
Prepare the source and destination servers
Step 2
Export IP configuration settings from source server and import to destination server
Step 3
Migrate IPv6 configuration manually
Step 4
VerifyTroubleshootRoll back
DHCP MigrationPre-Migration
Step 1
Verify that the number of NICs match on the source and destination servers
Step 3 Step 4
Proceed to Migration
Step 2
On 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 cmdletUnauthorize DHCP
Step 3 Step 4
Authorize the DHCP server
Step 2
On 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 2
Roll back migration if necessary
Retire Source Server if migration successful
Print Server Migration
Pre-MigrationAccess 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
File Server MigrationPre-Migration
Step 1
On the Source:Back up full server or system stateIf you are migrating DFS, back up ADDS
Step 3 Step 4
Notify users and ask them to stop using the serverProceed to migration
Step 2
Inventory 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
File Server MigrationMigration
Step 1
On the Source:Freeze administrative changesExport settings
Step 3 Step 4
On the Destination:Configure DFS replicationImport settings
Step 2
Migrate 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 MigrationPost-Migration
Step 1
Verify the migration
Step 3Step 2
Troubleshoot migration if necessary
Roll back migration if necessary
Step 4
Retire Source Server if migration successful
LAB
Setting up Windows Server Migration ToolsPreparing and Migrating DHCPPreparing and Migrating File Services
Summary
Windows Server Migration ToolsMigration Guidelines
TechNet PortalInfrastructure Services MigrationPrinter and File Share Migration
Q & A
© 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.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.