Enrollment Script

Hi and welcome.
Generally speaking, something like that should be possible. Since you're talking about doing it directly after enrollment, you might need to use an Applescript call inside a script for the dialog for the end user to make a choice from a drop down menu (Personal or Enterprise) **. What they choose could simply create a hidden identifier somewhere on the Mac that would get picked up by an inventory collection Extension Attribute script. From that Extension Attribute info you can create your Smart Groups for any inclusion or exclusion stuff. Generally, a simple file or folder created somewhere works fine for the identifier, but you could also do something like create a property list file with data in it. (probably overkill for this, but still an option)

As for how to trigger the above script, you would want to make a JSS policy scoped to all Macs with a trigger of "Enrollment Complete" to run the script. So in theory at least, as soon as they're done enrolling the Mac, it will run the policy, the script will run, prompt them for the info and then collect inventory, placing their Mac into the appropriate group(s).

Keep in mind this is only one of many possible ways to do it. I'm sure other folks will chime in with other solutions to this. the above was just off the top of my head and not thoroughly thought through, so I could be overlooking something.

[s]** EDIT: you could also use jamfHelper for this. It has a drop down menu window style that might work for you as well. It gets installed upon enrollment.[/s]
EDIT 2: never mind. I forgot, the drop down stuff in jamfHelper is only used for delay options so can't really be used for selections.

@mm2270][/url - Right, I've found other scripts on here like: https://jamfnation.jamfsoftware.com/discussion.html?id=5890 that used a PERL script to prompt a user to say Yes or No to installing software updates, im just not savvy enough to edit it to poluplate some other information. and this one (https://jamfnation.jamfsoftware.com/discussion.html?id=12546) populates an extension attribute with the remaining disk space. So it all looks doable, just was looking to see if anyone already invented this wheel.

Just to expand on @mm2270 script, here's a version of the same thing that uses the JAMFHelper instead of AppleScript. That avoids the ugly 'run as end user' stuff.

#!/bin/sh                                                                                                                                                     

button=`/Library/Application Support/JAMF/bin/jamfHelper.app/Contents/MacOS/jamfHelper -windowType hud -title "Computer Ownership"  -description "Please define if this computer is a personal device or company owned." -button1 "Personal" -button2 "Company"`

if [ $button -eq 2 ]; then
    echo "Enterprise" > "/private/var/systemtype"
    echo "This is a company owned mac"
elif [ $button -eq 0 ]; then
    echo "private" > "/private/var/systemtype"
    echo "this is a private Mac"
fi

@thoule and @mm2270 thank you both very much. And please excuse my ignorance, but how would I turn this into an extension attribute now?

To implement this process, do the following (note, this isn't every click, but pretty close. Hopefully you can follow along)

Add the script:

1. Click the gear on the top right of the screen
2. Click Computer Management, then choose Scripts
3. Create a new script, using the code in my example with whatever modifications you'd like

(note, add the jamf recon line like the other example - that updates the server with new info instead of waiting 24 hours)

Create the Extension Attribute.- that will read in the setting defined by the script

• Click the gear on the top right of the screen
• Click Computer Management
• Click Extension Attribute
• Set the input type to Script
• Enter the script below

#!/bin/sh
cat /private/var/systemtype

Now that you've got the extension attribute, you can create a smart group off of that.

Obviously, learning some good BASH scripting is critical to being able to effectively managing a group of Macs.

Just one minor correction. Extension Attributes need to echo the result back within specific tags in order to be added into the Casper database for that client.
So for example, taking what @thoule wrote above, it would actually need to look something like this:

#!/bin/sh

result=$(cat /private/var/systemtype)

echo "<result>$result</result>"

But in general, what is explained above is the exact process you'd want to use.
1- Add the script into your Casper db
2- Add the Extension Attribute as explained
3- Then you'll need to create your policy, as I mentioned in my first post. Make sure its scoped to all Managed clients with only "Enrollment Complete" as the sole trigger. Add the script using jamfHelper to the policy to run. When a client enrolls, as soon as its done, the jamf agent will check against the JSS to see what must be run, and run the policy, popping up the message.

Hope that all makes sense, and thanks to @thoule for adding in some useful input to the thread.

oops- you're right. Thanks, mm. Glad you're watching :)

@thoule and @mm2270 I wish I could give you both credit! This works great!! Thank you so much!!

and if you wanted to go a bit further down the rabbit hole, you could perhaps look at writing the result directly into the JSS via the API