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
Hello,
Here are my replies to the last two posts.
First, to Elizabeth:
Thanks for the information. It sounds like a complicated process to try and keep everything in check manually, especially since we also run Blackberry Enterprise server. Understood on your inability to respond to MS' policy.
Secondly, to Ray:
OK, I think I can safely say that MS knew about the required DST changes in the Exchange 2000 product as of August 2005. When it "technically" took affect is irrelevant.
Again I expect MS to make good on its support of Exchange 2000 as it knew of this forthcoming issue while Exchange 2000 was still in mainline support. If the plan back then was not to make good on the patch, why not have let us know right then and there?
As of today, I now see there IS a patch out, but ONLY for customers with an extended support agreement. Not good. This is a less than scrupulous way to "push" users off Exchange 2000.
It isn't that we don't want to upgrade, far from it. Like any decent sized company, we spend a large part of our time (and money) doing just that. We do, however, try to co-ordinate upgrades of major systems (like Exchange) such that we "wear out" both hardware and software simultaneously, thereby avoiding riskier in-place upgrades. In this case that means Exchnage 2007 this summer.
We spend a large portion of our budget on technology, with the lion's share going to Micorsoft. The least we expect in return is solid, trustworthy support. If MS does not make this patch available to all its Exchange 2000 customers, then it makes me question my ability to trust them with my organization's needs in the future.
Here are my replies to the last two posts.
First, to Elizabeth:
Thanks for the information. It sounds like a complicated process to try and keep everything in check manually, especially since we also run Blackberry Enterprise server. Understood on your inability to respond to MS' policy.
Secondly, to Ray:
OK, I think I can safely say that MS knew about the required DST changes in the Exchange 2000 product as of August 2005. When it "technically" took affect is irrelevant.
Again I expect MS to make good on its support of Exchange 2000 as it knew of this forthcoming issue while Exchange 2000 was still in mainline support. If the plan back then was not to make good on the patch, why not have let us know right then and there?
As of today, I now see there IS a patch out, but ONLY for customers with an extended support agreement. Not good. This is a less than scrupulous way to "push" users off Exchange 2000.
It isn't that we don't want to upgrade, far from it. Like any decent sized company, we spend a large part of our time (and money) doing just that. We do, however, try to co-ordinate upgrades of major systems (like Exchange) such that we "wear out" both hardware and software simultaneously, thereby avoiding riskier in-place upgrades. In this case that means Exchnage 2007 this summer.
We spend a large portion of our budget on technology, with the lion's share going to Micorsoft. The least we expect in return is solid, trustworthy support. If MS does not make this patch available to all its Exchange 2000 customers, then it makes me question my ability to trust them with my organization's needs in the future.