I had this problem recently and the fix was quite easy, but finding out why it was failing (to install any updates on any machine connected to the SCCM SUP) was difficult.
the basic errors in the WUAHANDLER.LOG file found on the client were repeated again and again
I googled the Scan failed with error = 0x80072efd. error and got some ideas that it was a lack of commuinication between the client and the sccm sup. This turned out to be correct in the end.
The SUP was a WSUS server running as a site server and was multihomed, one network card served the internal network and the other served the public. The SCCM server was on the internal network and tried to access the WSUS but got an error
<![LOG[Existing WUA Managed server was already set (http://SCCM.WINDOWS-NOOB.COM:80), skipping Group Policy registration.]LOG]!><time="16:54:10.490+-60" date="03-27-2009" component="WUAHandler" context="" type="1" thread="4348" file="sourcemanager.cpp:1032"> <![LOG[Added Update Source ({504B2CDB-3C06-4402-977E-C1D96D591F16}) of content type: 2]LOG]!><time="16:54:10.505+-60" date="03-27-2009" component="WUAHandler" context="" type="1" thread="4348" file="sourcemanager.cpp:1372"> <![LOG[Async searching of updates using WUAgent started.]LOG]!><time="16:54:10.521+-60" date="03-27-2009" component="WUAHandler" context="" type="1" thread="4348" file="cwuahandler.cpp:587"> <![LOG[Async searching completed.]LOG]!><time="16:54:32.875+-60" date="03-27-2009" component="WUAHandler" context="" type="1" thread="5796" file="cwuahandler.cpp:2099"> <![LOG[OnSearchComplete - Failed to end search job. Error = 0x80072efd.]LOG]!><time="16:54:32.875+-60" date="03-27-2009" component="WUAHandler" context="" type="3" thread="4844" file="cwuahandler.cpp:2966"> <![LOG[scan failed with error = 0x80072efd.]
After much troubleshooting i decided to ping the Configuration Manager wsus server from a working machine, it reported the correct IP on the internal network. I then checked a non working client and pinged Configuration Manager wsus server from it, it replied back with the IP address of the WSUS public ip.
That was the Eureka moment ~!
As a quick test, and configuring IIS on the WSUS server to 'Listen To all IPs' the WSUS server was responding with the correct IP address when pinged, and windows updates started flowing
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
I had this problem recently and the fix was quite easy, but finding out why it was failing (to install any updates on any machine connected to the SCCM SUP) was difficult.
the basic errors in the WUAHANDLER.LOG file found on the client were repeated again and again
I googled the Scan failed with error = 0x80072efd. error and got some ideas that it was a lack of commuinication between the client and the sccm sup. This turned out to be correct in the end.
The SUP was a WSUS server running as a site server and was multihomed, one network card served the internal network and the other served the public. The SCCM server was on the internal network and tried to access the WSUS but got an error
After much troubleshooting i decided to ping the Configuration Manager wsus server from a working machine, it reported the correct IP on the internal network. I then checked a non working client and pinged Configuration Manager wsus server from it, it replied back with the IP address of the WSUS public ip.
That was the Eureka moment ~!
As a quick test, and configuring IIS on the WSUS server to 'Listen To all IPs' the WSUS server was responding with the correct IP address when pinged, and windows updates started flowing
hopefully this may help someone in the same situation
cheers
anyweb
Share this post
Link to post
Share on other sites