First of all, I personally think that simply exporting and importing data is not a perfect Intranet WSUS server solution. I believe you have come to a conclusion in your experiment !!
The first patch update for the Intranet WSUS server is the same as that for the WSUS server migration)
Inter-WSUS: The first server of the patch server on the Internet)
Windows 2003 Server Enterprise Edition SP2 + WSUS 3.0 + SQL 2005 SP2 + IIS +. NET Framework 2.0
Lan-WSUS: second server of the Intranet patch server)
Windows 2003 Server Enterprise Edition SP2 + WSUS 3.0 + SQL 2005 SP2 + IIS +. NET Framework 2.0
After WSUS 3.0 is installed on the Inter-WSUS server, do not synchronize it immediately to prevent a large amount of junk information from being generated after synchronization.
Open the WSUS 3.0 console ----- Update Service ------ Inter-WSUS, click "Import update" in the Operation window on the right, and find the latest patch from the update directory of Microsoft, check whether the patch has any replacement patch. If yes, give up!
After selecting the patch package, click "View Selection bar" in the upper right corner, and then import the update. In the WSUS 3.0 console, open "Update" --- "all updates" ------ "not approved" ------ "any status" to approve all patches.
After approval, the WSUS server automatically downloads the patch !!
After the WSUS server patch is downloaded, back up the server:
1. Copy the patch to save the WsusContent directory under the directory to the USB flash disk or start the hard disk.
2. export metadata: Run --- cmd ----- to go to the c: \ Program Files \ Updata Services \ Tools directory and run the command wsusutil export d: \ wsus. cab d: \ wsus. log
3. Open the SQL Server Management Studio Management tool, connect to the SQL 2005 database, and back up the SUSDB database to the DS disk SUSDB. bak file.
Then, perform the following operations on the Lan-WSUS Server:
1. The Server Installation process is the same as that on the Internet.
2. Copy the patch file on the Internet to the patch directory, copy the patch directory on the USB flash disk or enable the Internet on the hard disk to the patch storage directory on the WSUS server.
3. Import metadata and enable wsus on the USB flash drive or hard disk. cab and wsus. copy the log file to drive D, open cmd, and go to the c: \ Program Files \ Updata Services \ Tools directory,
Run wsusutil import d: \ wsus. cab d: \ wsus. log time is a little long. This step should be omitted for exporting on the Internet patch server, but I have not tried it !!)
4. Stop the Update services Service.
5. Open the SQL Server Management Studio Management tool to connect to the SQL 2005 database.
6. Database ---- SUSDB ---- right-click ---- task ---- detach, and perform the detaching operation on the SUSDB database to disconnect all connections to the SUSDB. Cause: an error occurs when you directly restore the database, indicating that the database is in use and you are not authorized to perform the operation.
7. Database --- attach ---- attach the SUSDB database. SUSDB database file location: c: \ Program Files \ Microsoft SQL Server \ MSSQL.1 \ MSSQL \ Data \ SUSDB. mdf
8. Database ---- SUSDB ---- right-click ---- task ---- restore ---- database ---- Source Device ---- add. Add an internet server SUSDB database backup file, and select under "select backup set for restoration. Click the options on the left,
Restore option: Select "Overwrite existing database". Otherwise, the restoration fails.
9. Start the Update Services Service, open the WSUS 3.0 console, view the patch status, group the computer, and client information, which is the same as that on the Internet !!
Download and install patches on the test client !!!
I have tested it !!
This method is also suitable for transferring WSUS servers !!!!
Now the Intranet patch server has been synchronized with the Internet, but there is still a requirement that if Microsoft releases a patch later, how should we synchronize data again ???
Method:
1. First, download the latest Microsoft patch on the Internet patch server, and use the "patch browsing tool" released in this forum in combination with the Folder creation time to determine the directory to which the latest Microsoft patch is downloaded.
2. Copy the latest patch directory and back up the WSUS database.
3. on the Intranet patch server, export the client list from the SUSDB database. The specific table name is dbo. tbComputerTarget.
4. Restore the Internet patch Server database, as shown in the preceding figure.
5. Import the Intranet client list and the dbo. tbComputerTarget table.
Start the WSUS 3.0 console and check related settings and patch status. The new patch is already in the approval list !!
Next, we will test the client's download and installation of the new patch !!
I have tested all the operations above !!!