Skip to content

Username upload via MUT triggers LDAP lookup #127

@Fay1013

Description

@Fay1013

Every year we prepare about 2500 iPads as part of our replacement schedule. We label with our asset tag, assigned client, and device name, and then scan that info along with the serial number and MAC address. We then use MUT to upload that data to Jamf. This has worked well in years past. We are just starting this year's project and notice that the results are different than expected and different from the last time we did this project.

Now as the MUT uploads, the inclusion of a username in the MobileDevice.csv file triggers an LDAP lookup, which 1) overwrites data in the MUT for Full Name and Building (we add more user friendly data via MUT than what is in LDAP) and 2) the MUT upload seems to take much longer than it used to. It also updates the record in the Users inventory, i.e. it changes values from what was previously there to whatever is in LDAP.

We have found a workaround, which is to first include the username in the .csv, and then MUT a second time without the username but with the Full Name and Building.

I am not sure if this is an issue with MUT or an issue with Jamf - I did open a case with Jamf to have them look at it. We are running Jamf Pro 11.4.1.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions