When a software update point is not configured to synchronize with its upstream update server in Configuration Manager 2007, the export and import function of the WSUSutil tool can be used to synchronize software updates metadata. The WSUSutil tool should be used to synchronize software updates on a schedule that is similar to the synchronization schedule configured on the central site. You will also want to verify that synchronization has completed on the upstream update source before using the tool to ensure that the most recent software updates metadata is synchronized. To verify that synchronization has completed successfully on the server configured as the upstream update source, check the site server for status message ID 6702 for the SMS_WSUS_SYNC_MANAGER component or look for the log entry in wsyncmgr.log on the site server that references status message ID 6702.

Note
The parent site server is the upstream update source for an active software update point and the current site server is the upstream update source for an active Internet-based software update point.

The user running the tool must be a member of the local Administrators group on the Windows Server Update Services (WSUS) server to export or import the metadata, and the tool must be run locally on the WSUS server.

Important
Never import exported data from a source that you do not trust. Importing content from a source you do not trust might compromise the security of your WSUS server.

The files in the WSUSContent folder (located in <WSUSInstallationDrive>\WSUS\WSUSContent by default) must also be copied from the upstream update server to the software update point so that locally stored updates and the license terms for software updates are available to the import server. Use the following procedures to export and import software updates from the export WSUS server to the import WSUS server.

To copy local files from the export server to the import server

  1. On the export server, navigate to the folder where software updates and the license terms for software updates are stored. By default, WSUS stores the files at <WSUSInstallationDrive>\WSUS\WSUSContent\, where WSUSInstallationDrive is the drive on which WSUS is installed.

  2. Copy all files and folders from this drive to the WSUSContent folder on the import server.

To export metadata from the database of the export server

  1. At the command prompt on the export WSUS server, navigate to the folder that contains WSUSutil.exe. By default, the tool is located at %ProgramFiles%\Update Services\Tools.

  2. Type the following:

    wsusutil.exe export packagename logfile

    For example:

    wsusutil.exe export export.cab export.log

    The format can be summarized as follows: WSUSutil.exe is followed by the export option, the name of export .cab file created during the export operation, and the name of a log file. WSUSutil.exe exports the metadata from the export server and creates a log file of the operation.

    Note
    The package (.cab file) and log file name must be unique in the current folder.
  3. Move the export package to the folder that contains WSUSutil.exe on the import WSUS server.

    Note
    Moving the package to this folder provides an easy import experience. You can move the package to any location accessible to the import server, and then specify the location when running WSUSutil.exe.

To import metadata to the database of the import server

  1. At the command prompt on the import WSUS server, navigate to the folder that contains WSUSutil.exe. By default, the tool is located at %ProgramFiles%\Update Services\Tools.

  2. Type the following:

    wsusutil.exe import packagename logfile

    For example:

    wsusutil.exe import export.cab import.log

    The format can be summarized as follows: WSUSutil.exe is followed by the import command, the name of package file (.cab) created during the export operation (and path to the package file if it is in a different folder), and the name of a log file. WSUSutil.exe imports the metadata from the export server and creates a log file of the operation.

See Also