AD Settings and Mountain Lion

[Lhsachs]

Has anyone else seen this issue:

My settings for AD in Casper are:
Create mobile account at login (checked)
Require confirmation before creating mobile account (unchecked)
Force local home directory on startup disk (checked)
Use UNC Path from Active Directory....SMB
Default user shell /bin/bash

What I find on some newly imaged systems are:

Create mobile account at login (unchecked)
Require confirmation before creating mobile account (checked)
Force local home directory on startup disk (checked)
Use UNC Path from Active Directory....SMB
Default user shell /bin/bash

So, I end up with network users with a local home....who don't show up in Users and Groups unless they are logged in.

Yes, I can fix this by unbinding from AD and binding by hand on the system....

Running Casper 8.6
Base image created with instadmg, default admin user (501) created with Mager Valp's CreateUserPkg.app v1.2b5

[Lhsachs]

Follow up: I've reimaged the same MacBook Pro with my 10.7.4 image, and the Active Directory came in properly.

Reimaged again with 10.8 - the AD settings still come up wrong. When I unbind from AD, and then use Casper Remote to join the system to AD - the settings come in properly!!! arrgh.....

.......
The netboot image I'm using is a new 10.8 one I created that does very well booting all systems. I'm just choosing a different build in Casper Imaging...

[Lhsachs]

This is becoming even more fun:
On a different MacBook Pro: a 13 inch mid 2009, The 10.8 build works: I see the Casper Installing window upon reboot, and AD settings are what are in Casper

The Mac I had issues with AD was a 17 inch MacBook Pro Mid 2010...

I also had issues with a thin build (left the 10.7.4 OS we got from Apple on the system - and just add apps and settings) - one of the new MacBook Pro Retina displays... (the others ones did NOT have the AD issue...) something odd....

[lindell]

I know this isn't much help, but I don't think it's a 10.8 issue. We recently found a couple of 10.7.4 machines with the exact same behavior as you describe, but I can't seem to reproduce it. Casper 8.6, Mid 2012 MacBook Air, same Casper AD script that has worked hundreds of times. Machines join during imaging, but the options are not set properly.