elbarro
asked on
OsX Server: Computer binding to Open Directory
I've been trying to apply Login restrictions through the Workgroup Manager tool to a computer object without success.
In order to bind the computer to Open Directory, I've done the following in the Workgroup Manager: On the computer tab, i've provided the computer name and provided it's IP address and mac address.
Is there something I'm missing? It seems there must be some other way to bind the computer to the directory that I'm unaware of.
In order to bind the computer to Open Directory, I've done the following in the Workgroup Manager: On the computer tab, i've provided the computer name and provided it's IP address and mac address.
Is there something I'm missing? It seems there must be some other way to bind the computer to the directory that I'm unaware of.
ASKER
Dear Boris,
I've done the prescribed and rebooted the client machine (setting several attributes from within WGM applying them to the computer object. However, none of the settings seem to apply.
I've set the following:
a) A custom message
b) removed the restart and shut down buttons
c) set the heading to the ip address as opposed to the default "name"
Could I be missing something else?
~Greg
I've done the prescribed and rebooted the client machine (setting several attributes from within WGM applying them to the computer object. However, none of the settings seem to apply.
I've set the following:
a) A custom message
b) removed the restart and shut down buttons
c) set the heading to the ip address as opposed to the default "name"
Could I be missing something else?
~Greg
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the advice. However, these are the steps I've gone through. Still, it seems the computer wont apply the settings. Is there a way to check if the computer is indeed setup in Open Directory? Ie, a way to debug the current situation?
~Greg
~Greg
ASKER
It seems the problem was actually a permissions issue. I repaired the permissions on the drive, rebooted, and everything worked! Thanks, Boris, for your help. It assured me that the problem wasn't somethign obvious.
-login as local admin
-start Directory Utility
-click plus button on the left bottom
-enter server FQDN or IP address
-click OK
-you may need to authenticate as directory admin
However, for a large number of computers you may want to set the Mac OS X server to be the DHCP client and push the LDAP info within the DHCP packet.
Boris Herman, ACSA