The “Directory Utility” is what we’ll use here. Then I tested the domain lookup in Terminal: Step 2: Configure Directory Services to use Active Directory In the following, I’ve set the DNS server IP and the search domain to my AD domain “NTAP.LOCAL”:
Best practices for connecting mac to windows active directory mac#
DNS is important here because it will be used to query the AD domain when we bind the Mac for the Directory Services.
This is done via “Network” settings in System Preferences. Step 1: Ensure the Mac is configured to use the same DNS as the AD domain Note: The steps may vary based on your environment configs and this covers just AD LDAP not OpenLDAP/IDM or other Linux-based LDAP. While most Linux clients are fairly straightforward for LDAP integration, MacOS does things slightly differently. (Centrify basically just uses the AD UNIX attributes and centralizes the management into a GUI – both are covered in the LDAP TR.) In these environments, you can either use either native UNIX attributes or a 3rd party utility, such as Centrify. One of the more commonly implemented solutions for LDAP in environments that serve NFS and SMB is Active Directory. That way, you get no surprises when accessing files and folders – user and groups get the expected ownership and permissions. When you do multiprotocol NAS in ONTAP (or really, and storage system), it’s usually best to leverage a centralized repository for user names, group names and numeric IDs that the NAS clients and NAS servers all point to (such as LDAP).
TR-4887: Multiprotocol NAS Best Practices in ONTAP This is known as “multiprotocol NAS” and I cover the best practices for that in the new TR-4887: In NetApp ONTAP, it’s possible to serve data to NAS clients over SMB and NFS, including the same datasets.
0 kommentar(er)
