Forum Discussion
Office 365 ProPlus Updates vis SCCM
We verified we are downloading all four languages that we are configuring Pro Plus to contain (English, Spanish, Portuguese-Brazilian, and Polish). So far we are primarily testing within one site so hard to say if its a DP issue or not. I created some test machines this weekend to reproduce the issue and analyze more logs and noticed that the update seemed to hang at Downloading (50%) for over 30 minutes before it went to installing. Of course my attempt to reproduce the issue failed and both machines installed the updates :). I would say out of 75 people we hear from at least 10 folks every month that they see the updates fail.
- Mahamdrafiq SayyadMar 08, 2018Copper Contributor
I am getting the below error while deploying Office 365 update Semi-Annual Channel Version 1708 (Build 8431 2215)
Error : CAS failed to download update (c412e7d8-a454-4994-8f43-10188c83f339). Error = 0x8000000e. Releasing content request.
Erro: Failed to download update 0X8000000E
- Mahamdrafiq SayyadMar 08, 2018Copper Contributor
Office 365 update Semi-Annual Channel Version 1708 (Build 8431 2215) we have downloaded the updates with 7 languages and redeployed on all client machines, the download is failing very frequently 50%
if you have any solution for this issue please assist.
Regards
Rafiq Sayyad
- Lars HOLMGRENNov 16, 2016Copper Contributor
Did you get this problem solved? I'm on latest build for SCCM (1606 UR1) and I see this issue on quite a lot of users, maybe thousands. It looks very random, different sites etc. I'm really confused and is out of any more ideas.
- Chris EckelNov 20, 2016Copper Contributor
Not yet... but we have a Premier Support call open. I spent about 90 minutes on the phone with the support tech last week and they are in research mode now. I'll definitely update this once I find out more from MS.
- Chris EckelNov 29, 2016Copper Contributor
Update on this - the MS support rep was able to repro our issue in their lab. They claim that even though we specifcy Current Channel, the update process is also looking for Deferred Channel (which we do not download). I went ahead and tested deploying updates from both channels to an affected client; however, this did not result in any change.