Appendix B: Migrate WSUS Update Binaries from the Source Server to the Destination Server Using Windows Server Migration Tools
Updated: July 19, 2011
Applies To: Windows Server 2003 with SP2, Windows Server 2008 R2, Windows Server 2008 R2 with SP1, Windows Server Update Services, Windows Small Business Server 2011 Essentials
Migrate WSUS update binaries from the source server to the destination server
You can use Windows Server Migration Tools to copy Windows Server Update Services (WSUS) 3.0 SP2 update binaries from the source server to the destination server in the same subnet.
Windows Server Migration Tools is a set of Windows PowerShell cmdlets. For more information about Windows PowerShell and working with cmdlets, see the Working with Windows PowerShell cmdlets section of Windows Server Migration Common Tasks and Information.
To migrate WSUS update binaries by using Windows Server Migration Tools
Open a Windows PowerShell session on both the source and destination servers.
On computers that are running Windows Server 2003, open a Windows PowerShell session, click Start, point to Administrative Tools, open the Windows Server Migration Tools folder, and then click Windows Server Migration Tools.
On computers that are running Windows Server 2008 or Windows Server 2008 R2, open a Windows Server Migration Tools custom Windows PowerShell session, click Start, point to Administrative Tools, open the Windows Server Migration Tools folder, right-click Windows Server Migration Tools, and then click Run as administrator.
Verify that the destination path has sufficient disk space to migrate the data.
In the Windows PowerShell session on the destination server, run the Receive-SmigServerData cmdlet:
You are prompted to provide a password to encrypt the data transfer. Remember this password, because you must provide the same password to send data on the source server.
In the Windows PowerShell session on the source server, run the following command, in which source_path represents the WSUS\UpdateServicesPackages folder on the source server and destination_path represents the WSUS\UpdateServicesPackages folder on the destination server:
Send-SmigServerData -ComputerName <DestinationServer> -SourcePath <source_path> -DestinationPath <destination_path> -Include All -Force -Recurse
After you enter the
Send-SmigServerData cmdlet, you are prompted to provide the same password that you created for the
Receive-SmigServerData cmdlet on the destination server.
- Run the command in step 4 in the same Windows PowerShell session on the source server in which source_path represents the WSUS\WsusContent folder on the source server and destination_path represents the WSUS\WsusContent folder on the destination server.
Windows Server Update Services 3.0 SP2 Migration Guide
Preparing to Migrate WSUS
Verifying the WSUS Migration
Post-migration Tasks for WSUS
Appendix A: Migration Data Collection Worksheet