Deploy an always up to date Google Chrome via Jamf

Articles, Technology

My approach to working with configuration management systems such as Jamf Pro Cloud is to be as hands off as possible when it comes to software updates. In this day and age there’s much smarter ways of ensuring your devices have the latest packages after imaging than to manually specify the installation package to the management platform.

For the majority of commodity software packages these days, it’s often possible to pull the latest version of an application straight from the vendors sites before an automated installation. That’s exactly what we’re going to do today:

      1. Create a script titled “Install Google Chrome”
      2. Add the following to the script:
        #make temp directory
        mkdir ~/ChromeTemp
        cd ~/ChromeTemp
        #remove any existing installations
        rm -rf /Applications/Google\
        #Installing Chrome
        curl -L -O ""
        hdiutil mount -nobrowse googlechrome.dmg
        cp -R "/Volumes/Google Chrome/Google" /Applications
        hdiutil unmount "/Volumes/Google Chrome"
        #Clean up
        rm googlechrome.dmg
        rmdir ~/ChromeTemp
      3. Create a policy that runs the script at your specified trigger time. I choose to set the frequency to run once after device enrolment – After it’s installed, Google Chrome will update itself  as needed (providing you haven’t put any measures in place to prevent this).
      4. Within your new policy,  add rules to kill any running instances and remove existing installations as described in How to stop running applications via Jamf MDM.


Do be aware that since you’re essentially pulling software from a vendors repository, you’re at the mercy of whatever they supply behind the link. So be mindful to only use this method with vendors you absolutely trust.


How to stop running applications via Jamf MDM

Articles, Technology

Before deploying applications, there’s probably two things you need to do. 1. Kill the process if it’s running. 2. Remove any existing installations if they exist. The following describes how to easily achieve this using Jamf’s built in tools.

Jamf Kill Process and Uninstall application

Don’t forget to change the name of the application you’re killing.

  1. Within your application’s deployment/ self service policy, add the “Files & Processes” configuration option.
  2. Specify the applications potential existing installation location. Check the option to delete if exists.
  3. Specify the applications potential running process name. Check the option to kill the task if running. If you don’t know the processes exact name, you can find this by the application and locating the process name in Activity Monitor.
  4. (Optional) continue to build out your policy if needed.
  5.  Save


  • Don’t worry, if the application is not found on the target system, Jamf will skip over this process and continue to execute the policy.
  • If you can’t find the process name using activity montior you will also find that it’s generally the same name as the file located at /Applications/APPLICATIONNAME/Contents/MacOS/FILENAME