$chromeVersions = (Invoke-WebRequest -uri $Uri).Content | ConvertFrom-Json Return the current release version of Chrome # Read the JSON and convert to a PowerShell object. # Get latest Google Chrome versions from public JSON feed - Aaron Parker Another benefit is that you get a media libary where you can easily rollback if lastest release is unstable. IMHO my scripts will only be published when they’re true evergreen. If I would download each and every time that would be stupid. In my Infrastructure as Code deployment I deploy 14 VM’s in 30 minutes. Not to mention what happens when the script runs about the same time on 2-3 VMs. This might makes sense in some case, but in terms of VMware Tools (working on it) it’s very unefficient, unstable and waste of time to download each and every time. Which means I needed to do stuff manually or simple download and delete each and every time. You see even with Google’s URL to their latest version it wasn’t possible for me to grab the version number. This was the missing piece of the puzzle to make my Google Chrome Enterprise installation script evergreen. Yesterday’s post Download and Install Latest Mozilla Firefox about evergreen URLs spiked quite some engagement in the community on Twitter sharing their Git resources.Īaron Parker shared his Function on how to read Google’s JSON file to find the latest version. At this point it was is clear that the MSI installer of the Chrome. 96 failed there with installation error 1722.Īfter some tests, Bernie installed the older Chrome 87 on system 2, and then was able to install Chrome. System 2: The machine running Windows 10 Enterprise 1809 did not have a Chrome browser installed yet the installation of Chrome.System 1: The machine running Windows 10 Enterprise 1809 had the previous version of Chrome browser installed the update installation went through.

The difference between the two test machines was: At Google there is this thread about Error 1722, but it did not help in the current case.

96 using the MSI file on two Windows 10 test machines, one system failed with the installation error 1722. They use systems with Windows 10 Enterprise 1809. An MSI file of the browser provided for enterprises is used to install each new Chrome version via the software deployment tool.

The automatic updates of Chrome via its updater are disabled via GPO. In Bernie`s corporate environment, the Chrome browser is deployed automatically via a software deployment tool. German blog reader Bernie reached out with this comment reporting an installation error that I'd like to briefly address. In addition, this security update closes 36 vulnerabilities in the older browser versions. Chrome 88 is a new development branch that has dropped both FTP and Flash support. I had addressed the browser update in the blog post Chrome.

Google chrome standalone enterprise msi