Windows 10: Windows 10 Post In Place Upgrade RDP Session Disconnects

I have issues after upgrading my Windows 7 Pro pc's via the in place method with RDP sessions kicking out. It is completely logging me out, I'm an admin on the domain, I have to connect via rdp again and it sometimes defaults to the local admin creds being displayed. Also, I notice issues when I try installing something remotely- it will often kick me off right away. I have other Win 10 Pro machines in my environment that are absolutely fine, they also came with Windows 10 already installed....I'm only experiencing this with the in place upgrades from Windows 7. I'm also see now that Windows 10 upgrades are failing to install on these. When I upgrade it installs Windows 10 Pro Version 1607 OS Build 14393.5. We run Intel i7's with a min of 16-32GB of ram.


Things I've already changed/checked:

Reg edits for Terminal Server session times

GP for session times

Trying to disable auto log off

Deleted reg entry for server session with pc


Any ideas? I'm seeing alot of questions similar but no real solution. Any help is appreciated. There is a setting I'm missing here :\


Thanks

:)

 

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.

 

Activate Screensaver when disconnecting from RDP session

Depending, how you disconnect, you can create a shortcut, like:

tsdiscon
start "" "C:\Windows\System32\Mystify.scr" /s

 

Server 2016 Essentials RDP session - no keyboard or mouse

After installing the latest build 14393.rs1_release_inmarket.161014-1755 I'm having this problem.

When reconnecting to a previously disconnected but running desktop session, after authentication I receive a black screen and shortly thereafter the session quits with the following error:

"Failed to reconnect to your remote session.

Please try to connect again."

This behavior is the same with MS RDP client in both Windows 10 and Android MS RDP client version 4.2.

If I connect from Linux the behavior is slightly different. Here I am able to connect to the session and see the desktop but I'm not able to get a response from keyboard or mouse. It's as if the session is not listening for input. The session remains
alive (animations continue to update e.g. clock) until I disconnect.

So far the only way I'm able to restore normal RDP session behavior is to reboot the server.