Jeff,
I found that I need to put the address of the OD server in both variables for it to work. Strange, but that is what happens. I don't use authenticated binding. I also make this an "At Reboot" script because like AD, each matching/binding has to be unique.
You might be able to have it work when imaging, just by changing to "at reboot" if you are pushing with Casper Remote, should just work as after on live machine.

Not showing up in WGM. Usually, I toss out the /Library/Preferences/SystemConfiguration which means I need to rename the computer and check the Network prefs. Then it shows up in WGM. This is probably the more drastic fix, but I don't know which file needs to be changed, deleted etc.

Good luck,
-Nathaniel
Saint Paul Public Schools

Is anyone using the built-in OD bind function in Casper 7? I've added it to my policy (as both priorities 1 and 10) and it seems to be listed in the contents of what will be imaged, and the logs indicate "adding line for binding," but when the machine reboots it's not bound to my ODM. Any ideas?

Jeffrey A. Strauss
Department of Educational Technology
Systems Administrator
Loyola High School of Los Angeles
1901 Venice Blvd.
Los Angeles, Ca 90006
(213) 381-5121 x265

Please consider the environment before printing this e-mail.

I found I had issues with OD bindings when I was running v7 of the Casper
Jeff Strauss <jstrauss at loyolahs.edu> on August 11, 2009 at 2:52 PM -0500 wrote:
Suite on my server, and v6.01 of Casper Imaging on my NetBoot image. Once
everything was at v7 or v7.01 the OD bindings started working again.

Steve

--
Steven Diver, Network Manager
Adlai E. Stevenson High School / www.d125.org
Email: sdiver at d125.org / Phone: 847.415.4304

"Be not simply good, be good for something."
-Henry David Thoreau (1817-1862)

I'm 7 across the board...

Jeff

I have not tried the built in features as I literally just upgraded to
Casper 7 yesterday. However, in version 6 I run an at first boot script
that binds the client to the specific replica, and it works like a
charm.

I can post that if you like?

-Tom

Please do. I wrote the script I use, but I'd like to see any differences. :)

This is for a simple vanilla bind, no authenticate bind, no computer
name.

#!/bin/bash #This script binds a 10.4.11 or 10.5 client to an LDAP (OD) server. #please input your FQDN to the variable below

newserver="myserver.com"

/usr/sbin/dsconfigldap -a $newserver /usr/bin/dscl localhost -create /Search SearchPolicy
dsAttrTypeStandard:CSPSearchPath /usr/bin/dscl localhost -merge /Search CSPSearchPath /LDAPv3/$newserver /usr/bin/dscl localhost -create /Contact SearchPolicy
dsAttrTypeStandard:CSPSearchPath /usr/bin/dscl localhost -merge /Contact CSPSearchPath /LDAPv3/$newserver

exit 0

As you can see this is very simple, very straight forward and I have it
running on all laptops as a first boot run script. Works like a champ.

U need to upgrade to 7.0.1 jamf fixed the OD issues, works fine now

Jeff, I've been using it for a few weeks now and haven't had any problems
with it. I was previously using a script, but am now solely relying on
the built-in binding.

Chad

Chad,

I've heard my issue was related to version 7.0 and was fixed in 7.0.1, which I'm installing today. This feature is cool and I want to use it. :)

Sent from a mobile device.

Oy. OK I'm having some issues with OD binding that I somehow need to get figured out. I've upgraded to 7.01 across the board and binding won't work with either the built-in option or with a script. I can bind manually after imaging, so I know that everything's cool on my ODM. Everything in the logs show that things are smooth, but the machines don't show up in WGM and there's no ODM info in Directory Utility.

Also (and this may or may not be related), when I select for the computer to reboot to the startup disk, it doesn't; it just sits in Imaging until the LaunchPad launches and I can select to restart the computer.

Anyone seen any of these issues?

Jeffrey A. Strauss
Department of Educational Technology
Systems Administrator
Loyola High School of Los Angeles
1901 Venice Blvd.
Los Angeles, Ca 90006
(213) 381-5121 x265

Please consider the environment before printing this e-mail.

Bah. Binding works post-imaging via policy. I'll just do that, since I have to image next week. Whew, came in the nick of time. :-/

Any further info on the issue would still be helpful, though.

- Jeff

It's not the binding it's ur imaging , do u run any other first run scripts or cs4?

U think ur first run script isn't being created, see other posts regarding Casper imaging crashing

I have not tried the built in BIND features of Casper v7 as I have just upgraded. I do however, run a post image script that works just fine to BIND all my clients to what replica I tell it to.