Link to home
Start Free TrialLog in
Avatar of Robert Wilmoth
Robert WilmothFlag for United States of America

asked on

Windows 10 login issue

I have a conference PC where I have many different users (probably 15) who regularly login and I have pre-logged all of them in and set up email, desktop etc... Users are supposed to log out but do not always do that. When there are as few as 3 people logged in and another user wants to log in they will click on the "other user" so that it brings up a login screen. Many times clicking on this "other user" will do nothing at all and the user is forced to reboot to be able to log in. It does not always happen but it happens enough to be a bother. I would like that everyone just log off and have even printed this on the keyboard but users will be users. Any idea why this happens and any way to recify it would be appreciated.
Avatar of Wayne88
Wayne88
Flag of Canada image

If I understand correctly, the Windows 10 machine is acting as a Terminal Server or Remote Desktop Server allowing many people to login concurrently and your limit is 3 at the moment.  Is this correct?

Is the problem you want more people to login simultaneously or the fact that people are not logging off?
Avatar of Robert Wilmoth

ASKER

This computer is no different than any other computer in our environment. It is a member of a Windows domain and is in the conference room hooked up to large TV type monitors. It is not a terminal server or remoted into. Although I would like users to log off this is not the main issue. The issue is when someone tries to login and clicks on "other user" since they were not the last to log in, nothing happens. You can click on "other user 20 times but it does not bring up the dialog box with username and password.
you are at the lock screen?  or is the user doing a switch user scenario?
It is on the lock screen.
ASKER CERTIFIED SOLUTION
Avatar of akahan
akahan
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I was not quite sure where this was going so I tried it. This does not work because when a user does not log out, the next user has no option to log on. The only login name on the lock screen is the last user to use the machine. At least the way it is now sometimes clicking on "other user" sometimes works.
Perhaps, using the directions at this link, you could prevent it from showing the name of the last user, and default to "Other User" (in addition to following the steps I mentioned above):

https://www.tenforums.com/tutorials/9134-do-not-display-user-name-sign-screen-windows-10-a.html#option1
Well, we're getting there. Using these two steps makes it so it does not show the last user unless they do not log out. In that case it is the only user displayed with no option for a different user to log in. I've got multiple users logging on to this machine at any given time.
If you don't mind installing a little non-Microsoft application, this guy seems to have encountered exactly the same problem as you have, and solved it; I can't vouch for his solution, but it's the closest thing I've been able to find to address your issue:

https://fitzcarraldoblog.wordpress.com/2015/12/20/automatically-log-off-inactive-users-in-windows-10/
This is not exactly the issue I am facing. Frankly, I would not care if all 15 people were logged in at the same time. The problem is that many times when a user wants to log in, selecting "other user" does not work. I just had it not work when there was only one user logged in. Unfortunately, this is a very complicated solution requiring me to log in as each user and then it still may not fix my issue.
This is buggy behavior but I guess, it's not windows alone but it's maybe induced by 3rd party software. Anyway, turning off fast user switching is what has been already suggested and what should be tried: disable-fast-user-switching-on-windows
Thanks to everyone for the help. I took the first solution combined with the group policy and I think it's going to work.