This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi,
I have installed in our environment SCCM CMG and the client is unable to receive software updates.
This is what I see in WUAHandler.log:
Its a WSUS Update Source type ({A4BF5916-DF74-44C1-BF58-68AE14A43278}), adding it.
SourceManager::GetIsWUfBEnabled - There is no Windows Update for Business settings assignment. Windows Update for Business is not enabled through ConfigMgr
Existing WUA Managed server was already set (https://MECMG.COMPANY.COM/CCM_Proxy_ServerAuth/72057594437927055), skipping Group Policy registration.
Added Update Source ({A4BF5916-DF74-44C1-BF58-68AE14A43278}) of content type: 2
Scan results will include superseded updates only when they are superseded by service packs and definition updates.
Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver')
Async searching of updates using WUAgent started.
Async searching completed.
OnSearchComplete - Failed to end search job. Error = 0x8024402c.
Scan failed with error = 0x8024402c.
Thanks
Rash
Hi,
The error code 0x8024402c is same as ERROR_WINHTTP_NAME_NOT_RESOLVED, which means that the proxy server or target server name cannot be resolved.
This error may be caused by the machine cannot resolve Management Point name or Software Update Point name.
We can try to ping the server name and correct the name resolution to resolve this issue.
I have exactly the same issue - having connected to VPN I managed to install updates from Software Center but that defies purpose of CMG.
Hi @HanyunZhu-MSFT ,
If I do a ping to the my CMG address should there be a ping?
As you can see I ping the CMG address of my organization, and it refers to the service in Azure, but no ping
Hi,
Thanks for you feedback.
Based on my knowledge, this issue not related to ConfigMgr and CMG.
It most likely the server name used by the clients is incorrect.
Here is a link that can used as a reference, please check:
https://learn.microsoft.com/en-us/archive/blogs/sus/wsus-client-sync-fails-with-80072ee7-and-0x8024402c-errors-in-windowsupdate-log