[trondah]

Thanks for the feedback 🙂

[trondah]

How about using package maker to create a snapshot package of the modules you wish to deploy?

[trondah]

Try importing using the command line tool ldapmodify -a -f file.

[trondah]

Re-imaging the client computer fixed it in my case. So something seemed to be messed up at the client side, any ideas on what it could be?

[trondah]

Did you find a solution to this?

I’m having the exact same problem, dsconfigldap says a computer record already exists (although it doesn’t), then fails to overwrite it.

Funny thing though, even though the computer record doesn’t exist, dsconfigldap creates it, but then says it doesn’t exist…

[trondah]

Create your image with InstaDMG (admin user can be added with the createUser.pkg addon), then deploy it with NetRestore.

[trondah]

Yeah Kerberized NFS is just a click away on OD 🙂

The OSX NFS server doesn’t handle resorce forks?

And does it matter if they are split into files?

[trondah]

Include this in your payload free package script:

/usr/bin/touch $3/var/db/.AppleSetupDone
/usr/bin/touch $3/Library/Receipts/.SetupRegComplete

Then after you create the image, mount it and check that those two files exist. Your new deployments should now skip the setup assistant and registration information.

[trondah]

I’d appreciate hearing about your progress on this, very interested in learning more about integrating OD with other directories.

[trondah]

Bump, I want to get this working as well, same setup. Did you have any success?

[trondah]

Interesting points. Could you elaborate on the NFS security model? I though Kerberos was pretty good?

Also, which filesystem attributes aren’t supported?

[trondah]

No worries. If anybody should find anything new on this subject, I’d be glad if you could leave a note here. I’m happy that I have a solution with PlistBuddy but would like to know exactly why that’s working and defaults is not.

[trondah]

As I mentioned in my first post, a proper kcpassword is in place. I’ve now narrowed it down to defaults vs PlistBuddy. One of the commands generates a working autologin com.apple.loginwindow.plist, the other does not. The actual deployment is being done to the image is done with a package and postinstall script.

[trondah]

Using defaults didn’t work. com.apple.loginwindow doesn’t exist until you write something to it, and creating it by using the command above doesn’t work. The loginwindow selects the user but doesn’t enter the password. It did work on one of my previous builds as mentioned though, I have no idea why.

On a sidenote, now that I’m using PlistBuddy to create the file, I noticed that PlistBuddy creates it in XML format instead of the standard binary plist format. Then I’m using the defaults command to write my other customizations in the loginhook, but I think I’ll consider using PlistBuddy more.

[trondah]

Got it to work again using PlistBuddy instead of defaults:

/usr/libexec/PlistBuddy -c “Add autoLoginUser string user” $3/Library/Preferences/com.apple.loginwindow.plist

Bingo!

This time I removed any other customizations to the loginwindow also, gonna try to find out if any of those was the culprit or if it’s just a matter of using PlistBuddy.

[Author]

Posts