Answer the question
In order to leave comments, you need to log in
Connecting to RDP without specific user login: how to implement?
Good afternoon friends!
Faced with the most stupid problem according to my feelings (and apparently I myself am the source of stupidity ...): there is an office PC, which, depending on the shift, is used by 2 different employees (conditional Masha and Zoya). They work on a thin client with an RDP connection to a remote Windows 7 computer.
The problem is that when the connection is started, a specific user is logged in, for example, Zoya. However, it is required that at the beginning of the working day the computer is turned on and an RDP connection is started without automatic login of a specific user, but the Windows login screen is displayed with empty fields "user" and "password".
Having played with group policies, it turned out to enable the so-called GUI authorization, where we see 2 icons: Administrator and "Other user". From here, 2 questions arose: how to remove the administrator account from the welcome / authorization screen and why, if authorization is not performed within 30 seconds, the RDP connection closes itself completely ...?
Answer the question
In order to leave comments, you need to log in
The solution was found:
On the server (and on regular Windows if it is not a server RDP), by default there is a 30-second timeout for GUI authorization, you can turn it off like this:
1. Go to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control l\TerminalServer\WinStations\RDP -Tcp
2. Create a DWORD string value
3. Let's name it: LogonTimeout (DWORD)
4. Set the value, for example, to 3600 minutes.
5. Reboot the server
Done. Connection no longer resets after 30 seconds.
Thanks everyone for the replies!
Connecting to RDP without specific user loginNo way.
But just two labels "Masha" and "Zoya" will not solve the problem?
https://gallery.technet.microsoft.com/scriptcenter...
Two local accounts, and each has its own RDP label on the desktop
No way. If I understand correctly, you want to double-click on the RDP to "launch" windows without any questions, like when you turn on the computer. But in fact, when the OS starts, the user is completely initialized, on his behalf and for him, the graphical shell, part of the programs, is launched. But you don't see it, because most likely there is only one user, there is no password, so the authorization window is skipped. And yes, in all multi-user operating systems (Windows of them), work without a user is impossible by definition. In your case, you should play around with adding shortcuts with RDP connection parameters
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question