Skip to main content

I tried searching for this particular issue in the forum but couldn't find it.



We are working on building our 10.8 image for next school year and have run into quite the little problem. The problem is that active directory doesn't seem to be binding on the machine until we log in with the local admin account. I can let it sit at the login screen for hours and it won't bind. But 1 or 2 minutes after I've logged in with the local admin it binds automatically. This is an annoyance as we are deploying a full 1-to-1 laptop program. I don't want to have to login to each machine, wait for it to bind, etc.



We're using Casper 8.62, Mac OS X 10.8.2, and the AD is on a Windows 2008 server.



Let me know if anymore information is needed, I can post some log files if need be.

How are you binding?
Do you have network restrictions preventing connectivity prior to loginwindow authentication?



Had issues getting airs to bind using the object created in the casper admin web interface. Had better luck scripting and setting the script to run at reboot.



The following is an extract - define the variables for your environment.
You can follow with dsconfigad commands to specify the options you want configured.



/usr/sbin/dsconfigad -f -a "$HOSTNAME" -u "$U" -p "$P" -ou "$OU" -domain "$DOMAIN"

No network restrictions.



We were binding using casper admins bind creation. I'll try the scripting method though! Thanks for the idea.

Do these laptops have Ethernet ports built in or are they MBA or rMBP?

Just to let you know that we have experienced this issue with Macbook Airs with SSD drives. As it runs so quickly some of the configuration on our PostInstall script and AD binding had issues due to identified problem in script run order (enroll script..etc..) soon after imaging.



Defect ID:D-003025



Hope JAMF will fix this in the next release as this is a major issue.

These are Macbook Airs with SSDs. I'm imaging through the USB network adapter. I've also tried with the thunderbolt adapter. 10.7.5 works perfect though.



But it would appear that the postinstall scripts aren't being ran like you said I dont think. More investigations tomorrow.

Do you have any packages/DMGs being installed on first boot? If not, try adding a few so that the scripts have more time to run.

I've experienced that some first-boot stuff doesn't seem to work when imaging 10.8, particularly when using a local repository on an external drive. Running quick-add on the second boot clears it up (in our case the enroll.sh was still sitting on the box).



Edit: In our case, certain JAMF preferences were not being created, which lead to the problem. If you were to try to manually kick of an inventory, for example, you'd get an error (Before quick-add).

Adding a package did it. Now it binds properly...hooray!



However, now I need to fix this pesky Computer Name bug. Computer should be named BA2001, I'm ending up with BA2001.local and the hostname is BA2001, but the Computer name in Sharing is Localhost. grumble. But I think everyone is having THAT issue.

Reply


Terms & ConditionsCookie settings