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



Set up: VMware ESXI in VirtualBox

Articles, Technology, Uncategorized

Setting up ESXI under virtualising can be awkward. Here i’ve listed a series of instructions to get the hypervisor up and running under VirtualBox. These setting should be similar in WorkStation, Parallels, Qemu, Fusion etc. For the purpose of this guide i’m going to use Vbox as it’s cross platform and settings should be the same if not similar on any host OS.

Please note running a self contained hypervisor under virtualisation will not have optimum results. It is recommended to run ESXI on dedicated hardware. This guide should only be used to tryout the product.

System Requirements:

  • Dual-core, 64 bit, processor with VT/ AMD-V support
  • 1.5 GB of usable ram
  • 20+ GB free storage

1. Download an install virtual box for here. As of writing this i’m running version 4.1.18

2. Download the vSphere hypervisor trial ISO file from here. You may need to register for a free account if you don’t already have one. I’m running version the latest 5.1 version.

3. Launch VirtualBox & create  new virtual machine.

New VM

Name your VM anything you want. Select ‘Linux’ for your operating system & ‘Ubuntu’ for the version. Press continue..

4. As I understand it vSphere requires at least 1.5 Gigabytes of RAM. Move the slider to represent this and move on.

Select Memory

5. Still in the wizard, create a virtual hard drive appropriate in size to the VM’s you plan on installing within ESXI/vSphere. I’ve selected ‘VHD’ for the drive type. My drive is also Dynamically allocated.

6. Continue the wizard and finnish creating the VM.

7. Before launching, go into the settings for the VM.  Here we are going to remove any parameters that are unnecessary. First disable the shared clipboard under ‘General’, ‘Advanced’.

Disable Shared clipboard

8. Remove ‘Floppy’ from ‘Boot Order’ found under ‘System’, ‘Motherboard’.

Remove floppy

9. Under ‘System’, ‘Processor’, ensure that more than one CPU core & ‘PAE/NX’ is enabled

Processor settings

10. Under ‘Acceleration’ it is essential to have ‘VT -x/ AMD-V’ enabled as these are prerequisites of EXSI/ vSphere.

11. Under ‘Storage’, we need to point the virtual optical drive to the ISO we downloaded earlier.

Select ISO

12. I disabled sound under ‘Audio’ as it’s redundant.

13. Now for the important part. According to others networking can be done through ‘NAT’ or ‘Host-only’ network adapters. However from my testing, I have found that using the ‘Bridged’ connection gives the best results. These settings can be found under ‘Network’, ‘Adapter 1’.


14. To finnish up i’ve also disabled USB support. This can be found under ‘Ports’, ‘USB’.

Thats’s about it. Once you’ve installed the OS and tested it, you can then go into the settings again and start adding items you may need such as multiple virtual hard drives and remote desktop.

Checkout this process in action:


What is ESXI –

Download vSphere –

Download VirtualBox –