Delivery Optimization: Download of a file saw no progress within the defined period - Error Code 0X80D02002.

Question

Hi All,We are deploying the Monthly patches from SCCM Server to Windows workstations. Some of the Windows workstations getting Error "Delivery Optimization: Download of a file saw no progress within the defined period - Error Code 0X80D02002" The update is deployed by ADR. I am getting this error on almost 500+ machines on every month. Please suggest

Answer 1

Hi, @Sugumar

Thank you for posting in Microsoft Q&A forum.

The error message "Delivery Optimization: Download of a file saw no progress within the defined period - Error Code 0X80D02002" indicates that SCCM is having trouble downloading files to the affected Windows workstations using Delivery Optimization.

This error can occur due to a number of reasons. One possible cause is that the affected machines are not able to contact the Delivery Optimization cloud service. To resolve this issue, check if the workstations have access to the internet and ensure that Delivery Optimization cloud services are not being blocked by any firewall or proxy server.

Another possible cause is that the affected machines are not able to connect to the peers on the network to download the updates. Delivery Optimization is designed to use a peer-to-peer mechanism to download updates from nearby machines to save bandwidth. Ensure that Delivery Optimization is configured correctly on the network and the machines are allowed to download updates from peers.

Additionally, you can check the SCCM logs to identify the exact source of the error. Check the Patchdownloader.log file to determine if there are any zero-byte files in the temp directory. If so, remove all files from the temp directory and retry the ADR.

---

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".

Answer 2

We recently had this issue. It turned out to be that when we launched IIS on the distribution points, the default site was not bound to port 443 with a valid certificate.