Forum Discussion
Office 365 ProPlus Updates vis SCCM
Hi all! We are deploying the monthly current channel updates with SCCM 1606 and some clients get stuck at "Downloading - 50%". Has anyone else seen this? The SCCM clients are on v1602 and we saw t...
We are experiencing the same problem with SCCM 1610 while deploying Office 365 Client Update - Current Channel (1611-5). The status gets to the status "Download 50%" and then it just hangs. I'm curious if anyone ever found a solution to this issue?
Well, that squashes my hope that this issue is resolved in SCCM 1610 :). Are your clients also on v1610?
I'm still pursuing this with Microsoft via a premier case. This past week we were able to determine that the download will start for a bit and then stop. During this time the UI just hangs on Downloading 50%. You can see this in the DataTransferService log in C:\Windows\CCM\logs. If you restart the ccmexec.exe service you'll see more files get donwloaded in the log; however, it will stop after a few files. Keep restarting the service and the cycle repeats.
The Microsoft support rep was going to take this information back to their senior engineer and look into it further.
Yes, our clients have been updated to 1610 as well. Also, our SCCM Operations Team installed KB3211925 on the MPs last night. We're still seeing either the problem I described in yesterday's post or the update just fails right away with this error: 0x8007755A(-2146994854). The update handler log has this error everytime the update fails: "CAS failed to download update (855487e5-cce6-47c0-976b-269a8ae5b03d). Error = 0x8007755a. Releasing content request."
Our operations team has been looking into this as well, but so far no one has any answers. The odd thing is that we're seeing different behaviors on different machines, and yesterday a few of the clients were able to successfully install the update after it had hung at 50% for about an hour.
This one is frustrating.
Very frustrating indeed! We too are seeing inconsitencies across machines. It also seems to vary per month for us. Machines that have failed for one month's update will have the next month work. Makes troubleshooting difficult.
it's such a relief to find that i'm not the only one experiencing this issue ahah
