onscryn

An MSP playbook for clients'
legacy Windows apps.

Every managed service provider has the same client: a small business with one line-of-business Windows program that cannot be replaced, a handful of remote users, and a VPN setup that keeps generating tickets. Per-app browser access trims the support load and the risk at the same time.

By the Onscryn team · Published · 6 min read

The hosts view
Hosts: the Windows machines the apps run on. Demo organization.

Where the time goes today

Legacy applications create a steady trickle of small tickets: a new hire who needs the program installed, a remote user whose VPN will not connect, a contractor who needs temporary access, a laptop that died with local data on it. None is large. Together they are a recurring cost for you and a source of risk for the client.

A VPN also hands each remote person far more reach than they need. A user who only opens one program does not need the client's network, and each extra account is another thing to tidy up when somebody leaves.

Install the client's application once on a Windows host, in the client's office or in their cloud account. Publish it in Onscryn and give each person a link and a sign-in. The user opens a browser tab on any device and uses the program. Nothing is installed on their machine and they never join the client's network.

New starter? Send an invite. Contract over? Remove the person and access ends on their next request.

What to set up per client

A repeatable checklist keeps this quick to roll out across clients:

  • A separate organization for the client, so members, apps and recordings are isolated from your other clients.
  • One enrolled Windows host that runs their application, where it can reach what it needs, such as a local database or file share.
  • Roles for each person: someone who does the work, someone who administers, someone who only watches.
  • Data controls chosen to match the client's sensitivity: clipboard, file transfer and watermark.
  • Recording and the audit log, turned on where the client or an auditor will ask who did what.

Selling it to the client

Lead with the outcomes the client already feels: no installers for new staff, remote access that does not touch the office network, and a clear record of who opened the application. Avoid technical detail the owner does not care about.

It also gives you something to charge for that is easy to explain: managed access to the client's critical application.

Things to check

Licensing is the client's to confirm with their software vendor, since terms for running a program on a host that several people reach differ by product. Windows also needs to be licensed wherever the host runs.

Plan, host limits and how many people use apps at once all affect cost, so check the pricing page against your clients' real usage. Start with one client as a pilot and widen once the process works. The 14-day free trial needs no card.

Questions.

Yes. Each client can be its own organization with its own members, apps and settings.

Try it on
your own app.