Skip to main content
Question

Avoid account creation ?


Forum|alt.badge.img+8

I am a little lost in all the changes Apple/jamf have made recent years. But overall when installing a new mac through DEP is there a way to avoid manual user creation on the mac ?

I would like to get rid of user must create a account manual on a mac, as they so often make spelling errors etc in their names and if the name of the account is not correct the certificates will not work as they are generated through that naming

We are using Azure SSO and have set azure up as IDP if that changes something. 

please help clearing up my mind 🙂 

5 replies

sdagley
Forum|alt.badge.img+25
  • Jamf Heroes
  • 3532 replies
  • November 19, 2021

@Captainamerica In your PreStage Enrollment configuration under Account Settings enable Pre-fill primary account information and Lock primary account information and that should use the user info from Azure.


Forum|alt.badge.img+8
  • Author
  • Contributor
  • 142 replies
  • November 22, 2021

I actually tried that, but what should account creation setting by in pre-stage?.

If I select do not create account it just go through the DEP initial steps as it should, but then just shows login screen with no user account available.

 


sdagley
Forum|alt.badge.img+25
  • Jamf Heroes
  • 3532 replies
  • November 22, 2021
Captainamerica wrote:

I actually tried that, but what should account creation setting by in pre-stage?.

If I select do not create account it just go through the DEP initial steps as it should, but then just shows login screen with no user account available.

 


@Captainamerica Here's the Account Settings options I use to have the Mac's local account created based on the user's AD information:

 


Forum|alt.badge.img+8
  • Author
  • Contributor
  • 142 replies
  • November 22, 2021

So you are using only azure Sso and then these settings ? Not jamf connect or anything ? 


sdagley
Forum|alt.badge.img+25
  • Jamf Heroes
  • 3532 replies
  • November 22, 2021
Captainamerica wrote:

So you are using only azure Sso and then these settings ? Not jamf connect or anything ? 


We're authenticating against on-prem AD via LDAP, and in theory Azure SSO would provide the same info.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings