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

Moving a Windows App to Hosting? Bring Its Custom Reports

Ask your team which part of the application they’d miss most if it changed, and someone will name a report.

Custom reports in hosted Windows applications depend on more than the application itself, because they use templates, data connections, fonts, printers, and export folders, and any of those can change in a move. This guide shows how to carry your report requirements into a managed hosting move and check that staff can still produce the outputs they need. It assumes no report will work until you test it.

Step 1: List the Reports That Matter

List the essential reports staff run, who runs each one, how many times a month, and the decision it supports, such as a job cost summary for pricing or an aging report for collections. Rank them, because you can’t test everything at once. If a report supports no decision, ask whether it belongs in the move at all. Reports that run overnight without a person are covered in our guide to overnight jobs.

Step 2: Map Templates, Connections, Fonts, and Export Locations

For each essential report, write down four things, starting with where its report templates live.

  • Report templates. Note where each one lives: inside the application, in a shared folder, or on one person’s PC, so a template on a local drive won’t follow the application.
  • Data connections. Note how the report reaches its data, whether through the database, an ODBC connection, or a spreadsheet, and which reporting add on or runtime it needs.
  • Fonts. Identify where the report renders and which fonts its engine requires. Test the hosted view, exported files, and printed output on the devices staff use. Microsoft’s guidance for SSRS reports shows why: a PDF that doesn’t embed a font needs it on the viewing computer.
  • Export and print locations. Note where PDFs and spreadsheets are saved and which printers receive output.

The access method matters here, because Parallels’ feature comparison lists Universal Printer Support and dynamic time zone redirection for both its Windows client and its web client, but lists drag and drop redirection for the Windows client and not the web client, so test the method your staff will use. Dates and number formats can also shift with regional settings, so compare those too.

Step 3: Compare Sample Outputs With the Same Test Data

Run each essential report on the old system and the new one, using the same copy of the data, not data from different days. Use identical filters, date ranges, and parameters, and run both under equivalent approved accounts, since user permissions can change what a report shows. Then compare totals, row counts, layout, page breaks, fonts, and exported files. For printed output, compare paper size, orientation, and scaling too. Save both outputs so someone else can check your result.

Step 4: Decide Who Fixes What

Custom reports in hosted Windows applications can fail in several ways, so the table below gives suggested starting points for troubleshooting. Agree the first contact and escalation path with your application owner, vendor, and hosting provider before migration.

Symptom Check first First owner (example)
A template is missing or edited Where it was stored. App owner
Layout or logic differs from the old output The template and the vendor’s notes. Vendor, with the app owner
The report can’t reach its data The data connection and any add on. Host, with the app owner
A font, printer, or export folder is wrong Where the report renders, its fonts, and the access method. Host, with the app owner
Totals differ The data copy, then the report logic. App owner, then vendor

Step 5: Add Report Approval to the Acceptance Checklist

Your application migration checklist should include report approval, because the move isn’t done until the reports that run the business pass. So for each essential report, its owner signs off the comparison before cutover. Use a sheet like this one, with a row for each report.

Output Dependency Owner Result Evidence link Approval date
Job cost summary (example) Template in a shared folder, report add on, PDF export folder Operations manager Pass, Fail, or Open Link to saved outputs Date signed
Aging report (example) Database connection, company font, default printer Office manager Pass, Fail, or Open Link to saved outputs Date signed
           
           

Open means testing isn’t finished or a problem isn’t resolved. An essential report marked Fail or Open blocks approval until it’s resolved, so record the evidence link and approval date alongside the result.

Our hosted application data migration checklist shows how to reconcile the data behind the reports.

Where CloudTop SaaS Fits

We host Windows applications on Azure with Parallels RAS. Whether your reports work in a hosted environment depends on the application and its add ons, so compatibility is specific to them, and we don’t promise that any report will work before a test. For legacy app hosting, bring your report list to the discussion, then use our compatibility checklist to screen the application first.

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

FAQ

Will custom reports in hosted Windows applications work after the move?

They may, but each depends on its template, data connection, fonts, printers, and add ons, so test each essential report before cutover.

Why can fonts change after a move?

Fonts depend on where the report renders and how it’s viewed or exported. Identify where the report renders and which fonts its engine requires, then test the hosted view, exported files, and printed output on the devices staff use.

Who should approve reports before a move?

The person who runs each report should approve it, after comparing old and new outputs from the same test data, so add that approval to your acceptance checklist.

Not sure your reports will survive the move?

Bring your report list, and we’ll discuss what your application and its add ons would need.

Discuss your reporting needs

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

AI Enablement