Simply put, what is server based computing? It is a model that allows applications or desktop sessions to be stored on a server, in a data center, and gives users the ability to access them from a thin client, PC or other device. Every user has a private session on a multiuser server operating system. It’s frequently referred to as thin client computing and is different from VDI, where each user is provided with a complete desktop operating system for his or her use.
How Server Based Computing Works
In this section, we’ll go over how the Server Based Computing works.
Server based computing (SBC) is a method of computing in which the software is stored on the server machines that are located within the data center. When using a terminal or thin client, only the screen output, keystrokes and mouse actions are communicated across the network to the user. Because the server on which the sessions are running is a multiuser operating system, the name thin-client computing is applied.
There are two protocols that are found throughout the history of SBC. The documentation for thin clients shows that the well-known compression protocols are Microsoft’s Remote Desktop Protocol (RDP) and Citrix’s Independent Computing Architecture (ICA). Under Microsoft platforms is given by Remote Desktop Services (RDS), a built-in feature of Windows (previously Windows Terminal Services).
Two Ways to Deliver It
SBC can provide either one of the following:
- Published applications. Each user is provided with his own independent and secure application instance—not an operating system that includes an application.
- Hosted desktop sessions. The user logs in to an operating system running on the server’s system. According to one VMware author, instead of running a Windows 10 desktop, they’re running a server operating system session such as Windows Server.
Many organizations employ a mix or each uses both, depending on what the needs of that mix are.
SBC vs VDI vs Local PCs
This is an original comparison of SBC vs. VDI vs. Local PCs.
This editor’s table provides a summary of published comparisons. It’s not a standard.
| Factor | Server based computing | VDI | Local PC |
| The benefits of VDI over traditional PC and factor server based computing. | Access to a shared multiuser server | Access to a full virtual desktop of their own | Access to a local operating system (OS) |
| User to server relationship | One user to many servers | One user to one server (VM) | None |
| Personalization | Limited, will share an environment | Full: users can customize and install apps | Full |
| return to typical protocols: RDP/ICA RDP/others None | |||
| Windows 7 Enterprise (for G7X) | Best for Task workers using standard applications | Users needing a personal or isolated desktop | Heavy local processing |
| Secondary applications must run on a multiuser server, greater demand on server resources, and must be managed in a distributed fashion. |
As described by a VMware author, the difference between VDI and SBC is that with VDI you have a complete copy of a desktop operating system where you can install and install customization, personalization, and application whereas with SBC you are running an application session and/or sharing a desktop operation system in your own session.
Benefits
- Lower desktop cost. One oft-cited benefit is that the number of thin clients can take the place of large full desktops, which helps to keep costs down when it comes to traditional desktop computing. A study in 2007 reported this but also noted that sometimes potentially better configurations were available for the same price in a low cost, upgradeable, PC; check on the price these days.
- Single repository of data and management. Data and applications remain in data center for a central support and administration.
- Longer hardware life. According to one older document from the vendors, the average lifespan of a thin client is 5-7 years compared to 2-4 years for a PC. Consider that one to be a vendor for the day.
- Power savings. They also reduce power consumption and heat production over traditional PCs according to vendors.
Limitations
Another limitation is that SBC can only be deployed for lighter software that would be compatible with Terminal Services or Citrix from the same 2007 review. VDI is not bound by these restrictions. That is because for graphics-intensive or processors-thirsty operations, the systems tend to remain on-site or stuck on a VDI. One reviewer talked about using Citrix for running large spreadsheets and retaining a full PC to run publishing or graphics applications which would not run on Citrix.
Another SBC attribute that is known is complexity. A vendor white paper admits that the Citrix production environment usually requires a certified Citrix professional to be configured, and that Citrix provides more functionality than RDP — for more money. That is a competing item that they sell, so add weight accordingly. In the same paper, Citrix would move towards a largely ‘cloud target operation,’ it is mentioned.
The majority of these documents date back to the 2000s and 2010s and, at the point of writing, the technology has merged with cloud based desktops & application streaming. Although these rules hold true, before purchasing, check the products and their licenses at the time of purchase.
Four-Question Fit Test
Four-Question Fit Test (Original Framework)
Answer these from first to last. It is an editorial approach, NOT an industry standard.
- Are the Applications performing well on a multiuser shared server? Otherwise, try VDI or local PCs.
- Do user need to personalize his/her desktop or install their own programs? If so, opt for VDI.
- Work loads are light or heavy? Shared sessions can’t be used for CPU- or graphics-intensive tasks.
- What is the network reliability? SBC requires a continuous connection therefore expect failures.
As long as the answers split, a hybrid is a good possibility.
Server Based Computing Checklist
Use the Server Based Computing Checklist (Linkable Asset) to confirm that you have configured a host to support five or more clients.
- Listed the applications users need
- Both are experienced with working on a multi user server OS.
- Reviewed licences for RDS / Citrix / Other solutions
- Servers specifically sized for their maximum number of simultaneous users.
- Capacity and failover plan && maintenance of planned network
- Select thin clients, PCs or a combination of both
- Determined who should be served with VDI vs.
- Sessions with high security level and authentication
- Piloted by a single department first
- Lessons learned/reviewed cost/PC refresh.
Guest Post Angles
These are topics that are relevant for IT infrastructure & end user computing publications:
- SBC vs VDI in 2026: who’s who needs what?
- Thin clients for call center or kiosks – Practical Solution.
- For small businesses, Remote Desktop Services: what it takes.
Pilot With One Department First
Air Travel with a PILOT aboard with the department’s inventory first.
Prior to a rollout plan, select one department having typical applications, like accounts or customer support, and start a four-week trial. Monitor login time, user reported performance issues, and any support tickets, and compare against existing desktops. The pilot will help to answer the questions what is server based computing in my environment as it will determine if your applications and your network and your users will be appropriate for shared-session.
