So I adjusted those keys in the same way. Afterall, I do login as an Administrator. But they all only mention Computer Configuration path.Ĭomputer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remtoe Desktop Session Host\Session Time limits>īut, I thought I should maybe also set the User Configuration as well. All the instructions talk about adjusting the GPO 2012 and above. I tried all the methods via a user account - but same problem. Reg key, GPO, local security settings and I just can't get it back to how it was (forever). All the suggested fixes for 2012 and above have not worked for 2019. The fix was simple and hasn't failed yet: Yes, I have resorted to TeamViewer - but I just prefer RDP and it's the quickest and nicest. I'm managed to fix the problem for the 2008 R2 server. I've searched alot and not seen many people complaining about this (yet). So, after all the work of diagnosing the problem - it does seem that only now are the servers forcing the logoff of the session when the session is closed. From the latest Win updates, I 'think' the fix for the Trickbot malware has screwed this simple setup: It look me a good number of hours to even diagnose what was going on - as these are critical VMs running and they would just quit (yet the underlying server hadn't rebooted). But that's the simplest way I like to run. I just simply login to the Administrator account and run a bunch of desktop apps that I just want to continue to run. This will reduce the likelihood that UPDs will remain connected if the server is restarted or loses power.Īdditionally, ensure all user sessions are logged off and do not allow new connections to hosts before performing maintenance and/or restarts.I log in to a few different servers using RDP (for a million years) and it's just perfect and quick - on my local network. Set GPO policy to log off disconnected sessions after X minutes.
How to prevent temporary profiles issues (i.e., mitigation):
Use this string value to easily identify individual users, for example: HOW to - Configure a Windows Server 2012 Remote Desktop Licensing Server - Free download as PDF File (.pdf), Text File (.txt) or read online for free. N.B., each objectSID profile has an expandable string value called ProfileImagePath. There are several different logs where you can find the information about Remote Desktop connections. When a user remotely connects to the remote desktop of RDS (RDP), a whole number of events appears in the Windows Event Viewer. Identify and delete any objectSIDs that have a. Profiles are listed using objectSIDs, for example:
HKLM\SOFTWARE\Microsoft\Windows NT\Current Version\ProfileList Delete any temporary use profiles from the ProfileList in Regedit.Go to Control Panel → System → Advanced System Properties → Advanced → User Profiles → Settings.ĭelete any profiles with Typeset as TEMP. Attempt to delete the temporary profile from Advanced System Properties:.Do not allow users to log on while troubleshooting. Users will receive temporary profiles if their UPD was attached to the RDS server when it was restarted. Although the user is not connected their sessions continue to run in the server background -therefore their UPD remains attached to the RDS server. The problem usually occurs when the user session state is disconnected. Changes you make to this profile will be lost when you log off."īackground: RDS server is configured with User Profile Disks (UPD). Possible errors may read, "Windows cannot find the local profile and is logging you on with a temporary profile. The problem is not uniform and may only occur for individual users. Problem: Users receive temporary profiles each time they log onto the Remote Desktop Server.