Microsoft WIndows Software Update Services
Remote Server Migration: Migrate Content and Approvals
Remote server migration requires that you share the Content folder on each SUS server you want to migrate to the WSUS server (or use the default share to access the content folder).
You do have to make sure that SUS is not synchronizing before you migrate content or approvals. You do not have to migrate both content and approvals from the remote SUS server. You can opt to initially migrate content and then migrate approvals at another time, or any number of combinations that suit your purpose.
Use WSUSutil.exe to migrate content and approvals from SUS to WSUS. For more information about WSUSutil.exe, see Migration Command-line Tool earlier in this guide.
If you intend to map SUS approvals to a WSUS computer group, first create the group on WSUS. For step-by-step instruction, see Create Computer Groups for Computers earlier in this guide.
To share remote content on SUS for migration to WSUS
1.
On the SUS computer, locate the SUS content store in the file system. By default, SUS content is stored in C:\SUS\Content\.
2.
Right-click the Content folder, and then click Sharing and Security (or Sharing, on computers running Windows 2000).
3.
In the Properties dialog box for the Content folder, click Share this folder.
4.
Click the Security tab, and ensure that the Everyone group has Read NTFS permissions for the Content folder.
5.
Click OK.
6.
Repeat this step on each SUS server you intend to migrate.
To migrate remote content and approvals from SUS and map approvals to a custom computer group on WSUS
1.
At the command prompt, navigate to the folder that contains WSUSutil.exe.
2.
Type the following:
wsusutil.exe migratesus /content LocationOfRemoteSUSContent /approvals SUSServerName "WSUSTargetGroupName" /logfilename
For example:
wsusutil.exe migratesus /content \\sus1\content\cabs /approvals sus1 "all desktops" /log remote_migration.log
To migrate local content and approvals from SUS and map approvals to the All Computers target group in WSUS
1.
At the command prompt, navigate to the folder that contains WSUSutil.exe.
2.
Type the following:
wsusutil.exe migratesus /content LocationOfRemoteSUSContent /approvals SUSServerName /logfilename
For example:
wsusutil.exe migratesus /content \\sus1\content\cabs \approvals sus1 \\log remote_migration.log
To migrate only remote content
1.
At the command prompt, navigate to the folder that contains WSUSutil.exe.
2.
Type the following:
wsusutil.exe migratesus /content LocationOfRemoteSUSContent /log filename
For example:
wsusutil.exe migratesus /content \\sus1\content\cabs /approvals sus1 /log remote_migration.log
To migrate only remote approvals
1.
At the command prompt, navigate to the folder that contains WSUSutil.exe
2.
Type the following:
wsusutil.exe migratesus /approvals SUSServerName /log filename
For example:
wsusutil.exe migratesus /approvals sus1 /log remote_migration.log
Top of pageTop of page
Step 3 Remote Server Migration: Test WSUS (Optional)
Any computer that is going to connect to WSUS must have the WSUS client. When you installed WSUS, the client self-update feature was set up automatically by the WSUS installer.
To deploy the WSUS client software for testing
•
Deploy the WSUS client in your environment to test WSUS (optional). See Update Automatic Updates earlier in this guide for instruction.
Top of pageTop of page
Step 4 Remote Server Migration: Point SUS Clients to WSUS
Point the SUS clients to WSUS. As the SUS clients check in with the WSUS server, they will find the WSUS Web site and self-update to the WSUS client.
To point SUS clients to WSUS
•
Use Group Policy or registry settings to point SUS clients to WSUS. See Determine a Method to Configure Automatic Updates Clients earlier in this guide for instruction.
Org. Link
Remote server migration requires that you share the Content folder on each SUS server you want to migrate to the WSUS server (or use the default share to access the content folder).
You do have to make sure that SUS is not synchronizing before you migrate content or approvals. You do not have to migrate both content and approvals from the remote SUS server. You can opt to initially migrate content and then migrate approvals at another time, or any number of combinations that suit your purpose.
Use WSUSutil.exe to migrate content and approvals from SUS to WSUS. For more information about WSUSutil.exe, see Migration Command-line Tool earlier in this guide.
If you intend to map SUS approvals to a WSUS computer group, first create the group on WSUS. For step-by-step instruction, see Create Computer Groups for Computers earlier in this guide.
To share remote content on SUS for migration to WSUS
1.
On the SUS computer, locate the SUS content store in the file system. By default, SUS content is stored in C:\SUS\Content\.
2.
Right-click the Content folder, and then click Sharing and Security (or Sharing, on computers running Windows 2000).
3.
In the Properties dialog box for the Content folder, click Share this folder.
4.
Click the Security tab, and ensure that the Everyone group has Read NTFS permissions for the Content folder.
5.
Click OK.
6.
Repeat this step on each SUS server you intend to migrate.
To migrate remote content and approvals from SUS and map approvals to a custom computer group on WSUS
1.
At the command prompt, navigate to the folder that contains WSUSutil.exe.
2.
Type the following:
wsusutil.exe migratesus /content LocationOfRemoteSUSContent /approvals SUSServerName "WSUSTargetGroupName" /logfilename
For example:
wsusutil.exe migratesus /content \\sus1\content\cabs /approvals sus1 "all desktops" /log remote_migration.log
To migrate local content and approvals from SUS and map approvals to the All Computers target group in WSUS
1.
At the command prompt, navigate to the folder that contains WSUSutil.exe.
2.
Type the following:
wsusutil.exe migratesus /content LocationOfRemoteSUSContent /approvals SUSServerName /logfilename
For example:
wsusutil.exe migratesus /content \\sus1\content\cabs \approvals sus1 \\log remote_migration.log
To migrate only remote content
1.
At the command prompt, navigate to the folder that contains WSUSutil.exe.
2.
Type the following:
wsusutil.exe migratesus /content LocationOfRemoteSUSContent /log filename
For example:
wsusutil.exe migratesus /content \\sus1\content\cabs /approvals sus1 /log remote_migration.log
To migrate only remote approvals
1.
At the command prompt, navigate to the folder that contains WSUSutil.exe
2.
Type the following:
wsusutil.exe migratesus /approvals SUSServerName /log filename
For example:
wsusutil.exe migratesus /approvals sus1 /log remote_migration.log
Top of pageTop of page
Step 3 Remote Server Migration: Test WSUS (Optional)
Any computer that is going to connect to WSUS must have the WSUS client. When you installed WSUS, the client self-update feature was set up automatically by the WSUS installer.
To deploy the WSUS client software for testing
•
Deploy the WSUS client in your environment to test WSUS (optional). See Update Automatic Updates earlier in this guide for instruction.
Top of pageTop of page
Step 4 Remote Server Migration: Point SUS Clients to WSUS
Point the SUS clients to WSUS. As the SUS clients check in with the WSUS server, they will find the WSUS Web site and self-update to the WSUS client.
To point SUS clients to WSUS
•
Use Group Policy or registry settings to point SUS clients to WSUS. See Determine a Method to Configure Automatic Updates Clients earlier in this guide for instruction.
Org. Link
vireas - 6. Jul, 13:35
