Mac shows Multiple Login screen when Hexnode Access is pushedSolved

Participant
Discussion
1 month ago

Hello everyone,

We have a bunch of Macs enrolled in our organization, and a few of them were enrolled via DEP. Our organization uses Okta for managing all users, so we basically use the same as network accounts on our macOS devices. When Hexnode announced Hexnode Access, we were really thrilled because it allowed our users to use Okta SSO directly on their macOS devices. However, our users are facing some issues. When logging into a macOS device, it initially asks for a local user account login. After that, users are redirected to the Hexnode Access SSO setup screen. This happens every time the DEP-enrolled devices restart.

Is this an issue with Hexnode Access or something related to DEP enrollment? Any clarity on this would be really helpful. Can I get a reply ASAP, as this is a priority issue for us?

Replies (3)

Marked SolutionPending Review
Hexnode Expert
1 month ago
Marked SolutionPending Review

Hello,

Thank you for reaching out to Hexnode Connect.

I understand your concern regarding macOS devices showing multiple login windows after restart. This behavior is caused by FileVault. When FileVault is enabled on a macOS device, the system first requires the local user credentials used to set up FileVault to unlock it. Only after this step is completed will the Hexnode Access screen be displayed.

This issue is unrelated to Apple’s Automated Device Enrollment (ADE). I recommend verifying the scenario by temporarily disabling FileVault on the device. Additionally, check if any FileVault policies are configured for your devices and either disassociate or reconfigure them as needed.

If you have any further questions, please don’t hesitate to reach out. We’re always happy to assist.

Best regards,
George,
Hexnode UEM.

Marked SolutionPending Review
Participant
1 month ago
Marked SolutionPending Review

Hey George,

Thank you, it’s resolved. Looks like the issue is indeed with FileVault. We verified the same on non-DEP enrolled devices, and the problem was confirmed. We do have a FileVault policy configured for the DEP-enrolled devices, so, as you mentioned, that might be causing the issue.

I just wanted to check, is there any way to bypass this issue by any chance?

Marked SolutionPending Review
Hexnode Expert
1 month ago
Marked SolutionPending Review

Hello,

I’m glad we could help. Unfortunately, there’s no bypassing it. Unlocking FileVault is necessary to access the Hexnode Access screen. Please let us know if there’s anything else we can assist you with.

Best regards,
George,
Hexnode UEM.

Save