RemoteApp file transfer without drive redirection
RemoteApp publishes a single application — not a desktop — so users can't drag files out, and drive redirection is often disabled by policy. TwinPane gives RemoteApp users a fast, policy-friendly way to open files locally and move them between their endpoint and the session host.
Why RemoteApp file workflows are uniquely painful
RemoteApp shows the user a single published application, seamlessly windowed on their local PC — which is great until they need to actually move a file in or out of that app.
No remote desktop to drop on
Users only see the published window, so the standard “drag to the desktop” workflow simply doesn't exist.
Drive redirection is policy-blocked
Many compliance frameworks require drive redirection to be off. RemoteApp users then have no Save-to-local path at all.
Open/save dialogs feel alien
The RemoteApp's open/save dialog shows the session host's drives, not the user's actual local folders.
One channel, every published app
TwinPane runs as a per-session service on the RemoteApp host and a lightweight client on the user's endpoint. They pair automatically and stream files over a dedicated, encrypted transport — no RDP drive redirection involved.
Local open from inside any RemoteApp
Files surfaced by the RemoteApp can be sent to the local PC with one click and opened in the user's native applications.
Mirror local folders into the session
Even without a desktop, the RemoteApp's open/save dialog can browse the user's real local Desktop, Documents, and Downloads.
Drive redirection stays off
TwinPane does not register as an RDP drive channel, so existing GPO and Intune policies that disable redirection remain enforced.
Same UX everywhere
RemoteApp users get the same file-access experience as full-desktop AVD, RDS, and Citrix users — one product, four stacks.
TwinPane vs. RDP drive redirection for RemoteApp
A side-by-side look at how they compare for the RemoteApp use case specifically. See the full TwinPane vs RDP drive redirection comparison →
| Capability | RDP drive redirection | TwinPane |
|---|---|---|
| Open RemoteApp file in local app | Save & re-open via mapped drive | One double-click |
| Works without a remote desktop | Awkward without desktop | Designed for published apps |
| Compatible with redirection-disabled GPO | No | Yes |
| Performance under WAN | Slow on large files | Compressed transport |
| Consistency with AVD / RDS / Citrix | Different per stack | One product, same UX |
| Firewall changes | None (RDP) | None — outbound only |
Roll it out for RemoteApp in three steps
The same workflow scales from a single RemoteApp publisher to a fleet of session hosts behind a connection broker.
- 01
Install on the RemoteApp host
Drop the TwinPane Server MSI on the session host or bake it into your image. It registers per-session automatically.
- 02
Push the client
Distribute the Client MSI via Intune, SCCM, or Group Policy. It pairs the first time the user launches the published app.
- 03
Activate centrally
Push the license through registry policy. Each activated client device uses one TwinPane license.
Recommended reading for RemoteApp admins
Practical references for shipping TwinPane on Microsoft RemoteApp publishers.
Group Policy & registry defaults
Lock down TwinPane behavior on RemoteApp publishers using ADMX templates and registry policy.
Intune Win32 deployment
Push the TwinPane client to user devices via Intune as a Win32 app, with detection rules included.
Silent install: client & server
Unattended MSI install switches for both the RemoteApp host and the local Windows client.
Troubleshooting: client / server pairing
Common pairing issues and how to verify the TwinPane channel is established for a RemoteApp user.
Frequently asked questions
What RemoteApp admins typically ask before rolling TwinPane out.
Can RemoteApp users transfer files without drive redirection?+
Yes. TwinPane provides a dedicated transfer channel that lets RemoteApp users open files locally and mirror folders without any RDP drive redirection enabled.
Is this approach policy-friendly for locked-down estates?+
Yes. Because TwinPane does not depend on drive redirection group policies, IT teams can keep redirection disabled enterprise-wide while still giving users seamless file workflows.
Does TwinPane behave consistently across AVD, RDS, RemoteApp and XenApp?+
Yes. The same client and server installers cover AVD, RDS session hosts, RemoteApp publishers and Citrix XenApp, so users get one consistent file-access experience.
Will it work for RemoteApp without a published desktop?+
Yes. TwinPane is built for the published-app case where the user never sees the remote desktop — files in the RemoteApp's open/save dialog can be opened locally with one double-click.
Does it require opening additional firewall ports?+
TwinPane uses the same outbound network paths as a normal RDP/RemoteApp session. No new inbound ports are required on the session host or the local PC.