The WSUS Deployment Guide has good general guidance on how to export/import content and metadata to a disconnected network. Here are some quick scripts that I whipped up to ease the process, as it’s something that you’ll probably want to do regularly.
WsusContent.bks is required. As is right now it will backup C:\WSUS\WsusContent to C:\WsusExport\WsusContent[date]_[time].bkf. It will create a summary log at %userprofile%\Local Settings\Application Data\Microsoft\Windows NT\NTBackup\data. If the initial backup creates a BKF that is too large to fit on a DVD, then you’ll need to use another method to transfer the data (xcopy, robocopy, oscdimg, etc.). However I’d recommend still running the backup the first time as it will clear the archive bit on the files so that the subsequent time this script is run, only the new content will be captured, thus the BKF will be significantly smaller.
Just an automated way to run the export with a unique CAB and LOG file each time. Both files, along with the above BKF need to be transfered.
Import the content before running this script. NTBackup cannot be automated to restore data so it must be done manually. Make sure to select the Alternate Location option and point to the correct WsusContent folder (to ensure the subfolder structure is maintained). This script requires you to give it the [date]_[time] code for the metadata you want to import.
A few other notes:
- Make sure the update files and language options are identical on both the export and import servers.
- wsusutil shuts down the Update Service when it runs.
- After the import completes wait several hours for the content and metadata to fully validate.
- Close the Update Services console before running the export or import.