It has been interesting reading this thread and some good advice offered. We crossed this problem over 10-years ago for a client when Internet speeds were a fraction of what they are now.
This led us to offering our solution as a commercial service, which is now our main delivery platform for our own FileMaker solutions, which are specifically designed to operate this way
We initially built our Windows servers on Rackspaceās infrastructure, but as they grew their service became less personal. We moved everything to the UK based Hyve infrastructure a few years ago and have also used AWS EC2 for testing and other purposes.
Originally we used Citrix XenApp Fundamentals (for small businesses) until Citrix took £10k for maintenance and phased the product out - you can still purchase maintenance from Citrix for this non-existent product. We will never go near Citrix again.
We investigated Parallels RAS, which on the surface looks really good, but their prices do not include the Microsoft Remote Access licenses (CALs), which means youāre simply paying on top of what Microsoft Remote Desktop Service (RDS) does as standard. Previously RDS was called Terminal Services, hence the confusion between Remote Desktop servers and Terminal servers.
Our FileMaker Server and Remote Desktop servers are all hosted on the same Hyve Internet infrastructure (similar to @bowdendata above) and FileMaker Pro is streamed to our Windows (RemoteApp client is built in and looks like any local app when running) and Mac clients (mainly using the free Microsoft Remote Desktop for Mac, which weāve been beta testers for years - when Microsoft were using HockeyApp for their feedback, we had excellent 2-way communication with the development team, now sadly lost with their current system - and occasionally Jump Desktop). We have clients who also run the full FileMaker Pro client on ChromeBooks (weak MS client, no 2 display support), iPads, Android tablets and it can even run on Linux, for which we have no experience.
It is expensive, the cost for a 5-client license is about £700. In our case everything is included within a monthly fee per user, hence clients have no FileMaker related IT costs as everything is managed and maintained by us.
Technically, the negative side of this includes lack of drag and drop into container fields, a Windows look and feel for Mac users (although some Command key shortcuts can be used), longer initial app launch (but quicker hosted file opening), navigating through the serverās folder structure to find the userās own computer for exporting, saving and importing, and probably some others that Iāve forgotten about as weāve been working this way for so long.
The positives are speed at least matching those of in house hosted system, (rare)connection breaks (say partway through a script with unsaved changes, or an uncommitted edited record) allows reconnection without loss of data, and centralised management.
We honestly expected our system to become redundant by now. However, the industry appears to be moving in our direction with virtual desktop services offered by AWS and Azure.
With Clarisās move to agile development and 3 recent FileMaker updates in quick succession, we are able to upgrade a few hundred users in minutes rather than days. We use plugins from Dacons and 360Works that again can be updated centrally (very important if an update breaks compatibility). All of this without any additional cost to our clients.
The VPN question is understandable and the only test that is relevant is to test access to the server via the VPN server and directly without it.
One thing I donāt believe has been mentioned so far is (normally) the slowest part of remote access - the usersā Internet connection. In 3rd world countries like the UK(sort of a joke), the contention ratios of users to bandwidth provides a pretty poor service. Business broadband has a much lower contention ratio and provides faster speeds.
Again as mentioned previously, the major factors are available bandwidth and database structural design, not necessarily the amount of data stored. Claris have made, and continue to make, good progress with remote connections using lower bandwidth. However, anyone wanting remote access must take onboard the need to design for remote access or make design changes as part of the process. You cannot currently overcome the problems of summary fields, unstored calculations, lengthy table occurrence chains, cross table reports, etc. Connection methods will not resolve these.
We still have some elements of these in our SaleFaith CRM due to its lengthy history. However, over the years we have evolved and now hardly use calculation fields,, the team almost have to beg to add another table occurrence, weāve even written a scripted alternative to using summary fields in subsummary parts. Removing the structural overhead with scripted processes to deliver the functionality when needed is our goal (hence me frequently going on about the missing OnRecordExit or OnRecordUnload script trigger).
We also design for Remote Desktop. For example: default locations to download to and upload from for each userās account and the devices they use, often automatically saving, naming and timestamping saved files to prevent users having to go through the path to their desired file destination.
Iām afraid there are no shortcuts if using FileMaker Pro remotely. It is a bit like a sports team - having one or two stars will be less successful than getting all players operating efficiently together.
By the sounds of it, your client can find budget for expensive hardware, but they may be throwing good money after bad.