Common problems with mounting/mapping network drive in AD?

[jonros]

Hello everyone,
We're just about to migrate our Jamf from eDirectory to Active Directory. I'm gonna have a meeting with our partner how's gonna help us with the migration. He tells us they have a good solution for us but sugests that we shell skip access to network drive within the AD because there will be more problems then good with it. Best way for all users is to use OneDrive instead. But that't not really how our policy works within our organisation.

You who have mapped network drives for you users/computer, how do feel it works and what products do you use to get the computers to be a part of the AD and to get access to everything?

[AJPinto]

Mixing macOS and AD usually does not work very well as Apple stopped developing macOS with domain joining in mind over a decade ago. Supplemental tools like Apples SSO extension, which are still supported by Apple, do not receive much development, attention or documentation. On prem file shares and AD are really a thing of the past, and Apple is extremely rapid adopt.

We still largely use on prem file shares ourselves (cost is a thing), and we just have users log in to the authentication window that popups up for the file share. We killed off SSO for file shares a few years ago when we moved to Jamf Connect. The drive from our users to get SSO working for shares again has not been significant so we have not configured it.

[Tribruin]

Do you use Jamf Connect? We use the Jamf Connect Shares option to mount Shares for our users based on user group assignments. 

I would love to get rid of on prem shares, but it doesn't look like that is going to happen anytime soon. 

[jonros]

@Tribruin no we don’t but I wish we did. But Who knows what the feature has to offer. :)