Choosing the model
Azure Virtual Desktop on shared hosts, Windows 365 at a flat price per person, or a classic terminal server with a cloud provider.
Not everyone needs a dedicated virtual PC. We match the model to headcount, software and budget.
Azure Virtual Desktop on shared hosts, Windows 365 at a flat price per person, or a classic terminal server with a cloud provider.
Hosts run in a region inside the EU, chosen according to where the required services are available, which makes conversations with your DPO and with clients asking where their data sits much simpler.
User profiles held in FSLogix, software baked into the base image or published as RemoteApp. Comarch, Symfonia or Płatnik behave just as on an ordinary PC.
Sign-in through Entra ID with MFA and Conditional Access, and no public RDP port. For clinics or accountancy practices, clipboard, USB and local printing can be blocked.
Older laptops, cheap terminals, staff members' own computers: anything with a current browser or Remote Desktop client will do.
Autoscaling switches hosts on in the morning and off at night, with a minimum running over weekends. A usage summary arrives every month.
Rollout time depends on headcount and software. We always start with a pilot.
How many people work at once, in which programs and from which devices. That drives the monthly Azure estimate.
A few people from different teams use the desktop for a week. We catch printers, scanners and programs that misbehave.
Host pools, base image, profiles and access rules. The client app is pushed to devices remotely via Intune.
Teams move across in groups, with a one-page guide and faster support during the first week.
The priciest virtual desktop is the one left running all night. Without autoscaling, Azure hosts tick over 24 hours a day although the team uses them for ten. A power-on and power-off schedule plus a cap on sessions per host can cut the bill noticeably, with no difference staff would notice.
That depends on how many people work simultaneously and on the software. An office worker on a shared AVD host usually comes out cheaper than a dedicated Windows 365 seat, while a designer needing a GPU costs far more. After the analysis you get a per-person figure in zloty, with licences and infrastructure itemised separately.
Most will, through device redirection inside the session. Older document scanners and label printers cause the most grief, which is why we test them in the pilot rather than after the whole company has moved. Fiscal printers and card terminals stay connected locally.
For them an ordinary laptop with BitLocker and Intune is the better fit. VDI needs a connection, albeit a modest one, since it only carries the screen image. A sales rep on the road or a site manager usually keeps a local machine.
On the technical side, yes. We describe how staff connect, which devices are allowed and how data is protected, so HR and your lawyer can write it into the policy. The policy itself and health and safety matters are outside our scope.
Tell us how many people work outside the office and which programs they use. We come back with a suggested model and a monthly cost.
Your enquiry has reached us
You will hear back within one working day, and if you have reported an outage that is holding up work, it goes to the front of the queue.
No match for that name. Try a different spelling or pick a bigger town nearby - all our support is delivered online, so your choice has no effect on the service.