Configuration for distribution points

Additional configuration is necessary to upload packages to certain distribution points using JamfPackageUploader.

Cloud Distribution Points

If you are using a Jamf Cloud Distribution Point, you do not need to provide any additional credentials.

However, if you need to upload packages greater than 5.0 GB in size, it is recommended to set jcds2_mode to true. This can be provided on a recipe-by-recipe basis, at the command line, or by adding to the AutoPkg preferences file. Note that this requires the installation of the python boto3 module. To do this, run the following command after installing AutoPkg:

/usr/local/autopkg/python -m pip install boto3

If you are using an AWS S3 Cloud Distribution Point and are using at least Jamf Pro v11.5.0, you can also use the default mode. As an alternative, and for large packages, you can set aws_cdp_mode to true. To use this method, you must install and configure the aws-cli tools, supplying your AWS S3 Access Key ID, Secret Access Key and region. Also, supply the bucket name in the following variable:

• S3_BUCKET_NAME

If you have an Akamai or Rackspace Cloud Distribution Point, the default mode should work so long as you are running at least Jamf Pro v11.5.0.

FileShare Distribution Points

If you are using an SMB Fileshare Distribution Point, you should additionally provide the following keys:

• SMB_URL - this must be the full URL including share name, e.g. smb://my.dp.server.com/JPShare.
• SMB_USERNAME
• SMB_PASSWORD

For example:

defaults write ~/Library/Preferences/com.github.autopkg.plist SMB_URL "smb://myjamfdp.com/JPShare"
defaults write ~/Library/Preferences/com.github.autopkg.plist SMB_USERNAME jamfuser
defaults write ~/Library/Preferences/com.github.autopkg.plist SMB_PASSWORD AVerySecretThing456

Note that local folders instead of SMB shares can be specified. Use the SMB_URL key but supply a file path instead, e.g. file://path/to/my/repo. You currently have to supply dummy values for SMB_USERNAME and SMB_PASSWORD - these will be ignored but are required.

Advanced Settings for multiple distribution points

If you are using multiple File Share Distribution Points, you have two options for supplying the credentials.

In the AutoPkg prefs file, you can provide an array of dictionaries with the key name SMB_SHARES, containing SMB_URL, SMB_USERNAME and SMB_PASSWORD for each File Share Distribution Point, as shown below. The array can have as many entries as required:

	<key>SMB_SHARES</key>
	<array>
		<dict>
			<key>SMB_URL</key>
			<string>smb://my.dist.point/JamfShare</string>
			<key>SMB_USERNAME</key>
			<string>jamfadmin</string>
			<key>SMB_PASSWORD</key>
			<string>password</string>
		</dict>
		<dict>
			<key>SMB_URL</key>
			<string>smb://second.dist.point/JPShare</string>
			<key>SMB_USERNAME</key>
			<string>jamfadmin</string>
			<key>SMB_PASSWORD</key>
			<string>password2</string>
		</dict>
	</array>

Alternatively, you can supply keys directly in the form SMB_URL, SMB_USERNAME, SMB_PASSWORD for the first DP, SMB2_URL, SMB2_USERNAME, SMB2_PASSWORD for the second DP, and so on. Any keys supplied in this form will override the SMB_SHARES array entirely. The advantage of using these keys directly is that they can be overridden, supplied directly in recipes, overrides, recipe lists or at the command line.

If you are using both a Cloud Distribution Point and SMB shares, you need to set the key CLOUD_DP to True. This is not necessary if you are only using a Cloud Distribution Point.

defaults write ~/Library/Preferences/com.github.autopkg.plist CLOUD_DP -bool True