Remote Desktop Services
70 TopicsBug: no reconnect to disconnected session with fSingleSessionPerUser=0
Affected: All Server 2019 Insider Previews including build 17713 Steps to reproduce: (no need to install RDSH role to reproduce the bug) enable multiple sessions per user: Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Connections -> "Restrict Remote Desktop Services users to a single Remote Desktop Services Session" to "Disabled" rdp to the server and log in as Administrator close the mstsc window or disconnect rdp to the server again, log in as Administrator and you will get a new session taskmgr now shows 2 Administrator sessions: one disconnected and the new one just created close the mstsc window or disconnect rdp to the server again, log in as Administrator and you will get a new session taskmgr now shows 3 Administrator sessions: two disconnected and the new one just created ... If fSingleSessionPerUser == 0 you will not be able to reconnect to any disconnected session. However, now the interesting part: If you lock the session before the disconnect (ctrl+alt+end -> lock, then close mstsc) you will be successfully reconnected. I suspect the error is in termsrv.dll's CSessionArbitrationHelper::Sessions_EnumDisconnectedUserSessions function. You can alsoe reproduce this without rdp, directly on the console. Set the policy as mentioned above, log in as Administrator, disconnect your own session in task manager, log in again and you get a new session. This bug seems to be in termsrv.dll since Windows 10 1803 already.Solved29KViews4likes15CommentsStep by Step instructions for installing RDS Session Deployment using PowerShell in Windows Server 2012 R2
First published on TECHNET on Mar 04, 2015 Hello AskPerf Readers! Dhiraj here from the Windows Performance team to talk about deploying RDS using Windows PowerShell on Windows Server 2012 R2.44KViews1like0CommentsRD Licensing Configuration on Windows Server 2012
First published on TECHNET on Sep 20, 2013 Good morning AskPerf! Today we are going to discuss the steps in installing/configuring Windows Server 2012 Remote Desktop Services Licensing in your environment using various available options.66KViews1like0CommentsRDS 2019 hangs and doesnt allow user login
I have 3 RDS 2019 server - 1x Connection Broker, 2x Session host server User profile disks are configured on the connection broker Users noticed blank screen while signing in to RDS session host servers, so we disabled the App readiness to resolve the blank screen issue. Few days later user complained about applications like word excel not closing and new user sign also took time. At this time even if I try to access "\\connection broker", it doesn`t open and keeps searching for path. Following events are observed at this time on connection broker: 1. Source - storvsc, Event ID 129, \device\raidport0 - this warning is observed continuously 2. source - winlogon, event ID - 4005, win logon process has unexpectedly terminated.1.9KViews1like0CommentsRDS 2019 Remote Apps RDWEB event id 10
Hi everyone, I have a server that I was able to publish remote apps before several new applications installations today. I was also able to use the GPO "Specify the default connection URL After the installation of the new software, I wanted to publish it. However, it didn't work. I check it using the rdweb URL and found this: When I went to the server I found event id 10: "RD Web Access was unable to access RDSSerever, which is the server that is specified as running the RemoteApp and Desktop Connection Management service. Ensure that the computer account of the RD Web Access server is a member of the TS Web Access Computers security group on RDSServer." I tried multiple solutions, but: 1. I don't have a group called TS Web Access Computers Security group 2. Even after changing the authentication to a domain admin it still doesn't work... Is my only option to remove and add the RDS again? Rahamim.3.5KViews1like1Comment