This guide is designed for system administrators who are planning to administer Adobe® Creative Suite® 5 or 5.5 (CS5 or CS5.5) with the Casper Suite. This guide provides step-by-step instructions for deploying, serializing, reporting on, and updating Adobe CS5 or CS5.5 with the Casper Suite.
Extension attributes are custom fields that allow you to collect almost any piece of attribute data from a computer.
Find out more about extension attributes on the extension attributes page.
Package manifests allow Composer to build packages from software that is already installed without taking snapshots.
Find out more about package manifests on the package manifests page.
Licensed software records in the JSS let you store information about the software licensed to your organization.
Find out more about licensed software templates on the licensed software templates page.
Licensed software template for Adobe Creative Suite 5.5 - Design Premium.
Adobe Creative Suite 5.5 - Design Premium.xml (1.28 KB)
Licensed software template for Adobe Creative Suite 5.5 - Design Standard.
Adobe Creative Suite 5.5 - Design Standard.xml (730 B)
Licensed software template for Adobe Creative Suite 5.5 - Master Collection.
Adobe Creative Suite 5.5 - Master Collection.xml (2.05 KB)
Licensed software template for Adobe Creative Suite 5.5 - Production Premium.
Adobe Creative Suite 5.5 - Production Premium.xml (1.39 KB)
Scripts can be executed on managed computers using a Policy or Casper Remote. Most scripts also work with other management tools.
Find out more about scripts on the scripts page.
Now the JSS appears to a respect exit codes (Yay!)... Downside is the existing installPKGfromDMG script appears not to return/pass an exit code if a PKG fails to install (Boo!). This modified version of installPKGfromDMG addresses... * Supplying parameter 5 with "YES" without quotes and case sensitive allows PKG exit code to be bypassed and returns a forced exit code of 0 to the JSS (if needed). * If a previous DMG mount is detected, will attempt unmount * If a previous shadow file is detected, will delete it before attempting mounting DMG * Passes and outputs PKG exit code to log * Passes and outputs exit codes to JSS
installPKGfromDMG.sh (12.2 KB)
Expanding on the functionality in July's installPKGfromDMG - Fix pass exit code to JSS Parameters now included are... dmgName="" # Required forcesuccessflag="" # Optional useinstallerapp="" # Optional allowUntrusted="" # Optional Require parameter 6 to be YES applyChoiceChangesXMLFile="" # Optional Require parameter 6 to be YES Supplying parameter 5/forcesuccessflag with "YES" without quotes and case sensitive allows PKG exit code to be bypassed and returns a forced exit code of 0 to the JSS (if needed). Supplying parameter 6/useinstallerapp with "YES" without quotes and case sensitive forces the use of macOS native installer binary to install the PKG. Supplying parameter 7/allowUntrusted with "YES" without quotes and case sensitive allows to bypass an invalid or expired certificate embedded within the PKG. Supplying parameter 8/applyChoiceChangesXMLFile with an XML filename allows the PKG to be supplied an xml answerfile. The xml file MUST be beside the PKG wrapped in your DMG. Please take careful note, that parameters 7 (allowUntrusted) and 8 (applyChoiceChangesXMLFile) are dependent on parameter 6 (useinstallerapp) being YES. I've also added mpkg if no pkg is found within the DMG. Additionally all parameters will be parsed in the logs so one can see if, when, and where something went wrong.
installPKGfromDMG.sh (15.3 KB)
Updated with new binary path. Please see installation instructions here: https://jamfnation.jamfsoftware.com/article.html?id=161
installPKGfromDMG.sh (7.54 KB)
Managed Preference (MCX) manifests allow you to enforce settings on managed computers with the JSS. These files also work with Workgroup Manager.
Find out more about managed preference manifests on the managed preference manifests page.