[ms office - o365] Deploying O365 updates with SCCM

[KevinB]

I'm struggling to get updates for O365 working with SCCM.

 

I have worked through this guide: https://www.prajwaldesai.com/deploy-office-365-updates-using-sccm/ and as far as I can see have done everything correctly. I have downloaded an update, deployed it to a small collection of just 1 PC (mine) for testing but nothing appears in the Updates section of Software Centre on the PC. If I look at Monitoring/Deployment/{the name of this deployment} it lists my PC in the "Unknown" section with "Client check passed/Active" but that's as far as it gets. Manually running "Software Updates Scan Cycle" and "Software Updates Deployment Evaluation Cycle" on the PC don't work.

 

I've checked that the COM application is present and configured (which seems to be a common cause of the non-delivery of updated) and it's all correct.

 

Anyone got any ideas?

[smarties11]

Have you set an SCCM client software update policy to allow management of the Office365 client? It will take a little time for this to be picked up.

 

What timescale did you set for the availability and deployment deadline? Unless you set these to 'as soon as possible' the SCCM client decides when to pull the update within the dates you set based on client activity.

 

Manually running the scan cycles on the client is always hit and miss. They don't start immediately; it just makes the request of the client and again the client decides when to run it based on activity.

[KevinB]

Hi @smarties11,

 

Yes, Office management was set as part of the install in the config.xml, and as a backup it's also set in GP. The machines I'm testing on have the correct registry key set to reflect this.

[smarties11]

I think we're talking about different things @KevinB. It's the SCCM client setting I mean, as in my screenshot below....

 

[KevinB]

Ah, sorry, yes we were talking about different things

 

The setting you're referring to is already set to "Yes" though.

[smarties11]

Seems a bit strange then! I see you said you've deployed the update to a collection containing only one PC - are the client settings above also deployed to that PC? Or could it be using the default policy? And I assume you're using the correct correct x86/x64 update flavour to match the O365 client architecture you have deployed?

 

It doesn't sound like you are doing anything different to us, I think I followed the same guide you linked to when we set it up a few months back too!

[KevinB]

Well, I've found the answer. And it's a pain We deploy Windows Updates from an onsite WSUS server independently of SCCM, and it appears that in order to deploy O365 Client updates, SCCM wants to set itself up as the client's WSUS server and push the update that way:

You can't have your WSUS server set by GPO, and have O365 updates sent out by SCCM it would appear.

 

Hey ho! Off to learn how to deploy all updates with SCCM now then

[free780]

You can update from a folder but you'd have to script the download of new updates. You won't get any reporting. It is better through Configmgr.