You can migrate a WSUS deployment hosted on Windows Server 2003 to a server running Windows Server 2012 R2 as long as you follow a particular set of steps.
The first step is to ensure that your Windows Server 2003 WSUS deployment has been upgraded to WSUS 3.0 SP2.
You can perform a migration if the WSUS server is using the Windows Internal database, or if the WSUS server is using SQL Server. You can migrate from a source server using the Windows Internal database to a destination server that uses either the Windows Internal database or SQL Server, but you can’t go from a WSUS server that uses a SQL Server database to a destination WSUS server using the Windows Internal Database.
TCP port 7000 is used by the Send-SmigServerData and Receive-SmigServerData cmdlets to perform the migration. This means you need to ensure connectivity on this port exists between source and destination server.
Once you have TCP port 7000 open, you’ll need to perform the following general steps:
- Migrate the WSUS binaries. You can use any method of copying files or use the Windows Server Migration Tools to perform this task
- You’ll need to migrate the WSUS groups. You can use the Windows Server Migration Tools to perform this task.
- You need to backup and restore the WSUS database. If you are using the Windows Internal Database, you’ll need to do a few clever things with SQL Server Management Studio to perform this operation. If you are using SQL Server on the source and destination server, things are a bit more straightforward. You can find more information about doing this using the following TechNet web page: https://technet.microsoft.com/en-au/library/hh852349.aspx
- Change the WSUS server identity. This way clients that checked in with the source WSUS server will not use the destination WSUS server.
You can find out more about migrating WSUS from Server 2003 to Server 2012 R2 by consulting the following TechNet web page: https://technet.microsoft.com/en-au/library/hh852339.aspx