Hi, I implemented a custom Gina (full implementation, not a stub) but haven't found a way to overcome the described below problem yet. It appears during Remote console logon. Case A. A user is logged on locally and you try to login remotely using the same user. Everything seems to work fine - the local consol session transparently gets passed to the remote consol (actually the sessions switch). The weird thing is that the local consol goes in "log off" state - if you use msgina it goes to "lock computer" Case B. Nobody is logged in locally or you try to login with different user then the one logged on locally. Something gets wrong. The following sequence of events occur: On the Remote console: 1. WlxInitialize 2. WlxLoggedOutSAS, WLX_SAS_TYPE_CTRL_ALT_DEL(1) - credentials acquired and verified; WLX_SAS_ACTION_LOGON returned 3. WlxGetConsoleSwitchCredentials - credentials passed and TRUE returned On the Local console: 4. WlxDisconnectNotify Now sessions get switched (remote become local and vice versa) On the Remote (old local) console 5a. WlxLoggedOutSAS, WLX_SAS_TYPE_AUTHENTICATED(7) - I try to call WlxQueryConsoleSwitchCredentials but it fails with ERROR_IO_PENDING 5b. WlxReconnectNotify (almost immediately after 4a) On the Local (old remote) console: 6. WlxInitialize - WHY??? 7. WlxLoggedOutSAS, WLX_SAS_TYPE_CTRL_ALT_DEL(1) And now the interesting part - second time credentials supplied! On the Remote (old local) console: 8. WlxLoggedOutSAS, WLX_SAS_TYPE_CTRL_ALT_DEL(1) - credentials acquired and verified; WLX_SAS_ACTION_LOGON returned 9. Remote console opens!!!!! Why the local console goes in "log off" state? Why does WlxQueryConsoleSwitchCredentials fails? Why WlxInitialize is called again? Why the after supplying credentials for a second time is succeeds? I know the answer of the forth question. It works as Case A (see above) works - the logon session already exists and it just attaches to it. Having said all that, have anyone found a solution of that problem? Can anyone help me? Thanks.
