As many of you know, there will be a change next year in the transition dates for US daylight saving time. I won't go into all the gory details here, but if you want them follow this link http://ww...
Published Nov 13, 2006
Version 1.0
Blog Post
For those of you that feel the update shoud be free because it was announced in 2005, let's think this thing through...
Let's say MS releases the fix prior to Exchange 2000 ending mainstream. So now you have the fix, but you can't apply it for a year and a half. So now it's 2007, and you apply it, and something doesn't occur as expected, or something goes wrong. It's 2007, and support is over. Would you be okay with that? Of course not, you'll be expecting support. So the fact that the fix is now available and not then is irrelevent. Offering a fix knowing there would be no support for it when it was implimented... that would be irresponsible.
It's a bad situation, I agree. But I can't really fault MS for not willing to eat the costs of modifying and supporting an outdated product because Uncle Sam decided we needed 4 more weeks of DST, and we needed it right away. I guess I missed that march on Washington.
Let's say MS releases the fix prior to Exchange 2000 ending mainstream. So now you have the fix, but you can't apply it for a year and a half. So now it's 2007, and you apply it, and something doesn't occur as expected, or something goes wrong. It's 2007, and support is over. Would you be okay with that? Of course not, you'll be expecting support. So the fact that the fix is now available and not then is irrelevent. Offering a fix knowing there would be no support for it when it was implimented... that would be irresponsible.
It's a bad situation, I agree. But I can't really fault MS for not willing to eat the costs of modifying and supporting an outdated product because Uncle Sam decided we needed 4 more weeks of DST, and we needed it right away. I guess I missed that march on Washington.