"Other" login user for AD login disappears upon reboot on macs running Mac OS 10.15.6

[tommayye]

Hi All,

I've got a client that I've joined their macs to the local windows active directory domain. The macs are running a variety of Mac OS from 10.13 to 10.15.

Two of their machines, a brand new mac pro, and an iMac running 10.15.6 have the "other" account disappearing from the login screen when rebooting. The current workaround is to log in as a local account, then switch users which it then appears.

The domain UPN ends with .local which I believe may be part of the issue due to this article.....

Network (AD) (other) user disappearing from log-in screen on mac os X

Solution: [ Email comes in that I've been tagged by someone on Spiceworks: "Ahh, somebody tagged me. I'm not terribly fond of that. What's this I find ? Oh my,

community.spiceworks.com

I tried the command in that article but it seems invalid.

Seeing if anyone else had similar issues?

 

[satcomer]

The other is referring to a network account where the user info is saved to server!

 

[chrfr]

Hi All,

I've got a client that I've joined their macs to the local windows active directory domain. The macs are running a variety of Mac OS from 10.13 to 10.15.

Two of their machines, a brand new mac pro, and an iMac running 10.15.6 have the "other" account disappearing from the login screen when rebooting. The current workaround is to log in as a local account, then switch users which it then appears.

The domain UPN ends with .local which I believe may be part of the issue due to this article.....

Network (AD) (other) user disappearing from log-in screen on mac os X

Solution: [ Email comes in that I've been tagged by someone on Spiceworks: "Ahh, somebody tagged me. I'm not terribly fond of that. What's this I find ? Oh my,

community.spiceworks.com

I tried the command in that article but it seems invalid.

Seeing if anyone else had similar issues?

Setting up a Windows domain with .local is bad practice, is not recommended by Microsoft, and will absolutely cause problems for Macs. The command in that article will not work because that file is protected by SIP. The only real fix here is to properly name the AD domain.

 

[hobowankenobi]

While you are sorting out AD binding issues: instead of binding to AD, you might consider NoMAD Login. Pretty slick for a free, open-source tool.