David Williams Technical

This document will explain how to create packages for Jamf that install the software with any configurations such as directing to licence servers etc….

This is done through Jamf Composer using snapshots.

Taking Snapshots

If the files you want to package are not already installed on the drive, Composer can take a snapshot of the file system before and after the files have been installed and create a package source based on the changes.

Composer can take two kinds of snapshots:

• Normal snapshots—These snapshots capture any new files on the drive. These snapshots can take anywhere from ten seconds to several minutes depending on your hardware and the number of files on the drive.

• New and modified snapshots—These snapshots capture any new files on the drive, as well as any files that have been modified. These snapshots can take longer than normal snapshots, since Composer records the modifications date of each file while performing the snapshot.

There are several benefits to using the snapshot approach:

• Composer monitors installations in all locations on the drive.
• You can quit Composer during the installation process.
• You can log out or reboot during the installation process.
• If you delete a file while making modifications to a package source, it may be possible to restore the deleted file. For more information about restoring deleted files, see Adding Scripts to Package Sources.

1. Log On as Admin and open Composer and authenticate as the Administrator.
2. In the toolbar, click New  

3. Under the Monitor Installation heading in the sidebar, select Snapshot.
4. Select Normal Snapshot or New & Modified Snapshot and click Next.
   

5. Enter a name for the package and click Next.
   

6. Install and configure your software, and then click Create Package Source to initiate the “after” snapshot.

7. Delete any unwanted files or process in Composer to ensure that the install is as clean as possible. 

8.  Open Jamf Admin and drop the package into the main window to upload to the Jamf Server.

9. Log onto Jamf and create a policy to deploy the software to test the install. (This is covered in a different set of documents)

10. Deploy software using the newly created policy to test its stability. (To ensure it does not affect any other Macs in the environment, just add a test device to the scope)