AD binding and launchd

[userosx]

I’m currently using a LaunchDaemon to automatically rename and bind our computers to AD. I have everything working, but have encountered an issue using launchd. I need to ensure the daemon runs after the NIC has received an IP address and the network is active. If not, our authentication method fails (internally developed, requires a network connection). Everything works after login 100% of the time. Okay, so this thread applies more to launchd than it does AD, but I’m not sure where to go. Anyone else using LaunchDaemons to bind to AD? If the password was included in our script, it would work. However, since it gets this from the network at the time of startup, if the network connection isn’t yet active, it will fail.

[userosx]

Never mind, I figured it out. I just had to add a “socket” to the LaunchDaemon to allow for the network authentication.

[jasonthat]

Hey userosx
could you tell me if you were using lauchnd to do the renaming & binding, after the machines had been imaged. sorry i am not familiar with lauchnd but would it be possible to use launchd for this purpose if my 500+ machines were already imaged. If so, what other ways are there to do this for all these machines over the network? Thanks.

[Author]

Posts