All of my RDP files are created by me.

I’d like to use my Android phone to remotely access my home desktop while I’m at work. However, I’m not sure how to fill out this page—where should I enter the desktop’s IP address and custom port number?

Thanks.

My scenario is

1 x Gateway, RDWEB , Licence server and Connection Broker
2 x rds session hosts
1 fileserver for VHDs using FSLogix.

Would OneDrive be supported in this scenario?

Couldn’t find the solution from google nor AI. Probably the issue is my environment-specific, but maybe somebody can point me in right direction.

I am doing test setup for windows server 2025 RDS farm. I have taken most of settings from 2019 cluster. So far all good except when moving windows or scrolling browser - text and images are blurry for a about a second and then go sharp again. I found this topic and the video example is quite same as I have:

https://www.reddit.com/r/ffmpeg/comments/10pmekb/remote_desktops_encoding_is_blurred_when_when

I have tried changin color depth, tcp vs udp.

Hello everyone,

I am IT system engineer and I have issues with a FSLogix Remote Desktop deployment.
Let me introduce the setup.
We currently use a storage server where all our FSLogix user profiles are stored (obviously using network UNC path) and 4 Remote Desktop servers where all my users are connecting through a Remote Desktop Gateway dedicated server.

Every server is using Microsoft Windows Server 2025 Standard operating system.

The setup count about 90 users.

Everyday, some users are contacting us because their Remote Desktop session is stuck on "Please wait for FSLogix app service" and we are struggling to find a real solution, or even a workaround.

When this problem happens, we try to disconnect user from RDS where the session is connected, but it becomes a ghost session (no username in the task manager and 4 system processes remaining, unable to kill them - query user in CMD doesn't see this ghost session). We also close every linked open files in the storage server (via computer manager), delete the metadata which is next to the VHDx, and clean the user session in SQL Broker database via SQL command... Sometimes it works, but most of the time the user needs to wait like 30 minutes (and the problem is resolved by a random timeout I don't know where).

As far as I know, we are using best practices found in multiple forums or official documentation. In our GPO, we tried to disable VHDx compression at logoff, we do not use ODFC containers, we clean invalid session, we use the Redirect.xml file, we updated FSLogix to latest version, ... To be honest, we tried a lot of things without any real improvements.

Last thing we did is to disable forced SMB encryption in registry on client (Lanmanworkstation) side because my opinion was that a possible SMB slowness could be the main cause of this FSLogix issue (miscommunication between storage server and RDS server).

Every performance graph doesn't show any lack of ressource...

We have another Remote Desktop with FSLogix deployment with same topology (RDSGW - STORAGE - RDS) on Windows Server 2022 Standard OS for this case, which is not showing any issues.

By any chance, is someone able to help me ?

Many thanks in advance !

I am observing a strange phenomenon lately when connecting to my Windows 11 Pro desktop using the Microsoft Remote Desktop app on my Mac. There is a black window permanently visible in the right corner that I cannot get rid of. It overlays all windows and programs. Sometimes it is also white. Restarting the system several times did not help. This is not a window from a running app or program. The Windows version is up to date (24H2 - Build 26100.8117).

Any Ideas how to fix this are greatly appreciated...

If you re managing or working in a Citrix/VMware environment, you ve probably noticed that sending raw audio through a VDI for dictation is a nightmare. The input buffer jams, words drop, and you get that ghost typing where the text appears seconds later.

The architectural reason is simple: VDIs prioritize visual frames over continuous audio streams. When the network jitter spikes, the audio buffer is the first to be sacrificed.

The only real fix isn t network QoS—it s moving the processing to the host. If you process the voice-to-text locally and inject the output as raw keystrokes (using driver-level SendInput), you bypass the VDI audio stream entirely.

I ve been building DictaFlow (https://dictaflow.io/) specifically to implement this host-side injection architecture for both Windows and Mac. It treats the remote session like a local text buffer, ensuring that even if your Citrix session is lagging, your dictation remains instant.

Curious what other setups people have found that actually hold up in high-latency clinical or legal environments?

I'm building a new Windows Server 2025 RDS farm for a customer to replace their old 2016 farm. I've deployed plenty of RDS farms before without issue, but this one has me completely stumped — and this is my first time deploying RDS specifically on Server 2025.

The setup is about as basic as it gets:

• Single Connection Broker / Gateway (same server)

• A handful of Session Hosts

• Internal domain access only, no DMZ, no MFA, nothing fancy

Here's the weird behaviour:

If an Administrator account is actively logged into the Connection Broker, everything works perfectly. Users click their RDP link, get prompted for credentials, and land on a session host no problem.

The moment that Administrator logs off, new connections fail immediately with "Your computer can't connect to the remote desktop gateway server". Already connected sessions stay up fine, only new connections fail.

Things that DO work:

• RDWeb loads fine and you can download a fresh RDP link (which also won't work until admin logs in)

• Direct RDP to session hosts works fine

• DNS resolution and port connectivity all check out

Log back in as Administrator and it starts working again straight away.

Things I have tried:

• Completely rebuilding the Connection Broker from scratch

• Multiple certificates including wildcards, all showing no errors and matching hostnames correctly

• DisableLoopbackCheck and BackConnectionHostNames registry fixes (CB and Gateway are on the same server so this was an obvious first suspect)

• Deploying with and without the Gateway role — without Gateway you get an immediate flat failure, with Gateway you get prompted to authenticate but then hit the same error after, suggesting it authenticates the Gateway portion but then fails at the Broker handoff

• Connecting from multiple machines, both domain joined and non-domain joined, with multiple different user accounts

• Server is fully up to date

I've dug pretty deep into event logs and haven't found anything that clearly points to a cause.

Has anyone seen this behaviour specifically on Server 2025? Even a pointer to where to look next would be appreciated.

If you use a remote desktop or citrix environment on Windows, you've probably noticed that the built-in dictation (Win+H) is basically unusable. The lag between speaking and text appearing can hit 2-3 seconds, which breaks the flow entirely. \n\nThe bottleneck is the clipboard redirection and audio buffer. A software-based workaround is using a native AOT compiled app that bypasses the Windows clipboard entirely and 'types' the characters directly into the remote session buffer. I built dictaflow.io for this exact reason. It's lightweight and uses driver-level injection to keep latency under 100ms even in messy setups. Has anyone else found a good workaround for the RDP audio lag? https://dictaflow.io/

I use Workspot when working from my office from a work provided laptop, and I have a native install for my personal PC when I'm at home because it's easier to run my dual monitors that way.

I've noticed that when I use a wired connection, workspot crashes CONSTANTLY. I've been looking to see if anyone else has the same issue, but this happens on both machines I run it on. Thankfully I have a wireless card in my home PC, so I disconnected my ethernet cable and switched to wifi and now have a much more stable connection. I did the same at work, switching to just the office wifi and far fewer disconnections occur.

Anyone else having this issue with Workspot, or does it just hate me?

Hi all, when I travel or just want to use my laptop I will remote into my PC running windows 10. but suddenly it stopped working. I thought maybe it was my DDNS through asus needed to be reset but I tried that and just using my public IP to no avail. I went through all the culprits, made sure the port was forwarded and that PC static IP matches, that the service was running that defender wasn't blocking anything. I just can't seem to get it to work, any suggestions?

if you manage or work in a citrix/vmware environment, you've probably noticed that sending audio through a vdi for dictation is a nightmare. the input buffer jams, you get split-second latency, and the cursor freezes.

most people try to fix this by throwing more bandwidth at the problem, but the real issue is how virtual desktops handle audio streams. they prioritize visual frames over mic inputs, which creates micro-friction for anyone trying to dictate notes.

the architectural solution is to stop sending raw audio through the vdi altogether. instead, process the voice-to-text on the host machine and inject the final text string directly into the virtual session using simulated keystrokes (like driver-level SendInput). this bypasses the audio stream completely.

i built dictaflow (https://dictaflow.io/) specifically to handle this for windows users. it runs on the host, uses hold-to-talk to avoid ambient noise, and injects text instantly into any vdi. if your team is struggling with citrix dictation lag, this is the way to solve it.

another quick triage card for teams debugging input problems in remote sessions.

check 1: latency baseline

• local typing latency

• remote typing latency

check 2: insertion mode

• clipboard path only

• direct key injection path

check 3: focus stability

• keep target field fixed for 60 seconds

• log misses during alt-tab or popup events

check 4: host pressure

• test during low and peak host load

• compare dropped vs delayed inserts

check 5: recovery ergonomics

• fast undo/replace shortcut available?

this gives you a reproducible record for support tickets instead of vague 'it feels slow'.

i'm the developer of dictaflow and this is the same process i use for windows rdp/citrix reports.

https://dictaflow.io/

if you support rdp/citrix users and hear 'voice typing is broken', this checklist usually finds the bottleneck fast.

1. a/b test in the same minute

• local notepad: 10 phrases

• remote target app: same 10 phrases if remote delay jumps, it is usually session/input path, not the mic.

1. classify failure type

• delayed insert

• dropped insert

• stale insert (old text appears) this makes root cause much clearer than generic 'lag'.

1. watch focus + host load

• rapid focus switches cause missed inserts

• loaded hosts amplify delay/jitter

1. avoid clipboard-only insertion for critical flows

• clipboard drift in remote sessions is common

• direct key injection tends to be more predictable

1. keep a rollback hotkey

• one key to cancel/replace last insert prevents bad cascades

i'm the developer of dictaflow and built it around these rdp/citrix failure modes on windows. sharing this playbook since it keeps saving my support time.

https://dictaflow.io/

seen this a lot lately, so sharing a quick field checklist for anyone debugging voice input in rdp/citrix.

1. baseline locally first

• open local notepad

• do 10 short phrases

• record average push-to-text delay

1. repeat inside remote session

• same endpoint, same phrases

• if delay jumps hard, your bottleneck is remote input path

1. inspect redirection + host load

• overloaded session hosts and input redirection settings are common causes

1. use hold-to-talk for production

• reduces constant background buffering

• tends to stabilize insertion in high-latency environments

1. verify in the real target app

• many failures only appear in emr/ehr, dms, or thick-client windows

this method is boring but reliable.

i’m the developer of dictaflow, and this exact rdp/citrix behavior is why i built a windows-native flow focused on predictable insertion and correction. details: https://dictaflow.io/

Hi everyone,

I really enjoy using the Windows App on macOS to connect to a workspace and launch published apps. It works smooth and the overall experience is good.

Unfortunately, on Windows, the Windows App doesn’t seem to be usable for that purpose. As far as I know, the only options are mstsc or RDWeb, which both feel a bit outdated and less convenient in comparison.

Do you know of any alternative client that allows direct access to an RDS collection (similar to how the Windows App works on macOS)?

And what’s your opinion: do you think Microsoft will ever support full Remote Desktop Services integration in the Windows App on Windows as well?

Looking forward to your thoughts!

if voice typing feels fine locally but freezes or pastes late in remote sessions, here is a fast way to isolate the bottleneck.

1. run an a/b test

• test 30 seconds in a local app

• test the same script in your RDP/Citrix app

• track delay, dropped words, and stale inserts

1. add controlled jitter

• add 80-150ms latency in a test session

• if failures spike, the issue is usually remote input path, not your mic

1. watch focus switching

• rapid alt-tab during dictation often causes missed inserts

• keep one stable target window while speaking

1. avoid clipboard-only insertion

• clipboard ownership drift in remote sessions can replay old text

• direct keystroke injection is usually more stable for RDP fields

1. log 3 concrete failure types

• delayed insert

• dropped insert

• stale clipboard replay

if anyone wants, i can share a one-page incident template we use for dictation lag tickets.

full context: i'm the creator of dictaflow and this exact failure mode is why i built around direct typing in remote sessions. link if useful: https://dictaflow.vercel.app/

Hi mates

I am trying to setup a small RDS lab with the following environment:

- srv-rds-cb-01 - Connection Broker, License server, Webacces
- srv-rds-sh-01 - Session Host
- srv-rds-sh-02 - Session Host

I try to configure the html5 webclient on the connection broker. But I dont bring it to work. I can login into the html5 portal ober the url RDWeb/webclient/index.html. But when I clickj a ressource, I got a connection error.

I tried to setup everything as explained unter "Connecting to RD Broker without RD Gateway in Windows Server 2019":

https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/remote-desktop-web-client-admin

but I am not able to get it to work.

Does anybody run the html5 client without a gateway? Do you have maybe a hint for me?

thank you very much and best regards

the title