Corporate America Not Ready For Vista 317
thefickler writes to point out a TechBlorge article about a study indicating how few corporate computers now deployed are capable of running Windows Vista. The article says that the study, by Softchoice, will be released next week. The study found that 50% of the PCs inventoried (from a sample of 112,000 from 472 organizations) are below Vista's basic system requirements. Roughly half of those PCs will need to be replaced outright to run Vista. 94% of corporate PCs are not ready for Vista Premium Edition. The article notes that the need to upgrade hardware "could... mean that organizations will hold off upgrading to Windows Vista until their next hardware refresh," as some analysts have been saying for a while now.
Their main market? (Score:3, Interesting)
I honestly can't think of any corporation... (Score:3, Interesting)
Hell now that I think about it, I got rid of the last NT 4.0 machine just two months ago. Unless your corporation is very small you keep PCs around until they die or become so obsolete they can no longer run the programs you need them to. In this case we had an active directory upgrade so we had to get rid of all the NT 4.0 machines as they were no longer going to work with the upgrade.
That isn't the computing life in my university (Score:3, Interesting)
TCO is waaaay out of line. (Score:4, Interesting)
I've talked to several customers of mine and many of them just bought new machines in the last 18 months.
They have no intentions of replacing them all over again just to run this new OS that's not all that revolutionary.
I'll bet that's the general consensus. In general of course.
Some people are happy about this, I am sure. (Score:2, Interesting)
Not where I work....yet (Score:2, Interesting)
As we are looking at moving to a 3 year rollover on hardware most of the hardware will not be Vista ready for at least the next two years, by which times there will be at least 2 service packs and numerous packs for the inevitable MSism in the OS.
LOL VISTA is crap (Score:2, Interesting)
Re:Why release to business first? (Score:5, Interesting)
Re:Their main market? (Score:2, Interesting)
Usually around the time that machines start failing, spare parts also become harder to find. When did you last see a new PII-400? Or perhaps a new Slot1 motherboard? If you can find a new one it'll probably cost more than a whole new machine!
You may also find that new perhiperals may not be compatible - maybe the drivers require a recent OS to install, or you need a port that those old machines don't have.
Finally, as has already been mentioned, given a choice between two identical companies, one with the latest computers and flat screens, and another with crap machines and blurry 15" CRT's - it's not rocket science to work out which I'd prefer. A few years ago, I worked at one of the latter - my developer friend had a 386DX40 w4Mb/RAM as his NT4 devbox, logon might take 15mins, compilation may happen overnight - the target customer boxen were dual P133 w/128Mb. I was alpha testing the software under Win95, and the customer was running NT - needless to say sometimes something that tested fine on my system wouldn't even install on theirs... New computers are pretty cheap compared with the losses of key staff turnover, and frustrated clients!
Re:J. Hasaclue CIO responds: (Score:3, Interesting)
That is a lot like getting comfortable with a thorn in your foot. It is not comfort; merely numbness.
They are going to have to switch to Linux at some point. There is no time like the present to start the process.
Why, it will run the very latest spyware and viruses, of course
Even with the budget, why waste the money? Switch to Linux. Lower TCO. No need to waste money on new hardware.
Clearly your CEO is not a hot babe
We are not deploying another Windows O.S. ever. We would have to be fools to move to Vista rather than Linux!
Re:Vista is the new ME (Score:3, Interesting)
However I agree with your post, I have to correct you on this issue:
To me, Vista needs one key thing. (Score:5, Interesting)
Number one on my Windows Vista wish list is that they virtualize the screen more.
What I want is actually very simple. I want to tell Windows - in one place - that my screen resolution is not 72dpi, but is in fact 125dpi. Once that is accomplished, all Windows elements should be scaled to that result.
For any application which does not specify drawing size, but rather specifies pixels - the new AERO graphics engine should do a simple calculation "X pixels * (125 / 72) = Y pixels" and draw it as Y. For fonts and other "vector" based drawing objects, this should be even easier as the curve calculations are already based on this kind of math.
If this is done properly, an 8pt font will take up the same physical area on a high resolution monitor as it does on a low resolution monitor. What's more, it will fit properly in buttons because the number of pixels on the button have been properly sized and should match.
Some people may WANT that optimized screen real estate. That's easily handled. They just need to set the DPI setting on back to 72, and their ultra-sharp tiny little fonts will be right back again. The only thing that could suffer - in theory - is looking at pictures. If something is supposed to be 10 pixels, it ends up being 17.36 for me. Rounding is where you get the "fuzzy" aspect.
Why does this matter? Right now, I'm looking at a 19" monitor which is optimized for 1280 by 1024 pixel resolution. The laptop is more extreme. It's a 17" monitor that is 1920 by 1080. Making some simple assumptions that the pixels are square and aligned uniformly (which they are not, actually) the two monitors come out to about 86 and 125 pixels per inch respectively.
LCD screens are not like the bulky old "tube" based screens. The pixels aren't projected onto a phosphor screen; they are actual hardware - like little light bulbs. If you decrease the display resolution, you're getting less crisp representation at each point than you would at the optimize resolution because the dots themselves cannot change size. They must therefore be approximated.
Where this becomes a problem is that many aspects of the Windows screen are designed to be a set number of pixels in height or width. The unit of measure is in pixels, not inches. This includes fonts, title bars, buttons, icons, and all kinds of other things. Much of the time, Windows doesn't know how many of those pixels fit on a linear inch of screen space on my screen. What people don't realize is that the old standard has been to assume about 72dpi for screen resolution. That means on my laptop, with nearly twice that resolution, things tend to be on half the ideal size.
Re:Their main market? (Score:2, Interesting)
Pay, benefits, name recognition, prospects, upward mobility opportunities, afterhours compensation, lunchroom selection, breakroom coffee/soda quality, company junkets, types of hand moisturizers in the restroom -- important.
Type of OS deployed? -- HELL no.
In particular, what you said is not true for pharmaceutical jobs. We use win 2k for personal workstations, *NIX on all servers, NT4.0 and *NIX to run 50% of instruments, the other 50% running off 98/95. And we still use 3.11 to run mass-specs. I am yet to see an XP computer or a Mac.
Background: I graduated 2006 with a BSci in Biochem, and now work for a large pharm. company [wikipedia.org] , making over $80,000/year.
Re:Vista is the new ME (Score:5, Interesting)
Re:"Premium Edition"? (Score:2, Interesting)
Re:Not ready for IE7 either (Score:2, Interesting)
Re:Spend $ on Vista, or on necessities? My choice. (Score:3, Interesting)
A new Dell GX6xx in quantity is about $500. I'm not sure what machines you were buying 2.5 years ago with core duos, but, I'm sure you might have been buying things that powerful. In our environement, a box from Dell shows up post-sysprep with our enterprise standard image on it (imaged AT Dell from our prepared image). A technician takes it out of the box, types a machine name, it auto-joins the domain, and policy (through BMC Configuration Management / Marimba) deploys any extra non-standard software for the users based on geographic and user-specific identifiers.
"I need something that will last for several years with near-zero fuss. I really can't afford to buy equipment that was obsolete last year, or that needs constant tinkering and upgrades and support."
Which is exactly why turning over a brand new Dell every 3 years (which matches the warranty period) makes sense for us - and for many, many, other large organizations. No tinkering -- we made the image. No upgrades needed -- it's new. And we're already the support. No fuss, no muss.
Also, as an added bonus, since the process we MAKE our enterprise standard image comes from a single unattended DVD (with a plethora of driver support, updated by us), when my "Developer" system was deployed, in dual-proc, 15k SCSI glory, it too ran the standard image, and got non-standard software deployed automatically.
"Assume that this machine will be in service for at least 3 years with near-zero maintenance."
From a hardware standpoint, we do. A rotating stock of 0-3 year old PCs is greatly cheaper than trying to stretch them beyond that age with upgrades, or to try to over-buy them with bleeding-edge technology at purchase time. We have similar support to our machines in terms of upgrades and maintainence (low), and I pay [for hardware], under $200 a year for PCs. If you're paying 2,000 but can stretch your PC lifecycle out, you'd better be getting 10 years from a PC without any upgrades. I assume you splurged for 64 megs of memory on the machine you bought in 1996? $200 is *nothing* for a productivity tool for an employee for a year.
This is pointless, of course. This is HOW large enterprise organizations are going to acquire Vista licenses and O2007 licences. Select agreements work that way. You can't buy a Windows 2000 license with your new PC - even if that's what ships on the disk. You just maintain enough OS/App/CAL/Exchange/whatever licences to match the NUMBER of machines that you have. Someday we'll have enough licences, and someday the suits will want to change the standard...just like we did from 2000 to XP a few years ago.
[For what it's worth, we embrace open source and open standard initiatves at our company. They honestly aren't mature enough yet, and the programs available aren't specific to our industry yet. We keep moving closer and closer, and someday, we'll divorce ourselves from Microsoft -- but that day isn't exactly tomorrow.]
Jeff (Score:2, Interesting)
Re:Their main market? (Score:3, Interesting)
Re:Yea, but when is any company ready? (Score:5, Interesting)
Well, I recently finished a project at a rather large corporation (which I'll mercifully not name here) that hasn't quite finished upgrading all its W95 machines to W98. They also have a few NT machines, mostly in the IT dept.
No, I'm not joking. And this isn't the first case like this that I've seen.
Funny thing was that the project I worked on involved migrating software from a big IBM mainframe to a flock of distributed unix servers. Talk about having one foot in each world.
Re:J. Random CIO's thoughts: (Score:3, Interesting)
Bitlocker for laptops
Neither wanted nor permitted, ever. Employees do not own the work files, the company does. EFS is OK as long as recovery keys are available and user's own keys are backed up. BitLocker gives the keys to the user, and expects the user to maintain the backups (such as on a Flash disk, per MS's recommendation.) There is no reason, from corporate POV, to permit this.
Better power management via group policy for desktops, just to name two biggies
This is not even on the radar, and existing computers can already be configured to do the right power scheme for you. Group policy is important when things change often; but this power scheme can be on the Windows image that you used to install (clone) from.
Unless you need hardware upgrades there likely won't be a funding need since the upgrade is likely covered under your SA agreement.
Yes, but you forgot the compatibility testing and user training. If you use tons of apps how can you be sure they all work on Vista, given your configuration and usage pattern? I have one mission-critical app that runs only on Win2K - not NT 4 and not XP! It controls now obsolete piece of hardware (no upgrades from the vendor) so I guess we are stuck with Win2K until the hardware dies.