Problems logging in to AD user account on Sonoma...

Potentially related to this issue: User switching doesn't work properly in m… - Apple Community

I have multiple problems on different Macs connected to our network, with regards to the UI behavoiur when logging in. We use AD to allow network users to sign into the Macs, using their AD accounts. We have been doing this for decades and are well aware of the fairly frequent issues introduced when Apple and Microsoft update components for AD and related security systems. Sonoma appears to have suffered from a repeat of these issues. Whether this is down to a MS or Apple issue is currently, for us, leaning toward it being an issue from Apple's side, as the issues appear to have started to appear following updates to the Macs being deployed. The Macs have it behaving inconsistently and generally unreliably, with the following issues being experienced:

1. A MacBook M3 Pro (macOS 14.7.8, updated to 14.8 as test - no difference) that when selecting "Other" from the login screen it simply shows the user login for the last logged on user. Hitting "ESC" doesn't show any of the other user accounts on this Mac at all, just the last logged in user.
2. An Intel iMac Pro 2017 (macOS 14.7.8) where, when switching the user, it will only show the login screen for the current logged in user. Hitting "ESC" does not show other accounts or "Other".
3. An Intel iMac Pro 2017 (macOS 14.7.8) where, when switching the user, it shows the other accounts, as well as "Other". I thought, "great!" However, when you select "Other" and try to go back to the other users and not set up a new network account, you can't get back to the login screen. It is stuck showing the login prompt for "Other". i.e. Username and password fields. However, if I log in to log in for a new network user, this one seems to be working OK and creates the new user account/profile without issues.

This ?UI behaviour has been working just fine, since it got fixed, following the last time it got screwed up by an update and is now doing it again. I have also tried re-binding one of these Macs to AD and it has made no difference to the behaviour.

We run a policy of current Major macOS release minus one, due to certain software we're running that has a high propensity to failure, with the latest and greatest (I'm sure I don't need to go into which vendor this is). So, at least I am now able to test Sequoia to see if this fixes it.