Traditionally, embedded computers have used direct attached storage (DAS) to host the operating system (OS). However, this approach can increase size, weight, power consumption, and cost (SWaP-C). What’s more, with DAS systems, upgrading the software on local media can be both time-consuming and labor-intensive. A better approach is to host the OS and application software (APP) for network client computers on a network attached storage (NAS) device. This eliminates the need for DAS, streamlines the embedded computer’s physical design and reduces overall SWaP-C. Even better, NAS systems simplify software updates across multiple embedded computers by enabling centralized software deployment over the network, significantly reducing time and effort.
Login and download the white paper to learn more.
- Pre-eXecution Environment Network Attached Storage (PXE boot)
- Reducing SWaP-C
- Data-at-Rest (DAR) Encryption
- Simplifying Software Updates
- Increasing Vehicle Uptime
Remotely hosting the OS and APP on a NAS is referred to as “network booting” or “NetBoot”. NetBoot delivers new efficiencies, better security, and significant savings to teams that maintain software on embedded network computers. While NetBoot is often referred to as “PXE boot” (pronounced “pixie” - short for Pre-eXecution Environment), not all NetBoot mechanisms employ PXE. NetBoot was initially developed to allow desktop thin clients to run without needing a locally installed OS. This eliminated runtime issues associated with DAS and reduces the total cost of ownership (TCO) for IT departments.