Skip to main content

Hello

We have just completed MAC enrollment to JAMF with pre existing mobile users being converted to STD users after enrollment. We use entra for jamf connect. We have a SAN that users access to R/W data. If another user logs into the mac (creates std account) he cannot access the san b/c his GID/UID is not what the san expects. He can read but not write. Our workaround is to wipe the mac, delete from jamf, create the mobile account then enroll into jamf and that user is good. 

Anyone have a similar issue? Ideas to fix?

I’m trying to understand how the SAN is using the IDs of the user. Is this a security feature where the SAN has a list of known IDs?

A new user (whether created directly on the computer or using Jamf Connect) will have something like a user ID of 501 and group ID of 20 for non-admins or 80 for admins. How does the SAN use these numbers to control access?

Or are your users possibly using fast user switching? That might cause problems if the first users has mounted the SAN under their account. Other users probably wouldn’t be able to use their own credentials, which might cause this problem. The first user would need to log out before another logs in.

Reply


Terms & ConditionsCookie settings