Sandra Davis7 said:How much RAM and virtual memory does a virtual machine actually eat up compared to just running standard Windows? I guess we're working with really limited RAM on our machines, and I'm a bit worried that SSD space might run dry eventually once Windows updates start rolling in. Would setting up a server, assigning domains, and spinning up VMs on these computers end up being too heavy on our resources?
Honestly, I think I got a little lost in your last post. I'm not entirely sure what you're asking here.
Setting up a domain makes administration easier, sure. But you don't need virtual machines just to migrate a system over to a domain.
As for how much memory a VM "eats"—it eats exactly as much as you decide to give it.
Look, if you're already strapped for memory and disk space, you're stuck. There's no magic fix. If you have so little space left that you're expecting Windows updates to wipe out the remaining capacity, there isn't much you can do. No matter what move you make, that space is still going to vanish.
And yeah, you mentioned "creating" a server. You usually have to buy one. Unless, of course, you already have hardware sitting around. Actually, if you're looking at 100 workstations and want room to grow, you should probably have at least two servers for redundancy.
Also, how are all these machines getting online? Is it just one single connection, or are there multiple gateways? What's the bandwidth looking like? Won't that choke your internet connection? Is the whole company in one building or spread across different sites? Are all 100 computers independently pulling updates from Microsoft?
Maybe consider setting up a proxy? It would save a massive amount of bandwidth. And is every single machine pulling its own antivirus updates? That alone eats up a ton of data. I'm guessing you don't even have an antivirus server right now—like a corporate setup that downloads the updates once and distributes them locally.
You mentioned users are browsing the web, downloading music, watching videos, reading news... everyone is burning through bandwidth individually. A proxy could be a lifesaver here. Not by throttling them, but by preventing 100 machines from downloading the exact same files 100 times; once one machine grabs a file, the others pull it from the proxy instead. Of course, configuring a proxy properly isn't exactly child's play.
Anyway, I'm rambling. Managing 100 workstations isn't something you can just wing. Well, maybe if it's some government agency where profit doesn't actually matter.