Guides / 8 min read
Windows software licensing when it runs in the cloud.
When a program runs on a computer you do not own, two sets of licensing rules still apply: Microsoft's for Windows itself, and the program vendor's for the software on top. Most trouble comes from assuming neither of them cares where the program runs. Some do. A little reading up front is far cheaper than finding out later.
Two licences, not one
Every Windows program sits on top of Windows. Microsoft licenses Windows, and the vendor licenses their program. Using a program remotely means that machine needs a valid Windows licence for how it is used, and you or your provider also need the right to run the vendor's software there.
A service that runs programs for you handles the first part as part of what it provides. The second part, your program's own licence, usually stays with you.
How program licences usually work
You will meet a handful of models. It helps to know which one you have.
- Per computer: the licence is tied to one machine. Moving it, or running it on a different one, may not be allowed without the vendor's agreement.
- Per person or named user: it follows you, so where the program runs matters less, but sharing it with others is usually not allowed.
- Concurrent: a set number of people can use it at once, often managed by a licence server.
- Subscription: you pay regularly, and the terms often say plainly whether hosted or remote use is permitted.
The questions worth asking the vendor
Whether the licence allows the program to run on a machine hosted by someone else. Whether it must be tied to hardware that I own. Whether activation will work on a remote machine. Whether there is an edition meant for remote or shared use.
Vendors answer these questions more often than people expect, and some have a clear policy. Get the answer in writing and keep it with your invoice.
Hardware keys and activation
Some software ties itself to a USB dongle or to the details of the machine it was activated on. A dongle in your own computer does not travel to a remote one by itself. Some vendors offer a software licence or a network version for exactly this reason.
If your program uses a hardware key, find out first. It is one of the most common reasons a program that otherwise streams well cannot be used remotely.
What we can and cannot tell you
We cannot interpret another company's licence, and nobody on the outside should. What we can say is that FarDesktop runs your program on a Windows machine, and that the program's own licence is between you and its vendor. If you are unsure, ask them, then try your program on a short trial.
Written with accountants in mind.
Questions people ask.
Does Windows come with the machine?
The Windows machine your program runs on is part of the service. Your own program licence is separate and stays with you.
Can I use my existing licence?
Often yes, but not always. It depends on the vendor's terms, so check before you move it.
What if the vendor says no?
Ask whether another edition or a different licence type allows it. If not, a local setup may be the only compliant option.
Keep reading
8 min read
A second computer for one Windows program?
A second PC for one program can cost more than it looks. How to count the real cost, the alternatives, and when buying the machine still makes sense.
Read8 min read
Working with a client's Windows-only tools
A client needs you in their Windows software and you work on a Mac or tablet. A checklist for access, licences, files, security and handover.
Read9 min read
Keeping client files safe on a remote PC
Using a remote Windows machine can keep client data off your laptop. What actually protects files, what does not, and the habits that make the difference.
Read