| Hi, in our company, we are thinking about switching to Windows Server 2016 and Active Directory. Right now we run LDAP/Open Directory on an old Mac mini with OS X Server Lion, which does not seem like a sustainable scenario for the future. Client workstations are Windows, OS X and Linux machines. The server acts as a directory service for domain authentication, logins, as the local DNS server and most importantly provides mountpoint information for workstations to automatically connect to our company's storage (which is a Dell Isilon cluster). And that is where we have run into problems integrating Active Directory with OS X. Joining the domain, logging in etc. works out of the box, but so far we haven't come with a way of providing OS X with mount information through AD. In the current setup with LDAP, OS X retrieves the mounts a and handles them with autofs, and we expect there must be a way of providing this through AD in a similar fashion. Documentation on this topic both by Apple and Microsoft is very sparse. I have followed instructions on extending the AD schema (e.g. "Modifying the Active Directory Schema to Support Mac Systems" http://markmail.org/download.xqy?id=f63mqp53otkqmgwi&number=1) but with no avail. All of these tutorials seem somewhat outdated as they were written at times when extending the AD schema was apparently necessary even for OS X clients to bind with AD – I have not found any newer information on whether this approach is still supported in today's OS X (currently we run OS X Sierra on our workstations). So my question stands: how must I extend the AD schema in order to provide OS X clients with mount information? Where does OS X's directory service look for mounts in the AD tree? Just to be clear, we are not worried about mounting home directories (that should probably work but we don't need that at all). | |