Virtual Desktop (VDI)
Give every employee the same Windows desktop on any device, no VPN needed
The desktop runs in the data centre, not on the laptop: staff connect from a laptop, a tablet or just a browser and pick up where they left off. Data stays on infrastructure in Türkiye rather than on the device, and Nesnet's team builds the setup with you.
Why now
- It's Monday morning and IT has twelve VPN complaints waiting. Setting up a VPN for every home worker, keeping it current and talking people through failed connections takes someone's whole day. With virtual desktops, outside connections go through a gateway Nesnet runs, with no VPN.
- PC refresh time has come round, and the quote for hundreds of machines calls for a big upfront budget. When the desktop runs in the data centre, an old laptop or a thin client connects to the same desktop, so a refresh doesn't mean a powerful PC on every desk.
- A sales rep left a laptop in a taxi, with the customer list on it. With virtual desktops the data lives in the data centre, not on the device: access is cut centrally and the employee carries on from a new device where they left off.
- The new release of your accounting application has to be installed on fifty PCs one by one, and the weekend has been set aside for it. When desktops come from one master image, the update is made once in the image and reaches every desktop.
- Ten consultants are joining for a three-month project, and each needs a laptop prepared and collected again at the end. Instead, they connect to a desktop from their own devices; when the project ends their access is closed and company data doesn't leave with them.
What changes
| Today | With Nesnet |
|---|---|
| Every home worker gets a VPN to install and support. | Users connect with the client or a browser, and outside access goes through Nesnet's gateway with no VPN. |
| Each desk gets a powerful PC that's replaced every few years. | The desktop runs in the data centre; an old laptop or thin client is enough to connect. |
| A lost laptop takes the company data on it with it. | Data stays in the data centre, and the lost device's access is cut centrally. |
| Application updates are installed on every PC one at a time. | The update is made once in the master image and reaches every desktop in the pool. |
| Temporary staff get a laptop prepared and collected again at the end. | Temporary staff connect from their own device, and access is closed in one place when the project ends. |
From today to live: how it works
- 1
Discovery call
Agree with Nesnet's team how many users need a desktop, which applications and devices they work with and which sign-in method you'll use. You leave with a proposed setup and a clear view of what drives the price.
- 2
Master image and pool prepared
Nesnet's team prepares the master image, the pool type (refreshed at every session or a persistent desktop per person), the application packages and the access policies to fit what was agreed.
- 3
Pilot users connect
A small group connects with the client app or a browser and does its daily work on the new desktop. Application, printer and connection-quality settings are tuned to that group's experience.
- 4
Rolled out to everyone
The pool opens to all users, and people outside the office reach their desktops through the external access gateway without a VPN. Old PCs stay in use, just for connecting.
- 5
Image upkeep and growth
Updates are made in the master image and rolled out to the pool, and more desktops are added for new users. As the user count changes, the invoice changes with it.
What you get
Access from any device or browser
Users connect with the client app from Windows, macOS and Linux computers and from iOS and Android phones and tablets. Where no client can be installed, a browser alone works over HTML5, and the user returns to the same desktop where they left off.
Secure outside access without a VPN
Connections from outside the office go through the external access gateway Nesnet runs, so no separate VPN client goes on the user's device. The gateway lets only the desktop connection in; the rest of your network is never exposed.
A second step at sign-in
Desktop sign-in can add a second verification step through a RADIUS-compatible system or one-time-code tokens. An account whose password has been stolen still can't reach a desktop without that second step.
Single sign-on with company accounts
Single sign-on can be set up with any corporate identity provider that speaks SAML, so staff sign in with their company account instead of another password. When a leaver's account is closed in the directory, desktop access closes too.
Compliance checks on connecting devices
The external access gateway can check at sign-in whether a device meets the conditions your organisation sets. A connection from an unpatched or unmanaged device is stopped before it ever reaches a desktop.
A picture that adapts to the network
The screen is carried by two display protocols that tune quality and compression to the network's speed and latency. The desktop stays smooth on a home connection, with video, audio and multiple monitors supported.
Hundreds of desktops from one image
Desktops are produced from a master image by fast cloning (instant clones) and use little storage. Preparing a desktop for a new user takes far less time than setting up a PC.
Update once
Operating system and application updates are made once in the master image, and when it's published every desktop in the pool moves to the new image. The previous image is kept, so a problematic update can be rolled back across the pool.
A fresh desktop every session
For shared computers, the desktop returns to the master image's original state when the user signs out. Files, settings or malware left by one user never carry over to the next.
A persistent desktop per person
Each user can have a desktop of their own, with settings and the data they create kept on a persistent disk separate from the virtual machine. Even when the image is refreshed, their files and desktop layout stay put.
Deliver applications separately from the image
Applications are packaged separately from the master image and assigned to users or groups. Giving the finance team a new application doesn't mean rebuilding the image; the package appears only on that team's desktops.
User settings that follow every session
Profile management carries a user's printer, desktop and application settings from session to session. Features such as clipboard, USB and file transfer are governed by conditional policies that switch them on or off depending on where the user connects from.
Published desktops and applications
With a Windows Server 2022 template you can set up published desktops where several users sign in on the same server, as well as individually published applications. A user who needs just one application opens that window instead of a full desktop.
GPU-backed desktops
For graphics-heavy software, a graphics profile from a data-centre GPU is added to the desktop, from 3 GB to 48 GB. CAD and 3D software run on the card, only the picture reaches the user's device, and model files stay in the data centre.
Peripherals and video calls
Devices such as USB drives, cameras, headsets and scanners can be redirected to the desktop, and local printers work as normal. Video calls can be set up so audio and video are processed on the user's device, keeping the load off the desktop.
Lose the device, not the data
Company files live on the desktop in the data centre, not on the user's device. When a laptop goes missing, access is cut centrally and the employee reconnects from a new device to the same desktop.
Company device and phone management
Device management enrols company computers, phones and tablets in one management point, and applications, settings and policies are rolled out from there. It's billed per device, and the invoice moves as the count changes.
Redundancy at the front door
The connection broker can run as several replicas and the external access gateway on several appliances. In that layout, if one goes down, new connections go through the others and users keep reaching their desktops.
Why Nesnet
Built around how you work
Virtual desktops aren't an off-the-shelf product that spins up from a panel; Nesnet's team builds them. Once your user count, devices, applications and identity setup are discussed, the pool is designed around them, so needs that don't fit a template are dealt with up front.
The external access gateway is already live
The gateway that handles connections from outside the office is a live endpoint at Nesnet. Nobody has to build and test that door from scratch for a new customer; your first user comes in through a route that's ready.
Your data stays in Türkiye
Desktops and user data sit on Nesnet's infrastructure in the Equinix Istanbul (Dudullu) and Türk Telekom Ankara data centres. Company files don't pile up on employees' devices, and nothing is moved to a region abroad.
Desktops, servers and backup under one team
Desktops run on the same infrastructure, and with the same team, as Nesnet's servers and backup. If the file and application servers your desktops use live there too, a problem never means going to separate firms for desktop, server and network.
Device management from the same place
Nesnet also runs a live device-management endpoint. The company phones, tablets and computers connecting to your desktops are managed by the same provider, per device.
Predictable, per-user billing
Desktops are billed per user each month, as e-Invoice or e-Archive documents. The invoice moves with your user count, and the hardware refresh budget drops off the calendar.
Example scenarios
A hybrid team that left its VPN problems behind
Situation
Half of a company's two hundred staff work from home a few days a week. Each one connects to an office PC over VPN, and VPN issues fill IT's day.
Outcome
Staff Windows desktops run in the data centre, and outside connections go through the external access gateway with no VPN and two-step sign-in. IT stops managing VPN accounts per user.
A contact centre on shared PCs
Situation
A shift-based team shares the same computers; applications are installed on each machine separately, and a broken machine disrupts the shift.
Outcome
Desktops are built from one master image and reset at sign-out. Application updates are made once in the image, and a broken desktop is simply replaced at the user's next session.
A design team using CAD from home
Situation
An engineering firm's designers work with large model files and are tied to powerful workstations in the office whenever they want to work from home.
Outcome
Designers run CAD on the data centre's graphics card through GPU-backed virtual desktops. Model files stay in the data centre and only the picture reaches the laptop.
A branch network putting off a PC refresh
Situation
A retail chain with eighty branches has ageing branch PCs; replacing them all means a big upfront investment and months of rollout.
Outcome
The old branch PCs are used only to connect, while applications run on desktops in the data centre. When a new branch opens, desktops are ready without sending an installation team.
A company giving outside consultants a safe workspace
Situation
A finance company will work with fifteen outside consultants on a six-month project and doesn't want customer data landing on their laptops.
Outcome
Consultants connect to desktops from their own devices, with file transfer and clipboard switched off by policy. When the project ends, access is closed in one place and the data stays on the company's infrastructure.
Who does what
| Nesnet | You |
|---|---|
| Builds the virtual desktop setup around your needs with its own team. | Decide how many users get a desktop; the charge is per user. |
| Runs the external access gateway that handles connections from outside the office. | Agree with Nesnet's team which applications your users need and which sign-in method to use. |
| Runs the infrastructure your desktops use with the same team as servers and backup. | Manage user accounts in your own directory and close leavers' access. |
| Runs the device-management endpoint. | Decide which company devices are enrolled in device management. |
| Applies the master-image and pool settings agreed during setup. | Set your organisation's rules for data policies such as clipboard, USB and file transfer. |
Who it is for
Remote and hybrid teams
Teams that work part of the week from home or on the road and need company applications from outside the office. Connections go through the external access gateway Nesnet runs, so nobody gets a VPN client to install.
Branches and contact centres on shared PCs
Organisations where shift teams, branches or training rooms share the same computers. Desktops are built from one master image and return to their original state at sign-out, so a broken machine never holds up a shift.
Design teams working with heavy graphics
Teams that want to use CAD, engineering and 3D software from home too. A GPU-backed desktop runs that software on the card in the data centre, and only the picture reaches the user's device.
Companies working with contractors
Companies bringing in consultants, interns or contractors for a project. Instead of shipping a laptop, you open a desktop and close it when the project ends, and company data never sits on the person's device.
Organisations managing company devices
Organisations that want to manage company phones, tablets and computers centrally. Device management comes from the same team as the desktop service, billed per device.
May not be the right fit
If a few users simply need the same application, a Remote Desktop Services (RDS) server on Virtual Servers is simpler than a desktop per person; the RDS template and user licence are ready there.
If you want to spin up desktops yourself from a panel in a few minutes, this product doesn't work that way; it's set up as a project together with Nesnet's team.
If your users work where there's no network connection at all, a virtual desktop isn't a fit; reaching the desktop always needs a connection.
Under the hood
Desktop virtualisation works like this: the Windows desktop runs in a virtual machine in the data centre, the screen image travels to the user's device, and keyboard, mouse, audio and redirected USB devices travel back. Nesnet delivers the service on an enterprise desktop virtualisation platform and sells it per user. The picture is carried over display protocols that adapt to network conditions. Desktops are produced from a master image by instant cloning; applications are packaged separately from the image, and user settings and conditional policies live in a separate profile layer. Connections from outside the office are handled by an external access gateway, which is live at Nesnet. Graphics desktops are backed by GPU graphics profiles from 3 to 48 GB, and company devices and phones are managed through unified endpoint management. The catalogue holds a Windows 10 virtual desktop template and a Windows Server 2022-based desktop template. What Nesnet adds is that its own team builds and runs it: the desktop line isn't a portal product, it's set up by Nesnet's engineers around your needs and runs on the same infrastructure as your servers.
Building blocks
- Desktop virtualisation platform
- desktop pools, connection broker, published desktops and applications
- Adaptive display protocols
- tune picture quality and bandwidth to the network
- Instant cloning
- fast desktop production from a master image, optional persistent disks
- Application packaging
- delivers apps as packages separate from the image
- User profile and policy layer
- user settings and conditional desktop policies
- Connections from outside the office
- a gateway for VPN-free access, live at Nesnet
- GPU graphics profiles
- 3–48 GB of graphics memory for GPU-backed desktops
- Unified endpoint management
- company device and phone management, per device
How it compares
| Option | When it is the right choice |
|---|---|
| A physical PC for every employee | If your staff are always in the office and an IT team looks after their machines regularly, physical PCs are simple and familiar. As remote access, image maintenance and refresh work grow, moving the desktop into the data centre makes more sense. |
| An RDS server on Virtual Servers | If it's enough for users to open separate sessions on the same Windows server — say they all use one accounting application — an RDS server uses fewer resources and you can run it yourself. If each user needs their own Windows desktop, central image management or a GPU, a virtual desktop is the better fit. |
| A VPN to the PC in the office | If a few people occasionally work from outside, a VPN and Remote Desktop to their office PC may be enough. That approach needs the office PC to stay on and healthy, and every user needs a VPN set up. |
Technical specifications
| Desktop service | Corporate virtual desktop |
|---|---|
| Desktop billing unit | Per user |
| Device management unit | Per device |
| Setup | Not a portal product, built by Nesnet's team |
| Infrastructure | Same infrastructure and team as servers and backup |
| Support line | 0800 606 1071 |
| External access gateway | Live at Nesnet |
|---|---|
| Access from outside | No VPN, through the gateway |
| Device management | Endpoint live |
| Compliance check | Connecting device can be checked at sign-in |
| Second factor | RADIUS-compatible system or one-time codes; single sign-on via SAML |
| Clients | Windows, macOS, Linux, iOS, Android; HTML5 in a browser |
| Display protocol | Two protocols; quality and compression adapt to the network |
| Peripherals | USB, printer and scanner redirection |
| Desktop templates | Windows 10 virtual desktop; Windows Server 2022-based desktop |
|---|---|
| RDS user licence (SAL) | Rentable for Windows Server-based desktops |
| Graphics profiles | 3 GB (1/16 card) … 48 GB |
| Graphics desktops | GPU slice in instant-clone pools |
| Instant clones | Desktops produced from a master image, refreshed at sign-out |
|---|---|
| Persistent disk | User data on a separate disk for dedicated desktops |
| Application layer | Apps as packages separate from the image |
| Profile management | User settings and conditional policies |
| Resilience | Several external access gateways, replicated connection brokers |
If something breaks
A user's device breaks or goes missing
The desktop runs in the data centre, not on the device, so the user connects to the same desktop from another device or a browser. The lost device's access can be closed through the user account and device management.
A desktop breaks
In an instant-clone pool, a broken desktop is rebuilt from the clean master image when the user signs out or an administrator refreshes it. User settings and files on a persistent disk are unaffected.
A connection broker or external access gateway goes down
The connection broker can run as several replicated instances, and the external access gateway as several appliances. In that setup, new connections go through the others when one drops.
An image update causes problems
Because the previous version of the master image is kept, the pool can be rolled back to it. Updates can be tried on a small pool first and published to everyone afterwards.
Frequently asked questions
Pricing and first steps
Pricing
Virtual desktops are billed per user, monthly. Device management is a separate per-device line, and RDS user licences can be rented separately for Windows Server-based desktops.
What the price depends on
- Number of users with a desktop
- The graphics profile chosen for GPU-backed desktops
- Number of devices under management
- RDS user licences (SAL) for Windows Server-based desktops
How to get started
- 1.Fill in the form or call 0800 606 1071.
- 2.Your users and applications are worked out in one call, with a proposed setup and a price.
- 3.The master image is prepared and your pilot users connect to their first desktops.
The desktop lives in the data centre, wherever your people are
Setting up a VPN for every user and updating every PC's image one by one wears IT down. Tell Nesnet's team how many users and devices you have; you'll hear back the same business day, and the setup starts with a pilot group.