VDI – remote work in which data never leaves the server room
WebDisk Blog · category: Cloud computing · reading time: ~9 minutes
In short:- VDI (Virtual Desktop Infrastructure) moves the entire working environment into the data centre: the operating system, the applications and the files all run on servers, and only the screen image travels to the user's device.- The biggest gain is control: company data does not sit on laptops, lost hardware stops being a data-loss incident, and a new workstation is created in minutes.- VDI is neither free nor universal: it requires servers, carefully considered licences and a stable network, and graphics work requires GPU acceleration. We describe the limitations openly.
Monday, 8:40 a.m. An employee calls: the laptop is gone from the car along with the backpack. The IT department's first questions are not about the hardware – that is insured. They are about the data: what was on the disk? Was it encrypted? How long will it take to rebuild the workstation so that the person can get back to work?
In a model where every computer carries a complete set of company data, such questions are unavoidable. There is, however, an architecture in which they sound entirely different: VDI. The desktop, the system and the files stay on servers in the data centre, and the user's device is only a window through which they are viewed. A lost "window" is simply replaced with another one – after logging in from new hardware, the user returns to exactly the same environment, at the point where they left it.
In this article we explain what VDI is (and what it is not), what its architecture looks like from a bird's-eye view, in which scenarios it genuinely proves itself – and what this convenience costs, because enthusiastic descriptions usually say nothing about the limitations. We wrote this text for people who make IT decisions in a company; it assumes no knowledge of virtualisation.
What is VDI and how does it work?
VDI is a model in which user desktops run as virtual machines on servers in the data centre. A virtual machine is a computer carved out in software – with its own operating system and applications – sharing a physical server with other such computers; the layer that makes this possible is called a hypervisor.
We connect to a virtual desktop through a remote access protocol: a compressed, encrypted screen image flows in one direction, mouse movements and keystrokes in the other. The client can be an existing computer, a browser, a tablet or a thin client: a simple endpoint device that stores no data at all, because its only job is to display the remote desktop.
An important distinction: VDI is not the same thing as "remote desktop to my computer at the office". A connection to a physical machine is a one-to-one relationship – the computer has to be switched on, and if it fails, the work stops. VDI is a centrally managed desktop farm: environments are created from a master image in minutes, assigned and reclaimed on demand, and the user is not tied to any particular piece of hardware.
What does a VDI environment consist of? Four building blocks
Deployments differ in the products they use, but almost every VDI consists of the same four elements:
- Servers with a hypervisor – the physical computing power on which dozens or hundreds of virtual desktops run. Processors and memory are shared, which allows them to be used more efficiently than in scattered laptops – but it requires capacity planning with headroom for peak hours.
- Connection broker – the service that authenticates the user (this is the natural place to plug in company sign-in and MFA – multi-factor authentication) and matches them with the right desktop: an existing one, or one being created for that very session.
- Master image and profiles – desktops are built from a single, centrally maintained system image (the golden image); user data and settings live in a separate profile layer. Hence two variants: a persistent desktop (the user always returns to "their" machine) and a non-persistent one (the session is created from a clean image and disappears after logout; the profile and the files remain).
- Access gateway – publishes the environment to the outside world: it encrypts traffic, enforces access policies and makes it possible to work from any network.
From the IT department's perspective, the most important consequence of this arrangement is: you update one image, not a hundred laptops. A security patch applied to the master image takes effect for everyone at their next login – with no hunting for devices that "happened to be switched off".
When does VDI genuinely pay off?
Remote work with sensitive data. All that is on the user's screen is an image – the files physically never leave the data centre. For regulated industries (finance, healthcare, law firms) this is a fundamental change to the risk model: control over the data no longer depends on the discipline of every single endpoint device. And if the desktops run in a Polish server room, the data also stays in the country – we wrote about why this matters in our article on Polish cloud computing.
BYOD, or private hardware at work. BYOD (bring your own device) usually founders on the question "how do we secure someone else's computer?". VDI turns the problem around: the private device stays private, because the company environment runs outside it – the hardware is only a terminal.
Teams whose composition keeps changing. Seasonal workers, contractors, call centres: a workstation is created from an image in a few minutes, and once the collaboration ends, access is revoked in a single move – with no hardware to recover and no uncertainty about what was left on it.
Business continuity. A device that fails, is stolen or suffers water damage does not take the working environment with it – the user logs in from other hardware and carries on. Centralisation also makes data protection easier: instead of chasing copies scattered across laptops, you cover a single infrastructure with backup – we describe how to arrange it sensibly in our article on cloud backup. It is worth remembering that VDI is not a backup in itself – backup copies of desktops and profiles remain a separate, mandatory layer.
How much does VDI cost and what will it not solve?
- It is an investment, not an automatic saving. Servers, storage array, network, software layer – the infrastructure bill can come as a surprise. Real savings appear elsewhere: in administration time, in cheaper endpoint devices that last longer, in the cost of incidents that never happened. Calculate TCO (total cost of ownership), not the purchase price.
- Licensing is a project in its own right. Licensing operating systems and applications in virtual environments follows its own, far from obvious rules – especially in the Microsoft ecosystem. It is a budget line and a point for legal analysis, not a footnote at the end of a quotation.
- The network becomes critical. Without connectivity there is no desktop – offline work in pure VDI does not exist. Comfort depends more on latency and connection stability than on raw bandwidth; a user with a poor internet connection will feel every hiccup.
- Graphics and multimedia cost extra. A standard virtual desktop handles office work well; CAD, video editing or 3D modelling require making GPU cards (graphics processors) available to the desktops – and that means more expensive servers and often additional licences. Video conferencing, in turn, puts load on the "camera → server → other party" path and in practice requires optimisations that redirect audio and video directly between devices.
- Centralisation also means concentration of risk. A failure of the VDI farm affects everyone at once – the project must build in redundancy and tested recovery from the outset. Otherwise we trade a hundred small points of failure for one big one.
What is the difference between VDI, DaaS and RDS?
When considering virtual desktops, you will come across three similar-sounding approaches:
- RDS (Remote Desktop Services, terminal services) – many users share a single server operating system, each getting their own session. The most economical in terms of resources, but with weaker user isolation and with application compatibility limitations.
- VDI – each user has their own virtual machine: full isolation and a "real" system per head, at the price of a bigger appetite for resources. You maintain the infrastructure yourself, or you rent it.
- DaaS (Desktop as a Service) – the same end result, but the entire infrastructure layer is maintained by the provider, and you buy desktops as a service, on a subscription. It is a natural extension of the family of models we described in the article on cloud as a service.
The boundaries can be fluid – DaaS is, after all, VDI that someone else is responsible for – but the "build or buy" decision determines the budget, the competencies required and the pace of deployment. And when the decision falls on "buy", the next question is the choice of infrastructure provider – we dissect that dilemma in our article hyperscaler or Polish cloud.
Where to start with a VDI deployment?
VDI rolled out in a rush across the whole company is a classic recipe for disappointment. The safer path:
- Inventory the applications. Check which programs have particular requirements (GPU, USB devices, licences tied to hardware) – they are what will determine how difficult the project is.
- Classify the users. Office work, specialist workstations, graphics – each group corresponds to a different resource profile and a different cost per desktop.
- Measure the network. Latency and connection stability from the locations where people actually work – not from the office next door to the server room.
- Count the licences before you buy anything else.
- Run a pilot with a small but representative group – including the person with the worst internet connection in the team.
- Gather feedback and keep calculating. Only a pilot yields the data for a sound TCO and a decision: VDI, DaaS, or perhaps a hybrid – virtual desktops only where they provide an advantage.
Frequently asked questions
Is VDI more secure than a laptop with an encrypted disk? These are different layers. Disk encryption protects data on a stolen medium; VDI means there is no data on the medium at all – it also removes the problem of copies on USB sticks and "private archives" – provided that the environment's policies block redirection of storage media and the clipboard; that is a configuration decision which has to be taken consciously. It does not, however, exempt you from the rest of basic security hygiene: strong passwords, MFA, updates to the master image. A compromised VDI user account is still compromised access to the data.
Can you work in VDI without the internet? No – and that is a boundary of the model, not a flaw in the implementation. The desktop runs in the server room; without connectivity there is no way to display it. If frequent offline work is a requirement, VDI may cover only part of the team, or may not work out at all.
What kind of connection is needed? A more modest one than intuition suggests – the protocols transmit a compressed image, not files. More important than bandwidth are low latency and stability: they are what decides whether the desktop feels responsive or irritating. That is why the pilot measures the experience from users' real locations.
Does video conferencing work on a virtual desktop? It does, but it is the most demanding scenario – by default the camera image travels through the server. Mature VDI platforms have optimisations that pass media directly between the participants' devices; it is worth checking whether they are available for the particular conferencing tool you use before deployment.
What is the difference between VDI, DaaS and RDS? In RDS, many users share a single server operating system, each in their own session – the approach most economical in terms of resources, but with weaker isolation. In VDI, each user gets their own virtual machine, and you maintain the infrastructure yourself or rent it. DaaS gives the same end result as VDI, except that the infrastructure is maintained by the provider and you buy desktops on a subscription.
How much does a VDI deployment cost and where do the real savings come from? VDI is an investment – servers, storage array, network, software and licences – not an automatic saving. Real savings appear in administration time, in cheaper endpoint devices that last longer, and in the cost of incidents that never happened; that is why you calculate TCO, not the purchase price. Graphics work additionally requires GPU cards, which means more expensive servers and often additional licences. We describe what an honest bill for the infrastructure itself is made of in our article on public cloud at a reasonable price.
Does WebDisk offer VDI? We provide cloud infrastructure services – computing power (public cloud) and data storage in a Polish server room – that is, the foundation on which such environments are built. We approach virtual desktops individually: whether VDI is the right answer at all depends on the scenario, the applications and the number of workstations. If you are considering it – write to us, and we will talk through your case before you spend a single euro.
Summary
VDI turns working environments scattered across laptops into a centrally managed service: the data stays in the server room, workstations are created in minutes, and lost hardware stops being a data-loss incident. The price of this control is investment in infrastructure, licences and dependence on the network – which is why a sound decision starts with an inventory and a pilot, not with a purchase. Are you considering virtual desktops in your company? Let's talk about your scenario – we will advise whether, and in which variant, it makes sense.