One of the biggest buzz words in IT at the moment is Green IT. IT does not have the best image when it comes to ecology; data centers in particular have a bad reputation because of the massive amounts of energy they use. Hence, when people talk about Green IT they often focus on servers. But if you want to go green, you can't neglect the desktops. Depending on the hardware you use there is much room for improving the ecological footprint of your company.
- Set up a SharePoint 2010 development environment - Mon, Sep 3 2012
- MBAM 2.0 – BitLocker Administration and Monitoring changes in Windows 8 - Thu, Jul 26 2012
- BitLocker in Windows 8 - Thu, Jul 19 2012
If you bring up the idea in your next executive board meeting it will get support but one question will be raised: What does it cost? If it involves high costs the support will dry up fast. But going green doesn't necessarily mean more expenditure. If everything is planned well, going green might even save the company some money. Here's an example of how we managed to go green and save some bucks:
Last year many of our desktops ran out of support and their advanced age caused more and more malfunctions. It was clearly time to get new computers. Up to that point we used common desktop hardware. A single desktop burned around 70 W when the desktop was idle; more when the computer was under load.
I thought there would be major improvements in the field of energy consumption in recent years. However, after the test examples from our hardware vendors arrived I measured their power consumption and was disappointed to discover that consumption was in more or less the same range as the old computers. Computing power, however, increased significantly. But because many of our desktops are only used for browsing the Internet and for scientific research in various online databases, they don't need a lot of CPU. So I ordered an Atom Ion-based computer for test purposes. I was surprised that it performed quite well—not enough to run Office or HD videos smoothly, but enough for browsing the web. The test example I got uses 18 W when idle and 24 W when running CPU burn.
This is a significant difference considering we usually exchange desktops after five years and our desktops run for 12 hours per day, every day per year. During this time span the energy savings from the Atom-based desktop would be around 919 kW. With energy prices around 0,14 EUR/kWh we would save around 128 EUR per computer. We have approximately 300 computers for public Internet access, so the energy savings would be 38.400 EUR over the five years.
Impressive? Kind of, but there are also some drawbacks:
The Atom platform is slow, and you have to thoroughly test if it meets the needs of the users. We never had a single complaint about the limited performance of the desktops in the whole year, but this is only due to their small area of operation. If you run CPU-intensive software, you should be aware that the performance per watt is much higher for Amd Athlon or Intel Core Duo processors.
If the desktops are in sleep mode or shut down most of the time the impact of a platform switch becomes less significant because both platforms burn around the same amount of energy when sleeping or turned off. Another point to consider is that the Atom platform isn't yet widely used in corporate environments. You will have a limited choice of vendors if you want extended business support. Last but not least, creating a clone image caused more work because of some exotic chips on the motherboard.
Subscribe to 4sysops newsletter!
All in all the decision to switch to Atoms was a good one: The financial department is happy because we spend less money, the helpdesk is happy because they have to carry a lot less when exchanging the desktops, and our consciences are happy because we waste less energy. Only the users’ happiness didn't increase: They haven't noticed any change.
Want to write for 4sysops? We are looking for new authors.
I wish Wake on LAN was more reliable. Generally our tests didn’t yield very high response rates. One moment I could flip a machine on remotely, then not the next.
We currently ask out users to leave their machines on when they leave. It’s an unsettling request but a lot of our machines are loading updates, replacing software, doing virus scans etc. Without this time I’d have more problems than we do.
Anyway if I could ask users to shut down when they leave, I could force the rest of the machines down with a good hour’s worth of warning. Then I could bring the machines up at about 4 or 5 in the morning to run those regular tasks. If someone wanted to remote into their machine, an app could flip it on for them or they could cancel shutdown, etc.
Perfect? No but, take that 70 watts x 700 machines and there’s some serious wast most of the night and morning. I could cut that in half.
Have you looked at Intel’s AMT in that’s in almost all corporate desktops? They are basically ILO/RSA/IMM for Desktops. Works great, and integrates with SCCM.
In the latest version of Intel AMT that is in the latest Q-versions of the 5-series chipsets it supports KVM-over-IP. A great feature to have for a larger company.
I’m not familiar with this. All the features you guys mention sound interesting. guess I have some homework.. or maybe there could be an article posted here? hint hint
Great article. I believe that the desktops savings would be bigger when companies embrace VDI