Topic: OS Migration and Testing
Typically for a roll out of a product you look at the incremental extra cost against measured benefit. The strongest benefit here is likely the ability to extend the life of the hardware and reduce ongoing support costs for the result.
But when SA comes up for renewal the cost saved would be factored in to justify the SA renewal. Remember that SA cuts across a variety of products (mostly server side) so the estimated $100 per desktop software cost savings (at volume rates) would, in addition to the savings for their coming server and exchange deployments (which are in plan) justify the SA renewal cost.
Now it might be interesting, after the fact, to roll up all the costs and take them against the alternatives but this is rarely done. IT shops typically operate project to project and don't have the bandwidth to do analysis that cuts across a series of projects (often this is because each project is generally staffed differently).
In the end, and what we often forget, is the true benefit of SA isn't the savings but the ability to avoid budget surprises by making spending predictable. Generally it is worse to blow out a budget than it is to overspend because budget surprised reflect on management competance and overspending isn't as visible.
This is one of the things I'm not sure folks like Google or the Open Source community really understand.
--"PC power ($28) savings."
I'm curious as to how they actually determined power savings. Did they hook up a power meter to a XP system and an identical Win7 system for a week? And where exactly is Win7 getting these additional savings from? The only real details I've found on this topic is at http://blogs.msdn.com/e7/archive/2009/01/06/windows-7-energy-efficiency.aspx They talk about slowing the processor clock, but that is assuming your processor supports it (things like Intel speedstep, which wasn't available on desktop CPU's a while back). XP also had the ability to scale down the processor clock.
--"It also found that Windows 7 ran on 4-year-old Dell hardware"
That is certainly possible, but again, as far as I know, the desktop CPU's 4 years didn't support lowering processor clock.
And what about losing memory to the OS? Win 7 requires 1GB vs 128 MB XP. And hard drive space? Win7 (16GB) vs XP (1.5GB).
--"Because Windows 7 (and Vista, actually) can be patched more easily in the background, "
I don't see why you can't just set up XP to update over the lunch break or after 5pm on Tuesdays.
You're thinking too much. The power savings is largely coming from turning the machines off or suspending them when not in use. Something they weren't evidently able to control under XP centrally as well. You've been able to lower the clock speed of the processor for some time, this is an automatic function for thermal management in place since the mid-90s. Typically we try to go the other way, its called overclocking. Current hardware typically allows you to do this more dynamically rather than through settings though.
We've had storage headroom for much of this decade. This is a financial company and would rather not have a lot of storage on PCs anway, the loss in capacity might actually be considered a plus because they would likely rather have the information remian on secure servers.
In a lot of companies people work throug lunch or take staggerred lunch breaks and work after 5. If the system is off you need to be able to wake it up to patch it. I can recall watching people actually have a patch reboot thier XP systems the middle of a powerpoint presentation. Auditors tend to work long hours and often don't take set lunches. So you could but it would disrupt the work.
Topic: Windows 7
Microsoft is keeping a low profile on the next version of its flagship operating system
Blog: We Need to Manage Information Not Software
Article: Skipping Vista Won't Solve OS Problems
News: Microsoft Issues Advisory on Windows 7 Zero Day
Related Topics
Dell, Desktops and Workstations, OS Migration and Testing
Lowering Your IT Costs with Oracle Database 11g Release 2This white paper identifies the key capabilities a database management solution needs to successfully deliver more information with higher quality of service, make more efficient use of IT budgets, and reduce the risk of change in data centers.
Software Forum: Information On Demand Virtual ExperienceThis interactive virtual forum presents leading IT experts providing the insights you need to turn your information into a strategic driver for innovation, business optimization and competitive differentiation.

Indispensable technologies and best practices to maintain your organization's most valuable asset.

Tools, tips and solutions to help you manage your data more efficiently to tackle today's challenging economic environment.

Hardware and software tools to create an enterprise infrastructure for data and business optimization.

Learn how virtualization reduces the TCO of managing your date, while contributing towards your sustainability efforts.
Windows 7 Upgrade Project KitMoving to Windows 7? The Windows 7 Upgrade Project Kit is the ideal support tool for managing all phases of an organizational upgrade to Windows 7. The tools and templates in this kit will help you develop a strategy and map out the implementation tactics which link your Windows 7 deployment to your company's bottom line.
Disaster Recovery & Business Continuity Template PackPrepare your company for any type of disaster you can envision and those you cannot. Immediately download this comprehensive set of templates and tools for documenting your business contingency plans.
Hi, Rob -- Ken here. Just wondering, is it typical for large shops to simply not factor in some swag at the proportional cost of a software upgrade beneath a program like SA if they are taking as hard a look at a rollout as Baker Tilly obviously is? Obviously, they'd be under SA anyway, but it seems that some cost-recognition would be in order, if for no other reason than to justify the overall SA outlay. But that's a cost center manager from an SMB talking, and of course we try to count everything.
Thanks, Hardin