#JAMF RUN SCRIPT UPDATE#
#JAMF RUN SCRIPT UPGRADE#
#JAMF RUN SCRIPT PRO#
#JAMF RUN SCRIPT PASSWORD#
#JAMF RUN SCRIPT MAC#

Your UID tool must be an executable script. This can be used to match a local user account's UID with a user's LDAP UID attribute. Specifies a path to a UID tool that allows you to set a local user account's UID to a custom value during account creation. To enable this setting, set this value to 'jamf'. When the Jamf Connect notify screen is configured, display Jamf Pro's policy logs during Automated Device Enrollment (formerly DEP) as status updates to users.

#JAMF RUN SCRIPT PRO#

Only one script can be used with Jamf Connect Login at any time.ĭisplay Jamf Pro policy logs as status updates on the Notify screen Specifies the path to a script or other executable run by the RunScript mechanism. Note: The ScriptPath key must bey specified.

#JAMF RUN SCRIPT UPGRADE#

Re-enabling the Login Window after a Major macOS Upgrade.

Troubleshooting Deployment with Automated Device Enrollment.

Editing the macOS loginwindow application.

Preferences with the defaults Command-Line Tool.

#JAMF RUN SCRIPT PASSWORD#

Password Hash Synchronization and Pass-through Authentication.Network and Local Authentication Restrictions.Configuring Settings with Jamf Connect Configuration Thankfully, a fellow Jamf user commented on a related feature request with a solution.

For us, we're using this script to set the value of 'Smelly' as 'Smells very bad.

Value - what you want the EA to be set as when this script is run.

EA Name - whatever name you used for your EA should be entered here.

Grab that ID number and put it in parameter 6.

EA ID - the ID of an extension attribute is displayed in the URL when you are looking at it in your Jamf Pro server.

This adds a layer of abstraction to your username/password string so it will require at least some effort for someone to determine what those credentials are besides just displaying them in plain text on your Jamf Pro server. You'll get output in a long string, and that should be placed in Parameter 5 on your policy. To do this format your credentials as apiuser:apipassword (meaning a username and password smooshed together with a colon in the middle of an actual user account that can write with the API, I very much hope it's not apiuser with apipassword as a password lol) and run through the terminal with echo -n 'apiuser:apipassword' | openssl base64.

Encoded credentials - take the username and password of your api account and use openssl to convert them into a base64 string.

Jamf Pro Server URL - the URL of your Jamf server, such as.

Ive an AppleScript app that mounts drives & printers depending on.

Parameter 4 - Jamf Pro Server URL (no port) Depending on what youre trying to achieve you could run a launch agent, that calls a script.

When you add the above template script to a Jamf server, take the time to label the parameters so that when it's used in a policy later it'll be easy to remember what information you need to provide for the script to work.

#JAMF RUN SCRIPT UPDATE#

I've made a template script that uses parameters set on a policy to update an EA using the API to make this relatively painless to do. Scope it to the computers you want, then under Limitations scope to the username. Policy triggered at Login, Under Files and Processes add your command to be executed as root in the Execute command section. If you want want to make this a little more user-friendly, you can make a Self Service policy that runs a script that updates this value using the API. Posted on 09-25-2018 03:52 PM Or a Policy. Once created you can find that pop-up menu in whatever tab of a computer record you specified (above, 'General') and change the value.

#JAMF RUN SCRIPT MAC#

(Maybe you can?) So you make a pop-up menu EA for techs to mark if a Mac smells on the computer record in Jamf Pro. You can't really write a script to pull smell status off of a Mac. So let's say the help desk staff notices that some Macs that come by are really smelly. One of the handiest ways to set info ad hoc is with a pop-up menu extension attribute. Other times you just need to set a simple value for a Mac on demand for reporting purposes. Sometimes you want to snag information off of a client Mac, and for that a small script to grab the info and report it up to the Jamf Pro Server is great. Not all extension attributes (EAs) are created equally.

Jamf run script