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.
This attribute verifies that the client can verify the certificate installed on the JSS. This attribute should be used prior to checking the preference "This JSS has a valid certificate installed" in the "JSS/URL Certificate" section of the Management Framework Settings.
JSS Certificate Validation.xml (1.12 KB)
This attribute verifies the Verification State of the MDM Profile installed on a client from the JSS. Results returned are "Verified", "Not Verified" or "Undecided" If an MDM Profile supplied by the JSS is not installed on the client, or if this script cannot find a Verification State attribute, this attribute will return a result of "Undecided".
MDM_Profile_Verification_State.xml (3.44 KB)
Counts the number of files in /Library/Application Support/JAMF/Waiting Room, excluding XML files.
Number_of_Cached_Packages.xml (726 B)
This attribute verifies that the client has certificate based communication enabled for communications with the JSS. Results returned are "Enabled" or "Not Enabled" based on whether the client has certificate based profile supplied by the JSS.
Verify Certificate Based Communication.xml (783 B)
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 Jamf Pro let you store information about the software licensed to your organization.
Find out more about licensed software templates on the licensed software templates page.
Scripts can be executed on managed computers using a Policy or Jamf Remote. Most scripts also work with other management tools.
Find out more about scripts on the scripts page.
I wrote this script to automate the process of re-partitioning the primary partition so that when Casper Imaging performs a block-copy of my images (which include "Macintosh HD" and "Recovery HD") I do not end up with multiple "Recovery HD" partitions. By default, Casper Imaging only targets the partition that contains the Macintosh OS, so without re-partitioning it is possible to end up with more partitions than required. The script works for both "primary partitions" and "logical partitions" including Fusion drives. The idea is to wipeout all local partitions and attempt to recreate what was there before. That way, Casper Imaging doesn't complain because the expected partition with "Macintosh HD" has not changed. I then follow-up the imaging process by running a script to convert any "primary partitions" to CoreStorage.
partitionDisk.sh (3.51 KB)
This script will display a message to the end user with a specified message. The message can be backgrounded so that a message is displayed and a process such as a policy is delayed until a user clicks the "OK" button. By default, the process will not be backgrounded and subsequent scripts or commands that run after this script will be delayed until a user clicks "OK".
displayMessage.sh (5.60 KB)
# Variables used by this script JSS_ID_PATH="" # Text file with one JSS ID per Line JSS_API_INFO_DIR="/tmp/jss_api_tmp" # Directory where working files for each JSS ID will be stored JSS_XML_INPUT="/tmp/JSS_XML_INPUT.xml" # XML Output to be uploaed to the JSS Computer Groups API STATIC_GROUP_ID="" # Static Group ID: This can be found in the URL when you click edit on a Static Group STATIC_GROUP_NAME="" # This is the name of the Static Group you want to overwrite # Variables used by Casper USERNAME="" #Username of user with API Computer read GET and Computer Group PUT access PASSWORD="" #Password of user with API Computer read GET and Computer Group PUT access JSS_URL='https://jss.jamf.com:8443' # JSS URL of the server you want to run API calls against
jss_api_id_staticgroup.sh (4.02 KB)
Managed Preference (MCX) manifests allow you to enforce settings on managed computers with Jamf Pro. These files also work with Workgroup Manager.
Find out more about managed preference manifests on the managed preference manifests page.