This message was deleted.

Let them update themselves.

Controlled in non-persistent and update themselves in persistent

Lots of controlled updating required in non-persistent in that case 🤣

maybe cut down on the versions used? 😄

Fully scripted builds with the lovely 'Evergeen' PowerShell module.

They aren’t the version used, they are the amount of times google has been updated. If you were using v117 that has been updated 4 times already this month with security updates. Anyhow, there are always different ways to doing things, in my case security is king so I let it update itself. However I don’t use NP

i have a simple pooled desktop cvad on prem and just change the chrome reg key from 0 to 1 when i crack it open for updates to let it auto-update itself and back to 1 when sealing.

neverred @Deyda

You have to also ask yourself way do you want to update browsers, I’d think most would say to apply security fixes. If that’s the case then you’d want them applied ASAP. If we take Google as an example it’s been updated 4x this month alone, therefore the quickest way to get those browsers updated on persistent devices is letting them update themselves. Now if we take NP, why wouldn’t you let them auto update, I think it’s because you’d be concerned about the performance hit upon first boot/login if it wasn’t updated in the master image. I’m not sure how often everyone updates their master image, I’m guessing not 4x this month though. So the question about how you update the browsers, if security is your concern, is what ever is the quickest - updating master image, auto updates, you pick your poison. Now if security isn’t the concern, rather how I do this in a controlled predictable fashion - using evergreen is key, along with updating master images for NP.

We push vDisk (PVS house here) update and use our software delivery for persistent, we approve the update and we push an update automatically and gradually to all.

Appv

Non persistent environment? Evergreen script 😊