Packaging Unity for Munki

I recently needed to package Unity for the Munki server we have in place at our college.

Unity is one of those installers that looks like a regular installer, but actually downloads a bunch of additional files depending on what the user selects during the install workflow.
Luckily, it’s fairly easy to use JAMF’s Composer software to create a ‘Normal Snapshot’ that tracks changes before and after running the installation.
Be sure to tweak the files Composer includes; the only files we actually need are inside the ‘/Applications/Unity’ folder.

However, on first run of Unity, the program does also try and create a folder where it can store a license file. If you’d just packaged Unity through Composer and done nothing else, you’d have missed this. (I know this because I made this mistake).

An error will be thrown up stating that Unity needs to spawn a process with admin rights to create this folder. Of course, if you have end users without admin permissions, this will then mean a call to the helpdesk for someone from IT to enter an admin password. This is a bad thing.

The fix? Simply add an empty folder with the path ‘/Library/Application Support/Unity’ that has read and write permissions for all users, into the source of the package snapshot in Composer and then click Build PKG.
Your file and folder structure should look much the same as below:

Screen Shot 2017-04-27 at 14.16.52.png

Problem solved!


Deleting Configuration Profiles through Terminal

Sometimes there’s a need to manually remove a configuration profile deployed by something like Apple’s Profile Manger; if for instance you cannot un-enroll the device, or you cannot access the ‘Profiles’ pane in System Preferences.

There’s a simple way I found to do this in Terminal.
The first command will list all the configuration profiles currently installed.
All these commands need to be run with sudo.

sudo profiles -P

This should present you with a list of all the profiles on the machine.
In my instance, I just wanted to delete all the ones installed, the following two commands will do this:

sudo profiles -d
sudo profiles -D

I found that after running these, some settings in the payloads of these profiles didn’t disappear, but a restart cleared that up completely.

Adobe Creative Cloud is needed to resolve this problem


Oh right, well I thought that was already installed.

I got this lovely little error message on some Macs that I was adding a CS6 package to. These had an existing CC 2015 enterprise serialised deployment package on them for the full CC suite, but we had a requirement to add Dreamweaver CS6 to the installation as well.
I built a serialised package just for Dreamweaver CS6, but for whatever reason, once this extra package was installed alongside our existing CC one, this error was thrown my way.

Adobe does have a support article here that pretends to solve this problem, but it only affects two apps (InDesign and Incopy), and the workaround mentions renaming a folder but I don’t know what to.

Anyway, here’s how I got rid of this error message.
Open up the Creative Cloud Packager program that comes with Enterprise license accounts, and choose Create Package.
I then choose Serial Number License since that’s our deployment method in our institution, and tick Creative Cloud Desktop Application.
Next, I paste in the enterprise license key…and finally I choose the Adobe products I want to package.
In this instance, I only want the Creative Cloud app at the top of the list, I left everything else unchecked, then clicked Build.

Screen Shot 2017-01-09 at 16.28.06.png

Once the building is complete, I then just installed it on the machines displaying the error, (I personally use the Install Packages feature of Apple Remote Desktop) and now the error has gone!

And now I can move on with my life.

Completely Removing Adobe CC

I had a need to completely and utterly, destroy and obliterate an Adobe CC 2015 installation the other day from an iMac in our college.

Of course this wasn’t as simple as running every uninstaller file from /Applications, but this was what I tried first, however it left behind what I think where licensing files as well as user settings in all manner of directories.

The next step was to try the ‘Creative Cloud Cleaner Tool’ which can be downloaded for free here. This gave me a list of parts in the old CC installation it detected and could remove…sure enough there were leftovers including some user license data.
‘Cleanup all’ removed some things, but there was a persistent Photoshop CC 2015.5 installation that wouldn’t disappear.

The next thing I tried was to build an uninstaller package using the Adobe Enterprise ‘Creative Cloud Packager’. This will build some sort of uninstaller script that looks for existing installation of the products you select, and then deletes the files.
Just to be on the safe side, I selected every Adobe product and built the uninstaller.

Screen Shot 2017-01-09 at 15.04.35.png

Once it’s built, I needed to run it with superuser privileges. Open a Terminal and punch in the following:

sudo /Users/tech/Desktop/Uninstaller/AdobeCCUninstaller

The path will vary according to where you’ve saved it; I put mine on the desktop.
This ran through every Adobe product, checked for its presence on the machine, and then removed the installation files for it.
It found a fair few remaining and at this point I was fairly confident I’d got rid of the applications themselves…however, user data was another matter and this is where Adobe have another support article of use here.

The following directories and files were deleted:
(An asterisk * replaces the names of individual Adobe applications, e.g. Photoshop)

Users/[User]/Library/Application Support/Adobe
Library/Application Support

Finally, just to be extra sure, I ran a Spotlight search on the word ‘Adobe’ to see if anything else was thrown up on the machine. As long as it wasn’t a user created file, I deleted it.
Empty trash, a reboot for good measure, and that was the last of Adobe on this iMac!