Skip to main content

I have created a script to check for Architecture and snag the correct installer for Chrome. This is currently working, hope this helps others.

There is a similar Topic here: https://community.jamf.com/t5/jamf-pro/install-latest-version-of-google-chrome-without-re-packaging/m-p/156742/page/2

Wanted to start a new one with the focus on Intel and M1

Thanks to @cbrewer for the solution I did not need to choose between and intel and an M1 installer, I also Changed the .dmg to a .pkg with the extra bit of agreeing to the license etc, with the appended URL.

 

#!/bin/zsh
# Changed the installer from .dmg to .pkg and took out the bit for choosing an architecture.

# make temp folder for downloads

mkdir "/tmp/googlechrome"

# change working directory

cd "/tmp/googlechrome"

# Download Google Chrome

curl -L -o "/tmp/googlechrome/googlechrome.pkg" "https://dl.google.com/chrome/mac/stable/accept_tos%3Dhttps%253A%252F%252Fwww.google.com%252Fintl%252Fen_ph%252Fchrome%252Fterms%252F%26_and_accept_tos%3Dhttps%253A%252F%252Fpolicies.google.com%252Fterms/googlechrome.pkg"

# Install Google Chrome

sudo /usr/sbin/installer -pkg googlechrome.pkg -target /

#Tidy Up

sudo rm -rf "/tmp/googlechrome"

#Bless Google Chrome app

xattr -rc "/Applications/Google Chrome.app"

 

In case anyone has found an installer that has separate Installers for Intel Vs. ARM You could use this as a template in the download section:

 

# Download Correct installer based on Architecture

arch_name="$(uname -m)"

if [ "${arch_name}" = "x86_64" ];
then
curl -L -o "<path to temp directory>/<Package Name>" "URL to Intel Package"
elif [ "${arch_name}" = "arm64"]
then curl -L -o "<path to temp directory>/<Package Name>" "URL to ARM Package"
fi

 

 

I think I see where it errored. In the 2nd script. It failed to launch an app that doesn't exist. I did check the app installed. Thank you for your help.


We want the launch one to run last, that's why I put a "z -" in the title.

I'm looking to run this script and it runs fine in terminal, but does not run when deployed via Self Service. Chrome isn't our primary browser, so it's only available there and will be left up to the user to update. No part of the script, from beginning to end runs properly. It's like self service isn't even trying to run it. Any ideas on where this could be hanging up? It has been copied and pasted directly from the latest script above.

I'm looking to run this script and it runs fine in terminal, but does not run when deployed via Self Service. Chrome isn't our primary browser, so it's only available there and will be left up to the user to update. No part of the script, from beginning to end runs properly. It's like self service isn't even trying to run it. Any ideas on where this could be hanging up? It has been copied and pasted directly from the latest script above.


I've had this happen before, what happens when you delete the policy and try again?

I'm looking to run this script and it runs fine in terminal, but does not run when deployed via Self Service. Chrome isn't our primary browser, so it's only available there and will be left up to the user to update. No part of the script, from beginning to end runs properly. It's like self service isn't even trying to run it. Any ideas on where this could be hanging up? It has been copied and pasted directly from the latest script above.


Also screenshots of the elements of the policy may help us as well if after recreation it is still not working 🙂

I ended up with the same result. Just a failure notification from Self Service and seemingly no activity takes place. I'm watching /tmp for the googlechrome folder to appear as my point of reference for if the script is even trying to run. I've also looked for logs, but luck there either.

 

 

 

I ended up with the same result. Just a failure notification from Self Service and seemingly no activity takes place. I'm watching /tmp for the googlechrome folder to appear as my point of reference for if the script is even trying to run. I've also looked for logs, but luck there either.

 

 

 


Very Strange, have you tried choosing a trigger (I know it's not needed with Self Service) or recreating it from scratch, I have had multiple policies fail on me (no indication of running) and had to recreate them for some reason, or is there anything that might prevent this from running on the machine, like another policy?

Very Strange, have you tried choosing a trigger (I know it's not needed with Self Service) or recreating it from scratch, I have had multiple policies fail on me (no indication of running) and had to recreate them for some reason, or is there anything that might prevent this from running on the machine, like another policy?


I finally broke down and hit up Jamf support. Looks like something just happened to be broken on the couple machines that I was testing on, regarding the device certificate for Jamf. I renewed it through terminal and archived the old one. That seemed to do the trick. It was weird because all of the other functions of Jamf were working through self service. App installation, etc. and the device was sending inventory and check-ins to our Jamf Pro server, but JUST scripts were broken. We're good now and the script works perfectly as written, so thank you for sharing it!

I finally broke down and hit up Jamf support. Looks like something just happened to be broken on the couple machines that I was testing on, regarding the device certificate for Jamf. I renewed it through terminal and archived the old one. That seemed to do the trick. It was weird because all of the other functions of Jamf were working through self service. App installation, etc. and the device was sending inventory and check-ins to our Jamf Pro server, but JUST scripts were broken. We're good now and the script works perfectly as written, so thank you for sharing it!


You are very welcome, glad you eventually got it up and running! 🙂

does anyone have a working script that will install Google Chrome web browser (universal)?

I'm using this old script but i've recently noticed on both Intel & M1 it's now not installing the most current Google Chrome version of 101.***. it's installing at version 98.*****

I'm testing that script from @Geissbuhler 

Thanks for this script @Geissbuhler .   We ran into an issue where Chrome wouldn't autoupdate on our MacBooks.  We don't give the staff local admin so they weren't able to do the reinstall that the Macs were requiring them to do.  Set the script up in Self Service and it runs flawlessly for this.

Reply


Terms & ConditionsCookie settings