jamwatn Posted February 4, 2022 Posted February 4, 2022 (edited) Hi, I am trying to manage 365 App updates via SCCM/MECM as these have been neglected at my school. I've created the following ADR rule and have the below updates: However, if I deploy this to a client, it receives this update: Which shows as following the 'current' channel which is obviously a bleeding edge version of Office which probably isn't ideal to deploy. Has anyone got a guide that they followed to automate the process, or is it something I have done wrong? Thanks Edited February 4, 2022 by jamwatn
MartinByard Posted February 4, 2022 Posted February 4, 2022 Hi @jamwatn, The issue there stems from what channel was sepcified when Office was installed, not what channel your ADR rules are providing updates for. To easily manage this in SCCM/MECM you can use configuration baselines, a guide for which can be found here: https://enterinit.com/changing-office-365-proplus-update-channel-with-configuration-manager/
jamwatn Posted February 4, 2022 Author Posted February 4, 2022 Hi @jamwatn, The issue there stems from what channel was sepcified when Office was installed, not what channel your ADR rules are providing updates for. To easily manage this in SCCM/MECM you can use configuration baselines, a guide for which can be found here: https://enterinit.com/changing-office-365-proplus-update-channel-with-configuration-manager/ Thanks for replying quickly. Interesting, so it looks like the 365 apps we have deployed are version 1608 (or so..), but my assumption then that all of our O365 clients would then have updated beyond this if they are set to current from install? If it means I need to change config on clients, can I use the Office365 portal to do this, or do I have to use the method you have sent me because it is on client machines that I am configuring?
jamwatn Posted February 4, 2022 Author Posted February 4, 2022 I've had a further go at the link you have send me. It updates the registry as expected, however Office still displays current channel and then SCCM begins to deploy 'Current Channel' still. Does anyone else deploy Current?
chris_uk Posted February 4, 2022 Posted February 4, 2022 I've had a further go at the link you have send me. It updates the registry as expected, however Office still displays current channel and then SCCM begins to deploy 'Current Channel' still. Does anyone else deploy Current? I'm on current, manual deployment to IT Team first, the 4 IT Rooms and then to the other workstations around the school. Usually all done within a few days after testing.
jamwatn Posted February 4, 2022 Author Posted February 4, 2022 I really cannot see why it won't change from Current to Semi-Annual I've changed everything I can find.
psydii Posted February 4, 2022 Posted February 4, 2022 We've been on current here and have been for years. Might be that your users are fine with that. Does mean they get the new-shiny faster. Always a fan of redefining requirements to match the available solutions.
MartinByard Posted February 4, 2022 Posted February 4, 2022 Hi @jamwatn, we noticed then we were changing the channels using the method I linked to, it was slow and sometimes needed a reboot for things to fully take effect (as you are editing the HKLM reg hive). We've mostly gone for the Monthly Enterprise Channel rather than full blown current, or Semi Annual.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now