Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

What "works in a browser" really means for Windows line-of-business software

Technical article
Hosting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

When a vendor or hoster says staff can use business software “in a browser”, clarify whether they mean a true web application (HTML rendered by the browser alone) or Windows software displayed through a Remote Desktop web client. The second is still a remote Windows session with a different edge protocol—not magically device-agnostic SaaS.

Why it matters

Buyers hear “browser” and assume iPad compatibility, offline resilience, and no client install. Windows LOB binaries often need keyboard shortcuts, local printers, scanners, or file paths that fail silently in a web-presented session. Marketing honesty prevents churn and unsafe workarounds (shadow IT spreadsheets).

How it works

Microsoft’s RDS role documentation states users can connect “through a supported browser by using the web client” while the compute remains on RD Session Host servers. Remote Desktop Web Access provides a portal that can “launch them through the device's native Microsoft Remote Desktop client application”—so even browser-first portals may bounce to native clients depending on configuration.

Microsoft’s web client documentation requires a PC running Windows, macOS, ChromeOS, or Linux; mobile devices aren’t supported at this time. Supported browsers include Microsoft Edge, Google Chrome, Apple Safari, and Mozilla Firefox (v55.0 and later). Clipboard support in the web client is text only via Ctrl+C/Ctrl+V; file copy/paste is not supported in the documented feature set.

A native web app runs request/response logic designed for browsers; a hosted Windows LOB app runs on Windows Server and streams display/input. Testing must cover both architecture claims separately.

Labelled example — browser honest: SaaS billing portal—works in Chrome on macOS without RDP.

Labelled example — browser-presented LOB: Decade-old Win32 ERP shown via RD web client—may work for data entry on allowed browsers only after pilot; printing uses the virtual printer / PDF path described in Microsoft’s web client article.

What to choose and why

Run a device/browser matrix pilot before you repeat “any device” language:

Test cell Record pass/fail
Allowed browsers on managed Windows Launch, login, core task
macOS on supported browsers Same task set
Android or iOS phones/tablets Use native Remote Desktop client, not the web client
Peripherals Print, scan, upload
Session drop Reconnect + unsaved work

Fail any cell → narrow the claim in contracts and staff comms.

Risks and limits

Assistive technology over remote sessions needs structured testing across client, session, and application layers—not assumptions from a sighted smoke test. No lab validation was performed for this article.

Sources

Related reading

Learning notes

  1. “Browser access” to Windows LOB is usually remote display, not a rewritten web app.
  2. RD Web may still invoke a native client under the hood.
  3. Architecture honesty belongs in sales and onboarding, not footnotes.
  4. Matrix pilots beat slogan-level compatibility.
  5. True web apps and streamed Windows apps have different limits and costs.