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

Upgrading a Hosted Windows App: Plan the Change

An upgrade that works on the vendor’s test machine can still surprise you on yours.

Hosted application upgrade planning is how you avoid that surprise. It means agreeing who changes what, how you’ll check the result, and what you’ll do if the change goes wrong, before anyone touches the live system. This guide covers keeping a useful legacy application in service through an upgrade, part of managed legacy app hosting, so the worksheet at the end holds the plan.

1
Reason
2
Roles
3
Safety net
4
Window
5
Sign off

Step 1: Record the Reason, the Target Version, and the Dependencies

Write down why you’re upgrading, such as a fix, a feature, or vendor support, and which version you’re moving to. If nothing forces the change, compare the risks of upgrading now with the security, support, and compatibility risks of delaying, because Microsoft’s safe deployment guidance notes that all deployments carry risk and that failing to update brings risks of its own. Then list what the application depends on: its database, the Windows version, integrations, custom reports, scheduled overnight jobs, add ons, and any license key. Ask your vendor to confirm in writing which Windows and database versions the target version supports.

Step 2: Agree Vendor, Host, and Customer Tasks

Three parties share an upgrade, but each assumes another one is handling the gaps. As an example, the vendor supplies the upgrade package, the host runs the environment, and you test the workflows, approve the result, and tell your staff. Treat that split as a starting point to agree under your support contracts, so name who installs the upgrade, who runs database conversions, and who executes recovery. Then agree how the parties contact each other, and name one approver who can say go or stop. A new version can change your license terms, as our guide to bring your own license hosting explains.

Step 3: Plan Backups, Rollback Limits, and Testing

Take a backup before the change, then rehearse restoring it before the change window. Our hosted application data migration checklist shows how to run a restore test. Record what the restore test demonstrated and which recovery limits remain.

Then define both recovery options and a decision deadline. Rolling back undoes the change and returns to the last known working version, while rolling forward fixes the problem in the new version. Microsoft’s guidance describes both, but flags database and other stateful changes as complex to roll back. For each option, agree how changes made after the backup would be preserved or reconciled, since that’s where data gets lost.

Run your application testing on a copy first, so you find problems without touching live data, and keep copied environment tests connected to test destinations. Production checks involving invoices, orders, or emails need an agreed method, so a test doesn’t create a real business transaction. Use real workflows, reports, and scheduled jobs, so you can keep a software upgrade checklist of what passed.

Step 4: Schedule the Downtime and Check Daily Workflows

Pick a window when work is light, tell staff what to expect, and agree who is on call. During the window, pause user writes and integrations, finish active jobs or stop them in a controlled way, and take the final consistent backup before upgrading. Complete the agreed application testing checks before reopening access, so have an approved user run the daily workflows, such as entering an order and printing. Compare the results with the old version using the same test data, then keep watching for the first few days.

The Change Worksheet

Use this change worksheet as your software upgrade checklist. Fill in an owner and an acceptance test for each line, and don’t schedule the window until each line has both.

Item Owner Acceptance
Business reason and target version   The approver agrees the reason and the version in writing.
Dependencies list   The vendor confirms each supported version in writing.
Vendor, host, and customer tasks   Each task, including install, database conversion, and recovery, has a name.
Backup and restore rehearsal   A restored copy runs, and the recovery limits that remain are recorded.
Roll back or fix forward, with a deadline   The approver knows what each option would lose and when the choice is made.
Test on a copy   Workflows, reports, and jobs pass on the copy.
Downtime window, write pause, and notice   Writes pause, active jobs are handled, and staff have the date and a contact.
Daily workflow check and sign off   Each daily workflow passes under an approved user, and the approver signs.

Where CloudTop SaaS Fits

We host Windows applications on Azure with Parallels RAS, but an upgrade changes the application, so responsibilities and scope are specific to your application, your vendor, and your agreement. For hosted application upgrade planning, bring the application’s name, its current and target versions, and your worksheet. Our compatibility checklist screens the application first.

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

FAQ

What does hosted application upgrade planning involve?

Record the reason, the target version, and the dependencies, then agree who does what and who approves. Plan a tested backup, a roll back or fix forward decision, and testing on a copy before the change.

Can I roll back an application upgrade?

It depends on your backup, your data, and your deadline, so record what the restore test demonstrated and which recovery limits remain, and decide in advance whether you would roll back or fix forward.

Who does what in a hosted application upgrade?

As an example, the vendor supplies the upgrade while the host runs the environment, and you test and approve. Treat that as a starting point, and agree who installs the upgrade, runs database conversions, and executes recovery under your support contracts.

Planning an upgrade to an application you already host?

Bring your worksheet, and we’ll discuss responsibilities and scope for your application.

Discuss upgrade coordination

AI Enablement