I totally get EAs - use them for loads of cases. I guess my question is are there any differences between computer level vs user level? I can only think of those being profile/mcx settings (apply to one, apply to all type). There's nothing different about a script I'd write (or gracefully, thankfully, borrow from many a JAMFer). The only difference is where it reports in JAMF (computer vs user tab)?
Are you talking about configuration profiles or extension attributes? EAs are just inventory items and the Inventory Display drop down menu lets you decide where it appears.
For config profiles, the most noticeable difference is the options you have available. User level profiles have most of the options you get with computer level, but can be scoped to user groups and have dynamic, user specific data inside them.
Referring to this page. Single option under the "user management" page.
I'm by no means a NOOB. but I've never bothered to check this page, really. Looking at an option for user inventory searching for a task and saw this. Wondered why it's on its own to differentiate versus a computer EA since they'll be doing the same thing, same script language, etc.
To further my thought along, EAs are generally run as a script with sudo rights by your management account. Essentially it's run as root, so any EA would run as root, therefore you're not going to populate any user specific data from a "user" perspective. You may collect data about that user but not necessarily the user themselves given how the script executes.
I'm saying why the difference? Who's using User EAs and why instead of computer? I guess @adamcodega points it out, but I don't user the User tab much....
We used the user extension attribute when users first came out. We created a "Department" field and ran a script that mapped the mobile device users department to the users EA department since there isn't isn't a department field under the users tab. We have since changed over to the position tab but it saved us last year.