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.
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
Opening a second location and keeping your Windows software?
Bring your worksheet, and we’ll discuss what your application would need.