Discharge7443/fleet
1
0
Fork 0
Code Issues Pull Requests Actions 6 Packages Projects Releases Wiki Activity

macOS setup experience: Clarify behavior (#38379)

Browse Source 
- macOS setup: "may" isn't that helpful. It doesn't make the user feel
confident on what they should document internally.
This commit is contained in:
Noah Talerman
2026-01-23 17:47:36 +09:00
committed by GitHub
parent 40bd4ccc45
commit e2500002ed
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
articles/setup-experience.md
+1 -1
View File
@@ -18,7 +18,7 @@ You can enforce end user authentication during automatic enrollment (ADE) for Ap
to populate and lock the macOS local account **Account Name**. For example, a
"johndoe@example.com" email will turn into a "johndoe" account name.
> **NOTE** If the host is restarted during the mdm enrollment process, there may be an issue with populating the macOS local account creation screen. The fields are not guaranteed to be populated with the user's IDP email and username.
> If the host is restarted during automatic enrollment (DEP), the macOS local account fields won't be populated with the user's IDP email and username.
3. Make sure your end users' full names are set to one of the following attributes (depends on IdP): `name`, `displayname`, `cn`, `urn:oid:2.5.4.3`, or `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name`. Fleet will automatically populate and lock the macOS local account **Full Name** with any of these.