วีดีโอ

Thanks for providing your feedback. On 1: The COM object is no longer needed with Cloud Updates, it is mentioned in the pinned comment and based on your feedback we also added it to the troubleshooting section of our Cloud Update documentation: learn.microsoft.com/en-us/microsoft-365-apps/admin-center/cloud-update#troubleshooting (should be online in next 48hrs) On 2: There are some scenarios which lead to the last user/email not being reported. We are actively investigating the issue. I'm sorry I don't have a better answer at the moment.

​@@OfficeDeploymentInsiders thanks

With Intune, expediting updates is more manual work in settin gup the configuration profiles and there is a slightly higher risk of e.g. getting the build number wrong or later on not removing the profile (which will pin the device to a specific version in the scenario of this video). With Cloud Updates it is much more straight forward, reduce deadline, remove waves or reduce wave delay hit save and you are done. If you do not update Cloud Update's configuration laater on, it will still push the latest updates to your devices in contrast to Intune which migh keep your devices on the version you specified as targetversion.

For Microsoft 365 Apps, you can't use WSUS standalone to manage updates. Never has been supported by WSUS, never will be. (It's different, if you have an SCCM running in addition to the WSUS server, then this documentation applies: learn.microsoft.com/en-us/microsoft-365-apps/updates/manage-microsoft-365-apps-updates-configuration-manager

Thanks!

When a target version is set, Office/Microsoft 365 Apps will update directly to this version. The local update engine does a delta comparison of 'what is on the box' and 'what should be on the box.' If local version is 'A' and target version specifys version 'C', it will directly download version 'c' of this file and overwrite the existing one, ignoring any version 'b' being available on the Office CDN. Or in other words: Updates are cumulative, not additive. It can always update from 'N-x' to 'N' in one pass.

Perfect thanks!

No, it doesn't. The Microsoft 365 Apps have their own inventory reporting mechanism implemented which will update the inventory in the Microsoft 365 Apps admin portal. If a device is Intune-managed, both technology stacks will work independently.

Please elaborate on your question. Update channels are a concept of controlling change, in itself it can't be disabled. But of course, you can choose to not deploy/use/support certain channels in your organization. Maybe I'm missing your point, happy to answer any follow-up questions.

Thanks for sharing your positive feedback!

Check out: learn.microsoft.com/en-us/deployoffice/admincenter/cloud-update#tenant-settings. In short, an exclusion window blocks updates from being deployed during a certain timeframe (e.g. 12/20 - 1/3). This can be be restricted to a group (no updates for Finance during their fiscal year end from 6/20 - 7/7). An exclusion group is not about a time frame, but about devices or users always being excluded from the Cloud update mechanism (e.g. certain servers or all CxO users).

Combining the native Intune Microsoft 365 Apps app and a configuration profile is a bit tricky.When using the native app mode, Intune will periodically evaluate if the local install still matches the configuration of the app (see th-cam.com/video/fA8lcnRXmkI/w-d-xo.html). If there is a drift, it will trigger a re-deployment of the app to enforce the configuration set in the app. This could lead to the following behavior: - Intune deploys Microsoft 365 Apps on Monthly Enterprise (through setup.exe) - Configuration policy sets Update Channel to Current Channel - Update engine fires, sees the new update channel configuration and updates local install to Current Channel - Intune evaluates the local install and detects a drift (installed=Current; set in app=Monthly ENterprise) and re-runs the setup.exe to reinstall Microsoft 365 Apps on Monthly Enterprise Channel - Rinse & Repeat What we have seen working is the following setup: - Intune Microsoft 365 Apps app configured to Monthly Enterprise, assigned to all users, excluded is group 'M365A CC' - Intune Microsoft 365 Apps app configured to Current Channel, assigned to group 'M365A CC' Now, if someone should be moved from Monthly Enterprise Channel to Current Channel, just throw them into the group 'M365A CC' and Intune will do the rest.

@@OfficeDeploymentInsiders I was hoping to use the settings catalog to set channels and give us better granular options compared to what you can do in the XML config designer. How could we use these then ?

Glad it helped!

In SCCM, error code 5 usually refers to 'Access Denied'. Please verify that SCCM can access the Office CDN at officecdn.microsoft.com to download the files. Check if SCCM (or its service account) is allowed to traverse your network, proxies and firewalls to the Office CDN.

Check out th-cam.com/video/g1rDR2aOAQc/w-d-xo.html!

1. If you do not know how to get to the "black page" you should not carry out anything on your computer with administrator rights. 2. The "black page" is the command line. To access follow this: Search bar -> Type: "cmd" -> Right click on Command Prompt -> Run as Administrator -> Click "Yes".

im looking at this: macadmins.software/docs/Network_Traffic.pdf

No way to force the check-in. Make sure that the active user is the one from the tenant you are looking at. It will check in at least once every 24hrs.

Hi @kinosounds. You can also use the Settings Catalog, as at the end the same registry values are set on the device. I used the ADMX template, as this is what I see most of the time being used. But you can go both routes, both will work. On Servicing Profiles/Cloud Updates: Those have priority over the Intune settings. If Servicing Profiles/Cloud Update is set to deadline = 0 and Intune is deadline = 1, the effective deadline will be 0.

Office 2019 is not a free product, for both personal as well as commercial use, a license is required. The ODT itself is a free tool and it can install Office 2019/2021 as well as Microsoft 365 Apps. The fact that you can successfully install the products using this tool does not imply that those are free products.

Good catch. Let's attribute this to the demo god :D The actual does not matter, just pick one and stick to it (not like I did in the video).

Please elaborate on your question a bit more, so we can see how to help best.

@@OfficeDeploymentInsiders I go into settings to update history and 5/7 updates say current channel (board) I was wondering if that's something that needs to be addressed if it's supposed to or if it wouldn't hurt my computer left like that. And if I do have to uninstall and then reinstall then how'd I go about doing that if needed.

Updates labeles as 'something Current Channel (Broad)' are most likely updates for the Windows Defender. Nothing to worry about.

@@OfficeDeploymentInsiders I had pretty much got it resolved thank you.

1. The policy setting via Intune configuration profiles is essentially the same as a GPO. It will keep the update channel applied via policy, and future update events will follow that channel. 2. Cloud Update (previously Servicing Profile) does take precedence over all other update management policies. Cloud Update Status in the Inventory > Show all devices view will tell you the devices that are managed and therefore have channel enforcement.

When deploying the channel change using the ODT, assuming it is <Updates Channel="InsertChannel" />, the action is silent and occurs in the background. The actual channel flip occurs when the next update sequence is triggered (automatic or via the backstage).

would like to see a short video explaining the new screens / cloud update