Recommendations on how to update User info for next year

Take a look at this...http://jssmut.weebly.com

fair disclosure...I know the software works but do not have as much info as I'd like to say it's going to work for what you are trying. Test this on a small batch on your development instance first.

http://jssmut.weebly.com/

Tangent question...

There is a Department LDAP mapping in JSS, however, it doesn't seem to map to a user field in JSS. There is a Department field in 'User and Location' but that is used for the JSS internal Departments you create. Any ideas where the LDAP department is used in JSS?

When the device does its inventory update it will pull in all of that stuff from your LDAP server.

EDIT: When you update just the username, that is.

I have a similar issue but is mainly due to leavers. I put in a request to have a way of updating LDAP information manually as it only updates when the user device checks in.

https://www.jamf.com/jamf-nation/discussions/22175/updating-users-ldap-information

I use the "Position" JSS mapping to link the AD Department field for users.

Did some testing. Doesn't look like MUT updates any of the info but the field you specify during the run. And there are only these fields:
Username
Full Name
Email
Position
Phone #.

Like @RLR I primarily use the position field as it is both a device and user field.

As for updating multiple fields, simply run the utility more than once using different csvs is what I would recommend, not terribly efficient as say what a script would do, but better than me developing one and debugging it or worse doing it by hand. As for other fields, it can do more depending on what you choose. For instance if you choose that you want to update iOS devices, you would get this pic

If you choose that you want to update users, you would get this pic:

I didn't even look at the device stuff in MUT! Ok there are all the fields. We have all that info in AD, it would be much easier if we could just get the JSS to re-sync that data as it is updated in AD. But making a bunch of .csv's looks like the only way to do it for now.

I tell you what...this app is somewhat of a Godsend to me. My scripting knowledge is limited especially with the API. I have 2 or 3 scripts that were developed for me with help that did multiple things, but sadly until I have time to study those, write my own and debug it and get them to always work, I love that someone else did some of that crapwork and put a nice friendly GUI on it for me even if it does take multiple steps to get what I want...still better than doing that sort of crap by hand.

Working with my Admin, I figured a few things out.

1. The Department LDAP field will only work if there is a matching Department created in JSS. Example:

LDAP field is Phone Number mapped to department field in JSS. That same value needs to be created as a department in JSS. When you re-fresh the LDAP info in User and Location it will then populate the LDAP department field correctly. Even though it is actually a JSS department entry.

1. My Admin thinks he can create a script that will call LDAP and then, using the API, update any fields in JSS we need. He has already created a proof-of-concept that works.