While the effects of the daylight saving time change in 2007 forward isn’t a business stopping issue, I’m sure you we all appreciate the expectation our clients have in the accuracy of their calendars, especially since our scope often includes computers in different time zones and regions.
I’m having trouble understanding how Microsoft has released an Operating System Patch (KB928388) to adjust for it in November 2006 without warning specifically on the patch download site or on the Windows update site the effects of appointments in the extended DST period. What we’ve seen on computers with this patch is a one hour offset in how appointments are displayed in Outlook 2003, when compared to un-patched systems, or to Outlook XP. Additionally, when appointments are made on a Blackberry, they are reflected on patched computers two hours off, and a time offset with certain appointment types extends beyond the daylight savings time periods.
This has already caused us havoc here, especially where we’ve seen different people who view the same shared calendar seeing appointments at different times. Since the Blackberry calendar is also different from what is seen on a patched workstation, as you can imagine, this issue is compounded when clients start making “corrections” to these appointments.
While I’ve contacted Microsoft, and also reached out to Blackberry about this, Microsoft’s response is a future client side Outlook 2003 patch/tool/hotfix will be released to adjust the dates. I’m now reading about Exchange server side CDO changes. If this consists up an upgrade of CDO.dll, it will now affect Blackberry, who will also need the upgrade, because Blackberry servers would then need the same version.
Blackberry doesn’t believe the Microsoft tool will correctly adjust its appointments that are two hours off, because they were unaware of that specific condition until I called it in. Windows Mobile is currently untested, so we’re not aware of its impact. Factoring in that Blackberry will also be releasing a patch to be installed on the actual handheld devices in the beginning of February, and we have no patch for Windows 2000, we further complicate this mess, and have very little time for testing and deployment.
Combine this with all the other DST changes needed in many other systems, from security cameras with DST in their firmware (with no updates available) to voicemail systems, to backup software, and we have a mini, self created Y2K scenario taking place. While not the end of the world, it’s not what we expected in exchange for a few hours more of daylight. For many off us, the extra work will consume it all, and there will be no energy savings, as congress had hoped.
Unless our clients hold off on creating certain appointments on a blackberry or on a patched workstation, and we’re able to deploy all of these patches and tools to all our clients at the same time, and before March 11th, we should expect a significant amount of confusion within our environments, and it may extend beyond just the 4 weeks effected by the daylight savings time change. I’ve already cautioned clients affected by the patch and have advised them to include the time within the subject line of appointments taking place during daylight savings time.
As we’ve found out here, not everyone who has been with calendar affected is yet aware. Why isn’t the 928388 update being pulled or have a HUGE warning about this impact? We have unknowing clients pulling it down and installing it, unknowingly impacting shared and public calendars…..How about a tool, like what is available for IE7, to allow administrators to prevent its download, so we can further contain this?