다음을 통해 공유

IT Camp Follow Up for Los Angeles (March 15, 2012) and Phoenix (March 16, 2012) – Part 2

  • 아티클

In Part 1, I provided the three PowerPoint Decks used so far.  In Part 2, I will provide a recap of the key commands for the Server Migration Tools as well as the commands for setting up the Boot to VHD that we used in the Hands-On Labs at the end of the day.  To get the full documentation on the Server Migration Tools, go here: https://technet.microsoft.com/en-us/library/dd365353(v=WS.10).aspx.  I’m pretty sure there are more things I need to follow up on, but my brain is so whacked right now, I can’t remember what else I need to provide.  Please let me know what else I need to provide and I will compile a Part 3 and get that posted out.  Thanks!!

Server Migration Tools

To add the Windows Server Migration Tools Feature to your Windows Server 2008 R2 machine, you would type the following commands from a PowerShell prompt

  • Import-Module ServerManager
  • Add-WindowsFeature Migration

Once the feature is added, start a command prompt and navigate to %Windir%\System32\ServerMigrationTools.  Execute SmigDeploy.exe with the appropriate options to create the Source OS Package for the version of the OS you are running on the Source Server (Windows Server 2003, Windows Server 2008, x86, x64, etc.).  Here are some examples:

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>

In my demo, I used the first one and specified a deployment path of C:\Labfiles\Source.  This will create the necessary files to be used on the Source Server that you will be migrating away from. 

On your Source Server, you need to have .NET Framework 2.0 or higher and PowerShell 1.0 or higher.  In my demo, I had to install PowerShell 1.0 since I was running Windows Server 2003.  I also copied the Source files from the previous step to the local server and ran SmigDeploy.exe on the Windows Server 2003 machine to register the tools.

In my demo, I performed a DHCP migration.  Below are the commands I executed on the Source 2003 Server.

  • Export-SmigServerSetting –FeatureID DHCP –User All –Group –IPConfig –Path \\server1\labfiles\migrationdata\dhcp –Verbose
    • For your path, you would specify a location that is appropriate for you.
  • ipconfig /all >\\server1\labfiles\migrationdata\dhcp\ipconfig.txt
    • I issued this command and saved the output so I can grab the MAC address in a later step

On the destination server, I was running a copy of Windows Server 2008 R2 Core and I ran the following commands on that server.

Command line

  • start /w ocsetup NetFX2-ServerCore
  • start /w ocsetup ServerMigration

PowerShell

  • Import-Module ServerManager
  • Add-WindowsFeature Migration
  • Add-PSSnapin Microsoft.Windows.ServerManager.Migration
  • Import-SmigServerSetting -featureid DHCP -User All -Group -IPConfig All -SourcePhysicalAddress <SourcePhysicalAddress> -TargetPhysicalAddress <TargetPhysicalAddress> -Force -path \\server1\labfiles\migrationdata\dhcp –Verbose
    • I replaced the <SourcePhysicalAddress> with the MAC address of the 2003 Server and the <TargetPhysicalAddress> with the MAC address of the 2008 R2 Core Server

Before starting the DHCP Server service and authorizing it with AD, be sure to Unauthorize the DHCP server on the 2003 box and delete it.

In the Hands-On Lab, I walked everyone through the steps to configure their computer to Boot to VHD.  Below are the steps for your records.

  • bcdedit /copy {current} /d "Windows Server 2008 R2 SP1 (VHD Boot)"
  • bcdedit /set {CLSID} device vhd=[c:]\vhd\server08r2sp1.vhd
  • bcdedit /set {CLSID} osdevice vhd=[c:]\vhd\server08r2sp1.vhd
  • bcdedit /set {CLSID} detecthal on
    • In the first command, everything between the set of double quotes will appear as the name of the boot menu option
    • {CLSID} is replaced with the output from the first command
    • The second and third command is based on the VHD file being located in the VHD directory of your C Drive with the file named server08r2sp1.vhd. You would use the directory and name that is appropriate for your situation.
    • To delete the entry when you no longer need it, please run msconfig.exe and go to the boot tab and highlight the entry you no longer want and delete it.