Skip to main content
Solved

Unable to sign in to local non-admin accounts

  • February 23, 2022
  • 3 replies
  • 12 views

Forum|alt.badge.img+8

I am testing using local accounts in stead of the mobile/network accounts made when AD bound in our environment as we are looking to use FileVault on the MacBooks. Got everything setup for my test group, FileVault profile all good, everything working well on my two standard users and local admin account. The moment I apply my Login Windows settings from my prod environment, all the standard users fail to authenticate. after un-assigning that I log in as local admin and change the Login prompt settings back to List users and the accounts work fine again. 

 

I am missing something? why would list users vs. name and password text fields  cause this? 

 

thanks in advance for any input. 

- Jeff P.

Best answer by Hugonaut

What does your Login Window Configuration Profile Payload look like? (Screenshots Help) Do your Window/Access Panes look like this?

 

  

3 replies

Hugonaut
Forum|alt.badge.img+15
  • Esteemed Contributor
  • Answer
  • February 23, 2022

What does your Login Window Configuration Profile Payload look like? (Screenshots Help) Do your Window/Access Panes look like this?

 

  


Forum|alt.badge.img+8
  • Author
  • Valued Contributor
  • February 23, 2022

What does your Login Window Configuration Profile Payload look like? (Screenshots Help) Do your Window/Access Panes look like this?

 

  


Access page is likely the issue.. funny reading it here I was reading it as only local users could sign in.. but looking at your image I am realizing it is enabling "Local-Only" users .. will test quick and confirm. 


Hugonaut
Forum|alt.badge.img+15
  • Esteemed Contributor
  • February 23, 2022

Access page is likely the issue.. funny reading it here I was reading it as only local users could sign in.. but looking at your image I am realizing it is enabling "Local-Only" users .. will test quick and confirm. 


Yeah, the way it's displayed is confusing - you're not alone in your realization. Confused me when I was configuring this payload as well.