I have been looking for a feature, but I do not see it in Casper anywhere. So, I did some creative scripting instead. However, I can see how this would benefit many different organizations. We have about 6,000 Macbooks in my environment and when we first rolled them out, all 6,000 users were set to change their password at first log in in OD. Well, lets just say that one server did not like 6,000 users trying to change passwords at the same time. This also goes for authentication as well. So, I wrote a script that will bind the client based off of naming convention. However, if I could just bind a client based on smart configuration in say Casper Admin, I would not have to do such things.
Often times you need to load balance how many clients authenticate against one server. Here where I work we allow about 1,000 clients per a server. Here is the example of my script, which I have now incorporated into my post image script.
#!/bin/bash
# use computer name to set OD server by naming scheme
case `/usr/sbin/networksetup -getcomputername` in WYA) ODSERVER=xs106-a.kckps.org;; HAR) ODSERVER=xs101-a.kckps.org;; WHS) ODSERVER=xs104-a.kckps.org;; SAS) ODSERVER=xs102-a.kckps.org;; SCH*) ODSERVER=xs100-a.kckps.org;; esac
/usr/sbin/dsconfigldap -a ${ODSERVER} /usr/bin/dscl /Search -create / SearchPolicy dsAttrTypeStandard:CSPSearchPath /usr/bin/dscl /Search/Contacts -create / SearchPolicy dsAttrTypeStandard:CSPSearchPath /usr/bin/dscl /Search -append / CSPSearchPath "/LDAPv3/${ODSERVER}" /usr/bin/dscl /Search/Contacts -append / CSPSearchPath "/LDAPv3/${ODSERVER}"
exit 0
