Updated: Google Chrome Update Tool for Android, using Workspace ONE API’s

Recent news from the Google Chrome team reminded me to revisit a previously created tool that allowed enterprises to manage public application updates in their digital workspace. The Chrome team announced that they would temporarily pause upcoming Chrome & Chrome OS releases, and focus exclusively on security updates. It became clear that I needed to update this tool, and tailor it for Google Chrome. 

Widespread use of Chrome, combined with the number of CVE's addressed in each release of Chrome requires every enterprise to have the ability to upgrade their endpoints. The solution needs to be tactical, precise, and meet the business needs. In other words, just allowing devices to auto-update applications on their on, won't cut it. 

Allowing applications to auto-update leaves the business asking; when will the application upgrade? Can we force them to upgrade? Can we force them to upgrade at a specific time?

No caption necessary.

While the tool is helpful, fulfills a need, is able assist with more than just Google Chrome; the script required end-user modification, and could be reworked to work with little modification required. The intention of this updated tool was that anyone could copy the code, and reuse it in their own environment with no modification required. But before we get to what the tool looks like; let's remind ourselves of what the experience is like for the end-user, before they call the help desk.

They see this, but don't worry, Workspace ONE has an API to solve that

In my spare time I updated the tool. The tool is a bit more tactical, and can be used to specifically update Google Chrome on Android devices. Some of the differences between the original tool, and this tool include;

  • No need to manually lookup Application ID
    • Function in PowerShell to locate application ID
  • Leverages config.ini file to store sensitive environment data
  • Purpose built, artisanal, handcrafted tool, curated for Google Chrome on Android
So, what does the tool look like? See below:

Lines deserving your attention include:
Line 13 requires the config.ini file to be in the correct location (script uses current location\config.ini)
Lines 20,21,22,23 use the UAT values stored in the config.ini file. All you need to do to use the script is setup your config.ini file. If you are using this in production, update the the variable $WS1Env.UATapikey to $WS1Env.prdapikey (in addition to prdb64 and PrdEnvironment).

For all the latest news on upcoming Chrome releases, be sure to check out the Chrome Releases blog from the Chrome team at:


Bonus Tip: Line 32 parameter bundleid can be modified for any public application. If you wanted to update the Hawaiian Airlines app, you would replace com.android.chrome with com.hawaiianairlines.app

Ryan Pringnitz


Popular posts from this blog

How to use Fiddler Everywhere to inspect Android network traffic to troubleshoot SAML authentication issues

Clean up duplicate identities and users from Workspace ONE using REST API's and PowerShell

Zimperium Delivery and Activation on Android Enterprise with Workspace ONE UEM Product Provisioning