Forum Discussion
Delivery Optimization fails for 99% of the company
DO policy (Lan mode 1) deployed on 75k devices, all of them comanaged. Compliance dashboard show 75k devices clearly contacting with peers on the same subnet, but only 1% is achieving >0 bytes saving...
Thank you so much for your suggestions.
All our PCs are comanaged, and our DO Ppolicy is deployed by Intune. But yes, Sccm configmanager is/could be still involved.
Not sure how much as is not clear to which workload depends DO, if any.
95% devices are in the pilot collection to set MDM as authority for WU.
Yes, delta downloads are disabled to the whole company. Doesn't makes sense to me, but it was set with such config when I arrived to the company. I also thought this could be the issue, so I enable it for a little group of 200 pcs located at the same office, and the same boundary. But unfortunately, after this OCT patch cycle, none of them appears in the Compliance Dashboard as BYTES>0
On DO logs I see a lot of FailureReason:Null, peer connection destroyed, socket connect error.
I see those errors even on Logs from a successful machine sharing 3.5Gb to the local network by DO. Makes sense to you?
I will recheck everything again. Thanks.
All our PCs are comanaged, and our DO Ppolicy is deployed by Intune. But yes, Sccm configmanager is/could be still involved.
Not sure how much as is not clear to which workload depends DO, if any.
95% devices are in the pilot collection to set MDM as authority for WU.
Yes, delta downloads are disabled to the whole company. Doesn't makes sense to me, but it was set with such config when I arrived to the company. I also thought this could be the issue, so I enable it for a little group of 200 pcs located at the same office, and the same boundary. But unfortunately, after this OCT patch cycle, none of them appears in the Compliance Dashboard as BYTES>0
On DO logs I see a lot of FailureReason:Null, peer connection destroyed, socket connect error.
I see those errors even on Logs from a successful machine sharing 3.5Gb to the local network by DO. Makes sense to you?
I will recheck everything again. Thanks.
Regarding the delay thresholds, we set it as recommended by MS, 60 sec
Recommended by official MS docs, by MEM help statements, and also directly from the fasttrack team of MS.
But who knows? I will try it.
Recommended by official MS docs, by MEM help statements, and also directly from the fasttrack team of MS.
But who knows? I will try it.