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.
Configuring session timeout for Remote Desktop Services web client (HTML5)
Is anyone aware of a way to customize the session timeout in the remote desktop services web client (HTML5)? An issue our users have been experiencing is if they are in a long running remote desktop session and they experience a disconnect, clicking the "reconnect" button on the pop up they receive doesn't do anything. They also can't navigate back to the main menu to select their session collection to reconnect. The fix is they need to click refresh and log in again, it appears that the cause is that the users' login session to the remote desktop web client has timed out. Ideally, we'd like to customize the session timeout to be a long value so they could get through a whole work shift without their existing authentication session being timed out.Remote Desktop Services Deployment fails with exceptions
I'm trying to deploy Remote Desktop Services on a single server on Windows Server 2019 Standard. I've tried both Standard Deployment and Quick Start with a Session-based desktop development but I'm getting the following error during the installation: Unable to add server REMOTEAPP.AD.DOMAIN.COM to the list of servers on the RD Connection Broker server REMOTEAPP.AD.DOMAIN.COM..Exception of type 'System.Runtime.InteropServices.COMException' was thrown. I searched for some hint about this problem but I had not find anything useful. I cannot even find any useful log into the events log, and I tried one more time after reinstalling the server from scratch. Could you help me please? Thank you very much!
TSplus as an alternative to RDS without paying RDS license fees to microsoft
Hello, We are evaluating whether to use TSplus (https://www.terminalserviceplus.eu/) as an alternative to Microsoft RDS/Terminal Server. According to TSplus we can not install or uninstall the RDS role, so we do not use RDS CALs and use TSplus CALs. This way it would not be necessary to pay for Windows Remote Desktop licenses. Is this correct? I can't find any information from Microsoft about it reading documentation. As I see it is correct that using TSPlus without installing Microsoft RDS it would not be necessary to pay Remote Desktop licenses. Could someone confirm me that it is so?Quser hangs and how to find the citrix load index equivalent
Dear all, at first, I was mostly active in a german forum, but most experts of it don't speak german... so I think in english I get more contact to admins with good knowledge. But could you give me some hints which foum, community here is the most activ one for questions on topics Windows Server, Remote Desktop Services and Active Directory? I found this sites and I am not sure how to select the right one: https://learn.microsoft.com/en-us/answers/tags/301/remote-desktop https://learn.microsoft.com/en-us/answers/tags/220/windows-server https://techcommunity.microsoft.com/t5/windows-server/ct-p/Windows-Server https://techcommunity.microsoft.com/t5/windows-server-for-it-pro/bd-p/WindowsServer Now to my current question on Remote Desktop Services: We have a farm with over 30 rdsh. Since some weeks we have login issues. We encountered, that we also have issues with getting session information with the "quser" command. The prompt hangs and no output is done. We have no idea why this happens. Did anybody seen this before? Second question: Some years ago we had Citrix Terminalservers. There was a thing called load index. The Citrix TS put up their load to the max value of 10000 during a logon process from a user. Afterwards it comes down to a lower value based on some math rules for ressources and so on. I haven't found any command in RDS to get a value alike the load value. Is RDS doing something similar to the load index like Citrix? Where can I get this value? How does a rdsh prevent too many logins at the same time? If we force simultaneously logons the user gets a message with i assume is in english "remote desktop services utilized" (in german Remotedesktopdienste ausgelastet). And also the quser command seems to take a "short break" and the output comes some seconds later. Best regards, StefanRemote 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.
Unable to install RDS roles on windows server 2019
Problem: Per my knowledge all requirements listed above, checks out: Domain Admin is also member of local admin group: a) What is causing this problem? b) How can I fix it? C) This is a fresh install of server 2019 Any help would be appreciated, thanks!
