Skip to main content
Solved

Strange Login Window Behaviour

  • April 3, 2025
  • 8 replies
  • 29 views

RDowson
Forum|alt.badge.img+9

I'm seeing some strange behaviour with the login window on devices in one Jamf environment but not in another.

All machines have the CIS L1 baseline and some additional lockdown restrictions on them. They should be asking for the username and password at the login window on startup and after a logout.

This works fine for devices in one environment but in the other I get the user account(s) listed on startup and only the password is required. It works as expected if you log out though.

I wondered if it was something relating to FileVault but, again, the configs between both Jamf environments should be the same. The only difference I can see is that one Mac is Intel (T2) and the other is M1.

Here are some examples of what happens on the Mac that isn't working as expected:-

Startup:

After logout:

Some of the settings applied:

Best answer by efil4xiN

i could be wrong but isn't this expected behavior for intel machines and filevault? This is  what I have seen this week working with intels again. 2nd screenshot is after logout and not reboot. didn't Rich cover this a few years back here 

8 replies

sdagley
Forum|alt.badge.img+25
  • Jamf Heroes
  • April 3, 2025

@RDowson make sure you don't have multiple Configuration Profiles configuring that setting as that will result in "undefined" behavior.


mvu
Forum|alt.badge.img+20
  • Jamf Heroes
  • April 3, 2025

@RDowson make sure you don't have multiple Configuration Profiles configuring that setting as that will result in "undefined" behavior.


Yeah, was thinking of multiple configuration profiles as well. We apply CIS level 2 here. I don't see this on Sequoia. 


Forum|alt.badge.img+8
  • Valued Contributor
  • Answer
  • April 3, 2025

i could be wrong but isn't this expected behavior for intel machines and filevault? This is  what I have seen this week working with intels again. 2nd screenshot is after logout and not reboot. didn't Rich cover this a few years back here 


RDowson
Forum|alt.badge.img+9
  • Author
  • Contributor
  • April 3, 2025

i could be wrong but isn't this expected behavior for intel machines and filevault? This is  what I have seen this week working with intels again. 2nd screenshot is after logout and not reboot. didn't Rich cover this a few years back here 


Thanks! I did wonder if it was an Intel vs Apple Silicon thing. Looks like it expected behaviour then.
The one in the screen grabs is an Intel machine so that makes sense.


mvu
Forum|alt.badge.img+20
  • Jamf Heroes
  • April 4, 2025

Thanks! I did wonder if it was an Intel vs Apple Silicon thing. Looks like it expected behaviour then.
The one in the screen grabs is an Intel machine so that makes sense.


We have intel boxes. I don't see this, but then again we're using Microsoft Platform SSO.


RDowson
Forum|alt.badge.img+9
  • Author
  • Contributor
  • April 4, 2025

We have intel boxes. I don't see this, but then again we're using Microsoft Platform SSO.


We're using Platform SSO too.


mvu
Forum|alt.badge.img+20
  • Jamf Heroes
  • April 4, 2025

We're using Platform SSO too.


Interesting. If it makes a difference, we're using it with Smart Cards config.


RDowson
Forum|alt.badge.img+9
  • Author
  • Contributor
  • April 4, 2025

Interesting. If it makes a difference, we're using it with Smart Cards config.


We're just username and password so maybe that's why it's different.