Windows 10: Restart RDP Session without logging in after reboot.

I'm using a Win 10 Pro PC as a server of sorts to store all my media files and host my dedicated gaming servers. This "server" doesn't have its own keyboard or monitor, I only connect using RDP from my main workstation. This works perfectly. My issue is with windows forcing my "server" to restart because of updates, which closes my RDP session which I leave open after having started it from my workstation or phone or whatever. What I want to know is: how I can get Windows to restart my RDP session after a restart without me having to restart it myself.What I already tried are the following "fi

:)

 

Prevent Forced Log-Off on Windows 10 when I end RDP session

Hello.

I have an old Laptop which I use to download files from my super slow internet and act as a NAS on the local LAN with an external hard disk. It has been running Windows 7 for years. The main method I use to access it is via RDP (Locally or over the internet).
Whenever I would disconnect an RDP session, the user would remain logged on, with all the apps started in the RDP session continuing to run.

I upgraded to Windows 10 today. The RDP behaviour seems to have changed.

Whenever I disconnect the RDP session, the user would be logged off and all apps started by me killed. Whenever I login again (either locally or via RDP), a brand new session would start.

1. This happens immediately after I disconnect the RDP session

2. I have tried setting the idle timeout in Group Policy to never, doesn't help.

Is there any way to override this in Windows 10?

*Edit - I tried Windows 8.1 and the same behaviour exists there, too.

 

RDP had multiple active sessions

Hi

the other day i had this unusual issue where a user was using RDP to connect to their work machine and instead of joining the existing session they had from a previous day it created a new one whilst also keeping the old one active, this prompted the user to select which session they wanted to join although upon reading the EULA and other forum posts this shouldn't have been possible. The user logged into the same remote computer as they usually do and signed in with the same set of user credentials both to create the initial session and the new session, Anybody have any ideas what caused this and have any suggestions from potentially preventing it in the future?

The user's desktop was Windows 10 Pro 21H2 and the remote desktop was Windows 10 Enterprise 21H2 if that helps.

 

"Access denied 0x80004005" issue - RDP session - Windows server 2016 - User logon time out

I have scheduled a task running all the time on my Windows server 2016.

Connecting through RDP, few functionalities require user to be logged on to the server to be processed but it seems user log offs after a time limit. After certain time limit, task was facing "Access denied 0x80004005"
Error

i have tried changing the following in RDP session host settings in group policy:

• automatic re connection -> enabled
• deny logoff of an administrator logged in to the console session -> enabled
• configure keep alive connection interval -> 99999
• session time limits -> disabled

But they didnt help my task, still its facing "Access denied 0x80004005" Error