topic Re: Extended auto-updates in Peer-Peer Topics

Extended auto-updates

Bill_Gibson — Fri, 14 Feb 2025 20:45:27 GMT

We have the Extended auto-updates setting set to "Allow..."
The hope was that devices would then receive updates as part of the 10 year update announcement.

Instead of continuing to be updated, what we are finding is that devices are stuck at the last stable release version.
As an example, the Acer Chromebook Spin 11 (R751T / CP511) will only update to version 126.
It seems as if we need to move these devices to the LTC channel to move them to 132 (and beyond).

This seems like a logical organization challenge as we would want our production devices assigned to the Stable channel, while we would need to have these extended support devices in a separate OU so that they can be assigned to the LTC channel.

Does this sound correct?
Would LTS also offer a path forward for these extended support devices?
Any feedback from those using the LTC build in production?

Re: Extended auto-updates

mhermmsd — Mon, 24 Mar 2025 20:11:40 GMT

They are stuck at 126 because that was the last stable version offered for that model as of June 2024. Devices using extended auto updates have to be on LTS channel, which currently is also 126. You should be creating an OU separately for those devices so they can be on LTS channel.

Re: Extended auto-updates

MattDPenn — Tue, 25 Mar 2025 17:36:19 GMT

Was that a part of the information given to us on the lead up to Extended Updates? I don't remember LTS being a requirement for it but then our district already uses the LTS channel to avoid the issues that crop up with Stable channel not being all that stable. Plus I originally wasn't planning on using the Extended updates so I may not have read closely but its looking more and more likely to be a necessity given forecasted budgets...