Jamf extension attribute

pinpoint has been designed to also be able to act as a JAMF JSS extension attribute. pinpoint when used in this mode will return a Google map URL which will then be stored as an extension attribute for the matching Mac computer record in JSS. You can think of this as being equivalent to Apple's 'Find my Mac'.

In order to use pintpoint to populate an extension attribute you need to create the extension attribute as per the picture below.

You then need to paste in to the script box the pinpoint.sh script.

Due to the way extension attributes work in JSS it will be updated at the interval you have defined the JSS recon process to run, this is typically weekly or daily. If this is the only use you make of pinpoint you do not need to directly install pinpoint on the client Macs at all as it will only be run via JSS.

If you are only going to use pinpoint.sh via JSS then the easiest way to do this is to paste the pinpoint.sh script in to the script box and hand edit the needed parameters including the Google API key and setting jamf=1 to tell the script to run as an extension attribute.

Note: Extension attribute scripts cannot be passed parameters, hence why you need to hand edit the values into the script, or see below…

If you are going to use pinpoint both as an extension attribute and in its normal mode i.e. installed on the client Mac then you will find it easier to use this script in the extension attribute which will retrieve the latest result from the client Mac by reading the value from the file on the client Mac.

Note: Scripts for extension attributes in JSS cannot be passed command line parameters, you will therefore need to hard code in to the script itself the Google API key and other parameters, especially setting the parameter jamf to = 1,