I need to create about 600 managed Apple IDs in Apple School Manager. I created a few test users in ASM and set up the sync time, but the users are not being created in the JSS.
The documentation talks about matching criteria for existing users, but we currently have no existing student users in the JSS and I don't see anything about importing new users from ASM. What am I missing?
Best answer by mcooper
After the sync has run you will need to import the users into the JSS. Steps to do this are found at the bottom of page 619 of the Administrator's Guide. http://resources.jamfsoftware.com/documents/products/documentation/Casper-Suite-9.93-Administrators-Guide.pdf
We have new users almost daily. I would like to see an option to set default import settings after the sync.
Good question @cdenesha. Apple School Manager and the Roster API only returns the person's Full Name, Managed Apple ID and optionally grade level in addition to some system identifiers. We do not receive any username fields nor do we receive any actual email addresses (might be a good feature request for Apple if this could be helpful information for your deployment).
Because of the nature of the dataset from the Roster API, we have been iterating workflows based upon the very critical Managed Apple ID.
As previously stated, JSS 9.93 will peel of the @school.edu for creating usernames and it will insert the Managed Apple ID as the email address verbatim when creating a new user (since email address is a required field for new users). As a part of our next release, we will extend the import logic as it relates to Managed Apple IDs and Email addresses.
In 9.96, a new user will still truncate the username (same as 9.93). Additionally, the Managed Apple ID will be inserted into the email field. The difference is that if there is an "appleid" subdomain, that will be automatically removed when populating the email field.
Example: Johnny Appleseed has a Managed Apple ID of jappleseed@appleid.school.edu. Upon importing, no matching user is found. The new user for Johnny Appleseed would have a username of "jappleseed" and an email address of "jappleseed@school.edu".
In this example, you could see how a school might create Managed Apple IDs based upon user email addresses and then always insert the "appleid" subdomain. Upon importing into the JSS, the user might match (based upon available criteria) and append to an existing user. Alternatively, a new user would be created and the JSS would essentially revert to the proper email address by removing the "appleid" subdomain from the Managed Apple ID. Of course, this assumes that your email address username and your directory service username match.
Note: In the long term, Student ID numbers or Global Unique ID numbers (from SIS) will likely be the best matching solution. Until now, there haven't been many compelling reasons to append this extra detail to users throughout all of the various systems at play. Once those ID numbers actually propagate from SIS to directories and into the JSS, they will offer a much more accurate matching solution for Apple School Manager.
We haven't, and we're finding that PowerSchool has assigned the same ID (which would end up being the "person_id") to some teachers and students. Has anyone else seen this?