List of supported Operating System’s and migration scenarios is listed here. In my case I am going to migrating a WSUS deployment from Server 2008 R2 running SQL 2005 to Server 2012 Standard with SQL 2008 R2 SP1.
Review considerations and system requirements can be found here.
First step is to install and configure the OS according to your organization’s standards (including updates). Second step is to install SQL 2008 R2 with SP1.
After launching Setup from the .ISO file I got the error below. Select Run the program without getting help.
Of course, then I just got the error below. Back to the drawing board! Open up Server Manager and install the .NET Framework 3.5 Feature Role using your Windows installation media.
Open up Server Manager and install the .NET Framework 3.5 Feature Role using your Windows installation media. You may need to specify an alternate location (which is just really your CD-ROM path). Mine was D:SourcesSxS
After that is done re-launch the setup and install SQL Server. I am not going to go through all the steps here, the only pieces I installed were the Database Engine and the Management Tools. Then apply SP1 to the SQL Installation.
While SP1 is downloading/installing go through the Preparing for Migration documentation here, including filling out the worksheet for the existing WSUS server.
Now, for the actual migration we are just going to be following the steps listed here.
In my situation I am migrating from a WSUS Installation on Windows Server 2003 x86 (Source Server) to Windows Server 2012 x64 (Destination Server). First step is to install the Windows Server Migration Tools on my destination server using the PowerShell command below.
Import-Module ServerManager Add-WindowsFeature Migration
After that you need to create a folder containing those migration tools to use on your source server following the instructions here. Make sure you get the create command to match your Source WSUS Server. In my case the command looked like this:
.SmigDeploy.exe /package /architecture x86 /os WS03 /path C:WindowsServerMigration
Next, open the C:WindowsServerMigration folder you just created. You should see a folder named similarly to mine which was SMT_ws03_x86. Copy this folder to your Source Server. Next, open a command prompt or PowerShell and change the directory to where you placed the folder above. In my case it was C:SMT_WS03_x86 and run the following command to register Windows Server Migration Tools:
Next step is to migrate WSUS Update Binaries from the Source Server to the Destination Server, instructions for which can be found here. For some reason the instructions aren’t in the original article, I had to click through about 7 different TechNet articles to find these steps.
On your DestinationServer open Windows Server Migration Tools (as administrator) and run the command below:
Make sure to specify a password you can remember!
On your SourceServer open Windows Server Migration Tools (as administrator) and run the command below:
Send-SmigServerData -ComputerName <DestinationServer> -SourcePath <source_path> -DestinationPath <destination_path> -Include All -Force -Recurse
In my case my Source Path was just D:WSUSWsusContent and my Destination Path was the same. You don’t need to create the folder structure on the Destination Server, the Migration Tool will complete that for you.
While that runs your Source and Destination Servers will look like this:
You can also check on the progress of the migration by comparing the contents of the WSUSWsusContent folder on the Source and Destination Servers to see how much has copied over. This is a screenshot of my Destination Server after about 15 minutes of migration.