This means, we do not require a full-blown operating system with complex programs such as development environments, Microsoft Excel or other programs that are installed directly on the client. Both in retail shops and in warehouses, most of the workflows are browser-only. The use case we've implemented this for is for browser-based tasks. This puts two requirements on this solution: The clients need sufficient RAM (we have observed, that it's getting tight with 8GB RAM, so we recommend 16GB) and the network needs to be fast for adequate boot times. During startup, the thin client image is loaded into RAM and booted from there. The thin client is booted from the network and stateless, which means that any device in the network can boot the thin client operating system, even if the device does not have a disk. Cost: Cheaper devices can be used, no full-blown laptops or PCs are needed.Maintenance: the devices do not need to be managed and patched (e.g.Security: an always up-to-date operating system including applications, as the image can be rebuilt periodically.Security: less attack surface, as fewer components are running.There are a couple of advantages to running a thin client: In this context, a thin client is a lightweight operating system containing a small amount of tools only, compared to a full client such as a client running the Windows operating system. This is a documentation repository that ties together all the repositories concerned with a thin client that can be network booted.
0 kommentar(er)
