ARTICLES (search) - Keyword, InstantDoc ID, or Source - Topic Index - Author Index - Department Index --------------------------- QUICK NAV --------------------------- ARTICLES (search) - Keyword, InstantDoc ID, or Source - Topic Index - Author Index - Department Index SUPPORT - Forums RESOURCES - User Groups - Event Calendar - IT Glossary - Windows 2000 Glossary - Training Centers - Career Center TECHWARE - Product Reviews - Buyer's Guides - Interactive Product Guides - Solutions Shopper - Auctions/Classifieds - Compatibility List TECHFOCUS - Windows 2000 Ready - Thin-Client Computing - Administrative Scripting - SQL Server Administration - Keeping Up with NT - Security - Exchange Server Administration - Training and Certification - Windows 2000 Pro OUR PRODUCTS - Windows NT Magazine - International Editions - SQL Server Magazine - Article Archive CD - Exchange Administrator Newsletter - IIS Administrator Newsletter - Win32 Scripting Journal Newsletter - Email Newsletters - Video Tapes - Windows NT Magazine TV ABOUT US - Contact Us - Advertising with Us - Meet Our Advertisers - Become An Author - The Lab - Affiliate Program - AWNTP Y2K Quiet on Most Fronts

Source: Web Exclusive, January 5, 2000
Dept: Security
Author: Mark T. Edmead

Lots of bark and no bite. That's how I'd describe Y2K's effect on computers and computer-based technologies. I don't know about you, but I didn't encounter one problemnot on my network, not with my public utilities, and not with my banking, grocer, or anything else I can think of. Apparently, all the preparations for Y2K have paid off; I'm not surprised that the impact seems rather insignificant so far.

What does amaze me is the fact that my test networks encountered no Y2K-related problems even though I loaded no Y2K fixes on those test systems. I thought it might be educational and rather fun to dig out of any Y2K-induced mayhem, but I suffered a let-down.

There I was, New Year's Eve, ready to upgrade test systems from Service Pack 5 (SP5) with no hotfixes to SP6a along with various third-party patches, but nothing happened to warrant that action. At first, I felt cheated out of another Ph.D. from the School of Hard Knocks, but as I sat sipping a glass of champagne just after midnight, I realized I wasn't cheated at all. Instead, I was taken care of. The fine engineers and developers at Intel, Microsoft, HP, Dell, Compaq, and countless other prominent companies have done an excellent job of minimizing Y2K's impact on technology. I'm truly impressed. Congratulations to everyone involved in that effort.

If you're among those people that did suffer technological failures at the hands of Y2K, I'd like to hear the details. I'd also like to hear from you if intruders attacked or probed your networks over the holiday weekend. Happy New Year 2000 and, until next time, have a great week!

) 1999 Duke Communications International, Inc. All rights reserved.

[ENDS]

-- John Whitley (jwhitley@inforamp.net), January 07, 2000