Slashdot Mirror
Rolling Your Own Business Desktops?
mike asks: "I'm mulling the logic of my company building its own desktop computers. As the IT Manager (plus sysadmin, janitor...) of a struggling-yet-thankfully-still-alive dotcom, money is really tight. We have around sixty ~400MHz desktops which are increasingly showing their age. Acceptable P4 systems from the big guys run at least $1000. By recycling the OS (Win2k), case, cdrom, floppy, and K/V/M, I figure I can assemble a good AMD system for about $600. That's a 40% savings. Is it worth it? The cost difference could very well determine whether this project proceeds or gets put on the back-burner again."
"Some negatives about rolling my own:
- Management: I won't get the special business features offered by some manufacturers. Dell's OpenImage, for example, looks awfully nice. But how much does that really buy me in a company of 60 machines? I don't use such stuff now; am I missing out on nirvana?
- Time to build: Even though we'd leverage Ghost wherever possible, handmade systems nevertheless take time to build, load, & configure.
- Supporting different platforms: Because money is so tight, I can at best afford a capital replacement rate of 25%-33% (15-20 units) per year. That means I'm committing to the support of 3 or 4 different platforms. Having just one platform is great, but how many companies, even ones that actively strive for it, truly enjoy that luxury? I inherited two platforms (Micron & Gateway); support isn't that bad. With proper planning, I don't see why we can't support four.
- Hardware quality: How much can I trust a popular Athlon chipset in a business environment? I feel silly bringing this up because I have a few Athlon systems at home, each with a different chipset, and they've been nothing but rock solid. But I know the lack of a really good chipset has been a large contributor to why AMD's aren't more prevalent in the business world. (well, that and long term bullying by Intel).
- I don't get a proven, prepackaged system that works right out of the box.
- Cost savings. Plain & simple.
- Increased horsepower per dollar spent.
- By choosing my own equipment (mobo especially), I suffer fewer OEM shortcuts.
- I have to admit that I'd enjoy the pure geek satisfaction of rolling out 'my' creation to the company.
For those that are curious, Ask Slashdot did an article on the AMD issue, here.
I see it this way. You are the one that will be working on these machines. You must factor in the knowlege that you made them and know what is in them. Just make sure you get a warranty on all the parts since you will not have one on the entire machine
Don't forget having to run your own assembly and tech support shop as well. I can usually coerce somebody to come out from Dell and replace my broken (video card, motherboard, CD-ROM drive) with little effort here at work if the need arises and it's covered under warranty. At your shop, YOU are the warranty guy.
Also, factor in the labor costs (which will be substantial), count the amount of time it will take for you to assemble a machine, the cost of ESD straps and mats (you will be using ESD mats, right?), the time it will take to set up an assembly area, and the space that will take up, etc.
I used to build machines for other people (family members, etc.) Now I just tell them all to buy a Dell because the hassle on me to maintain them is WAAAAAY less. The only machine I build myself anymore is my personal box, because I spec out stuff that is too high-end for a manufacturer like Dell anyway.
Nope.
:)
If it was a full retail version of Win2K, it can be transferred. But nobody has full retail -- everyone has the OEM version. That's part of the lock-in of preloads.
OEM versions can't be moved from one machine to another. Also, Microsoft has strict rules about what constitutes an "upgrade". I don't have them here, but "upgrading everything around the W2K license" is not an upgrade, it requires the purchase of a new license.
Don't take my word for it, though, or anyone on slashdot. Check out http://www.microsoft.com/licensing, and see how Microsoft is making it so much easier for the consumer, by not having so many confusing programs designed to save the customer money.
By gouging the crap out of everyone, you now don't even have to go to the bother of trying to save money. You can just assume you are going to get poked, and sure enough, you are! Don't even *need* to read those agreements anymore.
Boy, that *is* easier. Thanks Bill!
I own and operate a small dotcom like business and we always bought the bits for our machines, and built them ourselves.
:-) Get someone else to burn it in - it's a waste of your time.
We bought the best components, big cases and were able to ensure everything worked as desired. But reliability is a BIG issue.
We recently stopped this practice and decided to buy from a small but reliable company (armari.co.uk). I bought a test machine (dual amd 1800+, 1GBram, etc.) and the build quality is amazing...we are now purchasing these machines (plus dual monitor) for all the team.
It's a big relief knowing that I can just call someone and have it fixed asap. Armari even provided named Win2k login, partioned the way I like, and system rescue CD's that in 10 minutes put the os, drivers and configs all back to factory ship.
No looking back to the dim and dark days of spending hours trying to get a SCSI card to boot a CD
Time to build: Even though we'd leverage Ghost wherever possible, handmade systems nevertheless take time to build, load, & configure.
Yes. But make damned sure that you're building them as an assembly line. The principle is that building a second one will only take 50% more effort than building the first; the third will take only 33% more effort than the other two, etc. Whatever old Henry Ford's theorem was. It works.
Set aside a room where no one else will bother you. *GOOD STATIC CONTROL* is mandatory. Do all stages of assembly at once, that way you're not wasting time fumbling back and forth for screwdrivers. Get going at a good clip with quality cases, and you should be able to assemble 100 systems/day - but that assumes you have *everything* where you need it when you need it, there's good padded shelving, and you've got a grunt taking care of taking cases out of boxes for you. It also excludes software load.
Just make sure you get a warranty on all the parts since you will not have one on the entire machineAbsolutely. But, assuming a competent builder (ie. not blowing processors with bad jumper settings or blowing boards by not having them seated right), the parts themselves should be pretty reliable. If you're buying good stuff, the biggest source of problems will probably be static handling.
Keep in mind that a modern memory or processor chip has literally millions of CMOS transistors. CMOS transistors have an incredibly thin layer of glass between the gate input and the source-drain circuit. A voltage applied to the gate influences the flow of current through the source-drain circuit. Trick is, the layer of glass involved is so thin that you can punch a hole in it with 30V. Next trick is that static electricity generates kilovolts (thousands of volts) with sufficient current to blow holes in the gate layer, but be imperceptible to you.
All it takes is one transistor out of the millions inside a modern chip to be defective and the computer will crash apparently at random... you know, when Windows VMM writes a 0 to a memory address and gets it back as a 1 later on... BSoD. Kernel Panic. Choose your flavor.
Wrist straps, static baggies, conductive floors, grounded workstations are *crucial*. Dell, Compaq, Asus and Abit spend millions of $$ on these things, and for similar reliability, you should demand the same standards every step of the way for your home-rolled machines. Make sure your computer store hasn't "helped" you by opening the static baggies. Write that one into the contract with the computer store. And make sure that the hard disk drives are still in their packing "egg-crate" things. You really don't want a box with a stack of hard disk drives. (Western Digital had a great video on hard drive handling floating around the 'Net, you should view it if you're building en masse.)
Fire and Meat. Yummy.
Fry's in Southern California has been selling $250 PCs from BTC with Linux on them. That's what I'm posting on right now. Works great! The Linux that comes on them is not a "real" Linux distro -- more like an information appliance shell -- but you can replace it with something else, and you're not paying for a Windows license if you don't need it.
Find free books.
We thought building our own would be cheaper, but the maintenance turned out to be a nightmare and cost us a lot more than the machines themselves. In once case, we had a machine that had a bad motherboard, then a bad replacement. Took almost 3 weeks to get that one machine up and running.
Dell is great. They'll come out and fix your machines for you. After the build our own fiasco, we went with Dell. The only problem we had of all the Dell machines was a bad IDE cable in one machine. Otherwise, things were great.
I bet you'll average more than $400 in labor time, for each machine, in the long run. Also, I think your math is bad. I bet you can get decent Dell P4s for $600 or so. A Dell, 128MB P4@1.7GhZ(without monitor), $500 after rebate.
To qualify for an OEM copy of windows, it must be purchased with a new cpu, hard drive, or motherboard.
I did the Celeron + slotket upgrade on my home PC, and can vouch that it's a good bang for the buck upgrade.
A Celeron 1GHz goes for $55 on Pricewatch. Look at $10 or so for no frills slotket. A 256MB stick of PC133 will set you back about $30. That's a little over $100 for a nice upgrade.
And as Tackhead said, it's a dead simple swap software wise. No hours of "New Device Found" hell that normally accompanies motherboard upgrades under Windows. You also get to keep your probably 440BX based motherboard with it's well tested and mature drivers.
"People that quote themselves in their signatures bother me" - athakur999
Bah. The first RIS job I did will be my last one. At least until I have to do > 100 PC's. I never did figure out all the problems we had with that install (project got pulled in the middle of it due to layoffs), but I think our Cisco switches did not like the DHCP requests from trying to boot off the network. About 35% of the machines had to be rebooted 5+ times in order to get a lease. And, even after it loaded (which took a god awful long time), we still had to configure each PC (for Outlook, custom apps, etc.)!
For the 15-20 PC's he's talking about, I think RIS is a little too much. Just make 2 images (assuming no SCSI drives), one for ACPI compliant PC's and one for APM PC's (assuming you have any), install your common programs (Office and the like) and sysprep them. Then just Ghost from a network server. That's the cheap, slow way to do it. Oh, and it'll also clog the network so you may want to do it off hours. Just make sure your server can support multiple streams (or use a few servers), or it'll REALLY slow you down. I'd suggest using Bart's network boot disk to boot from (hopefully you have supported NICs, most major ones are) and then you can assign an IP if you have trouble with DHCP.
Or, if your cases are easy to work with (most recent OEMs, barring HP and Compaq, are) Ghost from a few internal hdds (much, much faster). Just give each of your tech 3 hdd's and 3 preconfigured Ghost floppies to boot from (start Ghost in the autoexec.bat file). By the time they've started the 3rd install, the 1st will be done. Reboot it and it'll detect the devices.
All you've got left is to install the custom apps, and configure email. If you're going to go thru the trouble of making MSI's for your apps, you may as well start using Active Directory's software install services as well. Then your users can just install their apps for themselves.
Will Microsoft even allow you to recycle your Win2k license on a new computer?
This really pisses me off. This should of been part of the settlement from the DOJ. M$ Screwed Consumers.
The OEMS had to accept the M$ price discount plan, and only sell OEM versions to stay in business. M$ should of never been allowed to tie an OS to hardware, too late, damage done.
We had a site license for m$ at work. We bought 40 pc's and could not get them without windows. We just paid for an OS which we would never use, and couldnt sell. What about all the schools across America that got double billed for an OS? Thats alot of tax money M$ should pay back. I wont even go into the tax scam m$ has, they do not pay federal income tax.
If I was going to roll out desktops.
1. Terminal Services/Citrix/etc... Will NEVER tie M$ into hardware, repeat never, rinse repeat, never.
2. Linux workstations.
3. Fast network, with gigabit upstream to the TS servers.
4. Ghost images on CD.
BTW, 400mhz boxes make good linux workstations.
-
Where does an 800 pound gorilla sleep, anywhere he wants.
But seriously I have worked on many many systems over the years and I have never had a problem which could be credibly linked to hardware failure brought on by ESD. I think that lots of less-experienced techs and help desk people blame any problem that they can't figure out on ESD. Got a BSOD that you can't explain? Here's a convenient line that no one can really disprove and makes you look smart. "It must have been mishandled by some other ignorant tech years ago and is just now showing symptoms." Right. How could even tell the difference between an ESD problem and a problem caused by irregular AC line voltages or manufacturing defects?
What the hell is a "latent failure"? As was stated above, ESD is measured in kV while CMOS tolerances are more like 30V. Either a transistor is blown or it isn't. I agree that ESD can damage transistors, and I also know that a computer may very well power up after suffering damage from this. However I think the notion that a system would power up and work normally for two years before going south is ludicrous. You seem to think that the static can somehow "weaken" the hardware without fully blowing it out.
My personal solution to the ESD problem is a compromise between the incredibly annoying wrist strap and "going commando" and risking relatively expensive hardware. I leave the power supply plugged into a grounded outlet while working on the machine. I know somebody's gonna flame me for this, but think about it. When the machine is plugged in the entire chassis is a path to ground which can bleed off excess voltage in the case of a static discharge. If you simply touch the chassis before you start working you will discharge any static electricity which is being carried by your body and you're good to go. Unless you are working on your computer while standing on a shag carpet in your socks while rubbing a balloon on your head then this is probably all you need to be safe. You could then unplug the AC line if you wanted, although I don't see any harm in leaving it plugged in during your entire operation. Outside of the power supply the voltages can be no more than 12V and low current so electric shock is really not an issue.
On a side note I think a much more common issue is the failure of the power supply itself, rather than motherboards and chips. In most machines I build the PS will burn out after a couple of years unless I spend a few extra dollars on a step-up model case like an Enlight.
Alright, flame away.
alex
--- Wherever you go, everyone is always connected...
I'm not sure what the chances are you'll even see this. 450 posts and the ones modded up are pretty negative. Oh well. . .
I'm currently rolling custom built machines for our 200 systems network. Oh, and I'm the only tech here. I do the servers, network, help desk planning, everything.
My place is a non-profit where a very small, chaotic budget. I'm never sure exactly when I'll have money to spend or how much. For strange reasons, when we go to spend money we have to go through a maze to buy complete equipment, but components are no problem. We couldn't buy a new company car, but we could buy all the parts to put a car together ourselves. Same goes for computers.
The savings we've seen building ourselves are huge. Adding the costs of the pieces and my time spent planning, building, and supporting these systems it is still cheaper than OEM systems and a support contract. A+ certified techs are a dime a dozen, so support of these wintel systems isn't really a factor if I were to leave. (They'd have to get a half dozen to do what I'm doing by myself in 40 hours a week, plus an MCSE and a CCNA, so I'm not worried about job security).
Here are some tips:
1) Plan out your configuration and use it for the next year. The most important component is the motherboard. It should be able to accept more RAM and a faster CPU than you are going to use initially. Spend lots of time developing a stable, user-friendly software config (OS and apps). As you need to replace systems throughout the year, use this config. After six months update the config with a faster CPU, more RAM, and maybe a larger HD. Update your software config with patches, fixes, stuff like that now also. At the year mark you can plan your new config.
2) Integrated components are your friend. I like the nVidia nForce boards because they have the (good) sound, video, and network integrated. Also, if one manufacturer stops making your board, you should be able to switch to another manufacturer but still use the same drivers. Very important for ghosting!
3) You really don't need the management software for 60 computers. That stuff is usually designed (and priced) for enterprises with several hundred if not thousands of systems. You should be able to keep most of that stuff in your head and in a small text-file database. Learn a little Python/tk and you can even build your own front end to the text-file. Cool!
4) Develop a relationship with a couple local component vendors, and a couple Internet vendors and have them bid for any purchase more than a couple grand. You'll definetely save money this way, especially if they know they are bidding and not just giving a price quote. I've saved thousands of dollars on a single purchase this way. Also, after a while the local guys will probably be able to send a couple guys your way to help out every once-in-a-while when you get swamped or stuck as a thank you for your business. Very Cool!
Following these tips, you only have four platforms to work with, you've saved money, you know exactly what you are working with, and you get a sense of pride from creating something from your own two hands.
I really can't recommend this approach highly enough.
obviously no deficiencies vs. no obvious deficiencies