Skip to content
This repository has been archived by the owner on Feb 8, 2023. It is now read-only.

Case Study Culture Amp

Jump to bottom
Francois 'ftiff' Levaux-Tiffreau edited this page Aug 10, 2017 · 1 revision

#Case Study -- Culture Amp

This page is to show you one way you can use SplashBuddy (SB) in your environment.

This deployment revolves around:

  • Triggering SB after a DEP enrollment.
  • Running a small script that runs custom triggers in our JSS.
  • Allowing your user to go get Coffee and wait until the process is done or allowing them to get along with their work.
  • Totally hands off deployment so your helpdesk has an easy life.

NOTE: This deployment does not use the progress indicators as it is not suitable in my environment.

Getting started

Firstly, clone the repo and extract to a directory of choice. Next we are going to build the App for use, note that at this stage you can modify the app if you wish to do so. In my case I've modified some of the text and colors to match my environment however I wont show this in this tutorial.

  1. Browse to the extracted directory and open 'SplashBuddy.xcodeproj'- Note: You need xCode to open this.
  2. Check this page in the wiki to build the App - https://github.com/ftiff/SplashBuddy/wiki/SplashBuddy-Development
  3. Once you have built the app lets go ahead and find it and move it a new CasperSplash folder for our project. Expand the Splash Buddy project file and check in the 'Products" folder for your new app > Right click > Open in finder > Copy to a new folder.

For ease of use, all I added an icon to the app before building.

Planning your packages and JSS

The next stage is for you to plan which packages you want to deploy on with SB. In my case I had a small list for testing purposes which already had policies in our JSS. I went to each one and setup a custom trigger. Custom triggers allow you to download packages with easy to remember names from the command line.

sudo jamf policy -event YourCustomTrigger

Here's an example of one of mine. Note I've added in "_CS", this is because I have a different naming technique for our custom triggers.

With custom triggers it makes it really each for us to setup a script that will run with SplashBuddy to pull the required software from the JSS.

Once you have setup a few of these you can create the SplashBuddy policy, scoped it to DEP machines and configure it to run "on enrollment". Leave the package section alone for now, we will go back and add it in later once created. Remember not to mark it active until you are ready. Else you may have machines attempting to run the policy if you are in a multi-engineer environment like me.

If you can, please contribute.

You can also freely edit the wiki, every little bit helps!

Thank you 🌈

Clone this wiki locally