• Status: Solved
  • Priority: High
  • Security: Private
  • Views: 50
  • Last Modified:

New WSUS Build

My current WSUS environment has been running for about 6 years and is almost completely useless at this point. W3WP.exe and SQLSERVR.exe memory and CPU usage are through the roof. Clients have to check multiple times because of timeouts and this has become a huge issue. I have run all the cleanup scripts and installed recommended WSUS patches and still poor performance. I have now setup a new server and right now it's getting the metadata from Microsoft. I'm 66% through and right now it is showing 11,000 updates. I've chosen all classifications except for drivers. This will take forever to download. Is there a way to point the new WSUS server at the existing WSUS server, that is local, and then switch it back to Microsoft after the downloads are complete? There are a few categories that are enabled on the new one that are not enabled on the old one but I can sync those from Microsoft later. Downloads will be a lot quicker from a local server. Thanks.
2 Solutions
Daryl BamforthTechnical ExpertCommented:
You can export from your current and import to the new, but honestly, if your old is that messed up might be safer to just wait till it finishes.

Joe FulginitiNetwork EngineerCommented:
WSUS will not download any updates unless they are approved.  You are better off approving only needed updates.
Olgierd UngehojerSenior Network AdministratorCommented:
You can synchronize with Microsoft or local upstream WSUS server.
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Donald StewartNetwork AdministratorCommented:
11,000 updates ??? I would only approve "Needed" updates to start with.
Samarjit BaruahCommented:
You can configure the new one as a downstream of the existing one and let it sync. once sync completes, configure it to point to Microsoft for getting new updates.
Daryl BamforthTechnical ExpertCommented:
To connect a downstream server to an upstream server:
In the left pane of the WSUS Administration console, click Options.
Select the Update Source and Proxy Server option and click the Update Source tab.
Select the Synchronize from another Windows Server Update Services server check box, and then type the server name and port number in the corresponding boxes.
If you are planning to use SSL for this connection, select the Use SSL when synchronizing update information check box. The port used for this connection will be 443.
If you want this server to be a replica of the upstream server, select the This server is a replica of the upstream server check box.
Click OK.
from MS Technet Article
Seth SimmonsSr. Systems AdministratorCommented:
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.

I have recommended this question be closed as follows:

-- Daryl Bamforth (https:#a42368367)
-- Joe Fulginiti (https:#a42368379)

If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.

Experts-Exchange Cleanup Volunteer

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now