"Bug" if Don't Display Last Logged on and/or Current Logged On User set via GPO
Basically we disable the last logged on user or the current logged on user name from being displayed on the unlock screen. Essentially windows forces it to the "Other User" log on screen every time the machine is to be unlocked. If these settings are set, the log on screen for the Logon App on Windows 10 (at least, havent tried other OS versions) displays a blank screen with the "Other User" button in the lower left hand corner of the screen, which they have to click, then it switches to the other user screen, displays any logon banner again, and then prompts for the Other User logon info.
If these local settings are set via GPO, can the Logon App just redirect to the Other User screen immediately by default? Current behavior is confusing for users.
Second follow up to this, looks like it completely locks you out of a windows core server when a user is logged in and the session locks. There is no a no option for 'other user' ... you get an option to "Select a user" with no users in the list.
version 2.7.1 which I believe is latest
Did a little bit more digging - the specific GPO setting is Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Interactive Logon: Display Username information when the session is locked.
When that is set to Do not display user information or User Display Name only, the logon app does not display anything other than switch user in OSE's with GUI, and on core servers it just shows "Select a User" and you cannot even switch users (locking you out until the server is rebooted)
I'd suggest opening a support case for this if you have not already -- the authpoint team should be able to help with this.
WatchGuard Customer Support