remote desktop-after session closed-question about other computer

Finally did a RD. It was easy to set up, surprised me, and has done what I wanted as far as maintaining files on our other computer.

My question is Comp A is a new build, connects to Comp B, with RemoteDesktop, and works OK. When I leave the session, Comp B which I connected to, now wants a password typed in to get back in the system. It"s at the usual logon screen. Didn't before. Is this normal, and could it be changed, not requiring one like the main one I use (Comp A), and the 2nd. question

because the screen is bigger on Comp A now, even using the controls in the RD logon, when I close session, the icons stay where they are at for the Comp A screen size, which means I have to right click on the desktop on Comp B desktop, select from the menu restore desktop, to get it to go back to Comp B screen size. Any way to auto do this?

Thanks

When you login via Rd you log off the current user that's why you need to log back in you may like to try free TeamViewer you can connect via internet and share better

ryker said:

Finally did a RD. It was easy to set up, surprised me, and has done what I wanted as far as maintaining files on our other computer.

My question is Comp A is a new build, connects to Comp B, with RemoteDesktop, and works OK. When I leave the session, Comp B which I connected to, now wants a password typed in to get back in the system. It"s at the usual logon screen. Didn't before. Is this normal, and could it be changed, not requiring one like the main one I use (Comp A), and the 2nd. question
Thanks

Client versions of Windows such as Windows 10 permit only one user to be interactively logged into the system. That user can be logged on locally or with Remote Desktop but not both at the same time. Server operating systems permit multiple interactive users.

It's a normal thing. When you connect to remote desktop, the server computer becomes locked locally, so no other person can use it in the same session as the remote one. When disconnected, the session remains locked, forcing the user to re-enter his credentials. This is fundamentally the same thing as locking the screen locally (Win + L). I don't know if it can be changed, seems like an inherent characteristic of how remote desktop works.

As for the screen sizes problem, if the client resolution is bigger, you can prevent messing with the server resolution by setting it from the client. In the connection dialog (client side), go to the screen tab, and choose the remote resolution to match the native one of the server. This will prevent such change, and the screen will remain at its original size. The obvious drawback is that it makes the working area on the client smaller, limited to that of the server screen.