RDP
20 TopicsUser CAL or RDS CAL for this kind of access?
My client need a VM with Windows Server 2022 installed. I've tell him to provide a Windows Server 2022 Standard 16 core installation but i'm confused with CAL license. The VM will start with an autologon on a user and then my customer will connect via RDP to that session (same user that starts in autologon) to manage the installed application (a SCADA automation software). Do I require a RDP CAL or a simple USER CAL? Thanks87Views0likes2CommentsRDP is locked to 30FPS for MacOS clients
I have found that even after going through the guide below, RDP connection remains locked to 30FPS if I connect to my Windows machine from my Mac. Frame rate is limited to 30 FPS in remote sessions - Windows Server | Microsoft Learn Is there any way to set the frame rate to 60FPS while using the Mac client for RDP? Thank you.65Views0likes0CommentsRDS Farm with FIDO2 Key
Hello everyone, I'm trying to install an RDS farm with fido2 (Yubikey). I think I have created the conditions. The farm is onPrem (hybrid joined), the FIDO2 key is registered in Entra. The farm works correctly with normal credentials. However, setting up the FIDO2 key is giving me a headache. If I log in directly to one of the session hosts, FIDO2 works. But if I want to log in via the session broker, as it should be. I am connected to the session broker as a host and not forwarded to the hosts. But I only found this out by chance when I added the user to the Remodesktopuser group on the broker as a test. Otherwise you just get the message: "Access to the session was denied" and the broker's event log says "Couldn't find the file" #################### redirectclipboard:i:1 redirectprinters:i:0 redirectcomports:i:1 redirectsmartcards:i:1 devicestoredirect:s:* drivestoredirect:s: session bpp:i:32 prompt for credentials on client:i:1 server port:i:3389 allow font smoothing:i:1 promptcredentialonce:i:1 gatewayusagemethod:i:2 gatewayprofileusagemethod:i:1 gatewaycredentialssource:i:4 full address:s:RDS-TEST-BR.xxxxxxxxxxxxx gatewayhostname:s:rds-test.xxxxxxxxxxxxx workspace id:s:RDS-Test-BR.xxxxxxxxxxxxx use redirection server name:i:1 loadbalanceinfo:s:tsv://MS Terminal Services Plugin.1.Test use multimon:i:1 alternate full address:s:RDS-TEST-BR.xxxxxxxxxxxxx screen mode id:i:2 desktopwidth:i:800 desktopheight:i:600 winposstr:s:0,3,0,0,800,600 compression:i:1 keyboardhook:i:2 audiocapturemode:i:0 videoplaybackmode:i:1 connection type:i:7 networkautodetect:i:1 bandwidthautodetect:i:1 displayconnectionbar:i:1 enableworkspacereconnect:i:0 disable wallpaper:i:0 allow desktop composition:i:0 disable full window drag:i:1 disable menu anims:i:1 disable themes:i:0 disable cursor setting:i:0 bitmapcachepersistenable:i:1 audiomode:i:0 redirectlocation:i:0 redirectwebauthn:i:1 redirectposdevices:i:0 autoreconnection enabled:i:1 authentication level:i:2 prompt for credentials:i:0 negotiate security layer:i:1 remoteapplicationmode:i:0 alternate shell:s: shell working directory:s: gatewaybrokeringtype:i:0 rdgiskdcproxy:i:0 kdcproxyname:s: enablerdsaadauth:i:1 username:s:yubikey@xxxxxxxxxxxxx ####################2.3KViews1like7CommentsMoving vb6 program windows via rdp with fixed resolution
Hello, we have the following problem. Environment: - Windows Server 2022 Terminal Server - VMWare 7 and 8 - Android Mobile Computer (Datalogic & Zebra) - Mobile app Remote RDP apk with resolution forced to 240x320 - VB6 programs Randomly while using the mobile computer when I open a new window or application it opens shifted relative to the others and also relative to the center. The connection does not go down you stay connected all the time. And being there fixed screen can not be moved. If I exit and re-enter everything is resolved. From what could be due VB6 programs for window management? I would like to point out that with Windows Server 2019 version it does not give any kind of problem. I ask for your help or advice404Views0likes0CommentsWindows server RDP black screen
Hello! I have 3 windows server machines in different places (with different domain, fully separated) with windows server 2019 OS, all of them does this, sometimes when I try to log in to the computer with remote desktop I only get a black screen, the CRTL+ALT+END does nothing, and after some time the connection closes. If I open the computer via idrac (DELL) nothing works I cannot move the mouse, the only solution is the hard reboot. I have a foth server with server 2016 OS which works well. I tried to update one of them to server 2022, but nothing changed the problem persists. The problem mostly occurs when I don't log out of the remote desktop, I just close the window. But it also happened that I logged out before. This is very annoying, what can cause this?15KViews0likes14CommentsRemote Desktop Android client - no permission to local files?
Hello, i have problem with opening .rdp files with RDP on my Android. It asks me for permissions to access the folder, but in the settings there is no option for that, only to set the rights to use the microphone and camera.. Can you fix it by putting the option to add permission to access local files? Thanks, Antonio1.7KViews1like3CommentsProblems with a shared local printer through remote desktop windows server 2019
We have a computer outside premises that uses a remote application installed in our server with an rdp file, they access the app and print with their local printer (not instaled in server because this is outside our intranet, they conect to our intranet via VPN etc) So, randomly the printer stops getting shared when connecting to the remote app and the only thing we can do is reboot the entire server. We still haven't located if it's related to a stopped service and which one. EDIT: i found an event around the day we were notified the printer isn't visible is related with the register Microsoft-Windows-TerminalServices-PnPDevices/Administrador and it just says "Redirection of additional supported devices is disabled by policy " I don't know if it has anything to do.859Views0likes0CommentsThe RDP service is operational, but it's not listening on port 3389
We have a Windows Server 2022 system and we are facing a significant issue with RDP freezing. The "umrdpservice" and "termservice" services are running without any problems, but when using the "netstat" command, it shows that the server is not listening on port 3389, which is the standard RDP port. I've tried various solutions, but the problem has persisted for a year, even though I regularly update the system. I've taken actions like increasing the session limit, but with no success. This issue is accompanied by an event log message: "RD Session Host Server session creation failed. The relevant status code was Only one usage of each socket address (protocol/network address/port) is normally permitted." However, this warning doesn't seem to contain specific information, as there is no second service that would be using the same port. The problem is that RDP connections can unexpectedly disconnect even up to 30 times a day, without any specific pattern in terms of timing. Please assist in finding a solution to this problem. It's worth noting that this issue is only present on Windows Server 2022, while versions 2019 and earlier do not experience these problems.812Views0likes0CommentsCustom resolution on Android Remote Desktop app only offers fixed ratios connected to device screen
I have two Android devices using nonstandard monitor display ratios (21:9, 5:3). I have previously set up profiles on one of these devices with a 16:9 ratio resolution that matches my remote session's actual physical display. This prevents a number of strange resizing issues when switching between a local and remote session. However, in the current latest (beta) version, 10.0.13.1167, I'm now limited to resolutions matching the device's ratio. Is there a way to change this to allow for picking a ratio, or at least revert to the previous functionality? If this is the wrong place for this, I apologize. I was linked here from a Remote Desktop support page, and couldn't find a better place via searching.6.1KViews2likes2Comments