10.7.3 AD logon not recognizing "short" account name

Cem
Valued Contributor

Hi all, I have finally started my Lion build.
I am using Casper AD bind config in Casper Admin and this has worked very well in 10.6.8. We use it at imaging as well as through Self Service.

However I have an issue/s with 10.7.3 as the unresolved link below (I also copy/pasted here)..OR Perhaps its an 10.7.3 AD plugin issue...;
https://discussions.apple.com/message/17538575#17538575

problem is;
IF Macs running 10.6.8, bound to AD. If my name is "Joseph Smith", I log on as "smithj" with no problem. I am now testing 10.7.3. I bind the new 10.7.3 machine to AD, but I cannot log in as "smithj". I CAN log in as "joesph.smith".

Now, on my 10.6.8 machine, I go to System Preferences/Accounts, authenticate as admin, control-click on my account (labeled "Smith Joesph") and go to Advanced Options. Under Advanced Options, the account name is listed as "smithj", and at the bottom, there are a list of Aliases, including "joseph.smith", "smith joseph", "joseph.smith@company.com", "Joseph.Smith@company.com", "DOMAIN/joseph.smith", "DOMAIN/smith joseph", "Smith Joseph"...

On the 10.7.3 machine, I look at my account under Advanced Options, and the account name is listed as "joseph.smith" (not "smithj"). There is nothing in the Aliases window. This would explain why I can only log in as "joseph.smith". So I added "smithj" to the Aliases window and restarted. Success! I was able to log in as "smithj". But then I went back to Advanced Options, and the Aliases window was blank again. I logged out, and was unable to log in as "smithj".

On both the 10.6.8 and 10.7.3 machines, the other Advanced Options retained the idential UserID, Group, and UUID for my account. Just the Account Name and Aliases information were different.

on top that; the home account is created as the shortname like "joseph.smith" NOT as before in 10.6 "smithj" . This will cause us a few issues too (when we start to rebuilding Macs and migrating their accounts and home folder etc…)

Anyone also has experineced this? Is there a fix or workaround?

BTW I have already open a ticket with our Apple Support re-this.

3 REPLIES 3

Cem
Valued Contributor

UPDATE: Apple is aware of this issue and I believe they are working on it to get it fixed.

jarednichols
Honored Contributor

If you're part of the Mac Developer program, I advise you to try the 10.7.4 seed.

Strongly advise.

(Hopefully that was vague enough.)

Cem
Valued Contributor

getting the 10.7.4 this afternoon... 10.7.3 is a no go zone! AD doesn't work, it has expired flat packages etc... I will stick with the golden rule; wait for the .4 update!