(imported topic written by JackCoates91)
Hi,
we’re posting initial Google Chrome support in Updates for Windows Applications today. As seen in other forum posts, there are some notes to Chrome support that make this worth discussing.
The first item to be aware of is that there are two editions of Google Chrome, a consumer edition distributed via EXE and a corporate edition distributed via MSI. While they are supposed to be cleanly interchangeable, this was not the case in our testing. We’re recommending that the EXE be uninstalled and replaced with the MSI.
Second, the MSI appears to be time or location stamped in some way during download; we found that the SHA1 of a downloaded file was unpredictable, despite version and size being the same. This prevents us from producing an installation Fixlet at this time; however, the MSI is easily distributed via the BigFix Software Distribution tool. This is probably the best method to distribute the software with.
Finally, it’s best to note that the automatic software update process will turn itself back on if the end user opens the “About Google Chrome” screen. To keep it turned off, use the Disable Automatic Software Updates Task to create an open action.
There are three Fixlets for Chrome support:
Google Chrome $version Available
– an audit fixlet to let you know that consumer or corporate edition is installed and not up to date.
Google Chrome - Consumer Edition Installed
– a removal fixlet for the consumer edition.
Google Chrome - Disable Automatic Software Updates
– a configuration fixlet for automatic updates.
thanks,
Jack