[Remote Desktop] account limitations

First of all, I confirm that a password is required to establish a remote connection...


Hello Eny, it's not a priority; I use Remote Desktop on my 2 PCs without user passwords. It's simply a matter of removing the restriction (Restrict the use of blank passwords for local accounts at console logon. This can be done via GPEDIT.MSC under Computer Configuration--Windows Settings--Security Settings--Local Policies and Security Options.

For Windows 7, the same path but it is called

Accounts: restrict the use of empty passwords for the local account at console logon.

yes, it works but it disconnects the remote user: only one holder at a time...

Hi
Yes, my PC is connected to a local network of two PCs
and as I said, I can connect as a guest, but I want to connect as an administrator,
Thank you

It works for me. I had the same problem with my Windows Server 2003, but Mida's solution helped me.

Hello,

it is not possible to have multiple sessions open on a remote PC via Remote Desktop. Only a Terminal Server (TSE) allows this because it actually opens different sessions each time. With Windows XP, the remote session appears locked or closed, and you can only reopen it when the remote client has disconnected, or when reconnecting locally, the remote client is closed.

There are two different modes of operation, depending on whether fast user switching is enabled or not. If it is not enabled, local sessions are closed (after a warning message depending on whether you are trying to open a remote session with an admin account or not, and whether it differs from the local account).

If fast switching is enabled, local sessions are disconnected.
Do not confuse "Disconnected" and "Closed". A disconnected session means that the user no longer has access, but the session remains active (active programs, etc.). So access via Remote Desktop "Disconnects" the local session in this case but does not close it, regardless of the account used for remote access (the same as the one opened locally or another one with the session open or not).

It's not that simple; there are many scenarios depending on the levels of users connected on both sides, but the simplest way is to use the same local and remote account (with administrator privileges), so you can avoid messages and session closures (whether fast user switching is enabled or not).

Thank you, it works perfectly; I've been looking for this solution for so long, I wonder why a user rated you -1 :s

Thank you, your advice helped me solve the remote access issue with Windows 7, it works very well now, thanks again.

me it doesn't work

I must inform you, however, that the "Local Security Policy" menu is not included in Windows 7 Home Premium Edition, only in the Professional, Enterprise, and possibly other versions.

Huge, there you go. Thank you.