Opening a Second Location With Your Existing Windows App

A second location means the same work now happens in two places, and your software has to follow it.

Multi location Windows application hosting can give both sites access to a central, managed application environment and shared records, subject to the application’s design, licensing, and testing. Microsoft’s multiple user guidelines cover applications that run for several users at once in Remote Desktop Services environments. This guide helps you plan the parts you control: the workflows, the records, the people, and the handoffs between sites.

1
LOCATION A
Starts the job
2
LOCATION B
Completes the job after the handoff
3
THE APPROVER
Signs it off

Step 1: Map Who Starts, Completes, and Approves

For each task, write down which location starts it, which completes it, and who approves it. A sales order might start at one site, ship from the other, and need a manager’s approval for a discount. Tasks that cross sites are where problems appear, so list those first, because they are your shared business workflows. Then ask what each person needs to see to do their part, and who is waiting on them.

Step 2: Decide Which Records Are Shared

Some records belong to both sites, such as customers, price lists, and open jobs. Others belong to one site, such as a local schedule. Decide which is which, and name who may change each shared record. Two people may try to open or update the same record at once. A named owner sets the rules. Confirm how the application enforces permissions and handles conflicting edits, then test two users attempting to update the same sample record. Write the rule in one sentence per record type, such as: both sites can view customer records, and the main office owns changes to the price list.

Step 3: List Each Site’s Users, Connection, and Devices

For each location, list who will use the application, how many people work at once, and what they connect with. The number at once matters, because your license and the host’s sizing may depend on it. Then check three things.

  • Connection. Each site needs a connection that suits the work, and a backup if work can’t stop. Our internet outage plan covers the fallback. Response times depend on each site’s connection and the application, so measure them in a test, and don’t assume both sites will match.
  • Devices. Note the printers, scanners, and signature pads at each site. Scanners need their own test, as our guide to scanner redirection in a hosted application explains.
  • Access method. Staff may connect with a Windows client or a browser, and features differ between them, so test the method each site will use.

Step 4: Agree Licensing and Requirements, Then Test a Handoff

A second location can change your license, since terms may count users, concurrent users, or sites. Ask your vendor in writing whether more users or another site need additional licenses, and ask your host what it needs to confirm for your application. Our guide to bring your own license hosting has an email template.

Then test a complete handoff before the new site opens. Use test data, each site’s intended devices and accounts, and representative simultaneous usage, and run one job from start to finish: start it at Location A, complete it at Location B, and have the approver sign it off. Confirm users can perform approved actions and cannot perform restricted actions, and that printing and any scanning work at both sites. Record acceptable response times, the results, and a named approver. Unresolved critical failures should block opening day approval. For second office planning, also name one contact at each site for opening day.

The Location, Task, User, and Handoff Worksheet

Fill in one row for each task, and add rows as you need them.

Location Task Users Handoff
       
       
       
       

Where CloudTop SaaS Fits

We host Windows applications on Azure with Parallels RAS, and service scope is specific to your application. For multi location Windows application hosting and legacy app hosting across two sites, bring your worksheet and the application’s name, and we’ll discuss what your application and license would need. Our compatibility checklist is the first screen for the application.

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

FAQ

Can multi location Windows application hosting serve two sites?

It can work, but it depends on the application’s license, its design for several users, and a test. Plan the workflows and records first, then confirm the rest with your vendor and host.

Will the second location perform the same as the first?

Performance can differ between sites. Test each under its expected working conditions.

Do I need more licenses for a second location?

It depends on your vendor’s terms, which may count users, concurrent users, or sites. Ask your vendor in writing before the new site opens.

Opening a second location and keeping your Windows software?

Bring your worksheet, and we’ll discuss what your application would need.

Discuss your second location

Need Old Job Records? Plan Access to Your Legacy Windows App

Somewhere in your office, an old Windows application still holds job history your team needs now and then.

Daily work has moved to newer software. A customer still calls about an old job, and someone has to find it. Legacy application access for historical records means planning for that call before the old server fails. This guide helps you decide what to keep reachable and how people will get to it. It also covers when managed legacy app hosting makes sense.

Step 1: List What Staff Still Need

Start with the questions people ask, because the database can’t tell you what staff still need. Ask the team which old job details and reports they still pull up, and how many times a month, then write each one down: the job number, customer, dates, quoted and actual costs, notes, attachments, and any report such as a job cost summary. A short list of real requests shows how much access you need, and it’s the start of your application archive planning.

Step 2: Compare Exports With Lookups in the Application

You can reach historical job records in two ways: export them, or look them up in the application.

Option Works well when Watch for
Exports Requests are predictable and the answers fit on a page or a spreadsheet. Missing attachments, reports that don’t match the original layout, totals that differ, and questions you didn’t plan for.
Lookups in the application Requests vary, or staff need the original screens and reports. The application has to keep running somewhere, with a license, a Windows version it can run on, and approved users.

Many offices use both, because exports cover predictable requests while application access handles the rest. So test any export before you trust it, by opening a few exported jobs and comparing them with the application.

Step 3: Name Approved Users, a Record Owner, and the Steps

Decide three things in writing. First, list the approved users by name and review the list on a schedule you choose. Second, name one record owner who decides who may look, answers questions, and removes people who leave. Third, write the retrieval steps so a new employee can find a job without calling the one person who remembers how.

Don’t assume the application limits what people can change, so ask your vendor whether it offers a role that can view without changing records, and test it.

Step 4: Understand Licensing, Support, and Access for Hosting

Managed legacy app hosting keeps the application running in a hosted environment, so approved users sign in when they need a record. Four things decide whether that works for your application.

  • Permission and licenses. Your vendor has to permit hosting, and requirements vary by vendor and license. Our guide to bring your own license hosting has an email template.
  • Windows support status. Confirm application compatibility and the Windows version’s support status. Hosting does not restore vendor support or resolve an unsupported operating system.
  • Keys and connected devices. A hardware key depends on your vendor’s terms, as our guide to USB dongle cloud hosting explains, and any printer or scanner needs a test.
  • Access. Decide who signs in, how, and who removes a user who leaves.

Each of these is specific to your application, so the answer for one program doesn’t carry over to another.

Step 5: Retrieve One Sample Job

Before you commit to a route, retrieve one real historical job record from start to finish, then compare it against a reference. Run this test through the proposed export or hosted environment, using an approved user’s account.

SAMPLE JOB RETRIEVAL CHECKLIST

Pick a real old job and write down what you need to see.
Retrieve it using the written steps and nothing else.
Compare details, totals, notes, and attachments with the original application or a verified reference captured before migration.
Open the report staff use most, and check its layout.
Have a second approved user repeat the steps.
Record the problems, the time it took, and who owns the fixes.

If the process is slow or unclear, fix it now, because you don’t want to find out when a record is urgent. Keep recoverable copies of the data, attachments, and application dependencies, and test that the chosen access route can be restored. Retrieving a job today doesn’t prove you can recover access later, and Microsoft’s disaster recovery guidance calls for tested plans that cover all components and the system as a whole.

Where CloudTop SaaS Fits

We host Windows applications on Azure with Parallels RAS, but whether we can host your old application depends on the application, its license, and a test, so compatibility and scope are specific to it. For legacy application access for historical records, bring the application’s name, its version, and your list from Step 1, because those decide what we can assess. If the old server runs Windows Server 2016, our Windows Server 2016 migration guide shows how to plan the move, while our compatibility checklist shows how to screen the application.

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

FAQ

How do I keep legacy application access for historical records after replacing my office server?

List what staff still need, test whether exports cover it, and name the approved users and a record owner, and then, if lookups in the application remain useful, discuss hosting it.

Are exports enough for historical job records?

They can be, but check an export for missing attachments, changed layouts, and totals that don’t match before you rely on it.

Does hosting an old application restore vendor support?

No, because hosting changes where the application runs, while vendor support depends on the vendor, and hosting doesn’t resolve an unsupported operating system.

Still need old job records from a Windows application?

Bring the application and your Step 1 list, and we’ll discuss what access to it would involve.

Discuss historical application access

A Hosted Demo for Your Windows Software: What to Plan

A prospect who has to install your software before seeing it may not see it at all.

A hosted demo for Windows software puts the application in front of the buyer without installing your application locally, so the demo follows the sales conversation instead of the setup steps. Browser access can avoid a client installation, while the Parallels Windows client requires one, so decide which access method the demo uses. Whether your product suits hosting is a separate question that needs vendor confirmation and a test, so settle that first. This guide covers what to plan once it does.

BEFORE

Choose the workflow, the access model, the sample data, and an owner.

DURING

Show one buyer workflow, with a named person ready for access problems.

AFTER

Reset the environment, close the access, and hand off to the next step.

1. Choose the Buyer Workflow

For an ISV software demo, start with the question your buyer needs answered, not with your feature list. Pick one or two workflows that answer it, such as entering an order or producing a month end report, and build the demo around those. Everything else in the environment is a distraction, so leave out administrator setup and unfinished modules. A useful test: could the buyer explain the value to a colleague afterward?

2. Compare Guided Sessions With Prospect Access

A guided session means you drive the cloud demo environment. Time limited access means the prospect signs in alone for a set period. Each fits a different sales stage, and many vendors use both: a guided session first, then access for buyers who want more.

  Guided session Time limited access
Control of the story You decide what the buyer sees. The buyer explores on their own.
Support load Lower, since you’re present. Higher, because access questions arrive later.
Preparation A reset before each session. Separate access, an expiry that ends active sessions, and a reset.
Fits best First conversations and first impressions. A buyer who wants hands on time before deciding.

3. Plan Sample Data, Access Separation, and a Reset

Sample data should look real and contain none. Invent customers, orders, and amounts, and make sure the data supports the workflow you chose, including one awkward case that shows how your product copes.

Access separation keeps one prospect’s data away from another’s, and separate logins alone don’t establish it. Give each prospect individual access, configure permissions or isolated copies to separate their data, and test that neither prospect can open the other’s records or files. Microsoft’s guidance on identity in multitenant solutions distinguishes verifying identity from enforcing access permissions. Our guide to defining a hosted edition pilot covers customer data separation in more depth.

A reset process returns the environment to a known state, for example by restoring a saved copy before each session. Decide who triggers it and how long it takes, then run the demo twice in a row to confirm the second run matches the first, before a real prospect depends on it.

Production separation keeps the demo away from real systems. Use test destinations for email, payments, exports, and integrations, and confirm that demo actions can’t change production data. At expiry, end active sessions as well as blocking new sign ins, and make sure a reset can’t overwrite another prospect’s active trial.

4. Decide Who Prepares It and Who Fixes Access

Name one person who prepares each demo, and name who answers when a prospect can’t sign in. A sales engineer can own the first, while the second needs a response path, so a stuck prospect doesn’t wait a day for an answer. Agree what counts as an access problem, and who handles each. If a hosting partner runs the environment, agree who contacts whom, as in our ISV hosting support responsibilities map.

5. Map the Handoff to the Next Sales Step

A demo ends, but the sale continues. Decide in advance what happens afterward: who follows up, what the prospect receives, when their access closes, and what the next step is, whether a quote, a longer trial, or a pilot. Record which workflows the prospect tried and what they asked, because that record shapes the follow up. Keep the message specific, mention what they tried, and offer one clear next step. For a buyer ready to go further, our guide to defining a hosted edition pilot explains what a pilot should prove.

Where CloudTop SaaS Fits

We host Windows applications on Azure with Parallels RAS. A hosted demo for Windows software is one use of that kind of environment. Discuss demo requirements with us so we can assess compatibility, scope, and pricing. Compatibility for your product comes first, and for legacy app hosting, our compatibility checklist shows how to screen it.

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

FAQ

What is a hosted demo for Windows software?

It’s a copy of your application running in a hosted environment, so a prospect sees it without installing your application locally. Browser access can avoid a client installation, while the Parallels Windows client requires one. You prepare the sample data and decide whether you guide the session or give time limited access.

Should each prospect get separate access?

Yes, when prospects explore on their own. Give each prospect individual access, configure permissions or isolated copies to separate their data, and test that neither prospect can open the other’s records or files. Separate logins alone don’t establish isolation, and access should end when the demo window ends, including active sessions.

Can my product be hosted for a demo?

That depends on your product, your licensing, and a test, so confirm it before you plan the demo. Screening your application against a checklist is the first step.

Planning a hosted demo for your Windows software?

Software vendors are invited to discuss whether a hosted demo fits the way you sell.

Discuss a hosted demo fit

USB License Keys: Check the Hosted-App Licensing Path

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

AI Enablement