Here I’ll go through some of the reasons and how you can troubleshoot the process.
There are also some situations you may run into where some or all clients stop reporting to the server and these steps will also help for those scenarios as well.
I have this GPO linked at the domain level - just to make sure it was not getting missed. I have run gpupdate / force as well as the MS noted command /detector - just to be sure it was not a timing delay.
So far, neither of the two computers I specified are showing up in the WSUS admin. Nick That log is a great little tip in itself, also very revealing in this case....
On the client run gpresult or to make sure that the details of the WSUS server exist.
If not then a couple possible causes include: To address this, you need to make sure that the group policy is successfully updated on each client and that the WSUS setting is properly configured.
The problem is actually getting the client computers to show up in the WSUS server.
Error 0x8DDD0018” or Error codes 0x80244019 or 0x80070422 when attempting to install updates.
So from what I can tell it looks like the client is inheriting the GPO okay....?
Does the log file show the computer connecting to your server? If you look in the registry, at HKLM \ Software \ Policies \ Microsoft \ Windows \ Windows Update Does it show the WU server and the WUStatus Server as your server name?
If yes then you can run the proxycfg command to check the win http proxy settings.
For more information on the proxycfg command you can check the following link: of the clients will have the proxycgf utility but if not then you can download it here: KB830605 – The configuration tool is available for Win HTTP 5.1 If you are finding proxy errors then what you can do is go to Internet Explorer – LAN Settings and configure the correct proxy and make sure you can reach the WSUS URL specified.
You need to make sure that the WSUS agent service (Automatic Updates) and BITS (Background Intelligent Transfer Service) are running.