Third-Party Updates Should Not Attempt 3 Downloads from Internet (WUMU)
When deploying third-party updates using CMG, the client will detect it's on the internet. In the CAS.log, you will see it things it should reach directly out to windows updates (WUMU) in the CAS.log. The DP returned on ContentLocation.log is actually the internal WSUS location of where the third-party update was downloaded. This path is not resolvable from an internet client and shouldn't be used.
If the client detects it's on the internet, it should never attempt to download from windows updates, since these updates are not applicable for that scenario. The update will timeout after 3 minutes and 3 download failures and will then fallback to CMG. This timeout can cause a lot of time.
For a repro, please see our YouTube video here: https://youtu.be/rZXexnGyee0?t=1041
Joe Alonge commented
I feel like this should be an easy fix for Microsoft. This would allow machines to be patched quicker and provide a better experience for your customers.
Justin Chalfant commented
Feedback ID = 6339f1cd-d261-4cae-812d-e1fa111fd3b6