#Jamf pro composer mac#

#Jamf pro composer mac#

Everything I know now was something of a crash course introduction by the old Mac Administrator before he left.

Much cleaner this time - That's a good idea, checking out some of the older conferences. With all the problems I've had to troubleshoot, I had a much better idea of what to look out for when recreating all my older packages through Composer. Thanks for the responses! I'm aware of the problems that can arrive from using Composer. Is that as simple as dropping the installer into it, and then deploying what is spit out? To be honest, I'm only familiar with Bash scripting on a very basic level. I have also read about, but not used (other than for the creation of our OSX Image) the AutoDMG/PKG application. This is the method we currently use for After Effects and Maya, but not yet for their associated plugins or other products. The alternative that has been recommended to me is to cache the actual installer for the app locally, usually in /private/tmp/, and then execute with a script afterward. Now, as I've learned more and more about JAMF deployment, I get the impression that using Composer snapshots to create packages is no good. This caused a few issues with file permissions - my own fault, but we're at a point where everything has (mostly) been running smoothly since the initial deployment last year. In the past, I have used Composer to snapshot and package everything we are deploying. We are in the middle of rebuilding our entire package database for a new push to OSX 10.11.6 (From OSX 10.9.5), along with updated versions of all the artists' applications and associated plugins. I've heard conflicting suggestions from colleagues/JAMF Nation discussions about the best method of packaging everything. Most of the packages we build are plugins for After Effects. We use JAMF to manage our Graphics department.