Jamf Connect in Labs

jake_
New Contributor

Hi everyone, 

We just implemented Jamf Connect and are still testing it. We had issues with devices randomly getting kicked off AD, so since we are on AzureAD now, we decided to get Jamf Connect. When we set everything up when a user logs in, we can reboot the machine, and someone else can log in. 

Now, after a reboot, no one else but the last user can log in. 

How can I get out of this? What are your best practices for using Jamf Connect in a lab environment? 

 

Thank you

1 ACCEPTED SOLUTION

AJPinto
Honored Contributor II

You are probably dealing with FileVault, and the FileVault screen looks very similar to the macOS Log in Screen.

 

Users must be granted a FileVault token by another user who has a FileVault token, the only token automatically issued is to the user who enables FileVault (and to any admin accounts on the device when FileVault is enabled). MacOS is really not friendly to shared device situations. If the devices are secured within a lab, disabling FileVault may be the best option.

View solution in original post

2 REPLIES 2

AJPinto
Honored Contributor II

You are probably dealing with FileVault, and the FileVault screen looks very similar to the macOS Log in Screen.

 

Users must be granted a FileVault token by another user who has a FileVault token, the only token automatically issued is to the user who enables FileVault (and to any admin accounts on the device when FileVault is enabled). MacOS is really not friendly to shared device situations. If the devices are secured within a lab, disabling FileVault may be the best option.

jake_
New Contributor

Thanks for the reply! 

FileVault is turned off on this device. It's usually the last user who can login and requires them to log off so another user can login.