For software protected by a USB key, the key is part of the license, so moving the app means asking what that license allows.

USB dongle cloud hosting can work, but your software vendor’s terms and a test decide it, and USB redirection alone doesn’t establish either one. This guide walks the path in order, from the key itself to a lab test, so you know what you’ve verified and what’s still open.

The Permission Ladder: Five Rungs From Key to Test

Each rung depends on the one below it, so work upward in order.

1. Name the key. Record the application, edition, key family, and key type.
2. Read the license terms. Look at network use, concurrency, remote desktop, and virtual machines.
3. Get permission in writing. Ask your vendor about hosting, remote sessions, and users.
4. Choose a key path. Pick how the license will reach the hosted app.
5. Run the lab test. Record what passed and what’s still unresolved.

Step 1: Pin Down One App, Edition, and Key Type

Start with one real application and its software license key, because the answer for one product says little about another.

Record this Why it matters
Application, edition, version Terms and key support can differ between editions and releases.
Key family and model Documentation is specific to a family. The evidence in this article covers Thales Sentinel keys.
Key type A USB hardware key, a software key, or a network key behave in different ways.
License type Standalone or network, and how many seats you own.
Vendor contact The person who can confirm terms in writing.

Step 2: Read What the Key Is Allowed to Do

Your vendor sets these limits, not your hosting provider, because Thales documents that software vendors define license terms for each feature, including concurrency, network use, remote desktop access, and virtual machine use. The table below shows what a refusal can look like, using descriptions from Thales’ Sentinel Licensing API status codes. These are API status descriptions, so your application may show different wording.

What fails Thales API status description What it suggests
Remote desktop use “An application is running on a remote desktop (terminal server).” The license may not allow remote sessions.
Virtual machines “The license does not allow running the application on a virtual machine.” Ask the vendor for a license that allows them.
Concurrent users “Too many concurrent user sessions are connected.” Ask the vendor whether an authorized license update or additional seats are required.
USB sharing “The protection key is not accessible due to a USB sharing violation.” Review the key path.

Thales says the virtual machine option applies to products locked to a Sentinel software (SL) key, so how a USB hardware key behaves in a virtual machine is a question for your vendor.

Step 3: Get Permission in Writing

Send your vendor four questions, then keep the answers.

  1. Will the license let a third party host the application?
  2. Is use through remote desktop sessions permitted?
  3. Can the application run on virtual machines?
  4. How many users can run it at once, and is that counted by login, process, or station?

Our guide to bring your own license hosting has an email template for the first question. Remote desktop licensing is a separate matter, because Microsoft describes per user and per device client access licenses, plus per user Subscriber Access Licenses for service providers and ISVs. Ask your hosting provider which Microsoft remote access licenses are included in the service and whether you need any additional licenses. These are separate from your application vendor’s USB key and software license requirements.

Why USB Redirection Alone Doesn’t Settle It

Redirection moves a device into a remote session, but it doesn’t grant any permission. For USB devices without a high level redirection method, Microsoft’s page on redirection over the Remote Desktop Protocol describes opaque low level USB redirection, which forwards raw USB requests and needs the device’s driver in the remote session.

Microsoft calls it a fallback whose performance, reliability, and feature support aren’t guaranteed by default, and it says a redirected USB peripheral can be used in one remote session at a time and not on the local device while a session is using it. Its table of supported peripherals doesn’t name license keys, so test any key you plan to redirect.

Parallels adds a client limit, because its RAS 18 administrator’s guide says the RemoteFX USB redirection setting applies to Parallels Client for Windows and no other client, and that the client relies on the Windows feature being enabled. Microsoft’s page covers the Remote Desktop Protocol in general, so confirm the requirements for your deployed Parallels RAS version.

Step 4: Choose a Key Path

USB dongle cloud hosting paths fall into three groups, so each one needs its own confirmation.

Path When it fits Confirm first
A network license or software key from the vendor The vendor offers one for your product. The terms, the cost, and the seat count.
A network USB server Thales says a standalone Sentinel HL key has to be plugged into the machine running the app as a rule, but over the network USB solutions can present it to a physical or virtual machine. Vendor permission, the hardware, and who hosts it.
Generic USB redirection When the vendor approves and a test shows the key works through low level USB redirection, with one remote session at a time. A test, written approval, and the requirements for your RAS version.

For the network USB path, Thales recommends specific devices from SEH Technology that it tested with Sentinel HL keys, but that recommendation covers Sentinel keys alone and says nothing about your vendor’s permission.

Step 5: Run a Lab Test and Record What Is Unresolved

  1. Use a test environment with an equivalent key type and license configuration, because a software test license can bypass restrictions that a production USB key enforces. If you can’t get an equivalent, record what the substitute can’t prove.
  2. Launch the app from a hosted session and check that it finds its license.
  3. Open two sessions at once, within the entitlements your vendor authorizes and no further, to test concurrency and sharing.
  4. Disconnect and reconnect a session, then run the app again.
  5. Record each failure against the vendor’s message.

THE TESTED CONFIGURATION

Write down what passed: the application and version, the key family and type, the key path, the Parallels RAS version, the client, and the settings that mattered. Passing a test establishes what you validated, so record your vendor’s written permission as its own entry, note what any substitute license can’t prove, and list what remains unresolved, such as other key families or other client types.

If your vendor says no, ask whether it sells a hosted edition or a network license, because keeping the software on vendor supported local infrastructure may remain a valid choice when hosting is prohibited. Our lift and shift decision framework helps you weigh that against replacing it.

Where CloudTop SaaS Fits

We host Windows applications on Azure with Parallels RAS, and on the discovery call we check how a key is enforced before we commit. We don’t promise that a particular key will work until your vendor confirms permission and a test passes, so bring the key type and your answers to Step 3. For legacy app hosting, our compatibility checklist covers the wider fit, and our guide to scanner redirection in a hosted application shows the same test first approach for another peripheral.

CloudTop SaaS is a CloudTop Office company, hosting Windows business software since 2000 through the parent brand.

FAQ

Does USB dongle cloud hosting work with my application?

It can in some cases, but your software vendor’s license terms, the key type, and a lab test decide it, so confirm permission in writing before you move.

Does USB redirection make my dongle work in a hosted session?

Not on its own, because Microsoft calls low level USB redirection a fallback with no guaranteed performance or reliability, a redirected device serves one remote session at a time, and a redirected key still needs your vendor’s permission for remote sessions, virtual machines, and the number of users.

What if my software vendor says no?

Ask whether the vendor offers a hosted edition, a network license, or a software key. Otherwise, weigh keeping it on vendor supported local infrastructure against replacing it.

Do I need Microsoft remote desktop licenses as well?

Ask your hosting provider which Microsoft remote access licenses are included in the service and whether you need any additional licenses. Microsoft describes per user and per device client access licenses, while service providers and ISVs can choose per user Subscriber Access Licenses. These are separate from your application vendor’s USB key and software license requirements.

Want your key type and vendor terms checked before you move?

A software fit review covers your application, your key type, and what your vendor has confirmed, so the licensing path is verified first.

Scope a software fit review