Windows 10: La console d'administration WSUS n'a pas été en mesure de se connecter au serveur WSUS par...

Bonjour,après une installation du rôle WSUS dans un WinSer2019 j'ai mis en place la connexion SSL via un ADCS pour faire transiter le trafic via le HTTPS, et je rencontre des erreurs de chargement de la section "synchronisation" dans le panneau de gestion wsus.voici une capture. erreur 7032La console d'administration WSUS n'a pas été en mesure de se connecter au serveur WSUS par l'intermédiaire de l'API distante. Vérifiez que le service Update Services, les ser

:)

 

The WSUS support thread

update on my install, i ad everything working inside a VM with 2 disk , when i moved it to the local vm machine WSUS would not work anymore , something do to with database error, sadly have not found a way to tell WSUS where the database is ....
on the new machine its still in the root of d:\ this as not changed so i don't know why WSUS can't connect to his database *Frown

 

WSUS Server 2016 showing up with 3 instances in the WSUS console

My WSUS Server 2016 showing up with 3 instances in the WSUS console

 

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: Microsoft Q&A

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.