* Dave feels your pain
Okay, I’ll admit it. Sometimes I do get what some might perceive as overly enthusiastic about new technology. Not always of course (e.g., I told you not to rush to push Windows XP out onto your users’ desktops). But I have been beating the drum for Vista and, lately, I’ve been talking up Longhorn. Sometimes I might go overboard. Or, as one reader recently reminded me:
“Earth-to-Dave: When you return from the stratosphere, maybe you might consider the realities of planet Earth. No, we haven’t loaded Vista in our ‘testing lab’ (a lab which does not exist). No, we don’t have time to play with beta versions of Longhorn. While Microsoft’s churn of what’s new-and-improved sound fun, the truth is, day-to-day support isn’t about ‘fun’. My major project this year is wrapping up a conversion from NetWare 4.11 to Windows 2000. Two of my other projects this year have been installation of a fax server and a home health telemedicine system that relies on old-fashioned modems for connectivity. Yes, fax and modems, sigh.”
Blunt, perhaps over the top, but all too typical of the networks that many of you are running. (Thanks, George, I think.)
I strongly adhere to the principle of “if it ain’t broke, don’t fix it.” I subscribe to the World War II slogan “Use It Up, Wear It Out, Make It Do.” But sometimes you just have to move on.
Windows 2000 Server with Windows NT Professional on the desktop makes a strong, robust network. It might not have all the bells and whistles of later versions, or of competing operating systems, but it’s proven, it works and it allows you to sleep at night. I would never advocating changing from that unless there were proven benefits in doing so.
And I do believe that Vista and Longhorn will provide those benefits.
There’s no need, however, to rush right out and begin an upgrade rollout. You do need to study the full implications of the change. That’s why I advocate the testing lab. And that needn’t be expensive setup. One PC, using Microsoft’s own virtualization technology, VMWare or the open source Xen is all you need to create a test environment. Not only will this let you try out the new leading edge technologies, but you could also pilot that NetWare 4 to Windows 2000 migration and learn about the problems that might crop up before you anger your users with a botched implementation.
Use that test environment to evaluate new stuff both in isolation as well as in concert with your current apps and services. No need to devote large amounts of time to it, either. Just test things whenever you can.
At some point you’re going to need to upgrade either your desktops or your servers. New applications or services that your management wants to implement will require it. The only real question is, “will you be prepared?” I hope so. And I’ll keep trying to push you to ensure that you are. But I do understand that you still have to make sure that the modems can call each other, and I do sympathize.
Downloads: Microsoft has made available PackageThis, an easy-to-use tool to create customized help files/ebooks. By choosing precisely the information you want from Microsoft Technet, you can build help for particular applications, modules, services – or for particular users.
