共用方式為

Step-By-Step: Migrating a Windows Server 2003 file server, NTFS and Share Rights to Windows Server 2012 R2

  • 發行項

 

MigrateFileServer

With time ticking in regards to end of support on Windows Server 2003, most IT professionals are in the midst of planning their migration. While most are focusing on migrating Active Directory and DHCP, some have expressed interest in migrating file services as well. Windows Server 2012 R2 provides a robust solution in terms of file services for organizations to take advantage of. Hence the creation of this Step-By-Step to further assist the process.

Step 1: Prepping the new Windows Server 2012 R2 machine

  1. Via Server Manager, navigate to Manage > Add Roles and Features
     

  2. Click Next until the Select Features screen is visible
     

  3. Ensure PowerShell 4.0 and ISE are installed
     

  4. Select Windows Server Migration Tools and click Next

    Windows_Server_2003_File_Share_Migration

    Note: The Windows Server Migration Tools include additional cmdlets that assist in the migration of server roles, OS settings files and shares from legacy Windows Servers
     

  5. Click Install

    Note: A reboot of this server might be required

Step 2: Generating the necessary PowerShell files for Windows Server 2003

  1. On the Windows Server 2012 R2 machine, open PowerShell in Administrator mode and type the following:

    SmigDeploy.exe /package /architecture X86 /os WS03 /path <deployment folder path>

    Note: Insert your desired path replacing deployment folder path in the script above
     

  2. Create the C:\MigratingTools folder on the Windows Server 2003 machine
     

  3. Copy the content from Windows Server 2012 R2 folder <deployment folder path> to the Windows Server folder C:\MigratingTools\
     

  4. On the Windows Server 2003 machine in the C:\MigratingTools folder, run SMIGDEPLOY.EXE
     

  5. On the Windows Server 2003 machine in the C:\MigratingTools\SMT_ws03_x86\ folder, click & run ServerMigration.pcs1

Step 3: Completing the migration

  1. On the Windows Server 2012 R2 machine, still running PowerShell in Administrator mode and type the following:

    Add-PSSnapin Microsoft.Windows.ServerManager.Migration
    Get-Command -Module Microsoft.Windows.ServerManager.Migration
    Receive-SmigServerData
     

  2. Enter a desired migration password when prompted
     

  3. On the Windows Server 2003 machine, open PowerShell in Administrator mode and type the following:

    Send-SmigServerData -ComputerName "Computer Name" -DestinationPath "X:\Users" -Include All -SourcePath "F:\users" -Recurse

    Note: Insert your Windows Server 2012 R2’s name replacing Computer Name in the script above
     

  4. On the Windows Server 2003 machine, open the registry editor and navigate to HKEY_LOCAL_MACHINE>SYSTEM>CurrentControlSet>Services>LanmanServer>Shares
     

  5. Right-click on the Share Key and select Export
     

  6. Save the exported key to a folder accessible by the Windows Server 2012 R2 machine
     

  7. On the Windows Server 2012 R2 machine, right-click the saved registry file exported from the Windows Server 2003 machine and select Merge
     

  8. Restart the Windows Server 2012 R2 machine

    Note: If your new server uses different drive allocations than the Windows 2003 Server, run the registry editor on the Windows Server 2012 R2 machine > navigate to HKEY_LOCAL_MACHINE>SYSTEM>CurrentControlSet>Services>LanmanServer>Shares and click on the share in question. Edit the Multi-String Path value to refect the new drive allocation

Comments

  • Anonymous
    November 03, 2014
    I am surprised when I see blogs about moving file shares and I see no mention Windows file server migration toolkit 1.2? Works great, lets you move multiple shares at once (Including DFS), cleans up ACLs, does a Finalize phase which takes down old share copies any data that changes during initial copy, and has the ability to pause a "project" to open and pick up at a later date remebering all the settings. Oh and its a Microsoft tool:

    http://www.microsoft.com/en-us/download/details.aspx?id=10268

    Any reason no mention here?
    • Anonymous
      March 07, 2017
      Does the toolkit support migration from a 2008 file server to a 2012 R2 server? It doesn't state support for 2012.
  • Anonymous
    November 05, 2014
    The comment has been removed
  • Anonymous
    June 17, 2016
    On Step 3, between items 6 and 7 there should be an extra step if the source and target drives do not have the same drive letter:Edit the exported regsty file using notepad and replace all instances of the original drive letter (F:) for the destination drive letter (X:). Save the file.Regards,Fred
    • Anonymous
      June 17, 2016
      Sorry. You noted that. Good article!!!
  • Anonymous
    February 13, 2017
    The comment has been removed