RDS 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.
RDS 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.
Remote App strange behavior with saved credentials
This problem has confused me for awhile now, and I haven't been able to find any solution. I'm not sure if this is an issue with the mstsc.exe on the client, or if it's an issues server side at this point. The bottom line issue, is that the "Remember me" checkbox for the remote app credentials will stop showing up, preventing the user from saving his or her credentials for the remote app connection. So, here's the scenario. I have a Windows Server 2016 environment, with it's own domain that provides access to applications to remote clients via Remote App services. Joining the clients to the domain isn't an option. We have a publicly trusted certificate deployed in our Remote App servers. When we setup a client machine, we do so through the Remote App and Desktop Connections control panel app, and enter the RDweb url. The client machines are a mix of Windows 7 machines to Windows 10. When we give the users their credentials, it's always in the format of <username>@<domain name> not <domain name>\<username> When we initially setup the client machine, usually the user will save his credentials. Which is fine. However, when their password expires, or when they want to change it through the web interface, things get weird. When everything is working fine, in the windows credential manager there are two entries, both in the Windows Credentials section. 1) <public FQDN of remote app collection> with the username in the format of <username>@domainname> 2) TERMSRV/<public FQDN of remote app collection> with the username in the format of <username>@domainname> When the users change their passwords via the RDWeb portal page, obviously it doesn't update their saved credentials. The expectation would be that the remote desktop client would prompt them for their new password, with the option to save it, as how it was when it was originally setup. And this is what happens, some times. They get prompted for their password, with a screen that shows them their username in the <domain>\<username> format, with the remember me box. Eventually though, it will break. And this is 100% repeatable by changing the password on the AD side, and trying to conenct again from the client. At some point, one of those times they change their password, they will be prompted for their new password with a credential screen with no remember me box. When it does this. if you look in the credential manager, there will be 3 entries. Windows Credentials: TERMSRV/<RDSessionHost FQDN> with username in <domain name>\<username> format TERMSRV/<public FQDN of remote app collection> with the username in the format of <username>@domainname> Generic Credentials: TERMSRV/<public FQDN of remote app collection> with username in <domain name>\<username> format After this happens, the users will never get the remember me box again, unless they completely delete the session from their control panel, and re-add it. Manually fixing the credentials in the credential manager to make them match how they were when it was working fine works temporarily, but will break again next time they reboot their computer, or the session disconnects from the servers. I’m not sure what to do with this next. If anyone has any ideas, it'd be greatly appriciated.Cameras To Redirect Custom RDP Property Does not Work
In mstsc.exe, under Local Resources > More.. there is an option for Video capture devices. Which lists my webcam and Devices that I plug in later. I have determined that this option the an RDP file is the string camerastoredirect:s:* So what I have done is ran the following command on my Connection Broker so that this line will be added to rdp file generated by the feed. Set-RDSessionCollectionConfiguration -CollectionName $CollectionName -CustomRdpProperty "camerastoredirect:s:*" When I run Get-RDSessionCollectionConfiguration I see the value has been added to CustomRdpProperty along with "use redirection server name:i:1" which seems to be a default on all collections. What I am trying to solve is, why does my custom RDP property not apply to the RDP files that are downloaded.
