We have SCCM 1802. I am attempting to deploy an Office 365 Client update to a small group of about 10 computers that are all Win10 1803. Most devices report Compliant even though the install never took place. (Only a couple installed correctly.) The O365 clients are enabled to receive updates from SCCM.
WUAHandler.log shows the that the scan successfully completes; the update never appears in UpdatesDeployment.log though other updates do; WindowsUpdate.log only has 2 errors:
"*FAILED* [80240007] Method failed [CAgentServiceManager::GetTargetedServiceMapping:3010]" - this one repeats
"*FAILED* [8024000C] LoadHistoryEventFromRegistry completed" - 1 instance
Computers that already have the update installed come back as being Complaint as they should. Devices having this issue include ones that were just imaged. I have also noticed that devices whose O 365 clients are not enabled to receive updates from SCCM also immediately move to Compliant when an update is pushed to them.
When I look at the update itself, it gives on the Summary tab the correct # of devices that require it. However, when I look at its Software Update Group, it has the wrong #s and shows most of our enterprise to already be complaint when most devices do not have it.
Update:
Update group:
What do these errors mean? I have recreated the collection, deployment package, and software update group. This issue only happens with Office 365 Client updates.
Skip
WUAHandler.log shows the that the scan successfully completes; the update never appears in UpdatesDeployment.log though other updates do; WindowsUpdate.log only has 2 errors:
"*FAILED* [80240007] Method failed [CAgentServiceManager::GetTargetedServiceMapping:3010]" - this one repeats
"*FAILED* [8024000C] LoadHistoryEventFromRegistry completed" - 1 instance
Computers that already have the update installed come back as being Complaint as they should. Devices having this issue include ones that were just imaged. I have also noticed that devices whose O 365 clients are not enabled to receive updates from SCCM also immediately move to Compliant when an update is pushed to them.
When I look at the update itself, it gives on the Summary tab the correct # of devices that require it. However, when I look at its Software Update Group, it has the wrong #s and shows most of our enterprise to already be complaint when most devices do not have it.
Update:
Update group:
What do these errors mean? I have recreated the collection, deployment package, and software update group. This issue only happens with Office 365 Client updates.
Skip
