Correct way to update Google Chrome MSI through Group Policy

I am deploying Chrome through group policy. This is working fine.

Obviously Chrome has a pretty regular update cycle. I am not allowing Domain Users to install Chrome updates.

Having subscribed to the release blog, and downloaded/tested a new release MSI, what is the "correct" way to deploy a Chrome MSI?

For example: do I use the built in Group Policy MSI update feature? Do I overwrite the MSI file with a new one? Do I delete the policy and make a new one, linked to the newer MSI? Or do I allow Domain Users to perform Chrome updates automatically?

P.S. As a humorous aside, if this question gets down-voted, closed or voted to be closed as non-constructive, I will probably kill myself. You will have blood on your hands.

Solution 1:

You ultimately need to check whether Chrome can be updated or not - suggest making a policy in a test OU with a machine in it.

If it can be updated, you could add a new MSI to the same GPO each time, and let it roll it out.

By unticking the 'Uninstall this application when it falls out of the scope of management' option, you can remove old MSIs from the GPO without it trying to perform an uninstall at the clients, when they next update their policies.

I know I've not been completely specific with this program, but I hope this helps anyway. With feedback, the answer can probably be made more specific to Chrome, but their enterprise MSI is not special as such, it is just an MSI!

EDIT / ANSWER / SOLUTION:

Just to sum up the answer to this question (based on the further discussion in the comments below).

• Create a GPO for handling Chrome (solely is a good idea for organisation)
• Each time a Chrome update is released, add the MSI as a new assigned entry in the Software Installation section of the GPO.
• Be sure to disable the "Uninstall software when it goes out of scope" option
• Since a GPO is applied in an old->new order, you can safely delete the software assignments for old Chrome versions, just keeping the latest version and one or two prior to this.

Credit to Snellgrove.