Flagship capability

Jentu diskless infrastructure, designed and deployed

Jentu removes the hard drive from the endpoint. Workstations and servers boot their operating system from a central image over the network, and every restart returns the machine to a known good state.

How the pieces fit

Schematic
How a Jentu diskless environment is put togetherWorkstations with no local hard drive boot a read only operating system image streamed from a central image server over the network. User documents are written separately to revisioned network attached storage.no local driveno local driveno local driveNetworkblock streamImage servergolden imagesread onlyStorageuser documentsrevisionedProcessing stays localBoot over EthernetOne image to patch

Processing still happens on the endpoint, so this is not virtual desktop infrastructure and it does not need a datacentre full of compute. The central server holds and streams the image. The workstation does the work.

We are a Jentu certified implementer. Our technicians design the image architecture, build the storage layer, migrate departments across and support the environment afterwards. Most of the value shows up in the years after the build, which is the part general IT providers tend to underestimate.

How it works

Jentu diskless infrastructure, designed and deployed characteristics
Boot modelNetwork boot, disk block streaming over Ethernet
ProcessingLocal to the endpoint, not centralised
Throughput1 Gigabit networking delivers SSD class performance; 10 Gigabit typically exceeds NVMe
Endpoint storageNone required
ScopeWorkstations, servers and IoT endpoints

Detail

What the work involves

Golden images per department

Accounting, legal, engineering and front office each get a versioned image. Roll a change out once and it lands everywhere that image is used.

Clean on every restart

The operating system and application layers are read only. Changes made during a session are discarded at power off, so a machine comes up pristine.

User data kept separate

Documents and profiles map to revisioned network attached storage, so wiping the OS layer never touches the work.

Smaller attack surface

No local drive means the largest attack surface on the device is simply not there. A ransomware payload that cannot persist across a reboot has a very short life.

Patching that can be undone

Updates are applied centrally to the image. A bad patch is reverted by rolling back to the previous version rather than visiting every desk.

Longer hardware life

Storage failure is the most common reason a workstation gets retired. Remove the drive and machines stay in service considerably longer, drawing less power and less cooling.

Outcome

A Toronto sleep clinic ran on CDOC built diskless servers for more than twenty years. In that time they recorded no workstation failures and no viral compromise, and stopped managing weekly patching entirely.

For over 20 years, our clinic ran on custom servers by CDOC in one form or another. Since installation, the server has run flawlessly. Because the workstations do not require a hard drive, we have had no failures of our workstations, and no need to worry about viral attacks, hacking, drive crashes, operating system failures or weekly patching.
Dr. Michael HawkeSilent Partners Sleep Labs

Questions

Common questions

What is Jentu and how does diskless computing work?
Jentu is a server controlled diskless computing platform. Workstations and servers boot their operating system and applications from a central image streamed over the network instead of from a local hard drive. Processing still happens on the endpoint, so it is not virtual desktop infrastructure. CDOC is a certified Jentu implementer and designs, deploys and supports these environments.
Does removing the hard drive slow the computers down?
No. On a 1 Gigabit network a diskless endpoint performs in the range of a local SSD, and on a 10 Gigabit network it typically exceeds NVMe. Performance scales with the resources of the central server rather than with the age of the individual workstation.
What happens to malware on a diskless endpoint?
The operating system and application layers are read only. Any change made during a session, including malware, is discarded when the machine powers off, so the endpoint comes up clean on the next boot. Malware that cannot persist across a restart has a very limited window to do damage.
Where does user data live if there is no local drive?
User documents and profiles are written to revisioned network attached storage kept separate from the operating system image. Resetting or rebuilding the OS layer does not touch user data.

Start with an infrastructure assessment

We look at what you are running now, where the risk sits and what it would take to simplify it. You get a written picture of your environment either way.