Due to the positive reception of my previous post on setting up OS X Server, I’m going to continue with some additional configuration tips. After having installed OS X Server and having a chance to experiment with all the possible service configurations, I felt it a natural progression to cover the setup of Open Directory.
A directory service is not a requirement to run any of OS X Server’s services by any means; however, the purpose of a setting up a directory is to have a centralized point of management for all network resources -- users, nodes, shares, and more -- all have their place in the directory database. This makes network/system admin management tasks simpler to perform since all the data is stored and organized in one container, from a handful of computers on your SOHO (Small Office, Home Office) LAN to one that spans the WAN (Wide Area Network) infrastructure of the entire enterprise.
Anyone with experience in setting up or managing Active Directory from Microsoft will feel right at home working with Apple’s Open Directory. Even those configuring OD for the first time will pick it right up, as Apple’s design sense makes this task as easy as a few keystrokes and mouse clicks.
Prerequisites to configure Open Directory
- Apple Computer or Server running OS X 10.7 (Lion) or 10.8 (Mountain Lion)
- OS X Server 10.7 (Lion) or 10.8 (Mountain Lion) installed
- Network connection*
- Static IP Address assigned to network connection**
Note*: Best practices recommend a wired, Ethernet connection is used for any server that will be providing services on a network to other nodes. Due to the higher bandwidth offered by a NICs (Network Interface Cards) Gigabit port, this allows the most amount of data to be sent/received without possibly becoming a bottleneck. While wireless connections have become ubiquitous, they also suffer severely from bandwidth reduction as more and more users access network resources from the Wi-Fi connections on their computer, smartphones and tablets.
This quickly becomes an issue that increases latency – causing the end-users to have to wait longer for the requests to be processed by the server – and that’s never good!
Note**: Assigning a static IP address to a network connection, while optional for configuring Open Directory, is highly advised. The main reason for this being that while nodes and mobile devices come and go on the network, typically, servers do not. Furthermore, the services being provided by these servers are used constantly by network devices; this means having a specific address assigned to the server/service will always allow the devices relying on said service to always find their way since the IP address does not change.
As we delve into other services in the future, such as DNS or Email, static IP assignments will not be optional, but rather a requirement. After all, what good is an email service when its users cannot send/receive messages?
Configuring Open Directory
#1 Launch Server.app and choose the OS X Server from the list, the click continue. (Figure A)







#8 The configuration process, which includes the creation of the service account, configuring links to services, and directory database may take some time. This depends on the specifications of your server, but typically should not take more than a few minutes on modern nodes. (Figure H)


Joining Nodes to Open Directory (10.7+)
#1 Open System Preferences.
#2 Click on Users & Groups. (Figure J)





#7 The selected server should now appear in the list of logon servers; click Done to complete the task. Now computers will be joined to the Open Directory Domain created in the previous steps and more importantly, allow them to access network resources and services, as they are added.
That’s it! Open Directory has been officially setup on the server and is now ready to accept network objects joined to the domain. With OD properly configured, management over computer accounts, users and groups, and network-based resources are all possible from the Server.app interface. Furthermore, an added benefit for enterprises lies in how it dovetails into other OS X services -- such as File Sharing, Mail, and Profile Manager -- forming a cohesive, single-point of contact for all server-based services, whether located on a single, local file-server or across multiple servers hosted around the world.
Full Bio
Jesus Vigo is a Network Administrator by day and owner of Mac|Jesus, LLC, specializing in Mac and Windows integration and providing solutions to small- and medium-size businesses. He brings 15 years of experience and multiple certifications from several vendors, including Apple and CompTIA.
