Posted on 07-14-2020 12:06 PM
Hello,
We currently don't allow users to self-enroll as we have not moved to one-touch deployments. We plan on enabling DEP authentication on Macs and one of the issues we found was that doing so will pre-fill the user account creation screen with the IT tech's account information (as they are the one that authenticated with Jamf).
I've been thinking of creative ways to avoid this and thought of the "Pre-fill primary account information" checkbox. Does anyone know if I can turn this on and leave both values blank to force the username/full name boxes to not populate at the next screen, allowing the tech to enter the end-user's username and display name? If not, can I do something along the lines of the below when pre-filling the data:
Full name: "Enter the user's first and last name"
Username: "Enter the user's AD username"
Thanks in advance,
Justin.
Posted on 07-14-2020 12:24 PM
@jtrant I have LDAP setup and just tested this with $FULLNAME and $USERNAME this may work for you. I think your workflow will work too.
Posted on 07-16-2020 06:36 AM
Thanks @kerickson, I'm hoping I can either force it to blank or pre-populate with instructions for the IT team to enter the user's account information.
Posted on 10-15-2020 08:07 AM
@kericson - I am toying with these settings in dev and Fullname is auto populating from LDAP. But it comes in as "Last, First". Historically we have always user "First Last" for the full account name.
I am curious if changing to this format might cause any issues.
Posted on 10-15-2020 09:35 AM
Yeah maybe switching this would fix the issue. There was a Jamf PI issue with this and Azure AD SSO. @Brett_Cox