Virtualizing Workstations For Common Hardware?

An anonymous reader writes "We have approximately 20 workstations which all have different hardware specs. Every workstation has two monitors and generally runs either Ubuntu or Windows. I had started using Clonezilla to copy the installs so we could deploy new workstations quickly and easily, when we have hardware failures or the like, but am struggling with Windows requiring new drivers to be installed for all new hardware. Obviously we could be booting into Ubuntu and then load a Windows virtual machine after that, but I'd prefer not to have the added load of a full GUI underneath Windows — we want maximum performance possible. And I don't think the multi-monitor support would work. Is it possible to have a very basic virtual machine beneath to provide hardware consistency whilst still allowing multi-monitor support? Does anyone have any experience with a technique like this?"

Comments

We did something else which was a lot more useful

[Merc248]

I used unattended on a FreeBSD box at one of my old jobs, since we had like five or so different models of computers. It works sort of like RIS, except it's easier to extend the system since it's all written in Perl and it's all open source. We dumped the contents of an XP disc on the server, then slipstreamed driver packs into the disc directory structure; this catches almost everything but the most obscure hardware out there. Unattended allowed us to run post-install scripts, so we threw in a bunch of other software packages that would install after the OS was done installing, like Office 2007, Adobe suite, etc.

This was substantially better than a disk image; we took care of all of the drivers in one fell swoop, so the only thing we used as a differentiator between computers was how the person used the computer (if it's a student lab computer, we loaded a bunch of stuff like Geometer's Sketchpad, InDesign, etc. If it was a faculty's laptop, we'd load software to operate stuff in the classroom.) We save space on the server, and we save time when it comes to putting together another "image" for a different use case.

But as others said above, I wouldn't virtualize the workstation, even if it eases up on the IT dept. a little bit; just be smart about what deployment method you use. I wouldn't recommend using unattended if you had only about three different models; it's likely substantially easier to just use CloneZilla.

Oh, and use a centralized software deployment system such as WPKG. Your disk images will go stale after a while, in which case you'll have to make sure that you can manage the packages installed on clients somehow.