ConfigMgr Scan failed with error = 0×80240438

ConfigMgr Scan failed with error = 0×80240438

If you use a Software update point for patch management, you might meet a scan problem when Forefront TMG (in my case) or another firewall is in place. Today, when I deployed a group of updates I’ve seen in the monitoring workspace that all target PCs are in the Unknown tab, so I’ve gone directly in WUAHandler.log and I found these entries:

The same error code in other logs such scanagent.log and updatedeployment.log. On GOOGLE, there is nothing about that. To solve this problem I tried to access from IE to my SUP (http://SUPServer:Port) (8530 in my case) and here I understood what happened. I created a rule on TMG to allow HTTP to the SUP and the issue was gone.

Leave a Comment
  • Please add 1 and 1 and type the answer here:
  • Post
Wiki - Revision Comment List(Revision Comment)
Sort by: Published Date | Most Recent | Most Useful
Comments
Page 1 of 1 (1 items)
Wikis - Comment List
Sort by: Published Date | Most Recent | Most Useful
Posting comments is temporarily disabled until 10:00am PST on Saturday, December 14th. Thank you for your patience.
Comments
Page 1 of 1 (1 items)