|
Re: Army migrating computers to Vista
It's not uncommon for large organizations to require "extensive testing" and wait out a long time to deploy something this widespread. Shake-out periods can last for 3 years. In my previous involvement with Windows 2000 and XP, my company took about 3 years to test those and release in “deployment sectors" even. It seemed kind of odd to start using the old stuff as the new stuff starts coming out, but having gone through it and understanding the process, that's what you have to do because you just can't trust that the brand new things will work off the bat for everything you got…which MS affects a large portion of what you got. And not everything works! So you have to solve your issues and that takes time. We had practically everything…mainframes, Windows Server, IIS, Unix, Linux, Sharepoint, running all sorts of vendor and in-house stuff in Cobol, C, C++, .NET, java, pearl, PL/1 (that's right…Programming Language 1), DB2, Oracle, Sybase, Access, SQL Server and more.
Small and Medium businesses maybe you can jump right into Windows 7 and not risk that much (depending on how deeply you are into IT). But you're not going to see many enterprises do something that reckless.
And remember that Windows 7 is STILL a Microsoft product and they are still going to hype it as much as they can just like they hyped Vista…and hyped XP…and hyped Zune…etc. It's not going to be "flawless" when they release it, no matter how much they spend on marketing. And in the far-fetched hypothetical case that Windows 7 is flawless, enterprise systems will not be flawless and will require shake-out. And in reality, there are those who can’t wait that extra couple of years to deploy Windows 7, despite what people like to believe. |