Mac on Domain

[tri_94]

Hi there

 

Very basically we are looking to put a Mac on to our domain. I've added fine and can log in and out and most of our network shares map fine.

 

However i need to map home drives, currently it maps to the root location and not the username itself. on windows we map to " %username%/documents" how do i do this with a Mac?

 

Many thanks

[3s-gtech]

I *think* you'll need to either script that or use an MDM to do it. Mac OS will connect the user's home area automatically using the AD settings but it won't mount a share or 'map' it. Generally that's enough - if that's not connecting properly there's something else wrong which we can try to find.

[free780]

Also be aware if a users password is changed the Keychain password in the Mac will not be in sync. This is why nomad and jamf connect exist to use local accounts.

[Face-Man]

You can switch this on when joining the domain see

 

https://discussions.apple.com/thread/250574831

 

But mac and AD break quite often hence NOMAD https://nomad.menu/ might be an option.

 

You should also remember Mac's can't see NTFS permissions so if you have not secured a share with permissions the user on a Mac may be able to find lots of restricted files on your network.

[2ilent8cho]

You should also remember Mac's can't see NTFS permissions so if you have not secured a share with permissions the user on a Mac may be able to find lots of restricted files on your network.

 

Thats not how it works, the client be it Mac, Windows or Linux don't see NTFS when accessing a share, they see a Samba. You cannot magically get access to a share you don't have permission to just because you are on a Mac. That only happens when it's misconfigured permissions.

[Face-Man]

That is how it should be configured but I've been to lots of schools where the share permissions are all users - full control because the security is "done" via NTFS permissions - not how it should be but I've seen it so many times there is no harm in warning about it