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
One more thought..
It looks like the US law changing 2007 DST was enacted in August of 2005. Exchange 2000 mainstream support was valid until 12/31/2005. Why would Microsoft not honor its obligation to resolve this DST change issue having known about since then??? I can see them not releasing the patch right away, but telling customers basically "tough luck" does not sit well with me.
This could be viewed this as MS not living up to their product support commitment, or taking this underhanded opportunity to "push" customers to a new purchase.
Corporate email is a key component of my company's network services. MS had better realize that it is trusted by corporate customers to provide products and support that allows businesses to focus on their main task, that being something other than worrying about something as straight forward as this DST thing.
Come on MS, do the right thing here...
It looks like the US law changing 2007 DST was enacted in August of 2005. Exchange 2000 mainstream support was valid until 12/31/2005. Why would Microsoft not honor its obligation to resolve this DST change issue having known about since then??? I can see them not releasing the patch right away, but telling customers basically "tough luck" does not sit well with me.
This could be viewed this as MS not living up to their product support commitment, or taking this underhanded opportunity to "push" customers to a new purchase.
Corporate email is a key component of my company's network services. MS had better realize that it is trusted by corporate customers to provide products and support that allows businesses to focus on their main task, that being something other than worrying about something as straight forward as this DST thing.
Come on MS, do the right thing here...