To: B.K.Myers who wrote (5586 ) 4/25/1999 7:50:00 AM From: Christine Traut Read Replies (3) | Respond to of 9818
Hi B.K.: Thanks for your usual thorough analysis of Microsoft's Y2K tools and information. I just met the product manager in charge of the Y2K Product Analyzer and web site at a Comdex presentation. He'd be pleased to know that you, as a first-rate experienced IT kinda guy, found the info useful. The man looked like he could use a few friends. Said product manager had a young assistant with him. Eager guy. Full of technical detail. In describing the Analyzer tool, he suggested that we all run it 'around December 1st'. Seems like they aren't quite done finding those Y2K problems and creating patches. My CIO client told me that the time to make a decision about updating 100,000 desktops has already passed. His people have to test the entire environment every time they change the O/S. Then they have to find those 100,000 desktops (most of which are laptops). Not pretty. So his company (and most in the world) is going to be going into the year 2000 without anything like the latest Microsoft Y2K patches. He's got a little wiggle room on NT server because he only has a few thousand and it's much easier to get to them. That's good, since Microsoft is saying that SP 4.0 is the minimum for Y2K compliance (heck, maybe we should call it Y2K stability). As to all of that wonderful detail, Microsoft is trying to tell people that they should understand exactly what each Y2K issue is, analyze their needs and decide!!! whether or not to make the software compliant. Sounds like a legal strategy to me. It is certainly not a customer support strategy. From the point of view of Civilians, Microsoft's approach just requires way too much technical expertise. And they are still hiding (prerequisite required) the fact that everyone is going to have to patch most of their software. Christine