Windows 10: Die WSUS-Verwaltungskonsole konnte über die Remote-API keine Verbindung zum WSUS-Server...

Server 2016 Standalone WSUS Console keep crashing The WSUS administration console was unable to connect to the WSUS Server via the remote API. Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. System.Net.WebException -- The operation has timed out Source System.Web.Services Stack Trace: at System.Web.Services.Protocols.WebClientProtocol.GetWebResponseWebRequest request at Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponseWebRequest

:)

 

WSUS - Servers not reporting in

Hi All,

I am busy with WSUS in a lab running off my laptop. Details are as follows:

1. 1 x Domain Controller running Windows Server 2019
2. 1 x WSUS Server running Windows Server 2019
3. 1 x Windows Server 2016 VM

I've installed WSUS on #2 and it's busy downloading updates I have selected. However, try as I might, I cannot get the other 2 servers to report in. Further information:

• All firewalls are disabled;
• I can ping via name/IP successfully;
• I can successfully run nslookup;
• I cannot browse the http://servername:8530 site (in spite of generating the SS;
• 2 GPOs were created (one for Test, one for PRD) and linked/enabled on the domain;
• WSUS Service running on the other 2 VMs.

What can I check to ensure that this works? The GPOs are applied, but do I need OUs within AD itself and the servers placed in those, or is leaving them in the default container fine for now? Like I said, it's for test purposes, but I obviously need to get
it running for further trials/tests I'd like to do.

Thanks!

Craig

 

The WSUS support thread

This thread is for all things WSUS (Windows Server Update Services). Discussion, installation questions, problems all go here.

What is WSUS? It's basically a big file cache for all your Windows/Microsoft updates, so all your updates are only ever downloaded over the internet once. Instead of getting your updates directly from Microsoft whenever you reinstall your operating system, you point Windows to your local WSUS server instead. This makes downloading the multi-gigabytes of updates way faster using your internal network and also saves your internet bandwidth, which is often metered and limited.

Note that it requires Windows Server to run. I recommend running the latest Server 2008 R2 for performance, stability and security, if you can. This is a 64-bit only OS. And yes, the server can update from it's own WSUS server too. *Cool

I've got links to a few resources below and I'll be adding more goodness to this post and the next one, as people make useful contributions to this thread.

Some WSUS resources to get you started:

The manual: http://technet.microsoft.com/en-us/library/dd939796(WS.10).aspx

WSUS home: http://technet.microsoft.com/en-us/wsus/default.aspx

WSUS forum: Technet forums - WSUS

WSUS wiki: www.wsuswiki.com


POINTING WINDOWS TO THE WSUS SERVER

Note that this procedure is all you have to do on Vista and 7. XP requires a little extra and the whole update process isn't as transparent or efficient.

- Click the Orb at the bottom left of the desktop aka 'Start' button
- In the search field enter GPEDIT.MSC
- In the Local Group Policy Editor (LGPE) console that appears, navigate to: Computer configuration > Administrative Templates > Windows Components > Windows Update
- Double click the Specify Intranet Microsoft update service location Group Policy setting. Note that Not Configured is showing in the State column






- The dialog box opens. Note that the Not Configured radio button is selected






- Enter the server details, by clicking the Enabled radio button and entering the same details in both Options fields. The server's name is the standard Windows name. My server is called afterburner *Smile






- Click OK. The main LGPE window now looks like below. Note that Enabled is now showing in the State column.





- Close the LGPE window

- Open the Windows Update window. It should now show You receive updates: Managed by your system administrator





Now, whenever you check for updates, Windows will access your WSUS server instead of looking over the internet to Microsoft's servers.
If you want to change it back at an time, simply change the Group Policy setting back to Not Configured.

 

WSUS Manual Entry

Odd question for MS Experts.

I have a WSUS environment, and 99% of my servers report to it. This makes it very useful as a list of servers and workstations. But there are 1% of our servers that are in the DMZ or off network. I want to use the list of my WSUS computers to know what
computers need to be patched, so they don't get forgotten.

These 1% never have to actually talk to WSUS, just appear in the list of computers so a human knows they exist.

How can I manually add a computer to the WSUS Server?

Can I manually manipulate the DB (Full SQL), and if so, how?