Generic PCs For Corporate Use?

porkThreeWays writes "I work for a government agency supporting about 1000 PCs. The economy has hit us just like everyone else and we are looking at ways to save money. We currently buy Dell computers and even with our government discounts end up spending about $1,000 for a pretty mediocre computer. I had the idea of building our own PCs for considerably less. We'd spec out a standard configuration that we'd use for 18 months. CPU speeds and RAM sizes may change during that time, but socket types, memory standards, hard drive interfaces standards, etc, etc would be required to stay the same. We have Dell warranties right now, but I could see just keeping spare parts on the shelf and building that into the cost of the PC. We'd also be able to transfer Windows licenses because the Dell installs are non-transferable. However, I couldn't find anyone on the large scale doing this. Is anyone on Slashdot using PCs they built themselves on the large scale?"

Comments

Competency of IT Staff

[ModernGeek]

So long as you have an competent IT staff, you should be good. It's so much better to have internal people swapping out bad hardware and dealing directly with the RAM vendors, etc when possible. Not only do the vendors of specific hardware normally have longer warranties, they're normally faster than the end vendor at swapping out hardware. Think of it this way, if you keep paying Dell to do support and replacing bad hardware, then what is keeping another, less competent person from taking your job? So long as you create a good mechanism for keeping up with machines, parts, and vendor relations, you should be good. I highly recommend this approach. From my experience in government IT, it seems that the ones who go with vendors who provide a lot of support, the employee gets replaced with a drone who just interacts with said vendor. By doing what you're talking about doing, and doing it in a well executed and organized fashion, you are not only doing your employer a favor by saving money, you are also securing your job. You might want to do this in increments, maybe 100 computers at a time. That way you can find problems that you'd never think would ever be an issue. Doing things in small increments at first is probably the best move you can make. Also, think about keeping parts on hand, maybe enough parts to replace all the parts in every 25 computers or so. That way you can fix failed hardware on site, and then worry about swapping with the vendor later. If you keep up with your data, you can find out what fails the most and when, and then you can become more efficient in dealing with vendors, part swaps, and stocking of said parts.