PDA

View Full Version : What does it mean to "bind" a computer to OS X Server?




Randy Kahle
Jul 7, 2011, 03:40 PM
I have read numerous posts in this forum mentioning the importance of "binding" a computer to OS X Server.

I have some questions:

What does this mean, technically?

What facet of the client computer is bound to the Server?

Once a computer is bound to OS X Server, what does this enable?

Randy



Mactasia
Jul 7, 2011, 03:58 PM
"Binding" occurs within Directory Utility (found in System > Library > Core Services) and it's something which is usually done when you are in an area where a server (or servers) provide services to computers on the network.

For example, I may bind a Mac to an Active Directory (windows server) so that I can login in with network accounts and mount home directories (hosted on a server).

Or there may be an Apple server hosting user accounts and homes, or other services like Mail, Contacts, and Calendars.

If you aren't in an enterprise (business/education) environment, then you needn't worry about it too much. Hope this helps.

thankins
Jul 7, 2011, 04:03 PM
"Binding" occurs within Directory Utility (found in System > Library > Core Services) and it's something which is usually done when you are in an area where a server (or servers) provide services to computers on the network.

For example, I may bind a Mac to an Active Directory (windows server) so that I can login in with network accounts and mount home directories (hosted on a server).

Or there may be an Apple server hosting user accounts and homes, or other services like Mail, Contacts, and Calendars.

If you aren't in an enterprise (business/education) environment, then you needn't worry about it too much. Hope this helps.


You also forgot about binding the machines to the the Open Directory server so that you can manage the machines...such as put certain apps on the dock, manage updates, and a host of other settings

Mactasia
Jul 7, 2011, 04:05 PM
You also forgot about binding the machines to the the Open Directory server so that you can manage the machines...such as put certain apps on the dock, manage updates, and a host of other settings

Indeed. Something that I do so much of that I didn't mention it! :)

Randy Kahle
Jul 7, 2011, 04:21 PM
Thank you for the replies.

I am understanding that binding a computer to an OS X Server allows the server to manage the client computers.

For my simple workgroup setting, that is a capability that I do not need initially. Initially I want to (in Lion) have an iCal server, the email server, shared file areas, push notifications to various devices, Wiki and a Web Server.

I'll let individual users manage their updates, settings and preferences, etc.

With the configuration I have described would you agree that I do not have to worry about binding client computers to OS X Server?

Mattie Num Nums
Jul 7, 2011, 06:22 PM
Thank you for the replies.

I am understanding that binding a computer to an OS X Server allows the server to manage the client computers.

For my simple workgroup setting, that is a capability that I do not need initially. Initially I want to (in Lion) have an iCal server, the email server, shared file areas, push notifications to various devices, Wiki and a Web Server.

I'll let individual users manage their updates, settings and preferences, etc.

With the configuration I have described would you agree that I do not have to worry about binding client computers to OS X Server?

Whats the infrastructure like? How many computers and how much management do you want.

Also, updates should be centralized. Its very dangerous having different computers on different OS's. If one update, such as 10.6.8 broke printers, gets downloaded in the wild you could be in remediation hell.

thankins
Jul 7, 2011, 07:56 PM
Thank you for the replies.

I am understanding that binding a computer to an OS X Server allows the server to manage the client computers.

For my simple workgroup setting, that is a capability that I do not need initially. Initially I want to (in Lion) have an iCal server, the email server, shared file areas, push notifications to various devices, Wiki and a Web Server.

I'll let individual users manage their updates, settings and preferences, etc.

With the configuration I have described would you agree that I do not have to worry about binding client computers to OS X Server?

I would go ahead and bind them - it honestly takes like 5 mins in Open Directory to bind them. Like the other poster side - you don't want each user downloading an update for a few reasons. If the update breaks a computer you can block it before hand and you also don't want 3 users all hitting Apple's update server at the same time killing your bandwidth