Is Setting Up Proxmox on Every Computer a Good Idea?

Running only a single VM like this could work for testing, but using it in production is a recipe for disaster. The complexity skyrockets since you're managing two OSes, each needing updates and maintenance, plus you could face slower boot times. If you’re the sole IT person, simplicity is your best friend. Team discussions can help evaluate this further!

Why complicate things when there are easier alternatives? Using VDI (Virtual Desktop Infrastructure) has its purposes, but it can drive up costs significantly. Deploying thin clients only makes sense if the use case is tightly controlled, like in a call center. For most office users, standard PCs would be simpler and more efficient.

You could technically run Proxmox on a dedicated host for specific use cases, but for most end users, a native OS performs far better. If the goal is quick recovery, just ensure that important files are backed up appropriately, not by virtualizing everything. The costs and complications of VDI generally outweigh the benefits unless you have strong use cases in mind.

This idea complicates things unnecessarily, especially if you’re just trying to backup data. You're basically adding overhead without clear benefits. Users should save their data on a network or cloud service, and in case a PC crashes, just re-image it quickly. There's no need for the added layers Proxmox brings, which just complicates the process.