For those who don’t know, EUC stands for end user computing.
Why is so hard to setup VMs for employees? Maybe I’m missing something but it seems like a matter of just creating a virtual machine with a GPU attached.
In our case we have over 1500 employees using it, but only about 500 at a time. It’s an extreme waste of resources to have to provision 3x the hardware rather than use ephemeral systems. Also it’s much easier to patch a “gold” image and recompose entire pools than have to manage all of the systems as if they were full on laptops. Just to name a couple things off the top of my head.
Yup. That’s another reason we don’t have individual systems. And most thin clients aren’t designed to connect 1:1 to a VM. They usually need a broker of some sort.
Citrix has a product for that don’t they? Pretty sure Microsoft does too, but I’m assuming it’s just in Azure and isn’t as good as third-party products.
Or if you don’t need the fancy stuff, good old RDS pools still work fine. You could probably write your own automation on top of Proxmox too.
Very significantly different performance requirements. The client communication needs tuning for fast UI response. Unified comms (zoom, teams, etc) need to be redirected to avoid bottlenecking through the server. usage patterns aren’t very well distributed (everyone logs in at 8) which means you can’t over subscribe as much.
Now what about EUC replacements. That’s the more sticky situation.
For those who don’t know, EUC stands for end user computing.
Why is so hard to setup VMs for employees? Maybe I’m missing something but it seems like a matter of just creating a virtual machine with a GPU attached.
In our case we have over 1500 employees using it, but only about 500 at a time. It’s an extreme waste of resources to have to provision 3x the hardware rather than use ephemeral systems. Also it’s much easier to patch a “gold” image and recompose entire pools than have to manage all of the systems as if they were full on laptops. Just to name a couple things off the top of my head.
Thin clients?
Yup. That’s another reason we don’t have individual systems. And most thin clients aren’t designed to connect 1:1 to a VM. They usually need a broker of some sort.
Thanks for the explanation
Citrix has a product for that don’t they? Pretty sure Microsoft does too, but I’m assuming it’s just in Azure and isn’t as good as third-party products.
Or if you don’t need the fancy stuff, good old RDS pools still work fine. You could probably write your own automation on top of Proxmox too.
Very significantly different performance requirements. The client communication needs tuning for fast UI response. Unified comms (zoom, teams, etc) need to be redirected to avoid bottlenecking through the server. usage patterns aren’t very well distributed (everyone logs in at 8) which means you can’t over subscribe as much.
It’s very different than a server workload.
Source: I run 80k of these.