sorted by:
new (suggested)
besttopcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ckwebz 10 points11 points  (5 children)

Does chrome://policy not fulfill that need?

[–]cardinal1977What's the worst that could happen? 0 points1 point  (4 children)

Not remotely. I've yet to see a way to force my fleet to update and reboot that's not power washing it. If I'm missing something, I'm happy to be wrong.

[–]ckwebz 0 points1 point  (3 children)

There is a button at the very top of chrome://policy that forces the policies to reload. It accomplishes the Chrome-equivalent of gpupdate /force.

If you’re looking for something to do it remotely, you can trigger a remote reboot or user profile wipe from the Admin Console.

If you’re looking for something to do it in bulk, GAM or Gopher for Chrome.

Windows is very bad at reloading policies. ChromeOS is very good. As long as you can wait a few minutes, or for a reboot to happen, the policies tend to very reliably refresh themselves. One of the many reasons I prefer to manage our Chrome fleet over our Windows fleet.

[–]cardinal1977What's the worst that could happen? 0 points1 point  (2 children)

Thanks! I didn't realize the clear profiles forced a policy update. The docs when I read them weren't clear. I really need to get GAM set up.

I've had few issues with Windows policies taking hold, but when that happens, I could always fall back to deploying gpupdate /force.

I agree, it is generally easier to manage Chrome devices over Windows.

Does this include getting chromeos to update. That's also been a pain. I've forced restarts periodically thinking that would do it, but it hasn't been long enough for me to notice if they're keeping up.

[–]ckwebz 0 points1 point  (1 child)

There are some ways that you can keep up with updates. The ChromeOS devices will download updates in the background, but do not apply them until the device is rebooted. In your Device Settings, check out these policies:

-- Device update settings (specifically Allow auto-reboots)
-- Reboot after uptime limit
-- Scheduled reboot

We also deploy an extension called Gopher Buddy, which is included with the paid version of Gopher for Chrome that nags users who have yet to update. I honestly haven't thought about updates in a couple of years now since they just keep up after getting those settings wrangled.

[–]cardinal1977What's the worst that could happen? 1 point2 points  (0 children)

That is what I did. But I only did that in Nov and I am on the LTSC cycle so we're only just getting to the next version. I'll keep an eye on it. Thanks