This is clear, concise, well organized, and shockingly entertaining for a technology video thanks to the host not being a disorganized or monotone. Well done! Thank you!
Do you recommend devices reach out to MS Update catalog for update contents or Distribution points for update contents? If MS update catalog, will device’s download their assigned release channel update contents? (Ex: SAEC channel devices downloading monthly channel updates) how can we control this?
In general, our recommendation is to utilize the Office CDN whenever possible. Only use on-prem content if you have a need to do so. With OfficeMgmtCom enabled, devices will look to ConfigMgr for instructions on which updates to install. A device on SAEC will not randomly update to MEC, unless you explicitly issue a channel change and deploy the MEC update.
you originally created a "Monthly Enterprise Channel" folder inside of your Microsoft 365 Apps folder but then in parts of your other videos you have the folder name "M365 Apps - MEC - April 2023" ?
Thanks lot , Sorry I have not seen the video fully yet but I have one question which I was googling , surely I will watch this video fully as its very useful . My question is once my SCCM admin has pushed the updates , does the end users need to restart PC or restart Office 365 Apps for them to receive the updates ? I know I can see the status in SCCM but for a non SCCM admin , what he can expect when the updates will be rolled out to all or most users ? Thanks in advance
The need to reboot depends. When updates are applied natively to Microsoft 365 Apps, a reboot of the device is not required. The user simply needs to restart their Office apps and they are good to go. With ConfigMgr, if the apps are open when the update is applied, instead of force closing the apps, it will put the device in a pending reboot state so it can apply the update at a convenient and safe time when the apps are not open.
@OfficeDeploymentInsiders thank you for such a highly informative video. I do have a question about our environment. We currently have 2202/2208/2302 builds in our environment, 24 of which are on 2202 but most of them have updated to the newer builds with no issues. Should we not be deploying the extended quality updates to force those workstations to update to a newer build?
We always suggest to move to the latest version as long as no app compat or other reasons are standing against it. Devices on e.g. 2202 SAEC can directly update to e.g. v2302 SAEC as long as it is offered to those devices. In case you need to keep those devices on an older version, you should surely deploy the monthly security updates to keep them secure.
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.
Thanks for the video. Is the dynamic source supposed to work with Office 2021 LTSC and the configmgr wizard? Once I delete the office folder from the package source, confimgr fails to distribute content, looking at the logs it tries to look for that office folder and its contents. It seems to work when I just manually create an application with setup.exe and the XMLs.
Yes, the dynamic method will work with LTSC as well. Review the properties for your application, specifically the content source path. Confirm its pointing at the root application folder (e.g., \\server\Microsoft 365 Apps LTSC 2021). When you distribute the content to your DPs that should be the only directory ConfigMgr cares about. For testing purposes, you could also try creating a new application from scratch and using the source folders you've created (setup.exe + XMLs).
@@OfficeDeploymentInsiders Thank you very much for getting back to me. Yeah creating new application with the exe and xml did work. Tried again to create the 2021 LTSC application with the configmgr wizard, after deleting the office folder from source, package distribution fails. (distmgr.log GetFileAttributesW failed for \\?\UNC\server\SCCM_Apps\Office test\office\). Tried the to do the same with Microsoft 365 Apps, followed same procedure and that had no issues distributing the package after deleting the office folder. There is something different in configmgr for 2021 LTSC.
@@neapolitanpizzafan I ran through it in my lab just to be sure. Currently running CM 2211. For the app I selected Office LTSC Professional Plus 2021 - VL. I'm not seeing this issue. I was able to distribute/redistribute the content with and without the Office folder present. The only directory reference is to the root application folder, which is what I would expect > Taking snapshot for content Content_ae3c35c2-2128-4791-b6a5-214df75d9fa5.1 from source \\domain.com\dfs\CM-Source\Applications\Microsoft Office\M365 Apps LTSC\
This is clear, concise, well organized, and shockingly entertaining for a technology video thanks to the host not being a disorganized or monotone. Well done! Thank you!
Thanks for sharing your positive feedback!
This helped me out Astronomically! CUDOS!
Glad it helped!
Do you recommend devices reach out to MS Update catalog for update contents or Distribution points for update contents? If MS update catalog, will device’s download their assigned release channel update contents? (Ex: SAEC channel devices downloading monthly channel updates) how can we control this?
In general, our recommendation is to utilize the Office CDN whenever possible. Only use on-prem content if you have a need to do so. With OfficeMgmtCom enabled, devices will look to ConfigMgr for instructions on which updates to install. A device on SAEC will not randomly update to MEC, unless you explicitly issue a channel change and deploy the MEC update.
you originally created a "Monthly Enterprise Channel" folder inside of your Microsoft 365 Apps folder but then in parts of your other videos you have the folder name "M365 Apps - MEC - April 2023" ?
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).
Thanks lot , Sorry I have not seen the video fully yet but I have one question which I was googling , surely I will watch this video fully as its very useful . My question is once my SCCM admin has pushed the updates , does the end users need to restart PC or restart Office 365 Apps for them to receive the updates ? I know I can see the status in SCCM but for a non SCCM admin , what he can expect when the updates will be rolled out to all or most users ? Thanks in advance
The need to reboot depends. When updates are applied natively to Microsoft 365 Apps, a reboot of the device is not required. The user simply needs to restart their Office apps and they are good to go. With ConfigMgr, if the apps are open when the update is applied, instead of force closing the apps, it will put the device in a pending reboot state so it can apply the update at a convenient and safe time when the apps are not open.
@OfficeDeploymentInsiders thank you for such a highly informative video. I do have a question about our environment. We currently have 2202/2208/2302 builds in our environment, 24 of which are on 2202 but most of them have updated to the newer builds with no issues. Should we not be deploying the extended quality updates to force those workstations to update to a newer build?
We always suggest to move to the latest version as long as no app compat or other reasons are standing against it. Devices on e.g. 2202 SAEC can directly update to e.g. v2302 SAEC as long as it is offered to those devices. In case you need to keep those devices on an older version, you should surely deploy the monthly security updates to keep them secure.
I get error 5 when trying to download the packages where can I look to see whats going on.
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.
Thanks for the video.
Is the dynamic source supposed to work with Office 2021 LTSC and the configmgr wizard? Once I delete the office folder from the package source, confimgr fails to distribute content, looking at the logs it tries to look for that office folder and its contents.
It seems to work when I just manually create an application with setup.exe and the XMLs.
Yes, the dynamic method will work with LTSC as well. Review the properties for your application, specifically the content source path. Confirm its pointing at the root application folder (e.g., \\server\Microsoft 365 Apps LTSC 2021). When you distribute the content to your DPs that should be the only directory ConfigMgr cares about. For testing purposes, you could also try creating a new application from scratch and using the source folders you've created (setup.exe + XMLs).
@@OfficeDeploymentInsiders Thank you very much for getting back to me.
Yeah creating new application with the exe and xml did work. Tried again to create the 2021 LTSC application with the configmgr wizard, after deleting the office folder from source, package distribution fails. (distmgr.log GetFileAttributesW failed for \\?\UNC\server\SCCM_Apps\Office test\office\).
Tried the to do the same with Microsoft 365 Apps, followed same procedure and that had no issues distributing the package after deleting the office folder.
There is something different in configmgr for 2021 LTSC.
@@neapolitanpizzafan I ran through it in my lab just to be sure. Currently running CM 2211. For the app I selected Office LTSC Professional Plus 2021 - VL. I'm not seeing this issue. I was able to distribute/redistribute the content with and without the Office folder present. The only directory reference is to the root application folder, which is what I would expect > Taking snapshot for content Content_ae3c35c2-2128-4791-b6a5-214df75d9fa5.1 from source \\domain.com\dfs\CM-Source\Applications\Microsoft Office\M365 Apps LTSC\