Software Update not required

Md. Rubiat Haque 151

Hello,

I am currently using MECM 2211 and I have more than 5000 devices in my environmemt. When I checked the software updates, I found that only 800/900 devices are showing required. Rest of the devices can't scan update.

I have windows 10 Version 1511, 1607, 1709, 1803, 1809, 1903, 1909, 2004, 21H2 and 22H2.

Only the devices which versions are 2004 and later, can scan properly. 2004 older versions can't scan for update.

I ran a scan report where I found total 18 errors and where I found that more than 1800 devices failed to scan. HTTP 404 URL error I found in 965 devices.

So, how can I fix the issue? It's very urgent for me because here is an audit issue. Also please tell me which windows 10 version can support by MECM 2211?

Thanks in Advance.

Rahul Jindal [MVP] 9,881 Reputation points MVP

2023-09-19T20:55:55.6866667+00:00

Well I will start by fixing the unsupported Windows 10 versions in the environment as these will get flagged straight away during audit. As for issue involving the scan, looks like the devices in question are not able to communicate with the SUP. Are they checking into ConfigMgr otherwise?
Md. Rubiat Haque 151 Reputation points

2023-09-20T04:08:37.33+00:00
Hello @Rahul Jindal [MVP]

Thanks for your reply. Actually I know very well if I upgrade all the oldest version to newer windows 10 then my issue will be resolved. But I have more than 1800 devices which has older version. How can I upgrade these? It's not possible to me to upgrade all the devices manually. And another thing is that when I ran Scan Report from SCCM, I got total 18 errors. The errors are following:

An operation failed due to reasons not covered by another error code. - 13 devices

Content location request timeout occurred - 1 device

Group policy conflict - 2 devices

Network connection: Windows Update Agent encountered transient network connection-related errors - 1 device

Not enough storage is available to complete this operation. - 2 devices

Operation did not complete because the network connection was unavailable. - 3 devices

Same as HTTP status 401 - the requested resource requires user authentication. - 4 devices

Same as HTTP status 404 - the server cannot find the requested URI (Uniform Resource Identifier). - 936 devices (I have to fix at least this error)

Same as HTTP status 408 - the server timed out waiting for the request. - 3 devices

Scan tool has been removed - 6 devices

The connection to the service endpoint died. - 3 devices

The data received does not meet the data contract expectations. - 2 devices

The policy for this program does not exist or is invalid. - 7 devices

The request could not be performed because of an I/O device error. - 1 device

The specified buffer contains ill-formed data. - 1 device

There is no route or network connectivity to the endpoint. - 765 devices (I have to fix this error also)

Unspecified error - 6 devices

WUServer policy value is missing in the registry. - 1 device

1 answer

AllenLiu-MSFT 44,101 Reputation points Microsoft Vendor

2023-09-20T06:32:26.44+00:00

Hi, @Md. Rubiat Haque

Thank you for posting in Microsoft Q&A forum.

For the devices failed to scan, we may start from checking WUAHandler.log on the clients for more details.

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Add comment".
Please sign in to rate this answer.
Md. Rubiat Haque 151 Reputation points

2023-09-20T06:34:15.07+00:00

Same as HTTP status 404 - the server cannot find the requested URI (Uniform Resource Identifier). This is the error

AllenLiu-MSFT 44,101 Reputation points Microsoft Vendor

2023-09-20T09:05:57.81+00:00

The error message "Same as HTTP status 404 - the server cannot find the requested URI (Uniform Resource Identifier)" indicates that the Windows Update Agent is unable to locate the update files on the server. This issue can occur due to several reasons, including incorrect port configuration, proxy configuration, firewall issues, network connectivity, or name resolution issues.

To troubleshoot this issue, you can try the following steps:

Verify connectivity with the WSUS computer by checking the URL of the WSUS computer using the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate. Try to access the URL to verify connectivity between the client and the WSUS computer.

Check whether the client can access the ClientWebService virtual directory and SimpleAuthWebService virtual directory. If these tests are successful, review the Internet Information Services (IIS) logs on the WSUS computer to confirm that the HTTP errors are being returned from WSUS. If the WSUS computer doesn't return the error, the issue is probably with an intermediate firewall or proxy.

If any of these tests fail, check for name resolution issues on the client. Verify that you can resolve the FQDN of the WSUS computer. Also, verify the proxy settings on the client to make sure that they are configured correctly.

Ensure that the WSUS virtual directories are configured to use SSL and are set to ignore client certificates. Verify that the software update point is configured to use SSL, and the WSUS computer is explicitly configured to use SSL. Review the certificate requirements and make sure that a server authentication certificate is installed on the software update point server.

Md. Rubiat Haque 151 Reputation points

2023-09-20T10:14:45.7366667+00:00

Hello @AllenLiu-MSFT

Thanks for your reply. My WSUS role is installed the same SCCM server and also my communication configured with HTTP

Md. Rubiat Haque 151 Reputation points

2023-09-27T11:32:12.0733333+00:00

Hello @AllenLiu-MSFT

My problem is still not resolved. I check firewall ports and nothing is blocking by my firewall. But I tried to access the URL of http://sccm.domain.com/8530 which I couldn't access. I have 5000 devices where some of devices uses proxy and some of devices have no proxy. But from all devices I can't access the URL. I can access it only from my SCCM server. But the devices are also can't access the url which have no scan issue. So, how can I fix it?
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Software Update not required

1 answer

Your answer