Approach to Updating Application Content in MECM

Question

I have the M365 Apps for enterprise semi-annual enterprise channel deployed in my organisation using MECM (currently version 2309). This is using the ODT tool with binaries stored in MECM content. This is all working fine but the binaries are from Nov 2022. Clients  thereafter update from the CDN as needed. I want new deployments to deploy the latest version from the semi-annual channel. Since this was originally deployed at a collection with all Windows 10 machines and hence all report as deployed I’m wondering what approach I should take?

 

Option 1: Create  a new app with updated content? This seems to just double-down on the existing pattern and issue. I’ll have the same issue when next release

Option2: update the content in place and re-distribute content? Will this cause an app revision increment/ re-deploy to client (want to avoid that!)

Option 2: We only have two DPs so simply copy the binaries in manually so there is no update revision to the app?

Answer 1

Hi,

In SCCM application management will allow SCCM admin to upgrade or replace existing applications using application superdense. To supersede an application, you have to create a new deployment type to replace the deployment type of the superseded application.

Option 1: Create a new app with updated content? This seems to just double-down on the existing pattern and issue. I’ll have the same issue when next release

Yes, you are right.

Option2: update the content in place and re-distribute content? Will this cause an app revision increment/ re-deploy to client (want to avoid that!)

Re-distribute content will not trigger re-deploy to client.

Option 2: We only have two DPs so simply copy the binaries in manually so there is no update revision to the app?

This is not recommended.