Best Practices — Multiple Locations
One Location — One Server
TranslationEvery pending.openthinclient installation starts with a single server instance. Depending on the size of the company, however, this installation can grow to include hundreds or more thin clients, raising the question of whether a single server is sufficient to serve all clients.
With a single server, administrators manage settings and configurations in one location, and back up only one machine.
When an update is required, update one instance, and all thin clients are thus updated.
However, if the single server fails, the entire operation stops.
Advantages and considerations of a single server
✅ A single management interface for all thin clients
✅ Apply
updates to only one installation ✅ Ensure all thin clients use the same version
✅ Backup required
for only one installation ✅ Simple
network configuration (e.g., IP address reservation, VLAN) ✅ When using the Business version with ≥25 thin clients, only one server ID and billing
✅ Only one host system needs to be licensed or maintained
⛔ Single point of failure
⛔ If the server fails, users can't work
⛔ Schedule
a maintenance window for updates ⛔ Test operation requires planning
⛔ Performance bottlenecks possible ("bottleneck")
One Location — Multiple Servers
As described in the article Multiple PXE Servers, multiple boot servers can be located on the same network. This naturally increases reliability.
During updates, update and test one installation first, then update the others.
However, administrative overhead increases because some tasks require repetition across servers,
which can reduce clarity.
Advantages and disadvantages of multiple servers
✅ Higher reliability
✅ If a server fails, some users can continue working
✅ Easier testing of updates, since only one installation can
be updated at a time ✅ Ability to use multiple installations with up to 24 thin clients (without support)
✅ Better performance for large installations through load balancing
⛔ Retain full redundancy, eliminating single points of failure
⛔ Centralize management interfaces for streamlined workflows
⛔ Schedule
updates for each installation ⛔ Thin clients may use different versions, which requires
targeted troubleshooting. ⛔ Backups require more storage because multiple installations must
be protected. ⛔ When using the Business version with ≥25 thin clients, manage
multiple server IDs. ⛔ Depending on the host operating system, plan for potentially higher Windows Server licensing fees.
Multiple locations — one server
Some companies have a large main location and several branch offices, e.g., sales offices, warehouses, and retail locations.
Provided the locations are connected to headquarters via a VPN, a thin client at a branch office can, in principle, be booted via PXE over the network just as easily as at the main location.
Advantages and disadvantages of a single server
✅ Use only one management interface for all
✅ Apply
updates to only one installation ✅ Deploy the same version
on all thin clients ✅ Backup required
for only one installation ✅ Simple
network configuration (e.g., IP address reservation, VLAN) ✅ When using the Business version with ≥25 thin clients, only one server ID and billing
✅ License and maintain only one host system
⛔ Single point of failure
⛔ If the server fails, users cannot work
⛔ Schedule
a maintenance window for updates ⛔ Plan test operations carefully
⛔ Expect performance bottlenecks when booting thin clients at remote locations
⛔ Network configuration (e.g., VPN, broadcast) requires expertise
Multiple Locations — Multiple Servers
With multiple locations, operate a separate openthinclient installation at each branch.
In this setup, both the main branch and all remote locations operate independently. With the appropriate network configuration, the administrator can enable management for each individual instance.
Advantages and disadvantages of multiple servers
✅ Higher reliability
✅ Each location is self-sufficient
✅ If a server fails, it affects only that one location
✅ Option to use multiple installations with up to 24 thin clients (without support)
⛔ Simplify
management by consolidating interfaces ⛔ Centralize access by configuring
appropriate network settings ⛔ Update
each installation at every location ⛔ Back up
each installation and allocate sufficient storage ⛔ Back up across locations with additional infrastructure
. Depending on the host operating system, plan for potential higher Windows Server licensing fees.
Alternative for multiple locations
As an alternative for a company structure with multiple locations, consider using localboot.
In this case, the thin client loads the openthinclient OS and the applications from a local storage medium, which can be, for example, a built-in flash card, hard drive, or a USB stick.