Chromebox inital setup: how to avoid auto-upgrade

  • 1
  • Question
  • Updated 3 years ago
  • Answered
  • (Edited)
EDIT MARCH 21, 2018: Please note that all conversations related to Chrome OS in this Community should be considered obsolete and out of date. As announced in our new Community, Rise Vision is adding support for Chrome OS with a new version of Rise Player for Chrome OS.

To receive updates, make sure to subscribe to the Rise Vision Blog, or join the new Community and post questions.
=====================================================================================================================================================

I know this forum is not devoted to ChromeOS but it is one of the supported platform.

Does anybody know how to avoid getting an automatic auto-upgrade when a Chromebox is started for the first time?
As far as I know, the first time a Chromebox is started, it gets an auto-update to the last Chrome version. This is annoying knowing for instance the RiseVision issues with the new Chrome 45.
How can I get a first boot with the original version of teh Chromebox (so far, I think it is 41).

Later on, I may control the version by enrolling the chromebox in a Google OU domain that controls the auto-update and allowed version. But it does not help if at first boot, the Chromebox is auto-updated and, as afr as I know, the downgrade is then not possible.

Thanks for advice.
Photo of Thierry Masson

Thierry Masson

  • 922 Points 500 badge 2x thumb

Posted 3 years ago

  • 1
Photo of HSuarez

HSuarez

  • 11,896 Points 10k badge 2x thumb
Hi Thierry,
In the Displays section in your account, you can go to the Player Browser section and further manage the version of the Player Browser associated with that Display into:
  • Auto upgrade
  • Current
  • Previous
  • User managed
Thanks,

Hannah
Photo of LUIS REYES

LUIS REYES

  • 1,016 Points 1k badge 2x thumb
Hi, also you can try this: from a brand new chromebox after you entered the network info, and then you  are prompted to accept the agreements, after that, immediately  press CTRL+ALT+E  (this was a tip from a google support) and that must stop the search for updates. For me worked fine...hope it works
Photo of Thierry Masson

Thierry Masson

  • 922 Points 500 badge 2x thumb
Great tip. I will try it.
Photo of Blake Freeman

Blake Freeman, Official Rep

  • 36,116 Points 20k badge 2x thumb
Thierry,

To my knowledge, there is no way to keep a ChromeOS device from updating if it is not a managed device.
Photo of LUIS REYES

LUIS REYES

  • 1,016 Points 1k badge 2x thumb
Hi Thierry, well yes  in fact these are the same keys combination to call the enrollment, (do not know why) but I have applied this just immediately after the network connection as some one from google support told me, to stop the update process.
And when you get to the log in screen , if there you go again with the same key combination, is where you see the enrollment process.

In this (large) post , we were talking about similar issues https://community.risevision.com/rise_vision_inc/topics/intermittent-freezing-first-minute-of-schedu...

Buy mainly, my problem also was on how to get back from OS 45 to an stable 44. 
In summary: I made a backup with the "recovery utility app" from a cheomebox that at that moment stlll has the 44 and then applied to the others, but avoiding updates with the above keys, and also under the management console set each device to NOT upgrade.

Hope it works!
regards
Photo of Thierry Masson

Thierry Masson

  • 922 Points 500 badge 2x thumb
Hi Luis,
Great sharing.
In the Google Doamian OU dedicated to the SignageAge Chromeboxes if I've set kiosk mode with RiseVision and disable auto-update strictly even not metioning 44.* as "Restrict Google Chrome version to at most".
THis is not so good because I finally checked that I still had chrome 43 chromeboxes.

My lesson learnt with Chromeboxes (and even interdependently of RiseVision) is that you need a very strong change and Chrome OS release management). We aim to deploy in 2016 around 100 RiseVision Chromebox stations worldwide for internal communication. I don't want to face a majour outage requiring downgrade  "recovery utility app". I've selected Chromebox because of easiness of management and ability to control a lot remotely (compared to Windows PC for which we have a very bad experience with virus and patching update). Hope I will be satisfied.
Thanks.
Photo of Thierry Masson

Thierry Masson

  • 922 Points 500 badge 2x thumb
A question for Luis who appears experienced in Chromebox ..

This morning (European time), I've created a ChromeOs Recovery USB media. I did it from a PC using the Chrome Recovery extension. I was able to recover the Chromebox perfectly well but I expected maybe not to get the very last version of Chrome OS. But I got the last chrome 45 version....

Luis, you told that it is possible also to create such recovery from a Chromebox directly and in this case, the recovery corresponds to the version of the Chromebox. Correct ? If correct, I've to get back a managed Chrome 44 from a remote site. 
Photo of LUIS REYES

LUIS REYES

  • 1,016 Points 1k badge 2x thumb
Hi.
Yes that is correct, you can run the recovery utility directly from the chromebox and get that  OS backup, then start the WIPE PROCEDURE for the Chromebox you want to apply it: turned off device, turn it on while pushing with a clip the recovery button, insert the USB with system 44. Once the process finish I just needed to be aware to push Ctrl+ALT+E after I set the network, accept the terms and conditions and at this moment press the key combination to stop searching for updates.

This recovery , as I understood can only be applied across the same CBox models.


I agree with you about the need of a more stable Chrome OS native devices and management.  What I like about Chromeboxes is the easy way to set it up and the Kiosk mode capability , and with the Chorme management, even when there are a lot of false alerts about devices going offline, one very useful feature is the print screen, that let me know (because a clock in the presentation) that everything it is ok.  But with a large deployment you need a better way to asure all it is ok.

I haven ́t tested any windows base yet, my only concern, is that  (maybe  I,am wrong) is that you can`t  run them in kiosk mode (or at least in a transparent way) and also the need of a third party console management.

Have you evaluated other devices...by the way.
regards
Photo of Thierry Masson

Thierry Masson

  • 922 Points 500 badge 2x thumb
Many thanks Luis for your valuable feebdack.
Thierry